Evaluating Tokens and Creating Transitions Based on Results

Deployment Management includes workflow execution steps that may be used to set up data-dependent rules for the routing of workflow processes. Token execution workflow steps enable a workflow to be routed based on the value of any field within a particular entity. A token execution workflow step references the value of a given token and uses that value as the result of the workflow step. A transition can be made based on the value stored in the product by using tokens in the execution workflow step.

Create a new execution step source with the field values as defined in Table 4-7. Execution window values for evaluating tokens.

Table 4-7. Execution window values for evaluating tokens

Field Name	Description
Name	Type a descriptive name for the workflow step source.
Workflow Scope	Packages
Execution Type	Token
Processing Type	Manual or Immediate
Validation	Selects or creates a validation that includes all of the possible values of the resolved token. For example, if the token is for the Priority field, use the validation for the Priority field here as well.
Execution	Type the token for the value that the transition will be based on.
Enabled	Yes

For example, IT needs to deploy changes to different servers depending on the type of object being deployed.

Figure 4-1. Transitioning based on a token

IT decides to use an execution workflow step to automatically evaluate the object type and route the package line accordingly. To accomplish this, an execution workflow step source, Evaluate Object Type, is configured with the parameters listed in Table 4-8. Example of execution window values for evaluating tokens.

Table 4-8. Example of execution window values for evaluating tokens

Field Name	Description
Name	Evaluate Object Type
Workflow Scope	Packages
Execution Type	Token
Processing Type	Immediate
Validation	DLV - Object Type - Enabled
Execution	[PKGL.OBJECT_TYPE]
Enabled	Yes