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 show which end path the workflow processed. The stop will also ensure that sub-workflow processes are stopped when the parent workflow is completed.
Inputs
- None
Returns
- None
Usage:
Example:
Let’s build and execute the “stopDef” example.
- Create a new process definition named “stopDef” and open it in designer mode.
- Drag the “Task, Decision, and Stop” steps to the canvas.
- Connect the dots between the “Start” and the other steps, as shown above.
- Click the Task1 (Manager1 Approval) step to configure its "Required" properties. Provide a task name. Navigate to the “Optional” tab and configure the user to whom the task is routed.
- Click the Task2 (Pros Cons Sheet) step to configure its "Required" properties. Provide a task name. Navigate to the “Optional” tab and configure the user to whom the task is routed.
- Click the “Decision” step to configure its “Required” properties. Enter a step name. Enter a condition to evaluate. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.
- Select the outgoing connection links for the “Decision” step and configure their properties as True or False.
- Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should stop processing after the task step completes.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-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 the import. Then, save the definition to confirm the changes.