Use subscriber, requester and actor placeholders

At Entitlement Catalog, when you configure a workflow action for a service, you can optionally replace the values in various fields with placeholders. Placeholders related to Subscriber or Requester are based on identifiers or attributes of people who play a role in the service transaction. For Actors, placeholders can only be based on their attributes.


  • To insert a Subscriber or Requester Person Identifier, use the format #{RoleName}[Identifier.{NameOfIdentifier}.Value].
    Example for the default identifier Windows user account of the Subscriber: #Subscriber[Identifier.Windows user account.Value]
    • If there are multiple values for an identifier, all values are listed, separated by a semicolon (;).
  • When you insert subscriber placeholders based on Organizational Attributes:
    • A default placeholder Name is available for the name of each organizational element (for example, #Subscriber.Departments[Name]). This placeholder is not based on an Organizational Attribute that you configured at Data Model > Organizational Attributes. For this reason, you cannot configure an Organizational Attribute Name manually.
    • The related organizational element is included in the placeholder (e.g. #Subscriber.Department.[DistributionList]).
  • You can use requester placeholders to identify an Ivanti Automation Agent. For example, in an Invoke Run Book action with a Run Book that uses the parameter $[RunBookWho], you can use placeholders to identify the Ivanti Automation Agent that should execute the Run Book. If a service is aimed at delivering Microsoft Visio, you can use the placeholder #Requester[DeviceName] to configure the service to be delivered to the device from which it is requested only; when the user switches to a different device, the service isn't delivered to this device.
    • Use #Requester[DeviceName] to resolve the device name of the requester e.g. (VM-win7). You can use this placeholder in managed environments. This method uses reverse DNS to identify the requester’s device name from which a service is requested. For this functionality to work, your DNS settings must therefore be configured correctly.
    • Use #Requester[DeviceID] to resolve the GUID of the Ivanti Automation Agent that is running on the device of the requester (e.g. "{A299DF-611E-4479-A25A-8C8A4BdB7B6A}"). In non-corporate and SaaS environments, Agent names are not guaranteed to be unique. Because Ivanti Automation can now schedule Run Books on Agents identified by GUID, you can use this placeholder to uniquely identify the Ivanti Automation Agent that should execute the Run Book. If the placeholder doesn't resolve in a valid Agent GUID, Identity Director tries to identify the Agent by device name (reverse DNS).

      If many users in your Identity Director environment work from a Terminal Server session, please consider the nature of the service before you use these placeholders: If the service installs software, this may lead to undesired behavior, as it is installed on the Terminal Server.
  • For password people attributes, the following placeholders are available for subscriber, requester and actor placeholders:




Use the encrypted value of the password. In the Management Portal and Web Portal, the password is masked and shown as [attributename]. For example, you can use this placeholder in an Invoke Run Book action to provide the encrypted password to Ivanti Automation Run Books.


Resolve the description of the password, e.g. "This is the domain password".


Resolve the value of the password as clear text, e.g. "1234DomainPassword".

See also