Actions and Conditions: Triggers and Condition Settings
In Kuika Process Automation, actions and conditions are important components used to automate business processes and create dynamic flows in processes. Actions are steps that are triggered when a certain condition is met. Conditions are the criteria that determine when and under what circumstances these actions are triggered. Thanks to this duo, business processes can proceed in a flexible and controlled manner in certain steps.
Actions and Triggers
Actions: Defines the actions to be taken at a specific step in the process. For example, they are defined as various tasks such as sending a notification to the user, updating data or starting the next step in the process.
User Actions: Actions such as sending a task or notifications to the user.
System Actions: Actions that happen automatically are classified as system actions. For example, the automatic termination of a process after a certain period of time or updating a database record.
Triggers: Events that initiate an action.
Timer Triggers: Triggered after a certain period of time, initiating the action (e.g. task closure after 24 hours).
State Triggers: A specific condition in the process is triggered (e.g. when a decision such as “Approved” or “Rejected” is taken).
Condition Settings
Conditions: Defines the criteria for actions to be performed. Conditions determine in which situation or under which conditions an action will work.
If-Then-Else Conditions: Defines the action to be taken when a certain condition occurs. For example, initiating the next step after a user confirmation.
Logical Conditions: Multiple conditions can be defined with “And/Or” operators. Thus, an action can be triggered only when all conditions are met or when at least one condition is met.
Dynamic Processes with Condition Settings:
If a task is not approved in an approval process, another user can step in.
Custom processes can be created, such as automatically closing tasks that are not completed by a certain date.
Setting Conditions: Create Exclusive Gateway allows the workflow to be guided by following certain paths when certain conditions are met. It is similar to condition settings that define the conditions under which actions and triggers will work. Through the Gateway, different paths are set in the workflow according to the conditions and these paths are managed using logical rules (for example, “Yes” or “No”).
Default Path and “Will Execute Otherwise” Setting: If none of the defined conditions are met, the workflow will proceed on the default path, which overlaps with the trigger and condition logic. When a specific action or path is not selected in the workflow, continuing the process with a defined default path provides a safety mechanism in the process of triggering actions.
Condition Sequencing and Control: Controlling the rules defined in Create Exclusive Gateway in top-down order emphasizes the prioritization and logical evaluation of trigger conditions. This sequencing ensures that the workflow proceeds in the right way with the right conditions.
