I know that values output from a step can be preserved in the event data by:
1. Creating a property on the workflow with the same name as the output
2. Ensuring that the step that generates the output value is executed before the "Create Event" step.
My question is this: what the *heck* do I do if a step's output value name is the same as that from another step?
For example, both "StatusPage Create Incident" and "xMatters Initiate Incident" have an output called "Incident ID", so if I create a property on the workflow called "Incident ID", how on earth do I control which value is stored?
The only solution I can come up with is a small custom step that takes the input value and stores in as a differently-named output, thus avoiding the name clash.
Comments
Please sign in to leave a comment.
Thanks, both!
I had completely misunderstood the complete process to get values preserved within the xMatters event - I don't think I've ever actually found any documentation on how to do it.
As a result, I had missed out the requirement to add the property to the message form and then, from there, drag the output from a step into the Create Event configuration ... thus avoiding the name clash that I was concerned with.
I look forward to reading/hearing more about "flow continuation" - I love how you guys continue to find ways to improve the product and make even more flexible than it already is.