Layton ServiceDesk - Settings - Libraries - Request Types

From Layton Support
Revision as of 21:25, 26 June 2013 by Tscholl (Talk | contribs)

Jump to: navigation, search

Btn back up.png Back to Contents

Previous article in this series: Request Classes

Request Types are used to categorize or group Requests and Problems based on user-defined settings. They are used as the basis for assigning individual Analysts and Groups according to Skills and they also link to the Solutions Base.

In a new request form, the Request Types can either appear as a tree structure with no limit to the number of levels or as interdependent drop-down lists (To configure, follow these steps). Any level in the structure can be used when logging a Request or Problem. For example, a Request Type could be specified as PC Hardware Fault only or a specific problem within PC Hardware Fault structure, such as CD Drive Failure.

Request Type configuration screen

Request Types can also be linked to Request Classes where only certain Request Types will be displayed or made available to a Request Class or form selected. So careful thought must used to define the Request Type structure that will support your particular business and operations.

To set up Request Types go to Administration > Libraries > Request Types. Then simply select the Request Type or name at the tree level above the level you require to insert a Request Type and click the Add New button. A new sub level can then be defined. To create a new top level Request Type click on the Request Type name at the top of the tree structure and click the Add New button. To edit an existing Request Type simply click on the Request Type and the options will be displayed.

To relocate a Request Type within the tree structure, simply drag the request type to the desired parent location. You will then be given the option of making the Request Type a Sub-Category of the parent request type or merging it. When defining a Request Type you can specify a default Priority to place against it. For example, you might want to define a Request Type such as Server Down. This might be a high priority Request Type, so you can specify a Priority to put against it. This means that when selected on a Request the Request Type Priority will be applied to that Request where the specific Request Type is chosen. Note: this will override the default system priority. You can also define a Site or Department Manager or specific Analyst responsible for a particular Request Type. The Request will be automatically assigned on this basis and will override any other assignment rules (except for any Business Rules). For example, a certain type of Service Request may have to be authorized by a manager before being assigned based on skills.

A Request can be defined as an Incident which means the Request will be automatically measured against the ServiceDesk available time. The Request Statistics by Incident Report will show the downtime as a percentage of the available time. This is useful for measuring availability of business critical Hardware or Software Systems.

To display Request Types as interdependent drop down lists instead of the tree view when processing Requests, the Request Type field is simply added to the Request Form, using Form Design and adding the sys_requesttype_id, as many times as there are levels in the structure. Then, by selecting a category from the top level drop down list only the sub categories of that category will appear in the next drop down list. (This is configured in Form Design by adding a single sys_requesttype_id for tree view or adding multiple sys_requesttype_id to display drop-down lists.)

If using Analyst Skills or Manage Analyst Group to prompt for assignment, once the Request Types are completed, the Skills to the appropriate Analysts or Groups may be added.

Also, remember the Request types are used as the main or automatic link to identify a Solution within the Solutions Base.

Next article in this series: Request Statuses

Btn back up.png Back to Contents

Personal tools
Namespaces

Variants
Actions
Main Page
Online User Guides
General Support
Release Notes
Toolbox