How to access the catalog variables (in the requested item) via the new flow designer ...?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2018 12:55 PM
Hi Experts,
I'm trying to understand the new flow-designer but failing doing my 1st piece of work ;-(
When using the flow-designer and i.e. starting with a trigger like new service request item is created.
... and I wand to do something with a variable used within the request ... I can't find the variable anywhere ...
Just as an example ... create a catalog item with a variable that is to be filled during the request process and try to update this variable value via a flow-designer workflow after the request item has been created ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2018 01:06 PM

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-12-2018 01:25 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-13-2018 12:42 PM
That does not appear to be possible as of Kingston. You could maybe do it with a custom action, but it would be pretty complicated.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-09-2018 06:20 AM
I've submitted an enhancement request for this particular item: FTASK37463
There are plenty of use cases for this and concatenation comes to mind as today that would require scripting. My example would be when you create a catalog task, you'd want to push the variables to Slack, Connect, or even the work notes in concatenated format. Today in a workflow without scripting, you can only hardcode the short description. So which would be easier to understand:
"Provision access for the users and dates"
-or-
"Innovation Lab Access: Provision for Aaron, Brad starting 8/10/18 through 8/15/18"
The concatenation includes the requested catalog item [possible already], and the variables for names and dates. This can be done via script as a business rule or part of the workflow, but that is exactly what FlowDesigner was meant to replace. This should get better with time.
This is even more important when blasting this over Slack, Teams, or other enterprise messaging systems.