Difficulty: novice
Content
| Table of Contents | ||||
|---|---|---|---|---|
|
Learning Objectives
After reading this article, you’ll be able to:
Know what problemtrees problem trees are
Create/edit problemtypes
Problemtrees
Problemtrees are used within requests to specify the sort of request and assign a treatment group. The problemtreeproblem types
What is a problem tree (= problem type scheme)?
The problem tree can be found in the navigationmenu under Request - > Problem type schemes. It is possible that you find more than one problem type scheme here. By default the problem type scheme with the name problemtree is applicable. To navigate to the problemtypes problem types click on the magnifying glass left from problemtreeproblem tree. This will open the problemtree problem tree used within the current environment:.
ProblemtypesProblem types explained
Within a problemtree problem tree, problem types are specified problemtypes. Examples of problemtypes could be problem types are Facility requests, IT requests etc. Importing these problemtypes can be done These problem types are initially imported using the problemtree import used problem tree import as described in the in the Request SBR (See see Standard requests SBR).
The
problem types should be imported hierarchically, as shown in the screenshot in the
previous chapter. When doing do you will have a parent
problem type with sub
problem types. When selecting the
problem type in requests this will be taken into account.
Note: the main problem type (highest hierarchical level) is also referred to as the ‘Solution group’.
General problem type settings
The general GENERAL settings of problemtypes is simple, they problem types are simple. They can have a parent problemtype problem type (creating the hierarchy), and a name/reference often chosen by the customer:
Aside from some general settings here we also decide the treatment group the request will be assigned to. More on treatment groups in the Standard requests SBR. This allows requests to be assigned to people within the treatment group of the problemtype only.
The Request type decides what kind of request is submitted Information/Wish etc. The priority decided the SLA time for requests.
Concerns
The settings ‘Area category’ and ‘Asset category’ act as a filter. When for example the area category is set on the problem type, users are only allowed to select areas of that category in the request.
Asset, Area and property settings
Within
problem types we can decide how to use property’s, area’s, or assets
Workorders
Workorders. Each of these settings have the following options:
Show
Hide
Required
For example for ‘Property’ this setting will determine if the property field on the request is hidden, shown, or required (so mandatory).
Hoven over the other settings to read what they do.
Work orders
Work orders can be created automatically for specific problemtypes problem types by setting “auto create workorder” to yes. For these workorders we can select a standard treatment groups and a role. Roles are created by the clients and are used as a lable (e.g. “Cleaning” or “Maintenance”). Roles can be created in the navigationMenu under Requests - Roles. The role will determine if a preferred supplier is linked and will submit the request to them. More on preferred suppliers in Preferred suppliers.
| Info |
|---|
We have not explained all settings in detail in this article. Hover over the settings to get a detailed instruction. |
Adding problem types
Adding a new problem type
To add a new problem type:
Navigate to Request > Problem type schemes
Click on the magnifying glass in front of the problem type scheme with the name ‘problemtype’
Click ‘New', and fill in the fields.
Note: if this is a sub problem type, don't forget to fill in the ‘Parent’ field !
Summary
| Rw ui textbox macro |
|---|
|
Search
| Live Search |
|---|