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: Check the ServiceNow observation for complain management topic
Improved display conditions for Accept and Complain buttons on RITM form.Updated UI action "accept" and "Complain".
Enhancement: Assignment group should not be added for resolution message for incident.
Assignment information will be captured for outbound message only when state is not resolved.
Enhancement: Change the protection policy to Read only for T-Systems Connector scoped app.
The script include which are used in the mappings is updated for the protection policy from protected to read only.
Enhancement: Fix the findings from ServiceNow for Jelly scripting,getRowCount.
Fixed the ServiceNow self-test tool observations. Updated related objects based on the results.
Bugfix:Ownership field is getting empty after receiving a synchronous error from SC3A to OTIP.
Ownership of the incident is updated to 'Local' in case of a sync error. When a retry is attempted for an incident record, the system first checks whether the assigned group is marked as 'Remote' in the Assignment Group Mapping table. If it is not marked as 'Remote', ownership remains with 'Local'. The ownership field is determined based on the connector property incident.routing.sender_name.Updated script include "errorResponse" and "assignmentGroupMappingUtils".
Bug fix: Fix related to empty CI id in T-Systems Connector app.
Fixed the script that was returning empty CI sys_ids.Updated script include "CatalogMethodUtils".
BugFix:Activate Schedule job "TSC Error Resend".
Scheduled job "TSC Error Resend" is activated.
- ITSM
- Below Plugins needs to be to be installed before installing the T-Connector app for this version.These plugins are needed for cross scope priviledges story:
- 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