Best Practices


About Exception Handling

Exception handling is the process of responding to the occurrence, during computation, of exceptions – anomalous or exceptional events requiring special processing – often changing the normal flow of program execution.

Adding a Step Outcome for Exceptions

Even under the best conditions, inputs can be unreliable. To handle missing or invalid data without crashing, steps need paths to account for errors or exceptions. We can add these outcome paths by selecting...

Catching All Unhandled Exceptions

Overview An exception is an anomalous or unexpected situation in a flow that requires special steps to handle it. In other words, it usually means something went wrong in your flow. Using exception handling is...

Catching All Unconnected Outcomes

Overview The Catch Outcome step catches outcome paths that are unconnected from the rest of the flow. It provides a universal mechanism for handling them. Usually this step is used to simplify or clean...

Using the No Data Result Path

If a flow step requires input that is not provided, the flow will stop running. For example, if a step requires input data from a user-completed form and the user submits the form with no data in the...

Adding Validation rules to Decisions Entities

A folder entity can have validation applied, set up in the form of rules or a flow created by the entity's action folder. Setting up validation rules is particularly useful if the Action menu is to...