Skip to main content
In addition to reacting to changes on its own form, the form event trigger can also be triggered automatically when another workflow executes a step that satisfies this trigger event; automatic triggering does not currently support triggering by business association rules.

​
Steps

Follow these steps to create an integration & automation whose trigger type is form event trigger.
  1. Sign in to the YiDA workbench and click My apps.
  2. Select the app for which you want to create the integration & automation to open the App settings page.
  3. Click Integration & Automation, and then select Create integration & automation > Create from scratch.
  4. In the dialog box, enter a name for the integration & automation, select Form event trigger as the trigger event, specify the form that triggers the event, and click Confirm.
  5. On the integration & automation editing page, click Form event trigger.
  6. In the settings dialog box, configure the form trigger event.
The trigger event can trigger subsequent step rules through the current form’s create success, edit success, delete success, comment success, or workflow event.
Configuration itemDescription
Trigger eventCreate successTriggers the integration & automation when a user submits a form successfully.
Edit successTriggers when a user edits previously submitted form data. Only edits to regular form data are supported; edits at workflow form Steps do not trigger the event.
Two modes are supported: trigger when specific fields are modified, and trigger when any field is modified.
Delete successTriggers the integration & automation when existing data in the form is deleted.
Comment successTriggers the integration & automation when someone adds a comment to a data record in the form.
Workflow eventWhen the form that triggers the integration & automation is a workflow form, triggering by approval result and approval step actions is also supported.
For example, after an approval is completed, update fields in the intermediate table if the result is Accept. In a procurement scenario, when a purchase request is approved, the purchase details are added to the procurement information intermediate table.
Note: Workflow events support Multiselect. This feature is only available for workflow forms. Premium workflow triggers are only supported in the Professional edition (Premier edition) and the Dedicated edition. If the trigger step configured in the integration & automation has an auto-approval rule, auto-approved tasks do not trigger this automation flow during actual workflow execution.
Trigger methodAutomatic triggerIntegration & automation flows support Allow automatic trigger. Once automatic triggering is On, the current flow is triggered when another automation flow or workflow satisfies its trigger event.
Note: Automatic triggering supports up to three consecutive levels. That is, Flow A => triggers => Flow B, Flow B => triggers => Flow C, Flow C => cannot trigger ≠> Flow D.
Automatic triggering does not take effect in the following cases:
  • For OA approvals initiated through integration & automation, the App event trigger configured after the OA approval is completed does not take effect. In this case, an OA approval submitted manually can trigger the automation flow.
  • When an approval is initiated through integration & automation, the workflow Create trigger configured on the corresponding workflow form does not take effect.
  • When data is created or updated through business association rules, the Form event trigger configured on the target form does not take effect.
  • When data is created or edited across apps through integration & automation, the automation flow configured on the target form does not take effect.
Data filterAll dataAll data means no filter is applied and every record is returned.
Filter by conditionFilter by condition means only data that meets the specified conditions is returned.
Multi-level conditional filtering is supported, along with “AND” and “OR” operators.

​
Configure Steps

After configuring the trigger type, add different steps to build the flow chart. For details on step configuration, see Step configuration.