Flow Designer - Inline Script option no longer present after upgrade

[Jon G1]

We're working on an integration using the Integration Hub Remote Instance Spoke.  It looks like something has changed in flow designer or the spoke because we previously had the option to set field-level scripts when setting up an "Export Incident Record" action. After updating to Xanadu, (or possibly one of the related upgrades to plugins) the option to show the script is gone, except the step still has the fields set as "Scripted (Expand to edit)"

It looks like the action is now set up so that the entire "Override Remote Import Set Fields" has an inline script option, but the individually selected fields no longer do. When I open the script for the Override Remote Import Set Fields line, the script just has the default how-to comment. This wouldn't be much of a problem if I could extract the scripts in any way, but I'm not having any luck.

I found this action step on the behind-the-scenes table sys_hub_action_instance_v2. Unfortunately, that's of little use since the data stored in "Values" on that record is encoded and I'm not sure using what format or how to decode it.

Opening the action in action designer isn't useful either. The "Override Remote Import Set Fields" input is a Dynamic Template, but I see nothing in the action definition that gives me any clues.

Does anyone know how to either 1) Fix this so that I have my inline script button back for those fields or 2) extract the script data another way?

[Mark Manders]

You could check to see if all store apps related to flow designer/workflow studio are all up to date and if not, update them and check if it's working as expected again. Otherwise, since it's due to an upgrade, log a case with NowSupport to have them assist on this, looking at what you already tried yourself.

[Jon G1]

Thanks for the tips - and yeah, unfortunately I went through everything I could think of. Turns out that SN changed the UI without giving any obvious way back. Here's what the UI used to look like:

Note the script buttons next to each field. I ended up just redoing the work. Just annoying that they do stuff like this. I'll leave this thread open just in case someone comes along with a "me too, here's how I fixed it" story.

[Chris139]

Hi Jon,

I have also run into similar problem after Xanadu upgrade.  I can help you get the inline scripted input back but be careful as dot-walking within that seems to be broken.

1) Create/update the true/false system property called "com.glide.hub.flow.inline_script.dotwalk.enabled" to true.

2) Ensure you have the right roles needed: inline script button is missing from the flow action - Support and Troubleshooting (servicenow.com)

3) Run "cache.do" if the inline script is still not there.

If you can find any help on the dot-walking problem inside of a scripted input within a flow, please let me know.  The only workaround I have found for this is to assign the dot-walked value to a flow variable, then reference that flow variable in your script instead of trying to dot-walk within the script. Or, worst case revert the flow back to flow engine v1 (need to get support to do this for you: How to switch the major engine for a flow - Support and Troubleshooting (servicenow.com)

Both workarounds are tedious as they only fix the issue on a per-flow basis - which could be quite problematic if a lot of your flows use dot-walking scripted inputs. 

I have a ticket open with ServiceNow and will update you if there's a global fix for this down the line.

[Chris139]

FYI,

ServiceNow has addressed this as a problem, they do intend to fix it: Inline script with fd_data does not read object from a Create or Update Task action in Flow - Known ...

Beware, that their suggested workaround only assumes that flows that dot-walk a catalog task are impacted, whereas I've noticed any inline script that dotwalks anything other than the trigger object or a flow variable, does not work.