clsProcessDefID Step
Description:
This step retrieves the GUID information for the current process definition.
Inputs
- varGlobalStoreID – variable/global to store the process definition GUID info
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “clsProcessDefIDDef” example.
- Create a new process definition called “clsProcessDefIDDef” and open the definition in designer mode.
- Drag a “clsProcessDefID” step to the canvas.
- Connect the dots between the “Start” step and “clsProcessDefID” steps, as shown above.
- Define a variable or a global to store the result.
- Click the "clsProcessDefID" step to configure its "Required" properties. Provide a name for the step. Provide the variable or global reference to store the process definition GUID info. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description.
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and then execute it. Render the process instance. Click the process step to view its properties. The “clsProcessDefID” step should fetch the current process definition GUID information and store it in the variable or global as configured.
- You must navigate the Process Definition page and search for the definition by its name. Use the column selector to view the DefinitionID column in the table. You notice the “definitionID” matches the variable or global holding the GUID value from the process instance.
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 import. Then, save the definition to confirm the changes.