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: Implementation the error handling for sync response in T-Connector for Change2Change integration
Added and updated the Synchronous response to the incoming messages stream. T-Systems Connector can provide response and acknowledgement in case of successful/unsuccessful message stream processing.
Updated script includes:CHM_implementationDocReply_in,CHM_broadcast_in,CHM_approvalReply_in,TSI_SyncResponseHandling,CHM_changeInfo_in and CHM_implementationConfirmReply_in.
Enhancement: Error handling for resolve status in case of sync and async errors during integration
When the incident state changes from In Progress or any other state to Resolved, and a sync or async error occurs, the value defined in connector property “incident.errorhandling.state” is used to revert the state back to the specified value.
Updated script include "errorResponse".
Enhancement: Implementation of the XML generation script for process control error response
Implemented functionality to return sync error response if process control is off for process incident, order,change to RITM, Change to Change in T-Systems Connector process control table.
Updated script include "MessageStreamV2" and "TSI_SyncResponseHandling".
Enhancement: Code refinement within T-Systems Connector
Business Rule "Message exchange triggering" log messages is updated for info instead of warning.
Also 'Send Message to T-Systems' script action for Log message with meaningful text.
Changed log level to debug in script include TSC_IncidentData_out.
Enhancement: log level all in script include TSC_WS_out is updated.
A new connector property core.http.logging.debug allows to configure HTTP Outbound log levels to values –
- basic: Captures essential attributes of the HTTP transaction
- elevated: Includes all Basic data plus all request headers, the query string, and all response headers.
- all: Includes all Elevated data, additionally including the full request and response bodies.
Default Behavior : If a logging property is inactive/missing or holds invalid value, logging automatically defaults to basic.
Updated script include "TSC_WS_out".
Enhancement: Enhance Process Control for Change2Change integration
On process control deactivation connector provide synchronous error during Inbound communication and error message shall be placed into the change worklog to state that the process is turned off and no message will be sent.
Updated Business rule "CHM Message Exchange Trigger[change_request]" and "CHM Message Exchange Trigger[change_task]".
Bug fix:T-Connector Message Stream message creation issue
The defect is fixedto handle the empty user record in 'x_tsigh_ts_connect_icu_user_mapping' table.Updated script include "outboundOrderMappingHelper"
- 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