Configure Assist for ITSM (SysTrack On-Premises)

The following sections explain how to configure ServiceNow to integrate with the on-premises version of SysTrack.

On-Premises SysTrack Integration Prerequisites

To integrate ServiceNow and an on-premises version of SysTrack, you need the following items.

Item	Description
ServiceNow HI account access	Allows the downloading of SysTrack apps
Supported release of ServiceNow	Required release for SysTrack apps
ServiceNow ITSM module installed	Required for Assist for ITSM app
ServiceNow account with Admin role	Required to configure integration
ServiceNow MID server	Required to communicate between ServiceNow and the on-premises SysTrack Master server to request snapshot creation and asset synchronization
Name of ServiceNow MID server	MID server name, as listed in ServiceNow
Windows Server Administrator account	Required to configure the service account and password, as well as the IIS configuration. Different accounts can be used.
Domain account with access to the SysTrack API	Required for Basic Authentication between ServiceNow and SysTrack
SysTrack Administrator account	Account with Tools Access Security (TAS) rights to access SysTrack Configure
SysTrack 9.0.462 or higher	Version required for ServiceNow 2.2.1 apps.
Connectivity between ServiceNow and SysTrack	Network access from the SysTrack Server to the ServiceNow instance

Multi-Domain ServiceNow Instances

If you are in a multi-domain ServiceNow instance, you must add records to the Assist for ITSM Domain Info table in ServiceNow, rather than configure the info in Properties. To access this table, click the Assist for ITSM Domain Infos link in the application menu. For each table record, you must include the full domain name and all the information about the SysTrack install for that domain. The value in the Domain Name field is the one used by the application script to match to the Incident domain and retrieve credentials from the relevant record. The Domain field denotes the domain under which the record exists. In most cases, the Domain Name should match the name in the Domain field, but you can configure the record differently if needed.

SysTrack ID

The SysTrack ID is used by the SysTrack Detected Issues and SysTrack Tools tabs to determine which user should be targeted when running tools that require a user context. Therefore, you might want to make sure all SysTrack-associated users have their SysTrack ID set correctly in the ServiceNow instance. This is not required, unless you want to run an automation as a specific user on the system. To enable editing, you might have to add the SysTrack ID field to the User form.

Assist for ITSM provides options to find and match users. First, Assist for ITSM tries to match the username. If there is no match, it tries the SysTrack ID. If this option fails, it tries the UPN and email address. These options enable Assist for ITSM to pull as much data as possible into ServiceNow.

NOTE: The best practice is to put a value in the SysTrack ID property:

The SysTrack ID is a property of the Caller object. If you need the Caller object to be populated, you must do that. SysTrack does not populate the Caller object.
If you leave the SysTrack ID empty, keep in mind that any user-ran Automations in ServiceNow will select a random user context from the available user sessions currently live on the endpoint, and the Automation will run under that user context. This could create unexpected situations for you if you have a user-ran Automation that, for example, deletes content from a specific folder when space is low, because that Automation will run on a random user's system.
If you follow the best practice and put any value in the SysTrack ID property, user-ran Automations will try to match that value with an account that currently has a session on the endpoint, and the Automation will run under the matching user's context. If the Automation does not find an explicit match, it will not run. This eliminates the possibility of unexpected situations like the one described in the preceding paragraph.

Configure ServiceNow for the Integration with SysTrack (On-Premises)

Follow these steps to configure your On-Premises SysTrack to be ready for integration with ServiceNow:

Configure Basic Authentication on IIS of the SysTrack Server. Basic Authentication must be added through Server Roles and enabled in IIS for the API virtual directory. A detailed setup document is available in the ServiceNow Store.
Log in to the ServiceNow Store with a HI permission account and download the Assist for ITSM SysTrack plugin.
Install the Assist for ITSM plugin on the Plugins page in ServiceNow.

Create the following ServiceNow groups and assign the listed roles to these groups. The roles were created automatically while you installed the SysTrack plugin. The names of the ServiceNow groups can be whatever you want to name them. The names in this example are Administrator and User.

Group	Roles to assign
Administrator	Assign the following roles. All are optional except the one marked as required: x_laso_systrack_bl.user (required) admin The x_laso_systrack_bl.user role is required for downloading and configuring the plugins. Having this Administrator group is not essential, because you can give the roles to the user responsible for configuration.
User	Assign the following roles. All are optional except the one marked as required: x_laso_systrack_bl.user (required) x_laso_systrack_bl.Autofixes x_laso_systrack_bl.AutomationHistory x_laso_systrack_bl.Compliance x_laso_systrack_bl.Tools The user roles correspond to the Assist for ITSM tabs. For example, if you want the user to see the Automation History tab, the user needs to have the x_laso_systrack_bl.AutomationHistory role.

Group

Roles to assign

Administrator

Assign the following roles. All are optional except the one marked as required:

x_laso_systrack_bl.user (required)
admin

The x_laso_systrack_bl.user role is required for downloading and configuring the plugins. Having this Administrator group is not essential, because you can give the roles to the user responsible for configuration.

User

Assign the following roles. All are optional except the one marked as required:

x_laso_systrack_bl.user (required)
x_laso_systrack_bl.Autofixes
x_laso_systrack_bl.AutomationHistory
x_laso_systrack_bl.Compliance
x_laso_systrack_bl.Tools

The user roles correspond to the Assist for ITSM tabs. For example, if you want the user to see the Automation History tab, the user needs to have the x_laso_systrack_bl.AutomationHistory role.

Add the appropriate users to the ServiceNow groups created in the previous step. The users will get the assigned roles after you add them to the groups.
Log into the ServiceNow instance with a user that has the roles required for configuration (see previous step). Search for SysTrack. The SysTrack plugins you installed will appear in the list.
Open the Properties page for the Assist for ITSM plugin. (The Properties link appears below each plugin name in the menu, as shown in the preceding image.) Use the following guidelines to configure the settings:

This example describes an on-premises setup, so leave the Cloud settings blank.
- In the SysTrack Installation Type field, select on-premises.
- In the HTTP Protocol field, select https.
- In the SysTrack Master Name field, enter the FQDN of the SysTrack master.
- In the MID Server Name field, enter the name of the MID server.
- In the Basic Auth Password field, enter the username and password for the account with access to the SysTrack API.

Select Sensors and Automations for Assist for ITSM

The sensors that you see in Assist for ITSM (on the Compliance tab) are the same as those you configured for use in Assist in SysTrack.

For Assist in SysTrack the enabled sensors are selected by a SysTrack System Administrator. All available System Checklist sensors are enabled by default, but a SysTrack user with Configure administrator rights (a SysTrack System Administrator) can edit settings and the underlying variables that determine whether the sensor is compliant from Configure. For more information, see the documentation for System Checklists.

NOTE: The Compliance Checklist in SysTrack has been renamed to System Checklist. In Assist for ITSM, the Compliance tab will retain the name Compliance, and it will display the list of sensors you have configured in your SysTrack System Checklist.

Edit the Assist for ITSM Fields and Tabs

For Service Operations Workspace only (not for Incident Management), you have the option to edit the views that control the SysTrack fields and tabs that appear on your Incidents. The fields and tabs are preconfigured to show everything you generally need. However, if you do have a need to change the views, see the steps here.