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 of Accept/Rework (complaint management) functionality in T-Connector.
This feature allows customers to explicitly "accept" or raise for a "complain" regarding fulfillment provided by T-Systems.
Please contact T-Systems Support team to enable this feature for relevant catalog items.Updated script includes "TSI_WorkflowUtils" & "outboundOrderMappingHelper",Created new workflow "Complain management" and updated "TSI - RITM Workflow_Parent". Cretaed Dictionary entry "Stage Transition.Accept/Rework" ,Created UI Action "Accept" and "Complain",updated script action "Send MultiInformation Msg to T-Systems",created message "x_tsigh_ts_connect.ritm.acceptance.deadline ".
Enhancement:CHM2CHM Pending Validation in Master Position on Task Level
Local task can be converted into remote task only in New change phase for Change integration.Updated Script include "CHMConvertChangeToTSYforRemoteGroup","CHMTaskServerValidationUtility", Cleint script "CHM-Remote Assignment Group Not Allowed" and Business rule "CHM Validation for Master TConnector TSK".
Bugfix:CHM2CHM: Setting task to Closed with future actual end date
Fixed the issue for Actual end date can't be future date from now.Updated business rule "CHM Validation for Master TConnector TSK".
Bugfix:Fix the issue for Process control looping
Fixed the issue to check the active process control for T-connector records only.Updated Business rule "Message exchange triggering[task]"
Bugfix:CHM2CHM:setting task to In Progress with a future actual starting date
Fixed the issue Actual start date can not be future date from now.Updated Business rule "CHM Validation for Master TConnector TSK","CHM- Set & Process Remote Assignment Grp",updated script include "CHMConvertChangeToTSYforRemoteGroup" and client script "CHM-Remote Assignment Group Not Allowed".
Bugfix:Task is added to Remote task ID even if it is local
Fixed the issue for Remote task id will not be added on the failure of local to remote conversion
BugFix: CHM2CHM It is not possible to add a remote group to a task with an empty AG.
Now allowed to add remote group in valid phase if Assignment Group is empty.
BugFix:CHM2CHM :Error message showing even the implementation not yet started.
When customer is master and no task implementation started, Change can be cancelled without showing any error message.Updated script include "CHMServerValidationUtility".
BugFix:future "actual beginning date" for local task is accepted without resistance
Actual start date not allowed as future date from now for Master Change.Updated Business rule "CHM Validation for Master TConnector TSK'
BugFix:Future "actual ending date" for a pss-implemented task is accepted without resistance
Actual end date now allowed as future date from now for Master Change.Updated script include "connectorHelper", "CHMConvertChangeToTSYforRemoteGroup" and "CHMTaskServerValidationUtility".
Bugfix: local task is reassignable to remote AG despite requirements
Master Task once bonded cannot be assigned to local.Updated script include "CHMConvertChangeToTSYforRemoteGroup'.
Bugfix:Process field is not visible on Forms Customer ID and connector properties table
Added the Process field to the form view of T-Connector Properties.
- 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