While Event references provide context-sensitive value references to the current event, you will sometimes need to access more specific information relating to the current state – attribute references allow you to do this.
For example, in a multi-review state, you might want to access information about each of the reviews, or a specific review, not just the most recently updated review.
A similar situation might arise for tasks, where you might want information about more than one task in an event that relates to a single task (or an event that does not relate to tasks at all).
You can access attributes from any Content review associated with the current workflow state by using a value reference in the form:
@ApprovalName > AttributeName@
For example, if you wanted the comment of the last approver of the "Technical" content review, you would use:
@Technical > approvalcomment@
|all events||A comma-separated list of users who have been assigned to the content review|
all events except approval events* events
For these events use @assignee@ without ApprovalName
The username for the user that was assigned or unassigned in the related event
|all events||A comma-separated list of users who Approved the content review|
|all events||A comma-separated list of users who Rejected the content review|
|all events||A comma-separated list of users who are assigned to the content review, but haven't yet Approved or Rejected it|
|all events||The note associated with the most recent Approval of the content review|
*The @Approval Name>assignee@ attribute reference is not supported for approval events
Triggers using these events will need to reference the named approval and use the
@approvalassignees@ event reference in the action macro if the assigned reviewer is required for the action