Global Request Sub-statuses
Home > Administration > Service Manager > Configuration > Request Sub-statuses
IntroductionThe Request Sub-statuses lets you define a number of descriptive states of a request that are related to the request being either Active or On-hold. Using the Sub-status can help control the situations under which a request is put On-hold or made Active again. An example of an On-hold Sub-status might be With Customer which when selected will place the request's status to On-hold and stop any allocated Service Level Target timers.
|
Related Articles |
Managing Request Sub-statuses
- Sub-status Name
- The Name of the sub-status is what will be displayed to an analyst from within a request
- Customer Label
- An alternative Label can be provided which will be visible to the customer from within the Customer or Service Portals. This is only applicable to request types that are accessible on the Portals.
- Request Type
- A sub-status can be made available to All requests types or you can select from one of the available request types on which this particular Sub-status will be available.
- Parent Status Active On-Hold
- The selection of a sub-status controls if the request is placed in either an Active or On-hold state when the sub-status is selected. A Sub-status that is set with a Parent Status of Active will either keep the request in an active state (New, Open, Resolved) or if the request is On-hold the state will change back to its Active state. A Sub-status that is set with a Parent Status of On-hold will either change the status of the the request to On-hold if it is currently in an active state (New, Open, Resolve) or it will maintain an On-hold state if it already on-hold.
- Language
- If you support more than one language in your environment you can provide the appropriate translations for these languages