A token is a dynamic value that controls how information (example: Text, colors, numbers, measurements) is interpreted and displayed throughout the system. Defined values can be used while designing forms, dashboards, Automation Processes, One-Step™ Actions, and fields.
Token features include:
- Counters: A counter is a token that automatically increases a defined initial value (number) by a defined increment. Counters can be used while designing forms, dashboards, Automation Processes, expressions, and One-Step Actions.
- Prompts: A prompt is a display window that requires users to provide information before proceeding with a process or Action (example: Specify the reason for putting an Incident into Pending status).
- Stored Values: A stored value is a named entity that stores commonly used information so that it can be accessed and/or reused from various places in CSM, such as One-Step Actions and queries.
- System Functions: A system function is a built-in placeholder token that dynamically adds variable information to a query or string (example: Current user's name).
Additionally, expressions, metrics, and fields can be used as tokens for One-Step Actions and other expressions, though they are not limited to token functionality.
Some tokens can be reformatted using modifiers and formats that change the visual format or calculated value of the token in a One-Step Action or expression. For example, a Date/Time field in a One-Step Action can be modified to display only the date without the time stamp for ease of use. For more information on applying a modifier or format, refer to the modifiers or formats documentation.
The easiest way to access tokens is through the Token Selector.
CSM provides several OOTB tokens. Use these tokens as-is, edit them, or create new tokens.