Purpose:  Implementing a tiered workflow (approval) process

Audience: 25Live Functional Administrators

1. Tiered Workflow enforces the "order of approval" for events. When this functionality was first introduced by CollegeNET it allowed users to customize the order. This functionality has since been changed to one specific order.

The tasks generated by an event request must be approved in the "workflow" order. This prevents resources from being approved before locations or notification tasks (custom attributes/requirements) being approved before locations or resources.  Reminder: tasks are generated by a requester who does not have the ability to assign a location or resource.  A task won't be generated by users who have the ability to assign a location and/or resource.

2. The first step to using Tiered Workflow is to enable it. You can do this under More > System Settings > Workflow Settings > Use Tiered Workflow

The first task in workflow will be approving the event type. If you have notification set-up on the event type then a task will be created to approve that notification. For example, if you have "Wedding" as an event type and an administrator needs to approve all Weddings that occur on campus, then that event type will need to be approved first before it progresses any further in the process. Not many schools approve event types so if you don't, then this step is skipped.

The next step is Locations, then Resources, and last is approval or Custom Attributes and/or Requirements.

3. Here is what Tiered Workflow looks like on the event task list. You can see it's arranged in a specific order and there is a progress bar that displays where in the workflow the event currently stands.