Last Updated: May 10, 2022
In automation workflows, human interventions are needed frequently. You can design human actions and trigger tasks based the on the actions using Button settings.
By default, four buttons PREVIOUS, NEXT, Cancel and Save are provided with actions Save, Save, Exit, Save and Exit, respectively. You can add more buttons as required by the automation flow.
For Approval flow, add button Approve with action Save and Exit.
Inline Tables are displayed below the main table with Button Name and Action fields.
In Employee Salary Administration HyperApp, the Supervisor sends an increment recommendation to the Approver. Approver either approves or rejects the increment.
- When the Approver clicks the Approve button, the Task to update the increment in Employee’s payroll record is triggered and State is updated to Approved.
- When the Approver clicks the Reject button, the Task to send an email stating “Sorry! The recommendation is beyond expectation.” is triggered and State is updated to Rejected.
When the Approver opens the form, the following screen is displayed.
Tasks are triggered and State of the record is updated based on the Approve/Reject button clicked.
Tasks triggered from Forms require cluster assigned in the node configuration.
This feature allows Business Users to access the Forms on mobile. You can send an email with the URL, clicking on which the user can open the form in mobile and take the necessary actions. The associated task is triggered based on the action taken.
If a Travel Request requires Manager Approval, the URL can be sent to the Manager and he/she can open the form in mobile and click the Approve button. The associated task to send email to Requestor will be triggered.
The URL is created by using predefined function Get Form URL function.
The URL is valid for one week.
A form can have a maximum of four buttons in the main table and two buttons for the inline table.
You can change the name of the default buttons Cancel and Save if required.