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: Implement the solution for Asynchronous response handling for retry mechanism for Incident
When T-connector sends an "ticket" to remote group request for incident and receives an asynchronous error response from OTIP,then the system should correctly handle the error and reassigning the incident ticket based on the incident.default.sender_group property to local group and ownership should be local.Updated script include errorResponse,TSC_error_in and errorHandler.
Enhancement:CHM2RITM:Add the worknotes related to dates with timezone in RITM and CTASK
Added Time Zone on the worknotes at the task level for ChangeToRITM. Updated workflow "TS - RFC Catalog Tasks".
BugFix: Fixed the issue related to Attachment and worknote sending from T-Connector to T-systems backend
A bug has been fixed where an attachment added immediately after another attachment was not being sent from the customer instance to the T-system. Also fixed the issue for comment added via inbound email action is also transferred. Updated business rule 'Send attachment on Inbound Trigger' and 'Send attachment'.
BugFix:CHM2CHM - Message ID are shown instead of message text for validations on instance with Yokohama version
Fixed the issue for showing messages instead of code, message table code field is removed. Updated message records.
BugFix:CHM2RITM: The work notes contains the object glide record for CTASK
Updated the worknotes with Actual GlideRecord. Updated workflow "TS - RFC Catalog Tasks".
Bugfix:Fix the Servicenow finding for Jelly statement
ServiceNow finding related to unsafe jelly statement is fixed. Updated UI page "setup".
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