When using When Adding or Modifying Records, the most common questions fall into 3 areas: trigger logic, field setup, and failure checks; this FAQ covers 3 common questions.
FAQ
What is the difference between “field is not empty when added” and “trigger when the field is modified”?
- These are two trigger cases for the same field.
- When a new record is added, the workflow runs if that field is not empty.
- When an existing record changes and that field is modified, the workflow also runs.
Can I set multiple trigger fields at the same time?
- One trigger supports one selected field as the trigger condition.
- If you want different fields to start different workflows, create separate workflows.
- Splitting workflows by scenario also makes later maintenance easier.
What should I do if the trigger fails?
- Click Logs on the left side to review the failure reason.
- Check whether the target table still exists and whether the field settings are correct.
- After adjusting the settings, test again by adding or modifying a record.
Glossary
| Term | Definition |
|---|---|
| Trigger | The starting condition of an automation workflow. When the specified event happens, the workflow begins. |
| Table | The record container in a WPS database table. The trigger must be linked to a specific table. |
| Filter condition | An extra condition added on top of the trigger event to narrow the actual execution scope. |