When working with Chat flows, I've noticed an option in the Update Data Action called "output from Flow", but I cannot find any documentation on it. For example, it's not at all mentioned in the
https://help.mypurecloud.com/articles/update-data-data-action/ article.
I've noticed the following behaviors:
- They are not available in Call Flows.
- It writes to the participant attributes, much set like "Set Participant Data" action.
- It's available for all variable types (but it doesn't output data for all variable types).
- Once set in a published flow, the variable cannot be renamed. Also, it seems impossible to removed (once published).
- Even if I remove it from the Architect Flow and republish, it's still there (in the Data overview, and taking up the variable namespace, so cannot add new variables with the same name, and shows up in autocomplete etc).
- And I cannot delete "trashcan" it from the data overview either. (I guess its just there stuck in my Flow forever now).
What's the deal with this "Output from Flow" action, and what are the differences compared with the "Set Participant" action?
They way I currently see it, "Output from Flow" improves over "Set Participant" action:
- It's referenced in the Data overview. That's very nice, unlike the "Set Participant Data" action, which are not available in the overview.
- It shows up in expression/variable autocomplete, as other Flow/State/Task variables do. Also very nice.
- Presumably they are updated right away, and not just "updated/available" once the flow completes, as "Set Participant Data" is.
- Seemingly it can be used for multiple data types.
There are also significant drawbacks, compared to the "Set Participant" and "Update Data" actions:
- Once used and published, it seem to be glued to the Flow forever. I would guess the thinking behind it is preventing breaking changes when a user removes it, but the fact there seems to be no way to get rid of it at all, I strongly dislike.
- I haven't tested recreating a flow from scratch e.g. using import/export, but what a bother that would be, even if it worked.
- It cannot be renamed in the UI. This - I guess - is because the variable name is directly coupled with the "output name" written to the participant attributes. This add's to the rigidity of the action. You want clear variable names in your flows, that usually means iterating.
- It seems to be availalble on all variable types but not all variable types write to the participant data (I haven't tested all which do).
- Is there a situation where those variables can still be consumed? (Otherwise it seems misleading to offer it on all variable types.)
Love to hear some thoughts on this "Output from Variable" option from other users!
- Do you use them?
- Pros/cons?
- etc
#ArchitectureandDesign#DigitalChannels#PlatformAdministration#SystemAdministration------------------------------
Joel Hellman
Hi3G
------------------------------