Join the #BuildWithBuildAgent Challenge! Get recognized, earn exclusive swag, and inspire the ServiceNow Community with what you can build using Build Agent.  Join the Challenge.

Request item, Flow designer stages not showing

Sitrix
Tera Guru

TLDR; How can I ensure stages set on the sc_req_item show in list view, despite using flow? 

 

Hello good people 🙂 I'm having issues while converting from workflow to flow.

As it is now (using workflow), whenever the request item is created it will have stage "request_approved" to begin with. This shows correctly in the list view - all is good.

find_real_file.png

When switching to flow however, this does not happen. The flow has 4 stages set (in the dot menu -> stages, including "request_approved"), all set to always show. Two of these are used within the flow, both display fine in the list view, request_approved does not.

 

find_real_file.png

 

From what I can read, workflows use the sc_req_Item's stages where as the flow use its own. So, if the list view only looks at the flow - how can I ensure that it displays the current value set on the request item as well?

Hope this makes sense 😄

 

- Cheers

1 ACCEPTED SOLUTION

Hi, the multiple task issue is a documented problem. It is caused by a business rule being triggered multiple times. You should be able to resolve it by adding a short timer where applicable to your flow. More info here:

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

View solution in original post

7 REPLIES 7

Sitrix
Tera Guru

Thanks the both of you, and sorry for the late reply 🙂

 

The issue is that request_approved is set outside the flow script. I've tested running two stages after eachother (request_approved and then delivered), using a log action for separation (can't run two stages next to eachother right?).

find_real_file.png

 

This kinda works, request approved goes to green and the list view moves on the delivered but it seems to generate a massive amount of sc tasks (10 instead of 1) - I have no idea why.

Hi, the multiple task issue is a documented problem. It is caused by a business rule being triggered multiple times. You should be able to resolve it by adding a short timer where applicable to your flow. More info here:

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

I see. Seems like the way to do it then, thanks a lot for help - both of you.

 

- Cheers 🙂