
- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
on 11-25-2021 05:05 AM
I think that this experience is worth sharing, so I am writing it down for everyone. Most of you might already know this, but this is for those few who doesn't.
I was working on the flow designer, for a client requirement(service catalog). I had to put in the stages in the flow so I imported the stages and placed them according to my flow design. I was not able to place a stage just above the ELSE/ELSE IF part of the flow. So, I used an update record action and updated the RITM stages through that action and then saved the flow and activated it.
The flow gave a notification in the lower left corner that it was activated but it was still not activated , because I could still se the activate button as green. I re-verified it by testing it using a few RITMs but after investigating the flow context, I understood that it was still the older version of the flow not the latest one. I tried activating the flow from the sys_hub_flow table. The flow got activated but still the version was old.
So, the in hand issue was, I was not able to activate the flow from the flow designer directly, I was able to activate it from the backend but that was also activated the old version not the latest one where I had made the final changes.
On further investigating I understood that I should not have added an update Record action just above the ELSE/ELE IF statement because it disrupts the IF/ELSE ladder. ( in spite of that the actions should be added in the branches of if and else so that the main ladder formation is not disrupted ).
Hope this helps.
- 608 Views
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Yes this works!
- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Does anyone aware of a known problem identified that might get this addressed in future versions?