Description:

This step generates a DB name automatically. 

Usage:

Example:

Let’s build and execute the clsGenerateDBNameDef example.  

• Create a new definition called “clsGenerateDBNameDef”
• Select the definition and click the “design” button
• Drag a clsGenerateDBNameDef step to the canvas
• Connect the dots between the start and clsGenerateDBNameDef step
• Define a variable/global to store the DB Name generated automatically

• Click the “clsGenerateDBName” step to configure its “Settings” properties. Provide a step name. Select the Tenant Manager connection from the drop-down list. Provide a variable/global reference to hold the DB name generated automatically during runtime. 

• Click the “clsGenerateDBName” step to configure its “Advanced” properties. You may provide the tenant with a meaningful database name. In this example, the database name is created as “TestDB -  35635c17-06b5-455b-a1e6-51507c1e971f” where the GUID value is provided by the system variable.initiatorID. 

• 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. Render the process instance. Click on the process step to view its properties. The step should generate a DB name as configured. 
• Here, the database name is generated automatically (a string of 32 alphanumeric characters)

• Here, the database name is generated as configured by the admin.