Flow designer set stage to request_approved instead of waiting for approval

PGhate
Tera Guru

Hello,

Stage value is configured to be 'waiting for approval' in flow designer just before Ask for approval action however in ritm it is set to 'request_approved'. Can anyone help me know the issue.

 

Thanks in advance

1 ACCEPTED SOLUTION

Hi @OlaN ,

There is a business rule but we do have conditions to skip its execution for certain catalog items. Stage being set to 'request_approved' happens occasionally and is very random.  I suppose below KB article seems to highlight the issue.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0996598

Thanks.

View solution in original post

5 REPLIES 5

OlaN
Giga Sage
Giga Sage

Hi,

Can you share an image of your Flow and also an image of what the issue is?

Generally approval can happen in many levels, both on the REQ and on the RITM.
So i'm guessing that it's set to "request_approved" because the REQ is approved, and therefore has started the Flow on the RITM.
Then on the RITM you might configure additional approvals, which should reflect on the "Approval" field.

Hello @OlaN ,

 

Flow has only ask for approval activities and there are no request level approvals. So once RITM is created 1st level approvals are generated on RITM and before ask for approval activity i have set the stage value to "Waiting for approval" however stage gets set to request_approved.

 

 

Trying the same on a PDI, and getting the result that the RITM is on stage Waiting for approval. (example and result below)

Do you have any custom business rules that modifies or sets the stage value when RITM is created/updated?

find_real_file.png

 

find_real_file.png

Hi @OlaN ,

There is a business rule but we do have conditions to skip its execution for certain catalog items. Stage being set to 'request_approved' happens occasionally and is very random.  I suppose below KB article seems to highlight the issue.

https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0996598

Thanks.