In the form action settings, "Execution Condition" is a key feature used to control whether a particular step is executed. By configuring the execution condition appropriately, you can more precisely control the timing of action step triggers, making the process smarter and more efficient.
Understanding "Execution Condition"
Execution conditions are logical judgments within form actions used to determine whether a step should be executed. When specific conditions are met, the system will execute that step; otherwise, it will be skipped. They are typically associated with field values in the form, user action selections, or other logical conditions.
When you want a step to execute only under certain conditions, you can set execution conditions to ensure the action is triggered only when appropriate.
When to Use "Execution Condition"
Execution conditions are not a mandatory option and are suitable for the following scenarios:
Condition-triggered operations: You want to execute a step only when certain conditions are met. For example, send a confirmation email only when the order status is "Paid," or update the database record only when the task status is "Completed."
Dynamic control: Control the direction of the process based on form fields or other data.
Process optimization: Skip unnecessary steps through conditional judgments to improve process efficiency. For instance, if a certain field is empty or does not meet requirements, subsequent operations need not be executed.
How to Set "Execution Condition"
Setting "execution conditions" can be achieved through a conditional expression, with the following steps:
Find the "Execution Conditions" option: In the settings page of the selected action step, locate the "Execution Conditions" option.
Open the expression editor: Click the expression editor button next to "Execution Conditions." This will open the expression editor page where you can define the condition logic.
Set the condition logic: In the expression editor, you can use fields, variables, functions, or expressions from the form to define conditions.
Use expressions or functions: In the expression editor, you can not only use simple conditional judgments but also leverage more complex expressions or functions for evaluation. For example, you can combine "AND," "OR" operators, and other functions to achieve multi-condition judgments.
Note: If you use a collection action, you can select the fields in the collection item in context.
Using the "Continue next step when execution condition is not met" Option
In some cases, you may want the process to continue even if a particular step is not executed. In this situation, you can enable the "Continue next step when execution condition is not met" option.
How to Use:
When setting the "Execution Condition," check the checkbox for "Continue to Next Step When Execution Conditions Are Not Met."
Once enabled, even if a step is not executed due to unmet conditions, the system will continue to execute the next step without interrupting the entire process.
This flexible condition control makes business processes more efficient and intelligent, allowing for automatic adjustments to the process execution logic based on actual circumstances.