REALTECH SmartChange SP4 HF06

Delete transport request from the queue through the 'SyM analysis Failed' window

This release adds a feature enabling users with the 'ZRTC_SA' ID: '/RTC/SA_09' Field 'QUE' authority to delete transports from the "/RTC/SA_TRKORR" table directly through the "SyM Analysis Failed" window. The Advanced List Viewer (ALV) now allows users to select multiple entries for deletion, and an extra delete button has been added for this purpose.

Customizing, Objects analysis, UI, Workbench

SC-1242

New action "Reassign" in TM Workflow Monitor

We are delighted to introduce a new feature that allows you to reassign a transport request to a new ITSM/Ticket through the TM Monitor. This option is visible only if the TM Integration Framework is active and can be used at any point in the workflow for released requests, via a right click on a single transport request.
The feature "Reassign" is available for ITSM types Jira and Solution Manager.

Prerequisites

In order for the feature to work properly, certain prerequisites must be met.

TM IF configuration
Following actions must be configured for both current and new ITSM system.

1. GET/REASSIGN (Reassign TR to a different [ITSM] ticket
2a. UPD/LINK_EXT (Link external transport)
2b. UPD/DEL_LINK (Delete link external transport)

The template entries can be copied and used as reference.

Authorization

SAP: The current user must have the TA authorization (Maintenance of TM attributes)
ITSM: The communication user (maintained user in the RFC connecting to the ITSM) must have proper rights to the new Ticket.

Functionality

When pressing the ‘Reassign’ function in TM Monitor for released transports, the popup to assign/reassign ticket id is displayed with configured ITSM IDs of action GET/REASSIGN. If the request is currently assigned to an ITSM, only ITSMs of the same type will be displayed. If reassignment is allowed for multiple ITSM systems, then the ITSM system which is currently assigned will be automatically selected.

The GET/REASSIGN action can be configured multiple times, allowing you to set different filter queries depending on Transport level, Project and Destination.

Example:

Troubleshooting

If an error occurs during the update calls to the ITSM(s), the calls are saved for later recall via transaction /RTC/TM_IF_MONITOR. The update can be triggered either manually or automatically (job schedule or subsequent update calls triggered by working with the specific transport request in TM Monitor. like approve, import, or switch status).

We hope you enjoy this new feature and find it useful in your workflow!

Integration Framework

SC-918

Display request details icons for modifiable requests

Display the buttons in ‘Request header’ tab for modifiable request. The buttons have the same functions as for released transports.

UI, Workflow Monitor

SC-1288

Enhance TM Integration Framework Template for the new action 'Reassign'

The Jira TM Integration Framework configuration template have been enhanced with two new actions REASSIGN (Reassign TR to a different [ITSM] ticket) for Item type ‘GET’ and DEL_LINK (Delete Link external transport) for Item type ‘UPD’. REASSIGN allows users to reassign transport requests in the TM Workflow Monitor and DEL_LINK allows users to delete the assignment of a transport request to a ticket. The new Reassign functionality is now available for ITSM types Jira and Solution Manager. Support for Service Now will be available in future releases.

Template entries for the new Reassign functionality

Jira templates: TEMPLATE_ JIRA CLOUD, TEMPLATE_ JIRA SERVER

GET/ REASSIGN - Reassign transport request to a different [ITSM] ticket
For all released transport requests existing in the TM workflow (Transport level = *, Project = *, Destination = * )

UPD/ DEL_LINK - Delete the assignment of a transport request to a ticket

Solution Manager templates: TEMPLATE_ SOLMAN_SMIN, TEMPLATE_ SOLMAN_SMIR

GET/ REASSIGN - Reassign transport request to a different [ITSM] ticket - for all released transport requests existing in the TM workflow (Transport level = *, Project = *, Destination = * )

Integration Framework

SC-1323

Missing button description after confirming collisions in Quality Assurance

When a transport has collisions, critical objects, or any other issue requiring approval, a pop-up window appears to approve them Once the corresponding button is selected, the button description will no longer be displayed.

The program has been corrected.

Quality Assurance, UI

SC-1310

Unexpected running of TM-Coding when releasing a transport from DEV system

Avoid the call of the function /RTC/TM_GET_MODIF_TR when SmartChange Transport Management is not active.

The program has been corrected.

Security

SC-1321

Jump to the ITSM ticket is not working for modifiable requests

On TM Workflow Monitor, in the modifiable request tab, clicking on ITSM Ticket ID is not jumping to display the ticket.

We have fixed an issue in the TM Monitor modifiable request tab, where clicking on the ITSM Ticket ID was not displaying the ticket as intended.
The program has been corrected.

Workflow Monitor

SC-1289

Avoid obsolete functions detected by the Panaya tool

SmartChange code contains calls to standard SAP function modules which are marked as obsolete.

SmartChange has been updated to replace the standard SAP function modules marked as obsolete. The function modules TABLE_COMPRESS and TABLE_DECOMPRESS have been replaced by the class /RTC/SC_CL_COMPRESS methods TABLE_COMPRESS and TABLE_DECOMPRESS.

Security

SC-1269

Wrong user when displaying syncRequest information on Maint

Once displaying Transport Request information on standard transaction via the double click of syncRequest on customizing view, the user is not authorized to do anything because it is using the ZRTC_SA_ADM user. The user doing this step was changed with the current user like in Workbench View.

The program has been corrected.

Synchronization, UI

SC-1293

No error message when calling /RTC/SA and user missing the authorization /RTC/SA_CON in the development system

When we want to check the object analysis in SYM and role /RTC/SA_CON is not assigned to the user in the development system the action is not performed because of missing authorization and no error message is displayed.

We have implemented an improved error message to more clearly inform the user when an action cannot be performed due to a missing authorization. This will allow users to more quickly identify the reason for their lack of access and take action accordingly.

UI

SC-869