Stages in subflows in Vancouver

kc1959
Tera Contributor

Hello all,

 

a colleague had read that adding stages into subflows are now supported in Vancouver so I added some stages and tested.

Unfortunately the stage is not being set as expected and displays the last stage set in the parent flow that calls the subflow.

 

The Vancouver documentation says:

While you can add stages to a flow that has a scheduled trigger, an end user cannot see the stages because there is no associated record for the stage field. Only use stages in flows that have record or Service Catalog triggers. Stages are not supported on subflows.

 

Can anyone confirm that they have successfully added stages to subflows in Vancouver and, if so, is there anything additional that needs to be done to set these stages?

 

I can't believe that ServiceNow have added functionality which doesn't work,

 

Many thanks in advance.

 

4 REPLIES 4

brajek
Tera Contributor

kc1959 - 

 

I am experiencing the same issue and am unable to find any information on how to get the stages from the subflow to display. I too cannot believe that ServiceNow would add functionality like this that does not work. 

 

Has anyone else found a solution for this?

 

Thank you.

 

ServiceNow's ability to release stable and working code has became so bad one has to ask what is going on over at SN. And they seem to have zero interest in fixing them. Setting stages is basic stuff and they can't even get the UI to work properly to even select/or even add one.     

In the latest version, you can't even select a RITM stage on a subflow.



David House
Tera Guru

I have run into this issue as well, and raised a Now Support ticket regarding it.

 

The response I received was that a Subflow can only affect the stages of a record if it is the only flow running on that record. In this case, where a Catalog Item is triggering a Flow, subsequent calls to Subflows do not allow stages to be affected, since that Subflow is not the only flow running on the record.

 

This is not how it appeared to be designed with the Vancouver release. However, support have advised the above.

 

I have submitted an enhancement request to hopefully get reimplemented:

https://support.servicenow.com/ideas?id=view_idea&sysparm_idea_id=5c9cc05c47678650b6d8aa25126d4355&s...

They took away functionality that already existed in Workflow, which is core ITSM. And it's now a "enhancement". 

ServiceNow needs to sort out their development teams, including those making management decisions for the platform.