Stage Rendering issues - Catalog Item - Workflow replaced by new Flow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 11:14 PM
Stage Rendering issues - Catalog Item - Workflow replaced by new Flow
Hi ServiceNow Community colleagues,
I would really appreciate any help/guidance in case anyone has seen this before and knows how we can resolve it please.
On several Catalog Items, we have moved them to a new FLOW and replaced/removed them from a previous WORKFLOW.
There are no issues with regards the 'Stages' displayed graphically when new Requests/RITMs are raised, using the new Flow.
However - there are Stage rendering issues, when any old RITMs that were opened using the old Workflow are displayed, as the new Flow is assigned to these Catalog Items.
Please see screenshots attached. The first two show the graphical view of 'Stages', when the old Workflow is still assigned to the Catalog Item. The second screenshot, shows the view of 'Stages', when the new Flow is assigned to that same Catalog Item. (Notice: it no longer renders graphically, just values eg: waiting_for_approval )
For some reason, when the new Flow is placed on the Catalog Items, the Stage names display as values not graphically any longer (for Open RITMs raised using the previous Workflow)?
Is there any way / solution to resolve this?
I had assumed that 'Stages' are synced between Flow and Workflow, so that a Flow replacing a previous Workflow, will still ensure the 'Stages' sync/match at a graphical level, when displayed ?
Has anyone seen this behaviour before, when switching Workflow to Flow on Catalog Items - how can this be resolved?
Many thanks once again for any help/guidance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-19-2024 11:19 PM
Hi,
Please verify you are setting stages in flows as well. in the same way how, you set in workflow.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-20-2024 10:13 PM
Hi @Anil Nemmikanti yes I have verified and am setting them the identical way.
This doesn't appear to be the issue - can you think of anything else that may be causing this behaviour ?
Many thanks.