Description:
This step retrieves the GUID 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 named “clsProcessDefIDDef” and open it in designer mode.
- Drag a “clsProcessDefID” step onto 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. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description.
- The “Logging” configuration is necessary for documentation and also measures workflow progress and 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 execute it. Render the process instance. Click the process step to view its properties. The “clsProcessDefID” step should retrieve the current process definition’s GUID and store it in the variable or global as configured.
- You must navigate to the Process Definition page and search for the definition by name. Use the column selector to display the DefinitionID column in the table. You notice that “definitionID” matches the variable or global that holds the GUID value from the process instance.
Definition Sample:
You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into 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.