How to give assignee groups their own templates and defaults
On this page
A ticket that a Create Action creates starts with the values of that action's own template. An administrator who wants tickets of one kind to land with one team gives that team its own template: a template that sets the Assignee Group field, and any other values the team's tickets should start with. The template is then applied through a Create Action. All of the setup is done in the Settings App.
Before you begin
- To sign in to the Settings App, your account needs the Basic Administrative Access permission. A ticket class's node, with its Workflow node, also needs that class's business-logic right, which the role editor lists under Business Logic Management. See Work in the Settings App and Permissions Reference.
- The group must exist. The list of assignee groups on a ticket offers only active technicians-only groups; see Persons and Groups.
Open the ticket class's templates
Templates belong to one object class. Assignee Group is a field of each of the five ticket classes: Work Order, Incident, Problem, Change Request, and Service Request.
- In the Settings App, open the ticket class's Workflow node, under the class in its business area.
- In the workflow tree, open Components > Templates.
- Click New to open an empty Template window, or select a template and click Edit (or double-click it, or press Enter) to change it. Copy Item copies the selected template and opens the copy.
Set the assignee group in the template
The Template window's General page has Name:, Description:, and a Fields group with the field grid.
- In Name:, enter a name that no other template of the same class uses, whatever its capitalization.
- In the Fields group, click New (or press Insert). An empty row is added.
- In Field Name, pick Assignee Group.
- In Value, choose the group. A lookup field's value cell takes the lookup's own editor.
- Add a row in the same way for each other field that the group's tickets should start with. To remove a row, select it and click Delete (or press Delete).
- Click OK to save the template and close the window.
The template cannot be saved while any row's value is empty: saving is refused with "Field values can't be blank." and that row is selected. A name already in use is refused with "This Name is already in use. Please use a different one."
Repeat these steps for each assignee group that should have its own template. For the value editors of other field types, see Value editors.
Apply the template through a Create Action
When a Create Action creates a record, the record starts with the values of that action's own template.
- In the same workflow tree, select Create Actions and click New, or select a Create Action and click Edit. For the fields of a new Create Action, see Create or edit a Create Action.
- On the Template tab, choose the group's template. Its values are applied when the ticket is created.
- To limit who may run the action, choose the roles on the Condition tab; see Restrict an action to roles. The Condition tab is hidden on Service Requests.
- Click OK.
The Template: list of a Create Action offers the reusable templates of the class. Make Custom detaches the chosen template into a definition of this action's own, keeping its field values; Make Reusable saves the current fields as a new reusable template under a name you enter.
Check which actions use a template
The Usage page of the Template window lists the workflow items and functions that use the template, and Open opens the editor of the selected one. A template that a workflow item refers to cannot be deleted: deleting it is refused, and the template's editor opens on its Usage tab.
Result
Each assignee group now has a template that sets it as the assignee group of a new ticket, and Create Actions apply those templates. In the Web App, a technician sees a Create Action through the action's role grants and the Create permission on the class; a Create Action with no role grant reaches everyone, and only enabled actions are offered. Each action's own condition narrows the list further. A ticket created with the action starts with the group and the other values of its template. For how a technician starts a Create Action from a list, see Create a record with New.
Related topics
- Templates and Defaults - edit templates, their field values, and the value editors.
- Actions - set up the Create Actions that apply templates.
- Persons and Groups - maintain the groups that tickets are assigned to.