Advanced approver placeholders in approval definitions

 

This article is for Zendesk approvals app Approve, which is our newest app for building approval processes.

If you're needing information on our older app named, Zendesk approvals app Approvals please see this section of our knowledge base.

Advanced placeholders are only available on the Pro tier of the Approve app.

Ticket fields

The Approve app allows for approvers to be dynamically referenced in ticket fields, organization fields and user fields. On ticket fields this could be an approver that's selected from a dropdown by an end user, or entered into a text field by an agent.

To reference an approver in a ticket field:

ticket.ticket_field_(id)

When referencing a dropdown field, the tag value must start with a valid user ID of the approver in question, such as 123_dropdown. When using a text field, you may specify an approver by user ID or email address. Multiple approvers can be specified separated by comma.

Organization and user fields

Users and organizations can also contain custom fields that can contain approver information and are accessed in an approval like this:

ticket.organization.(organization field key)

ticket.requester.(user field key)

ticket.assignee.(user field key)

Indirections

It's also possible to reference the approver in a custom field of an approver itself found in a custom field. For example, if you had a custom field called "Manager", this way you could reference the manager's manager, or even the manager's manager's manager. This also works if an approver field contains multiple approvers, the app will then include all the managers of the approvers in the field.

ticket.ticket_field_(id).(user field key)

ticket.organization.(organization field key).(user field key)

ticket.requester.(user field key).(user field key)

ticket.assignee.(user field key).(user field key).(user field key)

 


Was this article helpful?
1 out of 1 found this helpful

Comments

0 comments

Please sign in to leave a comment.