The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Flow Designer - Inline Script option no longer present after upgrade

Jon G1
Kilo Sage

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)"

 

JonG1_1-1729497747838.png

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?

7 REPLIES 7

Jon G1
Kilo Sage

Hi Chris, good suggestions, but unfortunately still no buttons where I need them.  I suspect the change of removing the buttons was intentional on their part, but it feels short-sighted.

 

Here's why I think it might be intentional: Both of those screenshots are of a field with the type Array.Object. An array of objects as the name suggests to help build out a payload. They went from it being set up so that you can have a script on each "object" within the array to having only one inline script for the entire array.

 

In the first screenshot, the inline script button for the main field (the array) is there all the way to the right and aligned with the name of the field. In my follow-up screenshot, each object has its own inline script option but nothing for the overall array.

 

I don't like it, but I can understand the design choice. What upsets me is that they implemented the change without any apparent regard for legacy Flows and scripts. If there was a simple switch in a system property to choose which behavior you prefer or an option to drop back to the older UI temporarily, I wouldn't mind it so much.

 

My other frustration is how much they guard the back end Flow tables. I tried to go find the scripts that way, by  browsing through the Flow tables to find the relevant instances and steps. It's in there somewhere, right? Well you can't do it - at least not easily. Every time I try to get into one of those tables, it redirects me right back to the Workflow Studio. Very frustrating to say the least.

Bryan Adams
Tera Contributor

Hi Jon - I had the same issue after upgrading to Xanadu. Upgrading the plugin Flow Designer - Designer [sn_flow_designer] to version 26.2.5 fixed it.

Thanks for the heads up! It looks like that update was just released today. I'll give it a go when I have a chance and see if that fixes the problem.