Multi-Valued Dimensions CM Variables

These multi-valued variables are built into Dimensions CM and may appear anywhere in a request template. Unlike single-valued variables, they are replaced by a list of entries, each of which may occupy several lines.

For some multi-valued variables, column variables exist that enable you to access information in a particular column. This column information can duplicate the information provided by the multi-valued variables, or provide additional information. Column variables also enable you to have greater control over the formatting of each variable. For details about formatting, see Using Substitution Variable Syntax.

The following table provides descriptions of the multi-valued Dimensions CM variables.

Multi-valued variable | Description | Column variables
%action_history% | A list of all actions performed on the request. Each entry includes a short description of the action, the action number and date, plus the login user name, full name, phone number, and department of the user performing the action. | %ah_action_number%: The action number. %ah_date%: The action date in format DD-MON-YYYY HH:MM:SS. %ah_status%: The state to which this request was actioned. %ah_user_name%: The full user name. %ah_user_phone%: The user's phone number. %ah_user_dept%: The user's department. %ah_action_note%: The action note. %ah_user_group%: The action history user group.
%audit_trail_failure% | Lists the details of the audit records for failed authentication attempts on a request. |
%audit_trail_success% | Lists the details of the audit records for successful authentication attempts on a request. |
%affected_baseline% | A list of all baselines currently related to the request. Each entry includes details about the relationship, the current status of the baseline, and the user who created the relationship. | %bln_action_number%: Request action number when the relationship was created. %bln_baseline_id%: The related baseline specification. %bln_baseline_type%: The type of the baseline. %bln_brief_desc%: A brief description of the baseline. %bln_creation_method%: How the baseline was originally created: merged, revised, etc. %bln_relationship%: The name of the relationship. %bln_status%: The current status of the baseline. %bln_template%: The template name that was used to create the baseline. %bln_user%: The OS id of the user who created the relationship. %bln_user_name%: The full user name of who created the relationship.
%affected_item% | A list of all item revisions currently related to the request. Each entry includes the full item specification, item library filename, the action number when the relationship was created, the type of relationship, and the full name of the user who created the relationship. | %ai_action_number%: The action number. %ai_item_id%: The item's identity. %ai_user_name%: The full user name. %ai_filename%: The item's filename. %ai_brief_desc%: The item's brief description.
%affected_part% | A list of all design parts currently related to the request. Each entry includes the full part specification, the design part category, the action number when the relationship was created, and the full name of the user who created the relationship. | %ap_action_number%: The action number. %ap_part_id%: The part's identity. %ap_user_name%: The full user name. %ap_user%: The user. %ap_category%: The design part category. %ap_brief_desc%: The part's brief description.
%parent_doc% | A list of all higher-level requests to which this request (child) is currently related. Each entry includes the higher-level request ID, its title (attribute no. 1), the action number when the relationship was created, and the full name of the user who created the relationship. | %pd_relationship%: The relationship. %pd_doc_id%: The document's identity. %pd_product%: The document's owning product. %pd_status%: The status. %pd_user_name%: The full user name. %pd_user%: The user. %pd_brief_desc%: The brief description.
%related_doc% | A list of all lower-level requests currently related to this request (parent). Each entry includes the lower-level request ID, its title (attribute no. 1), the action number when the relationship was created, and the full name of the user who created the relationship. | %rd_action_number%: The action number. %rd_relationship%: The relationship. %rd_doc_id%: The document's identity. %rd_product%: The document's owning product. %rd_status%: The document's status. %rd_user_name%: The full user name. %rd_user%: The user. %rd_brief_desc%: The document's brief description.
%update_history% | A list of all modifications other than actioning to the request. Each entry includes a short description of the modification, the action number and date, plus the login user name, full name, phone, and department of the user making the modification. | %uh_action_number%: The action number. %uh_date%: The date in format DD-MON-YYYY HH:MM:SS. %uh_user_name%: The full user name. %uh_user%: The user. %uh_user_telephone_no%: The user's telephone number. %uh_user_dept%: The user's department. %uh_user_note%: The user's note. %uh_user_group%: The update history user group.
%attribute_update_history% | A list of attribute updates made to the request. Each entry includes the action number and date, plus the login user name, full name, phone, and department of the user making the modification, details of the attribute and the value before and after the change. | %auh_action_number%: The change document action number indicating when the update was done. %auh_user_name%: The full user name of the user who did the update. %auh_date%: The date the update was done. %auh_user%: The OS name of the user who did the update. %auh_user_telephone_no%: The telephone number of the user who did the update. %auh_user_dept%: The department of the user who did the update. %auh_user_group%: The group of the user who did the update. %auh_user_note%: The user note of the user who did the update. %auh_attrno%: The attribute number for which the change was made. %auh_attr_variable%: The attribute variable for which the change was made. %auh_old_value%: The old attribute value. %auh_new_value%: The new attribute value.
%user_roles% | A list of the primary, secondary, and leader users for every role in the lifecycle. |
%description%, %description_end% | The detailed description of the request. These two substitution variables must appear on separate, successive lines in a request template. |
%action%, %action_text%, %action_end% | These three variables are used to define a subtemplate for action descriptions. The subtemplate is part of the overall request template and contains a list of all recorded action descriptions. This subtemplate starts with the variable %action% and ends with the variable %action_end%, both appearing on separate lines. Between these, the variable %action_text% must appear on a separate line, to define where the text of the action description will appear. You can also use the column variables described to the right, as well as the other substitution variables described above (including user-defined variables) in the subtemplate. NOTE This subtemplate is required for add action description operations to be recorded in the database, regardless of whether you want the data to show up in a browse template. NOTE The action descriptions are stored separately. If you add variables to the template they do not affect the action descriptions previously entered (the action description substitution variables are not substituted). | %user_name%: The full name of the user entering the action description. %user_department%: The user's department. %user_location%: The user's site. %user_telephone_no%: The user's phone number. %date%: The date of the action description was entered. %time%: The time of the action description was entered.
%chdoc_attachments% | A list of files that are attached to the request. |
%primary_user% | A list of users who currently have the request in their inbox and have the primary role capability. |
%secondary_user% | A list of users who currently have the request in their inbox and have the secondary role capability. |
%leader_user% | A list of users who currently have the request in their inbox and have the leader role capability. |

Related Topics

Single-Valued Dimensions CM Variables

User-Defined Variables