Have you ever tried to move update sets that contains flows from Tokio version to Utah and saw blank page when opening newly imported flow? And that flows contains subflows block? I did 🙂 And guess what, ServiceNow support said: “recreate flows from scratch” 😀 But I found a solution, not perfect, not nice, but it will prevent you from recreating flows form scratch. So, have a nice reading 😉
First and important – don’t panic, it’s not end of your recent work. Now I know that 🙂 But at that time, crying was an option 😉
Let’s start. Hopefull you have an update set with this problematic flow. I had.
First thing to do is to request personal instance (https://developer.servicenow.com/) but in Tokio release. After a while, when you have your instance ready, go to Retrieved update sets and import your buggy update set with a flow. It may show some errors, but mine worked like a charm.
Now, open flow designer, find your flow and open it… It opens, right 🙂 We could finish this “tutorial” right now – you can recreate a flow based on what you see on your dev instance – possible, but time consuming.
In my case, problematic actions was “if” statements, which somehow do not like newer version of instance. I removed those actions on my dev instance, saved it to update set, exported it and imported on already upgraded Utah version instance… and it worked. Yeah, I had to re-do if statements, but still – much better than recreating everything from scratch.
If “if” statement is not the problem, feel free to experiment and search for an activity that is causing a problem 🙂
Have fun 🙂
Leave a Reply