Difference between revisions of "Routing Rule Templates"
Jump to navigation
Jump to search
| (37 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| + | This document can now be found at its new location in the [https://docs.hornbill.com/servicemanager-config/email/routing-rule-templates/ Hornbill Document Library]. | ||
| + | |||
| + | [[file:hornbill-document-library.png|Routing Rule Templates|link=https://docs.hornbill.com/servicemanager-config/email/routing-rule-templates/]] | ||
| + | <!-- | ||
<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]] > [[Administration]] > [[Service Manager Administration |Service Manager]] > Email > Routing Rule Templates | + | __NOTOC__ |
| + | {| style="width:100%" | ||
| + | |[[Main Page|Home]] > [[Administration]] > [[Service Manager Administration |Service Manager]] > Email > Routing Rule Templates | ||
| + | |style="text-align:right;"|[[:Category:Service Manager Administration|Index]] | ||
| + | |} | ||
</div> | </div> | ||
{|style="width: 100%" | {|style="width: 100%" | ||
| Line 6: | Line 14: | ||
|style="width:73%"| | |style="width:73%"| | ||
== Introduction == | == Introduction == | ||
| − | The Routing Rule Templates provide a way to define default settings for requests that are automatically raised from emails using the Routing Rules. | + | The Routing Rule Templates provide a way to define default settings for requests that are automatically raised from emails using the Email Routing Rules. An unlimited number of Routing Rule Templates can be created. Each Email Routing Rule can link to a single Routing Rule Template. A single Routing Rule Template can be used by multiple Email Routing Rules. |
|style="width:5%"| | |style="width:5%"| | ||
| | | | ||
| Line 16: | Line 24: | ||
== Template Options == | == Template Options == | ||
| − | + | {{#ev:youtube|GR28a72yITw|300|right}} | |
| − | * Name | + | [[File:routingruletemplate.png |thumb|link=https://wiki.hornbill.com/images/8/8e/Routingruletemplate.png|300px|Routing Rule Template Form]] |
| − | * Description | + | Each Template provides a number of options to define the default settings for the requests that are raised from an email routing rule. |
| − | * Request Type | + | ::* '''Name''' |
| − | * Service | + | ::: The Name is used for both providing a reference in the list of Routing Rule Templates and for selecting the routing rule template when defining a Email Routing Rule when the '''raiseNewRequest''' operation is used. |
| − | * Catalog Item | + | ::* '''Description''' |
| − | * Team | + | ::: An optional description of the Routing Rule Template can be provided to help others that have access to this list understand the purpose of the template. |
| − | * Priority | + | ::* '''Request Type''' |
| − | * Assets | + | ::: Available request types include Incident and Service Request. This is a mandatory option. The selected option will result in that type of request being raised. |
| + | ::* '''Service''' | ||
| + | ::: All the defined services that have a status of ''Catalog'' are available within this list. Despite this being an optional field, using Services is highly recommended. | ||
| + | ::* '''Catalog Item''' | ||
| + | ::: The Catalog Item option is only available if a service has been selected and that service has available Request Catalog Items | ||
| + | ::* '''Team''' | ||
| + | ::: Select a Team that this request will be assigned to. Keep in mind that a BPM Workflow can also be used for automating the Team assignments. If a Service has not been selected, all teams will be available to select from. If a service has been selected in the Service field, only the teams that support that Service will be available. | ||
| + | ::* '''Priority''' | ||
| + | ::: Allows for the initial priority to be set for the request. Keep in mind that the a BPM Workflow can also be used for automating the Priority. | ||
| + | ::* '''Assets''' | ||
| + | ::: One or more assets can be selected. These assets will be associated to the request and available within the Assets section of the request | ||
| + | ::* '''Add Attachments''' | ||
| + | ::: This option determines whether attachments sent on an incoming email are added to the request as attachments for display within the request's 'Attachments' section. | ||
== Routing Rule Operations == | == Routing Rule Operations == | ||
| − | Service Manager provides a number of Routing Rule Operations that can be selected when configuring the system [[Email Routing Rules]]. | + | [[File:routingrule.png|thumb|300px|link=https://wiki.hornbill.com/images/0/0c/Routingrule.png|Email Routing Rule Form]] |
| + | Service Manager provides a number of Routing Rule Operations that can be selected when configuring the system [[Email Routing Rules]]. The Routing Rule Templates are only available to the '''raiseNewRequest''' operation. | ||
::* '''raiseNewRequest''' | ::* '''raiseNewRequest''' | ||
| − | ::: This operation must be used if you wish to use the Routing Rule Templates. When this operation is selected an option is made available select the Routing Rule Template that you wish to use when that Email Routing Rule is met. | + | ::: This operation must be used if you wish to use the Routing Rule Templates. When this operation is selected on an Email Routing Rule, an option is made available to select the Routing Rule Template that you wish to use when that Email Routing Rule is met. |
| + | ::* '''updateRequest''' | ||
| + | ::: This operation does not use Routing Rule templates. This uses the default application settings to set the requests' initial settings | ||
::* '''logOrUpdateIncident''' | ::* '''logOrUpdateIncident''' | ||
::: This operation does not use Routing Rule templates. This uses the default application settings to set the requests' initial settings | ::: This operation does not use Routing Rule templates. This uses the default application settings to set the requests' initial settings | ||
| Line 36: | Line 59: | ||
::: This operation does not use Routing Rule templates. This uses the default application settings to set the requests' initial settings | ::: This operation does not use Routing Rule templates. This uses the default application settings to set the requests' initial settings | ||
| − | [[Category: | + | == Attachments == |
| + | Attachments can be automatically added to the request attachments section using the following operations. | ||
| + | |||
| + | ::* '''raiseNewRequest''' | ||
| + | ::: When this operation is selected on an Email Routing Rule, the option to enable/disable the adding of attachments is available on the Routing Rule Template that you wish to use when that Email Routing Rule is met. | ||
| + | ::* '''updateRequest''' | ||
| + | ::: This operation does not use Routing Rule templates. This uses four application settings to control the adding of attachments for Incidents, Service Requests, Changes and Problem Records | ||
| + | |||
| + | ::::* '''app.email.routing.rules.update.addAttachments.IN''' | ||
| + | ::::* '''app.email.routing.rules.update.addAttachments.SR''' | ||
| + | ::::* '''app.email.routing.rules.update.addAttachments.CH''' | ||
| + | ::::* '''app.email.routing.rules.update.addAttachments.PM''' | ||
| + | --> | ||
| + | [[Category:HDOC]] | ||
| + | <!-- service-manager-config/email/routing-rule-templates --> | ||
Latest revision as of 23:41, 9 February 2024
This document can now be found at its new location in the Hornbill Document Library.
