Published at: 2026-09-17
workflow-triggers-and-field-change-reference
This article explains Workflow trigger methods, post-actions, and field change rules.
Trigger a process
Execution Order:
Trigger -> trigger conditions and filters -> branch conditions -> immediately executed activities
Trigger methods
| Trigger method | Description |
|---|---|
| New | Triggers after data is created. You can trigger on submission or after approval passes. |
| Void | Triggers after data is voided. |
| Restore | Triggers after data is restored. |
| Field update trigger | Triggers after specified fields change. |
| Scheduled trigger | Triggers at a specified time or cycle. |
New triggers support:
- Trigger directly on data submission: The system checks conditions immediately after submission.
- Trigger after data approval passes: The system checks conditions after approval passes. If no approval exists, the trigger runs directly.
Field change triggers
| Time point | Meaning |
|---|---|
| Before change | The field value before saving. |
| During change | The field changes from the old value to the new value. |
| After change | The field value after saving. |
Scheduled triggers
| Type | Description |
|---|---|
| Run once | Runs once at a specified date and time. |
| Repeat | Runs by day, week, month, year, or custom day interval. You can set a start date and End Date. |
When you configure a scheduled trigger, check the time zone, date field, date offset, execution time, frequency, and end rule. Each execution still checks filters and conditions.
Actions after trigger
Add Immediately Executed Activities in a branch path. You can add multiple actions to the same branch. Actions run in list order, and you can drag them to adjust the order.
| Action | Purpose |
|---|---|
| CRM reminder, SMS, email, External Notification | Send notifications. |
| Field change | Update fields on the current object, main object, or Related Object. |
| Data operation | Execute data processing. |
| Initiate Business Process, initiate flow | Start subsequent processes. |
| Data Lock / Unlock | Control whether data can be edited. |
| Change Owner, change team members | Adjust data ownership or member permissions. |
| New task, schedule, Sales Records | Create follow-up items or records. |
| Execute APL code, execute Conversion Rules | Execute custom logic or business conversion. |
A branch can end after a match or continue matching. View execution results in the Workflow Execution Log.
Field changes
Field changes update fields such as Lead Stage, account level, Opportunity Status, Owner, Date, or Amount.
Update scope
| Update method | Description |
|---|---|
| Update current object | Updates the object that triggered the Workflow. |
| Update main / Related Object | Updates the main object or another Related Object associated with the current object. |
When you select a main object or Related Object, confirm the relationship and target data.
Field values
In Update the following fields, select fields. In Change To, set values. Values can come from:
- Fixed values.
- Current object fields.
- Main object or Related Object fields.
- System variables or other available variables.
Click Add Field Change to update multiple fields at one time. Field values must comply with the target Field Type, option values, and required-field rules.
Execution rules
- Multiple fields in the same activity run with that action.
- If multiple actions update the same field, the later action might overwrite the earlier result.
- If a field value does not comply with rules, the field might not update. Examples include an empty required field, division by 0 in a number calculation, an out-of-range result, or a missing option value.
- Updating the main object or Related Object requires view and edit permissions for the target data.
- Later actions might read field values after the field change. If dependencies exist, order actions by dependency.
FAQ
| Question | Check item |
|---|---|
| Workflow did not trigger | Check the Trigger Object, Trigger Timing, conditions, filters, branches, and Enable Status. For New triggers, also check the approval trigger timing. |
| Scheduled task did not run | Check the time zone, date field, date offset, execution time, frequency, End Date, and filters. |
| Field did not update | Check the update scope, target field, Field Type, option value, required-field rules, field permissions, and Execution Log. |
| Field value was overwritten | Check whether multiple actions update the same field, and review the action order. |
| Notification or another action failed | Check the Execution Log, service and template, target process, APL code, Conversion Rules, and Data Permission. |