Difference between revisions of "Services Request Configuration"
Jump to navigation
Jump to search
| (3 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/request-configuration Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Request Configuration|link=https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/request-configuration]] | ||
| + | <!-- | ||
| + | |||
| + | |||
<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 Portfolio]] > [[Service Details]] > Services Request Configuration | __NOTOC__[[Main Page|Home]] > [[Service Manager]] > [[Service Portfolio]] > [[Service Details]] > Services Request Configuration | ||
| Line 22: | Line 28: | ||
== [[File:IncidentIcon.png |25px|link=|Incident]] Incident == | == [[File:IncidentIcon.png |25px|link=|Incident]] Incident == | ||
<div style="width:73%"> | <div style="width:73%"> | ||
| − | + | ===Incident Configuration=== | |
<div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More"> | <div class="mw-collapsible mw-collapsed" data-collapsetext="Show Less" data-expandtext="Read More"> | ||
::Setup and configure Incident Management for this Service. | ::Setup and configure Incident Management for this Service. | ||
| Line 58: | Line 64: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 111: | Line 118: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 157: | Line 165: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 200: | Line 209: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 250: | Line 260: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 299: | Line 310: | ||
[[File:Service_Categories.png|right|500px|Link=]] | [[File:Service_Categories.png|right|500px|Link=]] | ||
:: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | :: Define which logging and resolution categories are available per request type per service. It is possible to configure which level of the category tree will be the starting level (exposed) when choosing a category on a request, either using Progressive Capture or on the Request Details from. If a Category Level is not selected, the root of the category tree will be used. | ||
| + | ::'''Note:''' If the Category Level is filtered to the last level on a branch, no Categories will be visible for selection. | ||
<BR> | <BR> | ||
</div> | </div> | ||
| Line 310: | Line 322: | ||
:: The Request Sub-statuses lets you define a number of descriptive states of a request that are related to the request being either Active or On-hold. Using a Sub-status can help control the situations under which a request is put On-hold or made Active again. An example of an On-hold Sub-status might be ''With Customer'' which when selected could place the request's status to On-hold and stop any allocated Service Level Target timers. | :: The Request Sub-statuses lets you define a number of descriptive states of a request that are related to the request being either Active or On-hold. Using a Sub-status can help control the situations under which a request is put On-hold or made Active again. An example of an On-hold Sub-status might be ''With Customer'' which when selected could place the request's status to On-hold and stop any allocated Service Level Target timers. | ||
</div> | </div> | ||
| + | [[Category:Service Manager]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Latest revision as of 21:50, 22 April 2024
This document can now be found at its new location in the Hornbill Document Library.
