Description:
Form approval buttons should be used when a form is routed for approval. This also requires submitting the form and completing the task. Form is routed as a task through the workflow process using the RouteForm step. Complete/Reject buttons can be configured using the property page for each button.
Inputs
- ID/Name - Name of widget generated by FlowWright (read-only field)
Design:
Example:
Let’s build and execute the “FormApprovalDef” example.
- Create a new form definition called “FormApprovalDef.”
- Select the Open Designer checkbox and click the “Create” button
- Drag a “FormApproval” widget to the canvas
- Double-click the “Approve” button to configure the “Settings” properties. Select the button type from the drop-down list with “Success” as the default setting. The application configures the control name. Provide the button label. Click on the check box to hide, which is required during the run time. Provide the redirect URL after the form is approved.
- Double-click on the “Approve” button to configure the “Styling” properties. Provide the style script. If the class was previously uploaded, select it from the drop-down list.
- Double-click the “Approve” button to configure the “Others” properties. Provide the tooltip text.
- Double-click the “Reject” button to configure the “Settings” properties. Select the button type from the drop-down list, with “Danger” as the default setting. The application configures the control name. Provide the button label. Click on the check box to hide it, which is required during the run time. Provide the redirect URL after the form is rejected.
- Double-click on the “Reject” button to configure the “Styling” properties. Provide the style script. If the class was previously uploaded, select it from the drop-down list.
- Double-click the “Reject” button to configure the “Others” properties. Provide the tooltip text.
- Create a process definition. Configure a route form step to use the above definition and route the form to a user.
- Generate and execute a new process instance. The form is routed to the user as a task. When the user selects the task, the form is rendered with the buttons as configured. On form approval or rejection, the page is redirected to the page as configured.