Difference between revisions of "Service Dependancies"
Jump to navigation
Jump to search
| (3 intermediate revisions by one other user 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/services/service-dependancies Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Service Dependancies|link=https://docs.hornbill.com/servicemanager-user-guide/service-portfolio/services/service-dependancies]] | ||
| + | <!-- | ||
<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;"> | ||
| Line 20: | Line 24: | ||
==Relating Services== | ==Relating Services== | ||
[[File:Service_Dependancies.png|800px|right]] | [[File:Service_Dependancies.png|800px|right]] | ||
| + | |||
| + | Use the '''+''' icon to begin the process of relating services: | ||
Use the following filters to find the services to associate: | Use the following filters to find the services to associate: | ||
| Line 38: | Line 44: | ||
xxx = The name of the service you are viewing when relating other services to it. | xxx = The name of the service you are viewing when relating other services to it. | ||
| + | |||
| + | Once services are related and dependencies configured, you can edit or remove the dependencies by using the '''Action''' icons next to each related service. | ||
==Utilise Service Dependancies== | ==Utilise Service Dependancies== | ||
| − | Via the business process designer, it is possible in workflows to automate the adding or related services to a request, by leveraging the defined dependencies to the request service. A use case is to automatically associate all business services to a change or problem record, based on the technical service the change or problem record is raised against | + | Via the business process designer '''(Under Requests > Request Services)''', it is possible in workflows to automate the adding or related services to a request, by leveraging the defined dependencies to the request service. A use case is to automatically associate all business services to a change or problem record, based on the technical service the change or problem record is raised against |
| − | |||
| + | It is also possible to automatically update the status of related services, through the business process designer '''(Under Request > Services)'''. In the workflow of a request, you can leverage the dependencies between services and only update the services status of services related of specific '''dependency''' types to the request service. A use case is to automatically update the status of business services related to the request technical service, which in turn would be visible to subscribed users of the business services, notifying them that, the service is impacted by an issue. | ||
==Launch Explorer (Configuration Manager Plugin)== | ==Launch Explorer (Configuration Manager Plugin)== | ||
| Line 51: | Line 59: | ||
[[category:Service Manager]] | [[category:Service Manager]] | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
Latest revision as of 18:23, 30 April 2024
This document can now be found at its new location in the Hornbill Document Library.
