- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 06:45 AM
Hello,
In my system there a multiple approvals needed for a change, and it's conditional as well. Problem I'm having is when the first approval happens it sets the approval column to 'approved' and sends out notifications indicating the change was approved. I would like to control this value in the change workflow instead, but I'm having a hard time figuring out what's setting it in the first place?
Thanks!
Dan
Solved! Go to Solution.
- Labels:
-
Scripting and Coding
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 08:48 AM
Thanks everyone! I got to the bottom of this, and it wasn't a business rule or in my change workflow. The approval engine was enabled for change requests. It appears that this is enabled OOB at least in Eureka. It is not enabled in Fuji by default, at least in my developer instance.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 07:21 AM
Hi Dan,
There's nothing OOB that does that and it would typically be handled either in a business rule or the workflow. I would start debugging by turning on debug business rules and approving one of the approvals, then see if there's a BR running on the approval table setting the change to approved. I would also check your workflow for an approval actions activity.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 07:32 AM
Thanks Brad. It's not quite OOB, as we've got the CloudSherpas excelerators. I did actually try looking at the business rules on the approval table and even if I disable all of them this still happens. It must be missing something.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 07:22 AM
Hi Dan,
If you're speaking strictly of approval states are you using group approval activity or user approval? They both give flexibility in different ways.
You can use the "wait for" in the user approval activity to wait for everyone to approve. Although this adds complexity if someone accidentally doesn't approve, or isn't available to approve. You could make up for the shortfalls of the easy UI "wait for" and base it on a scripted condition - which gets complicated but can handle most anything needed.
The group approval can do similar, but the "wait for" condition is based more on approvers from each group approving (rather than everyone)
When you drag the user approval activity into the workflow and open it up - it's on the left hand side half way down it's just called "wait for". I would gather you would select from the dropdown: Everyone to approve - All users must approve
Approval and Rollback Activities - ServiceNow Wiki
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2015 08:48 AM
Thanks everyone! I got to the bottom of this, and it wasn't a business rule or in my change workflow. The approval engine was enabled for change requests. It appears that this is enabled OOB at least in Eureka. It is not enabled in Fuji by default, at least in my developer instance.