Resource Types in Advance Request Blocks

A resource request block lets collaborators ask for things the event has to source: golf carts, a backline package, a labor call, a generator. What they can ask for comes from the event's resource types, the same catalog procurement uses. Older versions of BackOps called these asset types, and you will still hear "asset request" for a request that names one.

Set up resource types before you build request blocks that depend on them, so each block can list the types it allows.

How a Request Block Uses Resource Types

When you turn on Resource request? on a request block, you choose its allowed resource types. A collaborator adding a line item picks one of those types, and the line item carries that type's attributes along with the block's own properties.

For example, a Golf Cart resource type might have a Type attribute with 4-passenger and 6-passenger options, so every golf cart request says which kind is wanted. A Labor Call might carry Call Name, Start Time, and End Time, so each requested call arrives with its scheduling details attached.

Where Resource Requests Go

Resource requests appear on the procurement Requests tab, where they carry their advance and resource approvals and can be turned into resource needs. Non-resource requests, such as credentials or parking passes, also show on the Requests tab for approval, but they are never sourced or turned into resource needs.

flowchart LR
    RT["Resource types"] --> RB["Request block (allowed types)"]
    RB --> LI["Collaborator line items"]
    LI --> RQ["Procurement Requests tab"]
    RQ --> N["Resource needs"]

Managing Resource Types

Resource types, their attribute library, and their categories are managed in Event settings, under Resources, and at the organization level as reusable templates. They are documented in full in the Resources section.

When an event copies a module template from your organization's library, the resource types its request blocks allow come with it.