› User interface › Forms › Form events and actions › Form actions › Condition actions

Condition actions

Use condition actions (Begin, Else, and End) to define conditions related to an event firing. At runtime, the event is only fired if the condition is satisfied.

For example, if a loan can only be given to a customer whose earnings are equal to or more than 20,000 $, you can create a condition action on the online loan form. If the salary = $ 20000 OR salary > $ 20000, the user is directed to another form where other credit liabilities are declared to process the loan request.

A condition action must include a Begin condition, a regular action, such as Redirect, and an End condition. You can automatically add an Else and/or End condition when creating a Begin Condition action to speed up the process.

For example, to create a condition action with a Redirect action within it, perform the following steps:

  1. Create a Begin condition action.
  2. Create a Redirect action.
  3. Create an End condition action.
  4. Save and deploy the site. At runtime, the action is executed only if the condition specified for firing the action is satisfied.

You can create actions in any order. However, once created, you must arrange them in the following order: Begin Condition > Regular action > End Condition.

You can create nested actions within the Begin and End conditions. Once created, nested actions appear indented making it easier to determine the actions that are bound within a condition. For example, 

BeginCondition1
Clear1
BeginCondition2
	Clear2
EndCondition2
EndCondition1

You can expand or collapse a condition to show or hide the actions within it. By default, a condition is expanded.

See also: