Emergency change workflow automatically going through second group approval marking them "No longer Required"

Winston
Tera Guru

Hello everyone, 

I'm using the a modified normal change workflow for our emergency change process because it's closer to what we already use. 

We have two approvals in it. To keep it simple the first approval is a change approval policy that sends an approval to a group listed in the change, the second is just a group approval that sends to another group. 

The first approval works fine. Sends out to the right people, gets an approval then moves on to the next approval, but then it goes right through the second approval and marks all the approves in that group as no longer required.

Notes

  • I'm using pretty much the same workflow in the normal changes with two approvals and it works fine. 
  • The first approval isn't marking the change as approved, the approved field still says "requested"
  • I've changed up the two different approvals multiple times and it always skips the second approval marking them no longer required. Is there a business rule somewhere making emergency changes only need one approval??

find_real_file.png

find_real_file.png

1 ACCEPTED SOLUTION

Winston
Tera Guru

After viewing the below post I added a timer one second timer before the second approval and it stopped automatically marking them as "no longer required". I'm going to open a Hi ticket on this because this can't be the best solution for this issue.

https://community.servicenow.com/community?id=community_question&sys_id=b3990fa5db5cdbc01dcaf3231f96...

 

find_real_file.png

View solution in original post

5 REPLIES 5

RAHUL Khanna1
Mega Guru

Till then you can mark this thread as answered , and later you can post the response from the HI Team.