Workflow Triggers
A trigger is the starting point of a workflow. It determines when a workflow starts and supports condition settings to ensure that only valid records can trigger the workflow.
HAP currently supports 9 workflow trigger types, as shown below:
1. Triggered by Worksheet
Triggers the workflow when a record is created, updated, or deleted in a worksheet.
Example:
When a new record is created in the Expense Request worksheet, the workflow automatically sends the request to the department manager for approval.
2. Triggered on Schedule
Runs the workflow automatically on a recurring schedule that you define.
For example, send a reminder to organization members at 6:00 PM every weekday: "It's the end of the workday. Don't forget to submit your daily report."
3. Triggered by Date Field
Select a date field in a worksheet to define when the workflow should run. The workflow is triggered whenever a date or time specified in that field is reached.
For example, select the Birthday field in an Employee Directory worksheet. On each employee's birthday, the workflow can automatically send them a birthday message.
4. Triggered by Member Events
Triggers the workflow when a member joins or leaves the organization.
For example, you can maintain an Employee Directory worksheet that stays synchronized with member information in the organization management console. When an employee leaves the organization, the workflow can automatically update the employee's status in the worksheet to Former Employee.
5. Triggered by External User
Triggers the workflow when an external user of the application registers, logs in, closes their account, or is disabled.
For example, when an external user closes their account, the workflow can automatically send them a farewell email.
6. Triggered by Webhook
A webhook allows HAP to receive data pushed from external systems. When data changes in another system, the updated data can be sent to HAP. After receiving the webhook request, HAP triggers the workflow and automatically performs the configured actions, such as creating a record or sending a notification.
This enables automated data exchange between HAP and external systems and helps streamline cross-system business processes.
7. Packaged Business Process (PBP)
A packaged business process can be called by other workflows through Call PBP node. It can also be triggered through shortcut buttons on custom pages.
8. Subprocess
A subprocess cannot be created independently. It must be created through a Subprocess node within an existing workflow.
A subprocess cannot be triggered directly. It is triggered only when another workflow passes data to it during execution.
9. Triggered by Custom Button
A workflow triggered by a custom button cannot be created directly.
You need to create a custom action in a worksheet first. The system automatically generates a workflow associated with the button.
The workflow is triggered when a user clicks the custom button.
Was this document helpful?