Template management

Walkthrough goes here.

A template is a standard set of services tied to a context. Attach it to a location, a group or a department, and anyone who lands in that context receives the set without a request being written for it.

This is where you build and maintain those sets centrally. The template itself lives here, under Offer management. Where it applies is decided on the location or the group it is attached to.

Two properties are worth knowing before you build your first one. A template proposes rather than dictates: when someone is assigned, the services come preselected and anything they do not need can be unchecked. And it prepares rather than orders. The items go into approvals like any other request, so the usual decision still happens.

The free stock option is the one that pays for itself. With it switched on, existing stock at the site is used before a new order is triggered, then pre-ordered goods, and only then something new. That is exactly the situation where returned devices otherwise sit in a warehouse while identical ones are being bought.

The moment to build one is when you catch yourself assigning the same three or four things to every new starter.

Read more

Template managementAutomated Service Assignment with Templates

Next

Not everything runs on a template. For everything else: Assign services centrally.