T-Systems customers can now seamlessly integrate their ServiceNow instance into T-Systems with ease.
Created from the ground up to allow you to take advantage of your T-Systems provided services from within your own ServiceNow instance, the T-Systems Connector removes the complexity, effort, and cost involved in custom integration.
Incidents can be communicated with T-Systems and remain fully synchronized, including all notes and attachments, bi-directionally over the interface until the Incident is resolved and closed.
Service Catalog content, created specifically for each customer, can be made available in your instance. Any requests made from this content will be sent directly to T-Systems for fulfillment, with the Request and Requested Item kept updated throughout the fulfillment process. The T-Systems Connector allows you the flexibility to place your own approval process on the requested items, making sure you stay fully in control of your process.
Any CI’s created or modified for you by T-Systems will be synchronized back into your CMDB for your visibility and use in Incident Management and Request processes.
Because no two ServiceNow implementations are the same, the T-Systems Connector is fully configurable, allowing it to adapt to your process, not the other way around.
T-Systems connector application is currently tested by using ServiceNow forms and lists views. Workspace views are under investigation, but not yet tested.
Connect a ServiceNow instance to the T-Systems internal Enterprise Service Bus
Minor Changes:
Enhancement: Prevent Duplicate Comments for Oversized Attachments in Incident Updates
When an update occurs on incident, if an oversized attachment is detected and has already triggered the exceeds size limit work note earlier, the script will skip adding the same work note again. Updated bonded attachment script include.
Enhancement: Implement the Logging Mechanism in T-Connector for CHM2CHM
Implemented Logging in case no soap template connector property found in ChangeToChange Outbound message. For ChangeInfo Inbound if default assignment group is not present for ChangeToChange incoming message then no Change will be created and reason will be logged in Connector Log table once that throws exception.Updated CHM2CHM related script includes.
BugFix:CMDB_regression_SynchCI_for additional relationship- Delete functionality NOT working from T-Connector
In case of any relationship is deleted for the predefined classes from T-System, that will get reflected via T-Connector CI sync and this will also remove the relation for CI.Updated script include "TSC_CMDB_Staging_Util" and "TSC_WS_out" and BR "Process CI Staging table".
Bugfix:T-Connector->T_Systems status updates @ CHM2CHM compromised after Zürich upgrade
At our end referring instance for SIT and certification is done on Zurich upgrade Patch0. We found one unexpected additional ACL on user group table. To allow read of group table and that is for T-Connector web service user we reverted GlideRecordSecure to GlideRecord api in one connector script until we fix this. HI-CASE is due with ServiceNow.
Updated script include "CHM_ChangeInfoTaskCreationInbound"
BugFix:Retry mechanism for chm2chm is not picking correct operation
For ChangeToChange retry function is enabled and that is only for ChangeInfo outbound where T-Connector installed.Updated script include "errorResponse".
Note: For mapping and property data,please connect with your T-Systems point of contact.
- ITSM
- The following plugins are recommended to be installed prior the T-Systems Connector app in order to support CMDB classes. However, the specific classes use will depend on the customer contract. These plugins are required to support the cross-scope privileges functionality:
- CMDB CI Class Models
- Expanded Model and Asset Classes
- Discovery and Service Mapping Patterns
- Cloud Provisioning and Governance: Terraform Connector
- Cloud Provisioning and Governance: Google Cloud Connector
- CMDB Mainframe
- CMDB Telecom CategoryCMDB Test Equipment