Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


HTML
<style>
.release-box {
	height: 30px; 
	width: 100px; 
	padding-top: 8px;
	text-align: center; 
	border-radius: 5px; 
	font-weight: bold; 
	background-color: #8efeb3;  
	border-color: #FCE28A;
}

.release-box:hover {
  	cursor: hand;
    cursor: pointer;
    opacity: .9; 
}
</style>
<meta name="robots" content="noindex">

<div class="release-box">
<a href="https://docs.perspectium.com/display/krypton" style="text-decoration: none; color: #FFFFFF; display: block;">
Krypton
</a>
</div>



Table maps handle how data being shared out of ServiceNow is processed. Your outbound table map for Azure DevOps Zendesk will require some field changes to ensure that data is mapped correctly when sent from ServiceNow to Azure DevOpsZendesk.


Procedure

To edit the table map for Azure DevOpsZendesk, follow these steps:


You should have two new field map created. 
Image Removed

UI Steps
sizesmall


UI Step

Log into your ServiceNow instance and navigate to Perspectium Common Documents > PSP Common Table Maps or simply type and then select Table Maps in the Filter Navigator on the upper left-hand side of the screen.

Then, search for and click into the table map of the table you are integratingthe table map. See the following table below for which table map you need for your integration:

Table Table Map
Incident Incident to Common Incident
ChangeChange to Common Change

You can easily search for this table map by typing the name in the search window under the Name field.


UI Step

Scroll down to the list of PSP Table Field Maps and click New

Create a field map for the following maps to map fields between ServiceNow and Zendesk as appropriate and click Submit when done:

Source FieldTarget Field 
Code Block
languagebash
${TM:psp_user;sys_id=$[GR:assigned_to]}

.

For example, you can map it so the ticket will show as a specific user as the requester. If not mapped, tickets created in Zendesk will show the requester as being the integration user entered in the meshlet configuration. 

assigned_tos
projectproject