Service Builder approval flow
Summarize
Summary of Service Builder Approval Flow
The Service Builder approval flow in ServiceNow manages the progression of services and service offerings from creation to publication. Administrators can utilize the standard approval process or customize it using Workflow Studio to fit organizational needs.
Show less
Key Features
- Standard Approval Flow: By default, services are approved automatically. The flow includes Draft, Awaiting Approval, and Published states.
- Service States:
- Published: The service or offering is available for use after approval.
- Draft: Indicates ongoing edits; cannot be searched or browsed in this state.
- Awaiting Approval: Submitted items undergo checks for standards compliance before publication.
- Editing Services: Only items in Draft state can be edited. Checked-out services create a Draft copy for modifications.
- Approval Process: Involves service owners, process owners, and portfolio owners to ensure quality and prevent duplication.
Key Outcomes
By following the approval flow, ServiceNow customers can ensure their services meet organizational standards and are effectively managed through the publication process. Customizing the approval flow allows for alignment with specific operational requirements, enhancing service management efficiency.
As you create and edit services and service offerings in Service Builder, various states get assigned and change on the services' way to being published (approved). Administrators enable the standard approval flow and can even customize it using the subflow option in Workflow Studio.
Standard approval flow
By default, the approval flow in Service Builder is set to approve services automatically.
- As you edit a service or offering, it's in a Draft state.
- After you submit your service or offering, it moves into the Awaiting approval state.
- After your service or offering is approved, it moves into the Published state.
When you check out an offering to edit it, the offering and its parent service both get checked out. The rest of the child offerings of that parent service remain in the Published state. After you finish editing the offering, submit it to the parent service so the offering can be republished (offerings are published via the parent service).
Service states
| State | Description |
|---|---|
| Published |
When a new service or offering is created and submitted in Service Builder, the item goes through an approval process before it's assigned to the Published state. The Published state indicates that the item is the version being used by the application and available for others. When you edit a published item, Service Builder automatically checks out the item for you and creates a copy for you to work on. The copy is set to the Draft state. |
| Draft |
A service item is in the Draft state in one of these scenarios:
|
|
Awaiting approval |
After submitting your service or service offering, your submission goes through an approval process. Your organization's approval flow confirms that the service is created according to standards such as naming conventions, descriptions, proper use of commitments, and key performance indicators (KPIs). It also enables a quality check to confirm services aren't duplicative. The following lists the tasks for each persona in the approval flow:
|
- You can only edit an item when it's in a Draft state. You can't edit a published item that has been checked out.
- An item in the Draft state is always inactive and doesn't show up in a search or when you're browsing.
- You can't change the Active flag of an item in the Draft state.
- The approval process is available starting with the Utah release and after. Depending on your organization, the approval process could take some time. Contact your administrator if you have questions about the approval process time.
Enable and customize an approval flow
Administrators enable the approval flow that comes with the base system by updating the 'Service Builder publish' subflow in Workflow Studio.