Description:
Generates a global unique identifier
Inputs
- varGlobalToStoreValue-- Variable/Global to store the value
- ID Type - A text tag to determine the ID type
- ID Start value - A number to determine the ID start value and the next value based on the ID type
Returns
- True – step executed successfully
- False – step failed to execute
Usage:
Example:
Let’s build and execute the “generateIdDef” example.
- Create a new definition called “generateIdDef”
- Select the definition and click the “design” button
- Drag three “generateID” and “synchronize” steps from the toolbox and connect them as below
- Define a variable/global to store the ID value generated
- Select one “generateID” step to configure its “Settings” properties. Provide a step name. Provide an ID type as below. Here, the ID value “CHECK” is suffixed by a unique ID generated by this step. The ID values created are stored in “deGenerateID” SQL table. Provide a variable/global reference to store the ID value generated.
- Select the “generateID” step to configure its “Advanced” properties. Provide the ID start value in any desired format. Repeat the configuration for other GenerateID steps. NOTE: The ID start value shall be the same.
- 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 in the images below. Configure the “Logging” using the following properties.
- Save the process definition, create a new process instance, and execute. This step generates a global unique identifier. Select the process instance to render and check the variables configured to store the unique ID value.
- The ID values created are stored in “deGenerateID” SQL table.
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.