Page Comparison

New template in the TM Integration Framework for ServiceNow connection

With this feature, you can easily configure a Service Now system within the TM Integration Framework, without knowledge of the technical details.
For the configuration following template is available:

• TEMPLATE_ SNOW_INC

For the ITSM configuration, 2 item types are available:

GET → Query to read Service Now Incidents
UPD → Update Service Now Incident

For the Workflow step configuration, the following actions are included:
For GET item type/Assign SNOW Incident to transport request:

• TEMPLATE_ SNOW_INC GET AFTER_WF_A After workflow assignment before release is finalized
• TEMPLATE_ SNOW_INC GET CREATION Creation of a request

For UPD item type/ Update SNOW Incident:

• TEMPLATE_ SNOW_INC UPD LINK_EXT Link external transport at creation of a request
• TEMPLATE_ SNOW_INC UPD RELEASE Release and export of a request
• TEMPLATE_ SNOW_INC UPD APPROVAL Approval of a request
• TEMPLATE_ SNOW_INC UPD IMPORT Import of a request

Configuration, Integration Framework, ServiceNow

SC-1209

Change date of the template entries to field type timestamp

With this feature, field CREATIONDATE has been changed to use field type "TIMESTAMP" for templates TEMPLATE_ SOLMAN_SMIN and TEMPLATE_ SOLMAN_SMIR. This configuration settings allows you to view the timestamps in a user friendly format.

Configuration, Integration Framework

SC-1214

ServiceNow configuration included in the standard TM Integration Framework

With this feature request, you can configure TM integration with a Service Now instance within the standard.

Integration Framework, ServiceNow

SC-887

ServiceNow update on creation

With this new feature, SNOW App - SmartChange tab is updated at transport request creation, if a SNOW incident has been assigned to the transport request.

Integration Framework, ServiceNow

SC-888

ServiceNow update on release

With this new feature, SNOW App - SmartChange tab is updated at transport request release, if a SNOW incident has been assigned to the transport request.

Integration Framework, ServiceNow

SC-889

ServiceNow update on approval and revoke approval

With this new feature, SNOW App - SmartChange tab is updated at transport request approval or revoked approval, if a SNOW incident has been assigned to the transport request.

Integration Framework, ServiceNow

SC-890

ServiceNow update on import into a target system

With this new feature, SNOW App - SmartChange tab is updated at transport request import into a target system via TM, if a SNOW incident has been assigned to the transport request.

Integration Framework, ServiceNow

SC-891

Display of the date non-technically in the popup of the request assignment (GET action)

With this new feature, timestamp fields read from external ITSM systems are displayed in SAP user-friendly, during the assignment of a ticket to a transport request.
In order to achieve this, you can now define the data type as 'TIMESTAMP' for a particular field in the TM Integration Framework cockpit:
/RTC/TM_IF_CONFIG > ITSM Systems configuration > ITSM system > Work item > Fields.

Integration Framework

SC-1087

OdataService: Return request TM workflow level and status for getting quality aspects

Add level and status information in OData to get collisions

Ex.

• /sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet?$filter=Trkorr eq 'MDQK900091' &$expand=NavToCollisions,NavToDependency,NavToCritObj,NavToSpecialAspects
• /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet('MDQK900048')/TR_Collision

OData Services

SC-1198

Quality checks with a custom-specific Special Aspect

The new feature is used to add custom Special Aspects checks at the quality aspects check.

A new custom Special Aspect can be created in the template of the Special Aspects:

For the implementation please use new enhancement spot. /RTC/TM_IF_ES_CUSTOM_SA_CHECK. This is deliverd with example implementation /RTC/TM_IF_BIM_CUST_SA_CHECKEX.

BAdI, Quality Assurance

SC-1083

Improvement of the change of the license key in the TM Controller

With this feature if a temporary key for the installation is used and if later this should be changed to a perpetual or subscription one, the change can be done in the TM Server on System/Groups using “Change license key”.

This change will also change the local license key in the development system.

Configuration, TM Connectivity

SC-1131

Limit import tracking into the same system

Import in a system defined as production, in users and groups, will be possible only for the users with authorization for authority object ZRTC_TM with ID '/RTC/TM_AC' = ‘IT’. (The users without authorization will not see PROD system and client in the search help for the target system for the personal queue )

If the source and target system and client are the same a popup message will be displayed for confirmation of the selection.

Roles/Authorizations, Security, Tools

SC-261

Automatically update the whitelist entries for all ZRTC* RFC Connections

The transaction /RTC/SC_WHITELIST will be used to update whitelist information in TM/SYM RFC destinations.

The transaction should be called from TM/SYM server.

Security, TM Connectivity

SC-1110

Archive TM-History data

A new transaction /RTC/TM_ARCHIVE is used to archive TM history data.

The archived transports can be displayed from the transaction /RTC/TM menu:
SmartChange > Workflow > Archive

TM History

SC-877