Difference between revisions of "Problem Records"
Jump to navigation
Jump to search
| (7 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/requests/request-types#problems Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Problem Records|link=https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/requests/request-types#problems]] | ||
| + | <!-- | ||
| + | |||
<div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | <div style="border:1px solid #90C0FF; background:#D0E0FF; width:99%; padding:4px; margin-bottom:10px;"> | ||
__NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Manager Request Types|Requests]] -> Problem Records | __NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Manager Request Types|Requests]] -> Problem Records | ||
| Line 6: | Line 11: | ||
|style="width:73%"| | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
| − | The Problem and Known Error forms are used to | + | The Problem and Known Error forms are used to investigate underlying issues and manage these through to identifying workarounds and eventually resolutions. The available tools help you record information against the Problem / Known Error, communicate with the affected customers, and collaborate with your co-workers. |
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 22: | Line 27: | ||
== Features == | == Features == | ||
| − | === | + | === Process Tracker === |
| − | The | + | The Process Tracker is a graphical representation of the [[Business Process Designer|business process]] that supports the Release process. This is an optional display which uses the stages and checkpoints within a process to visualize the progress. |
| − | * The entire process is displayed as a grey bar with circles representing the different stages | + | :* The entire process is displayed as a grey bar with circles representing the different stages |
| − | * The active stage is represented by a large green circle followed by a connector to the next stage | + | :* The active stage is represented by a large green circle followed by a connector to the next stage |
| − | * The connector will progressively turn green until the next stage is reached | + | :* The connector will progressively turn green until the next stage is reached |
| − | * Checkpoints are displayed below each stage | + | :* Checkpoints are displayed below each stage |
| − | * Grey Checkpoints are yet to be completed | + | :* Grey Checkpoints are yet to be completed |
| − | * Completed Checkpoints are represented with a green check mark | + | :* Completed Checkpoints are represented with a green check mark |
| − | * The | + | :* The Process Tracker shows just the Stages, and when the mouse if moved over the The Process Tracker , the Checkpoints are exposed |
| − | * The | + | :* The Process Tracker can be ''Pinned'' to make the display of the Checkpoints persistent on all Incidents |
=== Request Menu === | === Request Menu === | ||
The request menu is represented by a vertical ellipse button in the top right of the request. The following extra options are available within this menu | The request menu is represented by a vertical ellipse button in the top right of the request. The following extra options are available within this menu | ||
| − | {{bullet1|Copy|The copy options will create an exact copy of the request. By default, copying a request will bring | + | {{bullet1|Copy|The copy options will create an exact copy of the request. By default, copying a request will bring the summary, description, site, priority, category, team, owner, assets, connections, custom fields, documents, attachments, and questions over to the new request. The app setting app.request.copy is available to change these global settings. The workflow associated with the newly created request will start from the beginning of the workflow.}} |
=== Request Notices === | === Request Notices === | ||
[[File:RequestNotice.png|375px|right|link=https://wiki.hornbill.com/images/thumb/f/f9/RequestNotice.png/800px-RequestNotice.png]] | [[File:RequestNotice.png|375px|right|link=https://wiki.hornbill.com/images/thumb/f/f9/RequestNotice.png/800px-RequestNotice.png]] | ||
| − | The Notices provide a way to highlight information about a request. | + | The Notices provide a way to highlight information about a request. You can add notices manually or as part of a [[Service_Manager_Business_Process_Workflow#Request_Notices|workflow]]. There are two types of available; Alerts and Information. These are displayed at the top of the request in order to make them highly visible to anyone viewing the request. |
==== Configure Notices ==== | ==== Configure Notices ==== | ||
| − | The option to Add or Remove notices is available at the top of the Information panel. Clicking this button will | + | The option to Add or Remove notices is available at the top of the Information panel. Clicking this button will provide you with opportunities to add or remove notices. |
{{bullet1|Add a Notice|In the top right of the Configure Notices form, you can click on the + to add a new notice.}} | {{bullet1|Add a Notice|In the top right of the Configure Notices form, you can click on the + to add a new notice.}} | ||
{{bullet2|Notice|Add the text that you would like to display in the notice. This is limited to 255 characters}} | {{bullet2|Notice|Add the text that you would like to display in the notice. This is limited to 255 characters}} | ||
{{bullet2|Type|Select from Alert or Information. Alert Notifications are displayed in red with an '''!''' icon, while Information notices are displayed in blue with an '''i''' icon}} | {{bullet2|Type|Select from Alert or Information. Alert Notifications are displayed in red with an '''!''' icon, while Information notices are displayed in blue with an '''i''' icon}} | ||
| − | {{bullet2|Visibility|Select from Portals, Service Desk or Both from where the notice | + | {{bullet2|Visibility|Select from Portals, Service Desk or Both from where the notice are visable}} |
{{bullet1|Edit a Notice|From the list of active notices, click on the pencil icon to change the text, type, or visibility}} | {{bullet1|Edit a Notice|From the list of active notices, click on the pencil icon to change the text, type, or visibility}} | ||
{{bullet1|Delete a Notice|From the list of active notices, click on the X icon to permanently delete the notice}} | {{bullet1|Delete a Notice|From the list of active notices, click on the X icon to permanently delete the notice}} | ||
| Line 56: | Line 61: | ||
=== Action Bar === | === Action Bar === | ||
{{#ev:youtube|ok7yKRZ6e4U|350|right}} | {{#ev:youtube|ok7yKRZ6e4U|350|right}} | ||
| − | The Action Bar contains | + | The Action Bar contains most functions that you can apply to a Problem / Known Error and is located near the top of the form allowing for quick access to standard features. |
| − | * The available Actions can be either made visible or hidden for different types of Problems, based on the | + | * The available Actions can be either made visible or hidden for different types of Problems, based on the associated service. |
| − | * The supporting Business Process Workflow that sits behind the Problem / Known Error can enforce the | + | * The supporting Business Process Workflow that sits behind the Problem / Known Error can enforce the focus to a specific action when it is required to be completed. |
* Use the Business Process Workflows to lock or unlock action items at any stage in a supporting workflow | * Use the Business Process Workflows to lock or unlock action items at any stage in a supporting workflow | ||
* Global Request Settings control which of these options are enabled when a Problem / Known Error is on-hold | * Global Request Settings control which of these options are enabled when a Problem / Known Error is on-hold | ||
| Line 103: | Line 108: | ||
=== Information Box === | === Information Box === | ||
| − | Located at the top right of the request form, | + | Located at the top right of the request form, it provides information about the request, including the team and person that the request is assigned to, its current status, the Date Raised, and the priority. Service Targets are displayed if the request is under a Service Level Agreement. |
=== Raised By=== | === Raised By=== | ||
| − | When a request is raised, the analyst | + | When a request is raised, the analyst is added to the Raised By collapsable section of the request. This section contains their contact information (Name (Handle), ID (Link to profile), Organisation, Email, Phone, Mobile). |
===Customer=== | ===Customer=== | ||
| − | If a customer is added to the request, a customer collapsable section will be visible on the request containing configurable attributes about the customer. | + | If a customer is added to the request, a customer collapsable section will be visible on the request containing configurable attributes about the customer. The desired attributes are Configured via the [[Request_Settings|request settings]] in the admin console. |
=== Details === | === Details === | ||
| Line 116: | Line 121: | ||
=== Timeline === | === Timeline === | ||
The Timeline keeps track of all the history of the request. Comment and collaborate on any update that has been made. | The Timeline keeps track of all the history of the request. Comment and collaborate on any update that has been made. | ||
| − | * Filter the displayed posts and comments based on the post type, using the '''Filter''' option. | + | * Filter the displayed posts and comments based on the post type, using the '''Filter''' option. Filters are persistent between requests so when a filter is applied it will be available on each request until the filters are removed. |
:* Select one or multiple filters, and the filter will persist when viewing any request. | :* Select one or multiple filters, and the filter will persist when viewing any request. | ||
:* The number of filters applied will be displayed against the filter | :* The number of filters applied will be displayed against the filter | ||
| − | :* Remove the filters by '''unselecting''' the filter options | + | :* Remove the filters by '''unselecting''' the filter options or selecting ''All'' |
| + | {{Infobox|'''Following the Timeline''' [[File:timelinefollow.png|right|300px|link=]] | ||
| + | A '''Follow''' option on the Timeline of a request allows anyone that is supporting the request or is a member of the request to receive Hornbill Notifications each time there is an update to the Timeline. Following a Timeline can only be set by the person who wishes to follow the Timeline}} | ||
=== Members === | === Members === | ||
| − | The Members feature lets you invite people into a request who may not normally have access. Adding a user as a member will notify them that they have been added. Once added they will be able to see the request as if they were part of the team. | + | The Members feature lets you invite people into a request who may not normally have access. Adding a user as a member will notify them that they have been added. Once added they will be able to see the request as if they were part of the team. Members can be added manually, or automatically using the [[Service_Manager_Business_Process_Workflow#Request_Members|Request Members Automation in the process workflow]]. |
| + | |||
| + | This feature can also be used to simply list and identify multiple support staff that are collaborating on the request. | ||
| + | |||
| + | The Request List provides a filter that shows all the requests where you are a member. | ||
| + | |||
| + | {{Infobox|'''Add Member Setting''' | ||
| + | The Advanced Application Setting in Service Manager '''app.requests.addColleagueAsMemberWhenRaising''' will allow you to control if the person raising the request will automatically become a member of the request. This is useful when there are people that are dedicated to only raising requests for particular services, but do not support these services. This will allow them to continue to have access to the requests they raise, without giving them full access to all requests belonging to those services.}} | ||
| + | |||
| + | {{Infobox|'''Notifications''' | ||
| + | Becoming a member of a request does not automatically enroll the user to receive update notifications. Once the user has access to a request through membership, they can choose to ''Follow'' the Timeline of the request to receive notifications.}} | ||
=== Activities === | === Activities === | ||
| − | Activities can consist of Activities that have been automatically created and assigned as part of a BPM workflow | + | Activities can consist of Activities that have been automatically created and assigned as part of a BPM workflow. At any point, a support person can manually add an activity to schedule any work that they are going to do. |
[[Category:Service Manager]][[Category:Videos]] | [[Category:Service Manager]][[Category:Videos]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Latest revision as of 22:12, 18 April 2024
This document can now be found at its new location in the Hornbill Document Library.
