Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Adding a validation rule to a flow action

Updated on April 5, 2022

Ensure that the data that your users provide meets the conditions that a case requires in order to go forward. By assigning validation rules to flow actions, you can prevent users from entering information that your application cannot process, and reduce the number of processing errors.

For example, a loan application might require the customer to provide a down payment. You create a validate rule that checks whether the down payment is sufficient. Next, you assign the rule to a flow action that executes at the end of the step in which the customer provides loan information. If the amount of the down payment is too low, the validate rule prevents the case from proceeding until the customer increases the down payment.
Before you begin: Create a validation rule. For more information, see Validating field input in complex scenarios.
  1. In the navigation pane of App Studio, click Case types, and then click the case type that you want to open.

  2. On the Workflow tab, hover over the name of the process to which you want to add a validation rule, and then click Configure process icon.

  3. In the top right corner of the screen, click Open process.

  4. On the canvas, right-click the connector to which you want to add the validation rule, and then click Open Flow Action.

  5. In the flow action rule, open the Validation tab.

  6. In the Validate field, select the validation rule that you want to assign to the connector.

  7. Click Save.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us