Explicit Entity Format

You can provide a specific context value for an entity so that the default context can be overridden. Some tokens can never be evaluated in the default context. In these cases, you must use the following explicit entity format to set the context:

[PREFIX="<entity name>".<TOKEN_NAME>]

The token builder generates tokens in the explicit entity format by providing a list of possible values. When such a list is available, the Context Value field at the bottom of the Token Builder window is enabled. You can do one of the following:

  • Type in the field to reduce the list

  • Click the auto-complete icon to open the Validate window

The value you select is placed in the token in the Token field to generate an explicit entity token.

For example, to reference the email address for jsmith, the token would be:


To construct the token [USR="jsmith".EMAIL_ADDRESS] in the Token Builder window:

  1. Open the Token Builder window.

    See .

  2. In the Token Builder window, select the User folder.

    Available tokens are listed in the Tokens column, and the Context Value field is enabled.

    The Token field displays the string [USR.].

  3. In the Context Value field, select jsmith.

    The Token field displays the string [USR="jsmith"].

  4. In the Tokens column, click EMAIL_ADDRESS.

    The Token field displays the string [USR="jsmith".EMAIL_ADDRESS].

    This is the complete token. Because the token is now complete, the Token field becomes enabled.

  5. Select and copy the text in the Token field.

  6. Paste the text into another field.

Note: For a list of all explicit entity format tokens, see Tokens.

Nesting Explicit Entity Tokens within Other Tokens

The explicit entity format can be used to nest tokens within other tokens to generate a value. For example, to print the description of the workflow that is associated with package #10203, the token would be:


This token is built using the following steps:

  1. Build the Description token for the workflow.

  2. Copy and paste the Description token into another field.

  3. Build the Workflow Name token for the package.

  4. Copy and paste the Workflow Name token within the Description token.

Internally, this token is evaluated in two stages. The inner token is evaluated and the token has the following internal representation:


The remaining token is evaluated and the final result is printed:

description of my workflow

Caution: PPM does not support nesting explicit entity tokens within other tokens in the following cases:

  • field level security for request header types and request types

  • workflow security

  • special commands for workflows