Description:

Form approval buttons should be used when a form is routed for approval. This process requires submitting the form and completing the task. The form is routed as a task through the workflow process using the RouteForm step. The property page for each button allows for the configuration of the complete/reject buttons.

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 it, which is required during the run time. Provide the redirect URL after the form is approved.  

• Double-click 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 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. The form is rendered with the configured buttons when the user selects the task. Upon form approval or rejection, the page is redirected to the page as configured. 

Definition Sample:

You may download the sample definition(s) from the link here and later import it (drag-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page. 

NOTE: Please verify and complete the process steps for any missing configurations, such as file path references and database connections after import. Then, save the definition to confirm the changes. 

Click here to download the sample file.