Request templates

Reusable blueprints for common request patterns — duration, timing constraints, and pre-set criteria in one definition.

Published

Settings → Templates — “Create reusable templates for common utilization request patterns. Templates define duration and timing constraints that can be applied to new requests.” If your operation schedules the same shapes of work repeatedly — a standard maintenance slot, a weekly production run — templates make each new request start correct instead of blank.

Creating a template

Add Template opens Create Request Template:

  • Name — e.g. Standard Week, Long Project.
  • Description — optional context.
  • Minimal Duration — a number plus a unit (Minutes, Hours, Days, Weeks, Months, Years). Requests created from the template inherit it; placements shorter than the minimum raise a Below Minimum Duration conflict.
  • Needs — the resource types a request made from the template requires, one resource per type. A template that names a type can serve as an operation in a routing. Types that hold people are not offered. People are added on the request.
  • Criteria — pre-set values from your criteria vocabulary. Pick a criterion, set its value, and it ships with every request the template spawns — “No criteria added yet. Add criteria to define values for this template.” until you do.

Managing templates

The list shows Name, Duration, Description, and Created; sort and filter from the column headers, like every list in Orkyo. Edit freely — changes affect future requests created from the template, not requests already spawned. Deleting asks for confirmation (“This action cannot be undone.”) and likewise leaves existing requests untouched. A template that a routing uses as an operation can not be deleted until the routing releases it.

Templates in the flow

  • Creating a request from a template pre-fills duration, resource types, and requirement values. The intake form becomes a confirmation step rather than a data-entry session. A template with no resource types leaves the request’s own choice alone.
  • A routing step names a template as its operation. The times on the step are the part’s. The template carries what the operation needs.
  • Templates travel: Export/Import move them as CSV or JSON (Import and export), and Presets bundle them with criteria and groups.

For the workflow view — building a template and spawning consistent requests from it — see Speed up intake with request templates.