- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2023 12:49 PM
When I try to add a script action there isn't one. How do I turn this on so I can use the advanced features and get extra data from different parts of the system? The documentation is clear that I should have this option, I've logged in as the local admin and have the same result. I've checked roles, etc. all based on documents and yet I can't find it. Why won't script action show up for me?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2023 01:12 PM
There's two ways to script in Flows
- inline scripts - totally not recommended, unreliable, prone to breading, hell to maintain - stay away.
- Script step in custom Actions - do this.
It is different from Workflows.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2023 01:20 PM - edited ‎12-01-2023 01:22 PM
This is how you create custom Actions:
This is what you should stay away from:
By creating and using custom Actions you are respecting the Flow Designer paradigm where actions receive input by dropping data-pills on them and provide output in the form of their own data pills.
Here's an attempt to put it into a picture:
And this is how a custom action than consumes data from pills and provides its own data-pills to be used as inputs for other actions:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2023 01:12 PM
There's two ways to script in Flows
- inline scripts - totally not recommended, unreliable, prone to breading, hell to maintain - stay away.
- Script step in custom Actions - do this.
It is different from Workflows.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-01-2023 01:20 PM - edited ‎12-01-2023 01:22 PM
This is how you create custom Actions:
This is what you should stay away from:
By creating and using custom Actions you are respecting the Flow Designer paradigm where actions receive input by dropping data-pills on them and provide output in the form of their own data pills.
Here's an attempt to put it into a picture:
And this is how a custom action than consumes data from pills and provides its own data-pills to be used as inputs for other actions: