Hi everyone,
I’m working on a custom implementation where I’ve extended the Request (sc_request) table to create an Asset Request table, with further child tables like Laptop Request and Mobile Request.
My requirement is to make the State field more business-friendly (for example, changing labels like Pending Approval to something users understand better) only for my custom Asset Request and its child tables, without impacting the base Request table.
Is the State field on sc_request restricted or controlled by the Service Catalog engine?
If so, what is the recommended approach to show business-friendly status values for custom request types while still keeping the system lifecycle intact?
Any guidance or best practices would be appreciated.
Thanks in advance.
