Requests

A request is how one area asks another for something. A work order asks for stock, a portal request asks for work, an inspection asks for a charge. The record that asks keeps the request under it, and the area asked sees it on its Demand list until someone answers it.

Raising a request

On a saved record, open ⋯ › Request….

1. Ask picks what you need: Stock, Work, A charge or A permit. The list holds the areas your organization has.
2. Fill in what that area needs to know:
   • Stock: the Class, How much, the Unit and where it Lands at. Left blank, the people on the asking record collect it.
   • Work: What, the Details and the Kind of work.
   • A charge: the Fee schedule, the Payer and Why.
   • A permit: the Permit type, the Applicant and Why.
3. Set Needed by and add a Note if it helps.
4. Save.

An administrator changes what each kind of request asks on the Forms page.

Following a request

The request shows as a row under the asking record, in the Requests row of its tree. Each one shows what was asked, Needed by and its state:

• Open: waiting for an answer;
• Answered: another area answered it with a record. The row names that record and opens it;
• Closed: finished or withdrawn.

A row's ⋯ opens each answer, and Change… or Close the request while it is open. The person who raised it and the people who manage the area asked can change or close it.

My requests, on your home page, lists the open requests on records you raised or are assigned to.

Answering a request

Each area that answers requests has a Supply · Demand switch at the top of its list page. Demand lists the open requests asked of that area, newest first, with urgent ones first. A row shows what was asked, the record that asked, its priority, its note and Needed by.

The answer control sits on the row, in that area's terms:

• Assets and inventory: Authorize…: how much someone may pick up, and from where; Create incident… and Create asset… for a request about an asset;
• Charges: Answer with a charge…
• Permits: Answer with a permit…

The answer links to the request. When the answering record finishes, the request closes on its own.

Requests to an outside system

Where your organization keeps assets, work or charges in another system, a Master system connection in Automations sends each request for that area there. The request reads Sent to the system until the system answers it. Its answer shows on the request beside the connection's name.