Default outcome in decision elements

I don’t like using default outcome in decision elements. I want to expressly define which path should be taken, and dont want the flow to take a path because i did not anticipate something.

Then I ran into an issue where a flow was finishing early because there was no matching outcome, and i had not mapped the default outcome. This was skipping a final notification step that was critical to the process.

So now, I created a subflow that i can use to send an ‘error’ notification in any flow, and i pass in the flow name, running user name, and ‘error message’. I already have an object I use to log errors from my code, and just write to that object via flow.

This way I can provide a path for the default outcome that expressly triggers an error notification, but can also allow the flow to continue to the next step. Progress!

 
2
Kudos
 
2
Kudos

Now read this

buried killer lightning feature in winter 17

Buried deep on p 359 in the winter 17 release notes, lies this understated gem of a feature Assign a Custom Record Page to Lightning Apps, or Make It the Default for All 3 sentences of description and zero screenshots later, and its... Continue →