Commands, tokens, and validations are used throughout Project and Portfolio Management Center to enable advanced automation and defaulting.
Commands are at the heart of the execution layer within the deployment system. They determine which actions are executed at specific workflow steps. Actions performed at a workflow step can include file migration, script execution, data analysis, or code compilation. Using Commands provides an overview of commands, and examples of how to use them.
Special commands are commands with variable parameters and are used in object types, request types, report types, workflows, and validation command steps. Workflows use special commands in their workflow step sources. These command steps perform a variety of functions, such as copying files between environments and establishing connections to environments for remote command execution. Using Special Commands contains information about how to create, edit, and use special commands in PPM.
Tokens are variables that PPM entities use to reference information that is undefined until the entity is used in a specific context. For example, entities use tokens to set variables in commands or within notifications to specify recipients.
Field validations determine the field types (for example, a text field or drop-down list) and the values the field can accept. Workflow step validation controls the possible results of exiting steps. PPM uses the following types of tokens:
Using Tokens shows how to use tokens.
Validations determine the valid input values for user-defined fields, such as object type or request type fields. Validations also determine the possible results that a workflow step can return. Validations are used for the field component type and workflow step results. Using Validations provides detailed information on how to use tokens.
Note: To access the user interface components described in this document, you must be granted the Configuration license.