<style> .chartjs-size-monitor { display: none !important; height: 0 !important; overflow: hidden !important; }p { margin: 0; }span.fr-emoticon.fr-emoticon-img { background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle; } span.fr-emoticon { font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0; } blockquote { border-left: solid 2px #5e35b1; color: #5e35b1; margin-left:0; padding-left:5px;}blockquote blockquote{ border-color: #00bcd4; color: #00bcd4;}blockquote blockquote blockquote{ border-color: #43a047; color: #43a047;} table.grid{ border-collapse: collapse;} table.grid td, table.grid th { border: 1px solid #ddd;} .fr-fic.fr-dib{ display: block; margin: 5px auto;}.fr-fic.fr-dib.fr-fir{ text-align: right; margin: 5px 0 5px auto;}.fr-fic.fr-dib.fr-fil{ text-align: left; margin: 5px auto 5px 0;}.fr-fic.fr-dii{ float: none; margin: 5px auto;}.fr-fic.fr-dii.fr-fil{ float: left; margin: 5px auto;}.fr-fic.fr-dii.fr-fir{ float: right; margin: 5px auto;}img.fr-dib.fr-fir { margin-right: 0; text-align: right;}img.fr-dib.fr-fil { margin-left: 0; text-align: left;}img.fr-dib { margin: 5px auto; display: block; float: none;}img.fr-bordered { box-sizing: content-box; border: solid 5px #CCC;}img.fr-shadow { box-shadow: 10px 10px 5px 0px #cccccc;}img.fr-rounded { border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;}</style><style>
.chartjs-size-monitor {
display: none !important; height: 0 !important; overflow: hidden !important;
}
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><style>
.chartjs-size-monitor {
display: none !important; height: 0 !important; overflow: hidden !important;
}
p {
margin: 0;
}
span.fr-emoticon.fr-emoticon-img {
background-repeat: no-repeat !important; font-size: inherit; height: 1em; width: 1em; min-height: 20px; min-width: 20px; display: inline-block; margin: -0.1em 0.1em 0.1em; line-height: 1; vertical-align: middle;
}
span.fr-emoticon {
font-weight: normal; font-family: "Apple Color Emoji", "Segoe UI Emoji", "NotoColorEmoji", "Segoe UI Symbol", "Android Emoji", "EmojiSymbols"; display: inline; line-height: 0;
}
blockquote {
border-left: solid 2px #5e35b1; color: #5e35b1; margin-left: 0; padding-left: 5px;
}
blockquote blockquote {
border-color: #00bcd4; color: #00bcd4;
}
blockquote blockquote blockquote {
border-color: #43a047; color: #43a047;
}
table.grid {
border-collapse: collapse;
}
table.grid td,
table.grid th {
border: 1px solid #ddd;
}
.fr-fic.fr-dib {
display: block; margin: 5px auto;
}
.fr-fic.fr-dib.fr-fir {
text-align: right; margin: 5px 0 5px auto;
}
.fr-fic.fr-dib.fr-fil {
text-align: left; margin: 5px auto 5px 0;
}
.fr-fic.fr-dii {
float: none; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fil {
float: left; margin: 5px auto;
}
.fr-fic.fr-dii.fr-fir {
float: right; margin: 5px auto;
}
img.fr-dib.fr-fir {
margin-right: 0; text-align: right;
}
img.fr-dib.fr-fil {
margin-left: 0; text-align: left;
}
img.fr-dib {
margin: 5px auto; display: block; float: none;
}
img.fr-bordered {
box-sizing: content-box; border: solid 5px #CCC;
}
img.fr-shadow {
box-shadow: 10px 10px 5px 0px #cccccc;
}
img.fr-rounded {
border-radius: 10px; -moz-border-radius: 10px; -webkit-border-radius: 10px; -moz-background-clip: padding; -webkit-background-clip: padding-box; background-clip: padding-box;
}
</style><p><strong>In this guide we will cover:</strong></p><p data-pasted="true"><a href="#TOM-in-the-CMDB"><strong>- TOM in the CMDB</strong></a></p><p><a href="#TOM-in-Action---Automated-Assignment-and-Escalation"><strong>- TOM in Action - Automated Assignment and Escalation</strong></a></p><p><a href="#Adding-TOM-Tables-to-the-CMDB"><strong>- Adding TOM Tables to the CMDB</strong></a></p><p><a href="#Populating-TOM-Tables"><strong>- Populating TOM Tables </strong></a></p><p><a href="#Building-TOM-Based-Assignment"><strong>- Building TOM Based Assignment</strong></a></p><p><a href="#Building-TOM-assignment-automation-for-other-Processes"><strong>- Building TOM assignment automation for other Processes</strong></a></p><p><a href="#Create-Escalate-Action--Optional-"><strong>- Create Escalate Action (Optional)</strong></a></p><p><br></p><p><br></p><p data-pasted="true"><strong><span style="font-size: 14pt;">TOM in the CMDB<a id="TOM-in-the-CMDB" class="fr-anchor" title="TOM-in-the-CMDB"></a></span></strong></p><p data-pasted="true">A target operating model (TOM) defines how your organisation intends to deliver and support its services, setting out clear ownership, accountability and responsibilities across teams. This establishes who supports each service and who is ultimately accountable for it. A TOM removes ambiguity from service delivery and ensures that decisions, escalations and changes are handled by the right people. Translating into faster incident resolution, stronger governance and reduced operational risk, as well as a clearer audit trail for compliance purposes.</p><p><br></p><p>In Halo, a target operating model can be stored against each configuration item in your CMDB. This gives you a clear record of who is responsible for supporting the service and who holds overall accountability for it. These records can then be used to inform assignment automations, automatically assigning tickets raised against this service to the appropriate team. As well as outlining the path of escalation to agents. </p><p><br></p><p><strong><span style="font-size: 14pt;">TOM in Action - Automated Assignment and Escalation<a id="TOM-in-Action---Automated-Assignment-and-Escalation" class="fr-anchor" title="TOM-in-Action---Automated-Assignment-and-Escalation"></a></span></strong></p><p>Halo can automatically assign tickets as soon as they are logged to the correct team, based on the configuration item the incident/problem/request has been raised for and the TOM associated with that configuration item. Lets see this in action. </p><p><br></p><p>In this example an incident has been raised associated with the "Workday PROD" business app instance. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImE1ZGQzODFmLTkzOGMtNDExYS1iNjdjLTJkZjEzMzhkNzM2MyJ9.fNxKE0E5E-sC1JREFVuIAhKhfxu0rLQ9qdVdGZ3IUP4" class="fr-fic fr-fil fr-dib" width="1635" style="width: 1637px; height: 788.482px;" height="788"></p><p><strong><span style="font-size: 10pt;">Fig 1. Incident raised for CI </span></strong></p><p><br></p><p>This configuration item has two TOM tables configured, which outline who (which team) has operational responsibility for this service, and who has ownership/accountability for this service. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImFkYzY1ZGFkLWRmZjAtNDZlMC1iMjQxLWNmMWYzZjc1YTI1ZiJ9.eHqkhZ7t55aVYvAzhZrXgoEr4hHVcef-X3Nwvb9rB00" class="fr-fic fr-fil fr-dib" width="1953" style="width: 1955px; height: 589.741px;" height="590"></p><p><strong><span style="font-size: 10pt;">Fig 2. TOM tables against a business application</span></strong></p><p><br></p><p>The operational table will inform the assignment and escalation path for incidents, problems, requests etc. where Workday PROD is the primary CI. </p><p><br></p><p>When an incident ticket is logged it will automatically be assigned to the 1st Line Support team, as this team have the "Level 1 Support" operational role for any incidents raised for this CI. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdjODBlNTVmLTAyMjctNGJiMS1iZjEyLTFiYTBmNGFhODQ1OSJ9.DQCFkEq3KTskyPVC97RSxZFCrPDsU_q2sl0MCCRf8Wk" class="fr-fic fr-fil fr-dib" width="1602" style="width: 1604px; height: 821.812px;" height="822"></p><p><strong><span style="font-size: 10pt;">Fig 3. Ticket automatically assigned to the correct team</span></strong></p><p><br></p><p>The escalation path will also be visible on the ticket. Showing the team which has the next level of operational role for incidents. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImFhZWE1NzEyLWNmOTYtNGU1Zi1hYjkyLWVkODU0NWM2ODQwYyJ9.gARgaujW-AbJfXyNpD-zVmK9U_xqY2fZpluwO7RjnTg" class="fr-fic fr-fil fr-dib" width="1603" style="width: 1605px; height: 822.324px;" height="822"></p><p><strong><span style="font-size: 10pt;">Fig 4. Escalation Path </span></strong></p><p><br></p><p>Escalation can also be automated, if desired, to have the ticket automatically assigned in line with the escalation path associated with the CIs TOM. Escalation is triggered using an action.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQzMTk4NzEwLWVlNzgtNGNkYS1hZTk0LTM2OTNjM2U2YjgyMSJ9.NiH_RU6YfzNIYeIE5_EcrB25Kfe9sarn8_2rfofPtm8" class="fr-fic fr-fil fr-dib" width="1579" style="width: 1581px; height: 802.352px;" height="802"></p><p><strong><span style="font-size: 10pt;">Fig 5. Escalate Ticket based on TOM</span></strong></p><p><br></p><p>When this escalation action is used the ticket will be re-assigned to a team in line with the TOM. Using the Figure 2 example, the ticket will be re-assigned to the "2nd Line Support" team as they have the "Level 2 Support" operational role, then to the "Infrastructure" team as they have the "Level 3 Support" operational role in this TOM. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM5NTMzMzFiLWM2YmQtNGUxMy1iNzE0LTI3MzkwZmNlNWE5ZSJ9.cn_65GfzkNW27ecDITBS7mmwqCVaTZswMhXdSr2ezhg" class="fr-fic fr-fil fr-dib" width="1585" style="width: 1587px; height: 804.041px;" height="804"></p><p><strong><span style="font-size: 10pt;">Fig 6. Ticket escalated in line with TOM</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Adding TOM Tables to the CMDB<a id="Adding-TOM-Tables-to-the-CMDB" class="fr-anchor" title="Adding-TOM-Tables-to-the-CMDB"></a></span></strong></p><p>TOM tables will be pre-built into instances of Halo deployed for ITSM/ESM teams, deployed after September 2026. If this is pre-built, minimal steps need to be taken to get this up and running in your instance.</p><p><br></p><p>If TOM tables and automations are pre-built into your instance you will just need to enable TOM tables for each of your CI types, jump to the section "Show the TOM tab on CIs"</p><p><br></p><p>If this is not pre-built into your instance, the next section will outline how to build this in. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Building TOM Tables - For instances with no pre-built functionality</span></strong></p><p data-pasted="true">If TOM tables are not pre-built into your instance you will need to create some custom fields, tables and a tab to store the TOM data. </p><p><br></p><p><strong>Create Custom Tables</strong></p><p>Create a table named "TOMProcesses" not linked to an entity. The table should have the following field:</p><ul><li>Name= TOMProcesses, Type of field =Text</li></ul><p>Then add the data values shown in Figure 7 to the table.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjZlYjgyMjhkLTZmZDgtNDY1YS1iZjkwLTlhZmU5Y2ViZWUzOSJ9.DGW5sNle6FkgnhVhxxCP0KjlViHtmJKPCY1LY916AKw" class="fr-fic fr-fil fr-dib" width="1675" style="width: 1677px; height: 440.627px;" height="441"></p><p><strong><span style="font-size: 10pt;">Fig 7. Data within TOM Processes Table </span></strong></p><p><br></p><p>Create a Table named "TOMOperationalRoles" not linked to an entity. The table should have the following fields. </p><ul><li>Name= TOMOperationProcess, Type of field = single select, Lookup Type= Dynamic List, sql script= <ul><li><em>select top 100 percent </em><em>CTTOMProcessesid as [ID], </em><em>CFTOMProcesses as [Display] </em><em>from CTTOMProcesses Order by CTTOMProcessesid</em></li></ul></li><li>Name = TOMOperationalRole, Type of field = Text</li></ul><p data-pasted="true">Then add the data values shown in Figure 8 to the table.<br><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQ2YmMzNmMzLTdjYTctNDI2OS05NmIwLWY4MmRkNDMxZjNjZiJ9.HBAskbmsk_1ELSCg--l_LRr6g_YhVMCO0skntZoE7nQ" class="fr-fic fr-fil fr-dib" width="1677" style="width: 1679px; height: 647.846px;" height="648"></p><p><strong><span style="font-size: 10pt;">Fig 8. Data within Operational Roles table</span></strong></p><p><br></p><p><strong><em>Note: The data added can be customised in line with the operational role that should be available for each process. You may have more/less operational roles applicable to each process.</em></strong></p><p><br></p><p>Create a Table named "TOMOperational" linked to the Asset entity, with "Create a Custom Field for this table" enabled. The table should have the following fields.</p><ul><li>Name = TOMProcessesCI, Type of field = single select, Lookup Type= Dynamic List<ul><li>sql script=<em> select top 100 percent CTTOMProcessesid as [ID], CFTOMProcesses as [Display] from CTTOMProcesses Order by CTTOMProcessesid</em></li></ul></li><li>Name= TOMORole, Type of field = single select, Lookup Type= Dynamic List<ul><li>sql script = <em>select CTTOMOperationalRolesid as [ID], CFTOMOperationalRole as [Display] from CTTOMOperationalRoles where CFTOMOperationProcess = $CFTOMProcessesCI</em></li></ul></li><li><em>Name = TOMOTeamGroup, Type of field = single select, Lookup Type= Dynamic List</em><ul><li><em>sql script= </em><em>SELECT top 100 percent [ID], [Display]FROM (SELECT 10000 + sdid AS [ID], sdsectionname AS [Display]FROM sectiondetailwhere case when (select CFTOMOperationalRole from CTTOMOperationalRoles where CTTOMOperationalRolesID= $CFTOMORole ) not like '%Approval%' then 1 else 0 end = 1 and sdinactive=0 UNION SELECT BHID AS [ID], bhdesc + ' (CAB)' AS [Display]FROM cabheaderwhere case when (select CFTOMOperationalRole from CTTOMOperationalRoles where CTTOMOperationalRolesID= $CFTOMORole ) like '%Approval%' then 1 else 0 end = 1 UNION SELECT 20000 + cnum AS [ID], cdesc AS [Display]FROM companywhere case when (select CFTOMOperationalRole from CTTOMOperationalRoles where CTTOMOperationalRolesID= $CFTOMORole ) not like '%Approval%' then 1 else 0 end = 1) AS Combined ORDER BY [ID] ASC</em></li></ul></li></ul><p><br></p><p data-pasted="true">Create a Table named "TOMAccountable" linked to the Asset entity, with "Create a Custom Field for this table" enabled. The table should have the following fields:</p><ul data-pasted="true"><li>Name =TOMAProcessCI, Type of field = single select, Lookup Type= Dynamic List<ul><li style="font-style: italic;">sql script= <em>select top 100 percent CTTOMProcessesid as [ID], CFTOMProcesses as [Display] from CTTOMProcesses Order by CTTOMProcessesid</em></li></ul></li><li>Name= TOMARole, Type of field = Text</li><li>Name = TOMAIndividualName, Type of field = single select, Lookup Type= Dynamic List, Data Load Type = >10,000 rows<ul><li>sql script = <em>SELECT $TOPSQL uid as 'ID', uusername as 'Display' FROM users WHERE uinactive = 0 AND uusername != 'General User' $SEARCHSQL</em></li><li style="font-style: italic;"><p>Search SQL Script = <em>and uusername like '%'+$search+'%' or uemail like '%'+$search+'%'</em></p></li></ul></li></ul><p><br></p><p>You should have now created four tables. </p><p><br></p><p><strong><span style="font-size: 11pt;">Create TOM Custom Tab</span></strong></p><p>Once you have created the relevant TOM tables you will need to create an custom tab to store these under against CIs. </p><p><br></p><p>Head to Configuration > Custom Objects > Custom Tabs > change entity to CI > New > set the name and type of the tab as shown in Figure 9. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjY1ZjFiMDJlLWU1Y2ItNGFjNC04MzBiLTY2YTZjOTMyMTk3NyJ9.EvpuE_sWTXZmpfgYFR2oAwP-XDILEcixCFlT_VRsdNE" class="fr-fic fr-fil fr-dib" width="1667" style="width: 1669px; height: 430.289px;" height="430"></p><p><strong><span style="font-size: 10pt;">Fig 9. TOM Tab details</span></strong></p><p><br></p><p>Then add the following custom fields to the tab:</p><ul><li>CFTOMOperational</li><li>CFTOMAccountable</li></ul><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjQxYzViZDlhLWYwN2QtNGM3Ni1iOTlmLThlYmJlOTBjN2NmNyJ9.hKfWxevOC9rrPGlXwrVuWZMEVD0IEjoK4f37uwE6ub8" class="fr-fic fr-fil fr-dib" width="1678" style="width: 1680px; height: 309.372px;" height="309"></p><p><strong><span style="font-size: 10pt;">Fig 10. Fields within TOM tab</span></strong></p><p><br></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;" data-pasted="true"><strong><span style="font-size: 12pt;">Show TOM Tables on CIs</span></strong></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">If the "Target Operating Model (TOM)" tab does not show against your CIs, you will need to enable this. </p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br style="box-sizing: inherit;"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Head to Configuration > CI Management > CI Types > select a type > Layout tab > set 'Tab Layout' to be custom > then edit the "Target Operating Model (TOM)" line here to set the tab to show. </p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjBlNzI0MWVkLTFlYjYtNGMyYS1iZTNmLTQxMWEyN2U4MjIzZiJ9.92HDWGLfj4OOYRvCfVVtytZ_NkWYxUOWxIM8rNcgpoM" width="1842" height="692" style="box-sizing: inherit; border-style: none; cursor: pointer; padding: 0px 1px; user-select: none; text-align: left; width: 1474px; height: 553.75px; max-width: none !important;" class="fr-fil fr-dib"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong><span style="font-size: 10pt;">Fig 11. Set TOM tab to show for CI type</span></strong></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><br style="box-sizing: inherit;"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;">Once set to show, the TOM tab will show within all CIs of this type. </p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImMwZmQyNWQ4LThjNzctNDFiNy1iYmVhLWY1NDljYjA4NDc4ZiJ9.FTGH2lo9jGON_ZVCuz7SzRvwNWTbxKh6DLec15WvXqs" width="2008" height="652" style="box-sizing: inherit; border-style: none; cursor: pointer; padding: 0px 1px; user-select: none; text-align: left; width: 1520px; height: 493.546px; max-width: none !important;" class="fr-fil fr-dib"></p><p style="box-sizing: inherit; margin: 0px; line-height: 1.4285em; color: rgb(0, 0, 0); font-family: sans-serif; font-size: 14px; font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: left; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: normal; background-color: rgb(255, 255, 255); text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial;"><strong><span style="font-size: 10pt;">Fig 12. TOM tab within a CI</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Populating TOM Tables <a id="Populating-TOM-Tables" class="fr-anchor" title="Populating-TOM-Tables"></a></span></strong></p><p>Once the TOM tab is available on the relevant CIs you can begin populating each TOM table with the relevant data. In this section we will outline how to populate these tables. </p><p><br></p><p><strong><span style="font-size: 12pt;">Operational Table</span></strong></p><p>The operation table should detail which teams are responsible for supporting this service when incidents, requests, problems etc. are raised for it. This can also be used to drive assignment and escalation automations. </p><p><br></p><p>When populating the Operational table you will need to set three values per row.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImYzNmIyNzZiLWIyM2YtNGZhNi05OTg4LTliYjEyYmY2MmIyZSJ9.4Hm4ozJfeVwQyUV6QdBUXSrjJ-j-E2tmhVsGxMtZeKc" class="fr-fic fr-fil fr-dib" width="1782" style="width: 1784px; height: 572.784px;" height="573"></p><p><strong><span style="font-size: 10pt;">Fig 13. Columns to populate for Operational TOM table</span></strong></p><p><br></p><p><strong>Process - </strong>Choose which process you are defining in the operational TOM. For example, if "Incident" this section of the model will apply to incidents raised (incident ticket types).</p><p><strong>Operational Role - </strong>Define the escalation level. </p><p><strong>Support Team / Approval Group - </strong>Set which team are responsible for supporting this process and operational role in the TOM model. The list of teams available to choose from here will be taken directly from the teams you have configured in your instance. </p><p><br></p><p>Ensure you outline the model (add data to the table) for each of your processes and operational roles (levels of escalation). </p><p><br></p><p><strong><span style="font-size: 12pt;">Accountable Table </span></strong></p><p>The Accountable table should detail which individuals are responsible for this service and the way in which they are responsible. </p><p><br></p><p data-pasted="true">When populating the Accountable table you will need to set three values per row.</p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImM4NTFiZjA2LWRkODAtNDI4OS1hYmI2LTQ4ZGQ2NTE2MTRlYSJ9.yQx78MtXBRKRIJbfHALZo1tVN56d6E0Fc7tlzTrrFw8" class="fr-fic fr-fil fr-dib" width="1785" style="width: 1787px; height: 575.45px;" height="575"></p><p><strong><span style="font-size: 10pt;">Fig 14. Columns to populate for Accountable TOM table</span></strong></p><p><br></p><p><strong>Process -</strong> Choose which process the individual is accountable for. For example, if "Incident" this section of the model will apply to incidents raised (incident ticket types).</p><p><strong>Accountable Role - </strong>Define the way in which the individual is accountable. </p><p><strong>Individual Name - </strong>Set who is responsible (accountable). </p><p><br></p><p data-pasted="true">Ensure you outline the model for each individual who is accountable for the service, and which part of the service they are accountable for. </p><p><br></p><p><strong><span style="font-size: 12pt;">Populating TOM tables in Bulk</span></strong></p><p>The TOM for each CI will need to be defined. You may choose to have each of your service owners define this for the CIs they are responsible for. This can be done as a manual exercise, by updating each of the CIs in Halo (as outlined in the previous section). Alternatively you can populate each TOM table for each CI using a csv import.</p><p><br></p><p>Templates for the csv files used for importing data into the TOM tables can be found attached to this guide, named "TOM Table import - Accountable Table.csv" and "TOM Table import - Operational Table.csv". If you are viewing this guide on our website you will need to obtain this attachment from our portal <a href="https://support.haloservicedesk.com/kb?id=3047" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p>When you have populated the csv file with your data import the data directly against each custom table using the "Import Data" option. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImIyYzI3OGE0LTQ2ODUtNGQ1YS04MmViLTQ0NzM4ZmQzNzg3MCJ9.ME7A0eQHHDGiTpi97hQNM6iMk55ZlX6K0Mv-GuaqEQY" class="fr-fic fr-fil fr-dib" width="768" style="width: 770px; height: 796.552px;" height="797"></p><p><strong><span style="font-size: 10pt;">Fig 15. Import Data to a TOM table</span></strong></p><p><br></p><p><strong>Populating the Operational Table</strong></p><p>The template for populating the operational table is shown in Figure 16, with some example data. Each row in the template represents a row in the table. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImNjOTlkMDVmLTBlOTktNDhjYy1iN2U3LTIzMDVmOGY2NTE1OCJ9.3TY19C6BrowbObsp8AV-dat3NMOrqb_HVuJp9pX8roU" class="fr-fic fr-fil fr-dib" width="1119" style="width: 1121px; height: 160.611px;" height="161"></p><p><strong><span style="font-size: 10pt;">Fig 16. Template csv for importing data into the Operational table</span></strong></p><p><br></p><p><strong>Key - </strong>Enter the ID of the CI you would like to add the data to. This CI's TOM table will be populated with data in these rows.</p><p data-pasted="true"><strong>CFTOMProcessesCI -</strong> In this column enter name of the process. Options are as follows: </p><ul><li>Configuration</li><li>Incident</li><li>Request</li><li>Problem</li><li>Change</li><li>Knowledge</li></ul><p><br></p><p data-pasted="true"><strong>CFTOMORole - </strong>Enter the ID of the operational role to set. To find the IDs for each operational role, head to the CTTOMOperationalRoles table. In this example, ID 2 corresponds to the Level 1 Support Role for the Incident process. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjJjYzE1NTdjLTRmZDktNGExYi1hYWY1LTc5M2QyZGViNWRmMiJ9.52s7F02kTXzPTQmDVTg8Kx_OqxDmIFZ7jiP9DBEj4G4" class="fr-fic fr-fil fr-dib" width="1670" style="width: 1672px; height: 522.548px;" height="523"></p><p><strong><span style="font-size: 10pt;">Fig 17. Operational Roles and their IDs</span></strong></p><p><br></p><p data-pasted="true"><strong>CFTOMOTeamGroup - </strong>Enter the specialised ID of the team, company (organisation) or CAB you would like to set. The specialised ID for a team is 10000 + the team's ID. The specialised ID of a company is 20000 + the company's ID. The specialised ID for CABs is just the CAB's usual ID. Team, company and CAB IDs can be found in the page URL when viewing in Halo. </p><p><br></p><p><strong>Populating the Accountable Table</strong></p><p data-pasted="true">The template for populating the accountable table is shown in Figure 18, with some example data. Each row in the template represents a row in the table. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjdlZmJlZDU5LTA4MGYtNDM1MC05MTU4LWI5YTFhZDJmYTY5YiJ9.kNwoKdb-ttXxjZk4mvjc8JGW3XKxAeEku-99iN6BCKU" class="fr-fic fr-fil fr-dib" width="1030" style="width: 1032px; height: 283.237px;" height="283"></p><p data-pasted="true"><strong><span style="font-size: 10pt;">Fig 18. Template csv for importing data into the Accountable table</span></strong></p><p><br></p><p data-pasted="true"><strong>Key - </strong>Enter the ID of the CI you would like to add the data to. This CI's TOM table will be populated with data in these rows.</p><p data-pasted="true"><strong>CFTOMAProcessesCI -</strong> In this column enter name of the process. Options are as follows: </p><ul><li>Configuration</li><li>Incident</li><li>Request</li><li>Problem</li><li>Change</li><li>Knowledge</li></ul><p data-pasted="true"><strong>CFTOMORole -</strong> Enter a text to display in the Accountable Role column. This is a free text field so you can type freely (HTML is not supported). </p><p data-pasted="true"><strong>CFTOMAIndividualName -</strong> Enter the user ID of the person you would like to set in the Individual Name column. User IDs are found in the URL when viewing a user in Halo. </p><p><br></p><p><strong><span style="font-size: 14pt;">Building TOM Based Assignment<a id="Building-TOM-Based-Assignment" class="fr-anchor" title="Building-TOM-Based-Assignment"></a></span></strong></p><p>Follow this section if you would like to leverage your TOM in Halo to automatically assign tickets to the relevant team. </p><p><br></p><p data-pasted="true">The TOM based assignment automation will be pre-built into instances of Halo deployed for ITSM/ESM teams, deployed after September 2026. If this is pre-built minimal steps need to be taken to get this up and running in your instance.</p><p><br></p><p>If TOM based assignment is pre-built into your instance you will just need to add the relevant fields the ticket types you would like to utilise this on and enable the automation, jump to the section "Enable Runbook".</p><p><br></p><p>If this is not pre-built into your instance, the next section will outline how to build this in. </p><p><br></p><p data-pasted="true"><strong><span style="font-size: 12pt;">Building TOM assignment automation for Incidents - instances with no pre-built functionality</span></strong></p><p>If your instance contains no pre-built functionality you will need to create the escalation path fields that display on your tickets and an automation runbook. </p><p><br></p><p><strong>Create Escalation Path Fields </strong></p><p>Head to Configuration > Custom Objects > Custom Fields > ensure "Entity" is set to "Ticket". Create two new fields with the following configuration:</p><p style="margin-left: 20px;">Field 1</p><ul style="margin-left: 20px ;"><li>Name = TOMEscalationL2</li><li>Field Label = Escalation L2</li><li>Type of Field = Text</li><li>Exclude from $ALLFIELDS and $ALLFIELDSQA variables = Enabled</li></ul><p style="margin-left: 20px;">Field 2</p><ul style="margin-left: 20px ;"><li>Name = TOMEscalationL3</li><li>Field Label = Escalation L3</li><li>Type of Field = Text</li><li>Exclude from $ALLFIELDS and $ALLFIELDSQA variables = Enabled</li></ul><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjU5M2QxMTNmLWMzYTItNGNlMS05Y2RiLTgyMmMwYTEzM2VlMSJ9.173yoIpemJN6BVdT6hVrRAX7kOYDiT1h9Qc7lCN92x0" class="fr-fic fr-fil fr-dib" width="647" style="width: 649px; height: 467.165px;" height="467"></p><p><strong><span style="font-size: 10pt;">Fig 19. Field to Create</span></strong></p><p><br></p><p>Once created, make note of the IDs of each field, these can be found in your Halo URL when viewing the field configuration. </p><p><br></p><p><strong>Create Automation Runbook</strong></p><p>Head to Configuration > Integrations > Custom Integrations > Integration Runbooks > Import from JSON. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjczNmFjYjBmLWU4NjUtNDNlOS04ODQ4LWRmMzI0Y2U4ZmFiYyJ9.P5K5HLWffk7-kFamqXQzr-TBLEeoDl-1HpWJwthajAA" class="fr-fic fr-fil fr-dib" width="1694" style="width: 1696px; height: 496.277px;" height="496"></p><p><strong><span style="font-size: 10pt;">Fig 20. Import from JSON</span></strong></p><p><br></p><p>In the pop-up paste the JSON attached to this guide "Service Automation Framework Incident Runbook.txt". If you are viewing this guide on our website you will need to obtain this attachment from our portal <a href="https://support.haloservicedesk.com/kb?id=3047" target="_blank" rel="noopener noreferrer">here</a>. </p><p><br></p><p>Once the runbook is installed open this up and head to the "Flow Chart" tab, here edit the step "Assign L1 & L2 & L3 Team". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjRkODVjOWNmLTJhMDgtNDA3OC1hOGMwLThkNDRkNWMwYzBjMiJ9.HdWwiCdLmSOdTv-w3S61W_jR4BVVel93XxfJntmLZkw" class="fr-fic fr-fil fr-dib" width="1392" style="width: 1394px; height: 762.947px;" height="763"></p><p><strong><span style="font-size: 10pt;">Fig 21. Edit "Assign L1 & L2 & L3 Team" step </span></strong></p><p><br></p><p>In here edit the custom field IDs highlighted in Figure 22 to be the IDs of the custom fields you created earlier. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjNiM2FhNjE2LTM4OTUtNDQ0Zi1iYjVlLTk4MzUyNGExMjk5NyJ9.012JGIkrPPYkHPXHd_I_UkFG7jD_KqDvujbRFiizh1c" class="fr-fic fr-fil fr-dib" width="1706" style="width: 1708px; height: 909.241px;" height="909"></p><p><strong><span style="font-size: 10pt;">Fig 22. IDs to update </span></strong></p><p><br></p><p>Repeat this for runbook steps "Assign L1 & L2 Team" and "Assign L1 Team". </p><p><br></p><p>Now head to the "Details" tab and add an event trigger for the runbook. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImI0NWUzYzVmLTE2ZmYtNGI0NC05ODY3LTlkNjZmYjIzYzBmYiJ9.9hrKQWd-lgb1RUMmUAfsAakFMvkvDpegGAuj35eQ5Xg" class="fr-fic fr-fil fr-dib" width="1654" style="width: 1656px; height: 596.591px;" height="597"></p><p><strong><span style="font-size: 10pt;">Fig 23. Add event trigger </span></strong></p><p><br></p><p>We recommend setting the runbook to trigger when each time a new incident ticket is logged, and a primary CI is set for the ticket (shown in Figure 24). </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijk1ODZjMDU4LTU0N2QtNGU1My05OGQzLWUxNTc4MzUwODdlZCJ9.DHp8dteHBljxQQihHAh6Z2mb1NG1tytfdTeH6p1uPdo" class="fr-fic fr-fil fr-dib" width="579" style="width: 581px; height: 483.484px;" height="483"></p><p><strong><span style="font-size: 10pt;">Fig 24. Event Trigger for runbook</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Enable Runbook</span></strong></p><p>Ensure the automation runbook is enabled. To do this head to Configuration > Integrations > Custom Integrations > Integration Runbooks > select "Service Automation Framework - Incident" > check "Enabled". </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjI4NWJmMGI3LWE0NjItNGFiMy1hMzM2LTVhMjY2NDk1MGJlMiJ9.LQSN3XjpYfBU3lRfUMIDtYU3ppSKdS0EfekKeHQ504k" class="fr-fic fr-fil fr-dib" width="1665" style="width: 1667px; height: 633.166px;" height="633"></p><p><strong><span style="font-size: 10pt;">Fig 25. Enable Runbook</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Add Escalation Fields to Ticket Type </span></strong></p><p>Add the custom fields created earlier to your incident ticket type. Head to Configuration > Tickets > Ticket Types > select incident > Field List tab > add field group. </p><p><br></p><p>Create a new field group called "Ticket Routing" with these two fields added. Set the visibility for these fields as desired, we recommend having the fields set to be hidden to agents if empty, so if a level 2/3 escalation path is not applicable to particular CIs, the field will not show. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImRhZDVhZTc5LWM1ZDAtNDc1My05ODI4LTFmOGIwN2JiNmI5NiJ9.uABaZkhnrqrVNgYRrEEkcutDzp1kslBC51c6MRdPRPs" class="fr-fic fr-fil fr-dib" width="566" style="width: 568px; height: 524.555px;" height="525"></p><p><strong><span style="font-size: 10pt;">Fig 26. Setting to Hide Field from Agents if Empty</span></strong></p><p><br></p><p>Once set, be sure to save the field group and the ticket type. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6Ijc0NTQ4ODM0LWVhZDUtNDZlZS1iNzE1LTNmZDc3ZDljOTE0NCJ9.ZGXJndn-RwSa3TDEurx6oQLsWYR93BHsDQJg0n_7sTg" class="fr-fic fr-fil fr-dib" width="1596" style="width: 1598px; height: 874.796px;" height="875"></p><p><strong><span style="font-size: 10pt;">Fig 27. New Fields added to ticket type</span></strong></p><p><br></p><p><strong><span style="font-size: 14pt;">Building TOM assignment automation for other Processes<a id="Building-TOM-assignment-automation-for-other-Processes" class="fr-anchor" title="Building-TOM-assignment-automation-for-other-Processes"></a></span></strong></p><p>If you would like to utilise TOM based assignment for your other processes, such as requests, problems, changes etc., you will need to replicate the build steps outlined in the "Building TOM Based Assignment" section for each of your processes.</p><p><br></p><p>Each process requires the following:</p><ul><li>x2 Custom Fields added to the relevant ticket type to store the L2 and L3 escalation paths. </li><li>x1 Automation Runbook to carry out the assignment</li></ul><p><br></p><p>The automation runbook will need to be adjusted for each type of process. If you require assistance with this reach out to your consultant or our support team. <a href="https://support.haloservicedesk.com/kb?id=3047" target="_blank" rel="noopener noreferrer"></a> </p><p><br></p><p><strong><span style="font-size: 14pt;">Create Escalate Action (Optional) <a id="Create-Escalate-Action--Optional-" class="fr-anchor" title="Create-Escalate-Action--Optional-"></a></span></strong></p><p>The escalation process can also be automated based on the TOM for a CI. Assigning the ticket to the team that has the next level of operational role based on the primary CI for the ticket. This functionality is not built into instances so you can follow the steps outlined here to build this into your instance. </p><p><br></p><p><strong><span style="font-size: 12pt;">Create Automation Runbook</span></strong></p><p>An automation runbook is used to power this escalation process, therefore this will need to be built into your instance. </p><p><br></p><p>Head to Configuration > Integrations > Custom Integrations > Integration Runbooks > Import from JSON. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImQ5N2QzZDJhLTU0OGEtNGQzZC04YTY2LTQ3YzU5MzI4ZWE2MyJ9.tOqpPfXfY5wVSeK9nVWF047croH09tEN2NPBvTEH3hU" class="fr-fic fr-fil fr-dib" width="1836" style="width: 1838px; height: 498.669px;" height="499"></p><p><strong><span style="font-size: 10pt;">Fig 28. Import from JSON </span></strong></p><p><br></p><p>In the pop-up, paste the JSON attached to this guide "Service Automation Framework - Escalation Runbook.txt". On saving this will create the runbook in your instance. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImY1MDEzODc4LWMyYjktNDAyMy04NTlhLTFmM2U1NjRhYWQzMCJ9.sR1Uwxg3NkxvIFJJCDaEEBd_Bjkk3MIE5x_gHMF83TQ" class="fr-fic fr-fil fr-dib" width="1829" style="width: 1831px; height: 406.889px;" height="407"></p><p><strong><span style="font-size: 10pt;">Fig 29. Escalation Runbook</span></strong></p><p><br></p><p><strong><span style="font-size: 12pt;">Create Escalation Action</span></strong></p><p>An action will need to be created to trigger this automation runbook and run the escalation. </p><p><br></p><p>Head to Configuration > Tickets > Actions > New > Create an action with the following properties:</p><ul><li>Button Name: "Escalate (TOM)" - or any appropriate name. </li><li data-pasted="true">System Use: Send Webhook/Queue Integration Runbook</li><li data-pasted="true">Webhook/Integration Runbook: Service Automation Framework - Escalation</li><li>Is a Quick Action: Yes</li></ul><p><br></p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjA4N2QwZWQ0LTc1YTctNDlhZi1hYWIwLTcxNGE1M2MzZTA1MSJ9.d64zKb0PwcO2BpNSEF6HwOUqEO15Xq1QiWp0MKpkiG4" class="fr-fic fr-fil fr-dib" width="1189" style="width: 1191px; height: 632.456px;" height="632"></p><p><strong><span style="font-size: 10pt;">Fig 30. Action to Escalate Ticket</span></strong></p><p><br></p><p>Now ensure this action is added to the relevant ticket workflows i.e. incident workflow(s). We recommend still having a re-assign/escalate action available so tickets can still be re-assigned in cases where there is no primary CI or no TOM for the primary CI. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6ImM4NzgwMDM0LWIzNmItNGY4Mi1iNDQ3LWZmZmI5Y2NiZThhOSJ9.TV-eNg4M47PamDE7TN6nOHAJya6ELS_NSVcvWQuRCsA" class="fr-fic fr-fil fr-dib" width="1347" style="width: 1349px; height: 492.088px;" height="492"></p><p><strong><span style="font-size: 10pt;">Fig 31. Escalation Actions for Ticket</span></strong></p><p><br></p><p>The "Escalate (TOM)" action can be used multiple times on the same ticket, to escalate to the next level each time, up to three levels.</p><p><br></p><p>If a CI does not have sufficient data in its TOM then assignment will fail and the agent will be prompted to assign manually. </p><p><br></p><p><strong><span style="font-size: 12pt;">Escalation Automation Breakdown</span></strong></p><p>The following process occurs when the TOM escalation action is used:</p><ul><li>Service Automation Framework - Escalation is triggered</li><li>The team currently assigned to the ticket is checked to see if it is the level 1 or 2 operational role for the CI. </li><li>The TOM is then checked to ensure a level 2 or 3 operational role is defined.</li><li>If the level 1 team is currently assigned, the ticket will be re-assigned to the level 2 team, (or the level 3 team if no level 2 is defined in the TOM). </li><li>If the level 2 team, is assigned, the ticket will be re-assigned to the level 3 team. </li></ul><p>If the automated escalation fails at any point an action will be added to inform the agent that automated assignment was not successful. </p><p><img src="https://halo.haloservicedesk.com/api/attachment/image?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpZCI6IjM3NjlhZTU5LTRkYjQtNDcyNy05YTYyLWM1Y2Q3OTBhNjcwZCJ9.NyHERWYtGtPQgf9o5UinMUdxmvDCa9UhWBp0awzLwn8" class="fr-fic fr-fil fr-dib" width="1469" style="width: 1471px; height: 505.028px;" height="505"></p><p><strong><span style="font-size: 10pt;">Fig 32. Action to Inform Agent the Automation has failed </span></strong></p><p><br></p>