Translating Approved Requests into Procurement Needs
Use the Translation tab to drag approved advance requests onto procurement needs and schedule blocks, consolidating many requests into the needs you actually order.
Translation is where requests become needs. A request says what one collaborator asked for; a need in a procurement says what the event will actually get. Translating a request means linking it to the need, or the scheduled block of a need, that fulfills it. Fifteen groups can each ask for golf carts, and translation lets you point all fifteen requests at one need for five carts, with each request still traceable to that need.
What the Translation Tab Shows
Open Resourcing, Procurement in the event sidebar and select Translation. The page has two sides.
The left side lists the requests ready to translate: every request that has all the approvals its request block requires and is not yet linked to a need. Search, group and choose columns to find the ones you want. Approving requests happens on the Requests tab.
The right side lists the event's procurements, in a Table view where each procurement expands to show its needs and their schedule blocks, or a Scheduler view that lays the needs out on a timeline. Search, filter, or select Create procurement to start a new one.
Link a Request to a Need
Find the need
Drag the request
The request leaves the left side once it is linked. Keep dragging requests onto the same need when one need answers several of them.
Where to drop depends on the need's resource type. A type marked Scheduled takes requests on its schedule blocks, so a request for Friday's golf carts goes on the Friday block. A type that is not scheduled takes requests on the need itself.
Start a Procurement from Selected Requests
Select requests on the left, then select Create procurement. The new procurement opens with one need for each resource type among the selected requests, with the quantity set to how many requests asked for that type and the attribute values of the first one. Name it, adjust the needs, and save.
Creating a procurement this way fills in the needs but does not link the requests to them. The requests stay on the left until you drag them onto the new needs.
Link Requests from a Need
You can also link requests from the need itself. Open a need from the procurement and use Linked requests: on a need whose type is not scheduled it sits on the need, and on a scheduled type it sits on each schedule block. Select the add button and choose from the requests for the same resource type.
Unlink a Request
Open the need or the schedule block, find the request under Linked requests, and choose Remove. The link is removed and the request itself is kept. A request with no other links returns to the Translation list. Deleting a schedule block also unlinks its requests, and copying a schedule to another need copies the blocks without their request links.