Post-installation tasks
There are certain tasks that must be completed post-installation, in order for your 1E and ServiceNow integration to work correctly. These tasks include both mandatory and optional configuration steps.
The 1E Core application communicates with the 1E system hosted in your production network. Configuration settings must be applied to manage how the 1E Core application operates.
App Menu
ServiceNow offers an application navigator that allows administrators to easily switch between different screens. To use the 1E Core application, first install it from the ServiceNow App Store, then search for 1E Core in the application navigator. Non-administrators (end users) do not have access to 1E Core.
Item |
Description |
Roles needed to view the Item's page |
|
---|---|---|---|
1E Core app roles |
ServiceNow roles |
||
Triggered Instructions |
Displays a list of instructions that have been run. |
x_1e_core_connect.admin |
admin (System Administrator) |
Instruction Definitions |
Displays a list of available 1E instructions. |
x_1e_core_connect.admin |
admin (System Administrator) |
Administration |
Displays a menu containing all the Administration functions for the 1E Core app. |
x_1e_core_connect.admin |
admin (System Administrator) |
App Configuration |
Displays the App Configuration screen where users can update the configuration settings. |
x_1e_core_connect.admin |
admin (System Administrator) |
Logs |
Displays the application specific logs. |
n/a |
admin (System Administrator) |
App Configuration Page
The App Configuration node is in the Administration section of the 1E Core application, where administrators can configure various application settings.
This page is only accessible to a ServiceNow user that is a member of 1E Core app role x_1e_core_connect.admin. If the user is also a ServiceNow admin the page will only be accessible after setting the scope to 1E Core.
All the fields on the App Configuration page are mandatory with default values except the MID Server. The domain separation feature (single-tenant or multi-tenant) will be autopopulated based on whether the Domain Separation plugin is activated. It can also be configured from the x_1e_core_connect.multi_tenant_instance system property.
Due to the limitations of ServiceNow property pages, there are no validation checks applied to any of the settings. You should take extra care to ensure that all the fields are filled out correctly.
Below is a list of the fields available on this page:
Field |
Description |
---|---|
1E Platform URL |
The base URL for the 1E Platform server (specifically, the server that hosts the Consumer API component of the 1E Master Stack). |
Switch to OAuth-based Authentication |
This checkbox controls the business application's authentication method to 1E. If selected, the application will authenticate using Modern Authentication; if not selected, it will use Basic Authentication. |
Are You Using MID Server for OAuth-based Authentication |
This checkbox determines whether the application will use the MID Server with OAuth on-premises. It has no effect if the application uses Basic Authentication with the MID Server, as the functionality remains the same. If selected, the application will use the MID Server for OAuth; if not selected, it will not.
Note that the decision to use OAuth is controlled by this checkbox. |
MID Server |
Name of the MID Server used for connecting on-premises 1E, if applicable. |
1E instructions gather data minutes |
This setting is specific to the 1E Platform and determines the duration, in minutes, that 1E will continuously collect responses for an instruction when ServiceNow sends an execution request. The unit for this setting is minutes, with a default value of 60 minutes and a valid range from 10 to 10,080 minutes |
1E instructions keep answers minutes |
This setting is specific to the 1E Platform. The value is used when ServiceNow sends an instruction execution request to 1E and controls the number of minutes that 1E should keep the instruction responses active. The unit for this setting is minutes, with a default value of 120 minutes and a valid range from 10 to 10,080 minutes. |
1E Endpoint Troubleshooting URL |
This optional setting enables the 1E Endpoint Troubleshooting link, under the related links header on an incident page. If this value is empty, then users will see an error message if they click on the 1E Endpoint Troubleshooting link. |
Save |
This button saves all the modifications made to the fields on the App Configuration page. |
Configuring multi-tenant
The 1E Core application now supports domain separation for 1E ITSM Connect and 1E Virtual Assistant applications.
The domain separation feature is automatically populated based on whether the Domain Separation plugin is activated, but it can also be configured manually using the system property.
This feature is only available in 1E Core 4.0.18 or later.
To enable this functionality, you have to set the value for system properties x_1e_core_connect.multi_tenant_instance (for 1E ITSM Connect) and x_1e_core_connect.multi_tenant_instance_va (for 1E Virtual Assistant) to true. Once you have updated this value to true, it now allows you to create new configuration records for different domains.
To view and configure the values of the system properties, follow the below steps:
-
Login to your ServiceNow instance.
-
Open the System Properties table by typing sys_properties.list in the filter navigator and press enter.
-
The System Properties table opens up into a new page. Now look for the details of x_1e_core_connect.multi_tenant_instance (for 1E ITSM Connect) or x_1e_core_connect.multi_tenant_instance_va (for 1E Virtual Assistant) property in the table as shown below.
-
Edit the value of the system property to True.
-
Click Update to save the changes.