Description:

This is the end of the processing step, giving you complete control. A workflow instance can have many execution end/stop points. For larger workflows with many endpoints, all paths can be joined to the stop step to view what end path the workflow processed. The stop will also ensure that sub-workflow processes are stopped when the parent workflow is completed.

Usage:

Example:

Let’s build and execute the “stopDef” example.          

• Create a new definition called “stopDef”
• Select the definition and click the “design” button
• Drag the “Task, Decision, and Stop” steps from the toolbox
• Connect the dots between the Start and the other steps as above
• Click the Task1 (Manager1 Approval) step to configure its "Required" properties. Provide a task name. Navigate to the “Optional” tab. Configure the user to route the task to. 
• Click the Task2 (Pros Cons Sheet) step to configure its "Required" properties. Provide a task name. Navigate to the “Optional” tab. Configure the user to route the task to. 
• Click the “Decision” step to configure its “Required” properties. Provide a step name. Provide a condition to evaluate. Click the Save button. 

• Select the outgoing connection links for the “Decision” step and configure the properties to be True or False. 

• Save the process definition, create a new instance, and execute. Render the process instance. Click on the process step to view its properties. The step should stop the processing activity after the task step is completed. 

Definition Sample:

You may download the ZIP file and extract the sample definition(s) from the link here. Then, you can 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.