Supporting Custom Event Team Member Roles in Multi-Step Approval Processes
Certain event workflows may require multiple levels of approval, for example, an event that requires approval from both the organizer’s manager as well as the company’s finance team. In these cases, specific action is required to ensure all levels of approver are assigned the appropriate Event Team Member role.
Who can use this feature?
- Business Admin Users - Browser
- Creating Event Actions for Multi-Step Approval Processes
- Event Team Members - Browser, iPad
- Assigning Approvers in Multi-Step Approval Processes
- Users require an Events Management License
Configuring Object Workflows for Event Approvals
All Users
To configure this feature, ensure Creating Event Approvals Using Object Workflows is enabled.
Creating Event Actions for Multi-Step Approval Processes as
Business Admin Users
Each level of approval requires a dedicated em_event_action__v record to assign the next approver’s role:
- Create the appropriate levels of approval in the workflow by creating Workflow Decisions.
-
Ensure the verdict that approves the event and advances the workflow is exactly labeled Approve.
This label can be translated, see About Language & Region Settings for more information.
- Navigate to the Event Actions section of appropriate em_event_configuration__v record.
- Select Create.
-
Populate the following fields:
- Button Name – Approve
- Starting Status – The event’s status in the workflow when the next approver is assigned
- Ending Status – Vault Workflow
- Approver Role – Select the appropriate role the next approver should be assigned
- Country Override – This field is optional
- Select either Save or Save + Create.
Assigning Approvers in Multi-Step Approval Processes as
Event Team Members
When an Event Team Member assigned as an approver in a multi-step approval process approves the event via the Approve verdict, the next approver is assigned the role and created as an Event Team Member according to the properties of the em_event_action__v record matching the event’s status.
The approval is reflected in a new em_event_history__v record, which also states the role of the next approver in the process.
