- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-13-2017 05:10 PM
While developing a workflow for fulfilling Service Catalog Request Items, I've created stages in the workflow. However, while testing, I'm finding that there is an additional stage being added called "Request Approved," which is causing confusion as we do not run requests through approvals. Is there a way to supress this stage?
Thanks,
--Nate
Solved! Go to Solution.
- Labels:
-
Customer Service Management
- 7,058 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2017 06:11 AM
Hi Nathan,
The Request Approved stage you see does not belong to the stages of the workflow you have defined, but it is created by the service catalog as part of the item request creation process.
Unfortunately, there is no easy way I know to get rid of this stage without having to modify the business rules and/or script includes which create the service catalog request.
In this thread you can see some investigation toward resolving the same problems. That might give you some starting point to get rid of the stage, but again, this stage is considered as the default for new service catalog requests, and get rid of it is not straightforward.
Hope it helps,
Ginés.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2018 04:39 AM
Howard,
I tried the css addition you provided but for me the customer is seeing this first default stage that we cannot get rid of. This would come from the widget. There is a default approval that comes no matter what you configure. This is the first stage I need to hide from the customer. We have some catalog items that have no approval so having this approval bubble confuses them. Then when it's a catalog item we have an approval, it looks like there are 2 approvals.
https://instance.service-now.com/sp?sys_id=812ce416db1e13009dc573d78c9619e2&id=sc_request&table=sc_request
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2018 05:43 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-21-2019 10:02 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-10-2018 10:58 AM
Thanks.
I was able to make this work for me.
I only had to change the data.choiceList to item.cl
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-27-2025 05:48 AM
@Howard Elton Thanks for sharing your solution. I found that it does work to hide the default Request Approved stage in the portal, but it only works if the workflow editor was used to create the workflow. The workflow editor always creates the Request Approved stage as the first stage, so we can reliably use your code to always hide the first stage bc we know it's always that default Request Approved stage. However, if flow designer is used for the workflow, it does not use the default Request Approved stage as the first stage, so we can't assume that is the first stage in our workflow. Let's say my flow designer I have added the first stage as 'Stage 1'. This code is actually hiding 'Stage 1' b/c it's the first stage in my flow designer workflow. I wanted to share this in case it helps anyone who is trying to hide that default stage.