REALTECH SmartChange SP6 HF04

Release 5.6.4.0

Released on Oct 24, 2024

New Feature

Product SmartChange
Priority Title Release Note Components Reference
High Jump to SNOW Ticket Using Item Type J2O A new feature enables users to navigate to a SNOW ticket using its GUID or ticket number based on the configuration of the J2S work item type:
  • If J2S is configured, the system redirects to the ticket using SYS_IC/GUID.
  • If J2S is not configured, the system reads the J2O entry and redirects using the SNOW ticket number.
Integration Framework, ServiceNow SC-1210
High Enhanced ServiceNow Integration Framework Templates with Reassign Function The ITSM ServiceNow (SNow) templates have been enhanced to include a reassign function. This enhancement introduces the ability to modify the project or destination using the action MODIF_TR, providing greater flexibility in managing assignments within the integration framework. Integration Framework, ServiceNow SC-1326
High Assignment Popup for ITSM Issues When Adding External Transport Requests In this version, transport requests can now be assigned to ITSM issues while being added to the TM Monitor via the "+" button.Steps to activate the feature:
  1. Ensure the ITSM system is correctly configured for the ADD2TM action.
  2. For adding transport requests previously assigned to a ticket, confirm the ITSM system is configured for the REASSIGN action.
Once transport requests are added to TM, the ITSM assignment popup will now appear on the screen.Additionally, a prior issue causing inconsistencies in TM attributes during ticket assignment for transport requests—released, re-added, and reassigned without initial ticket assignments—has been resolved.
Integration Framework, Workflow Monitor SC-1643
High OData: Enhanced Length of Collision Reason Field The maximum length of the reasoning field for collisions in the OData service has been increased to 200 characters, enabling more detailed input through OData interactions. OData Services SC-1777
Product Transport Management
Priority Title Release Note Components Reference
High Increased Length of Reasoning Field for Collisions The maximum length of the reasoning field for collisions has been increased to 200 characters, allowing users to provide more detailed explanations. Quality Assurance SC-1756
High Quality Assurance Popup: Display Release Date and Time in All Tabs The latest update introduces two new columns, "Release Date" and "Release Time," to the Collisions tab in the Quality Assurance popup. These additions provide users with a clearer and more detailed overview of release information directly within the tab. Quality Assurance, Release Management SC-1769
High Save and Cancel Functions Added to Release Management The Release Management transaction has been enhanced with a new Save button, enabling users to confirm and save multiple changes collectively before committing them. This improves data accuracy and provides better control over the release management process. Additionally, a Cancel option has been introduced, allowing users to discard unsaved changes if needed. Release Management, UI SC-1764
High Context-Based Display of TM Attribute Values in TM Workflow Screens The user exit WORKFLOW_01 has been enhanced to improve the handling of TM attribute values in the main workflow screen and the History screen. A new parameter, CONTEXT, has been introduced to differentiate between the two screens:
  • M for Monitor
  • H for History
This enhancement ensures that TM attribute values are correctly displayed based on the context from which the workflow is accessed.
TM Attribute, TM History, User Exits SC-1590
High Update TM Reset and TM Backup with New Tables The /RTC/TM_RESET report has been enhanced to include the latest development tables. Furthermore, a new table, /RTC/TM_RESET, has been introduced, enabling clients to specify tables within the RTC namespace that should not be reset when the report is executed. This provides greater flexibility and control over the reset process, ensuring critical data remains unaffected. TM Reset SC-1738
High Support for Tab-Delimited Files in Report /RTC/TM_GET_ATTRIB_FROM_EXCEL The report /RTC/TM_GET_ATTRIB_FROM_EXCEL has been enhanced to support tab-delimited files in addition to XLS files. Users can now upload data from tab-separated files, improving flexibility in file handling. Additionally, a search help has been added to assist users in selecting the appropriate file for upload. Tools SC-1798
High Create a release log A new release log feature has been implemented in the release screen to enhance tracking and transparency regarding transport requests (TRs) associated with each release.Log Information: The following details will be captured in the log:
  • Modification Date: The date on which the action was performed.
  • Modification Time: The exact time of the modification.
  • User: The user who performed the action.
  • Action: The specific action taken regarding the release.
Supported Actions: The log will track the following actions:
  • Creation of the release
  • Adding TRs to the release
  • Deleting TRs from the release
  • Closing the release
  • Reopening the release
  • Changing time of release
  • Changing date of release
  • Changing release name
SC-1721
High Check if all TRs have been imported before closing a TM release In the recent release, it has been implemented a new validation mechanism to ensure that all associated transport requests are successfully imported before allowing a Transport Management release to be closed. This enhancement prevents release closure if any transports are still pending, providing better control over the transport process and ensuring completeness. SC-1730

Fixed Bugs

Product Transport Management
Priority Title Release Note Release Note Solution Components Reference
High SE16 Permission Required When Releasing a Transport Request A bug was identified where the system triggered an additional standard authorization check for SE16 permissions when releasing a transport. This occurred due to an incorrect check for the TM BAdI activation status, which unnecessarily invoked SE16-related authorizations. The check for TM BAdI activation has been adjusted to prevent triggering additional standard authorization checks. The program has been corrected. BAdI, Roles/Authorizations SC-1795
High Msg Server Group Field Does Not Allow Lowercase Characters In the maintenance of Systems & Groups, the "Msg Server Group" field was incorrectly restricted to uppercase characters, preventing users from entering lowercase values. The program has been corrected to allow both uppercase and lowercase characters in the "Msg Server Group" field. Configuration SC-1808
High JIRA Actions Triggered Incorrectly Without Ticket Assignment JIRA actions were triggered even when ticket assignment was not mandatory, causing the URL to be constructed incorrectly and resulting in a web call error. Web calls for JIRA actions are now triggered only when a ticket assignment is present.
The program has been corrected.
Integration Framework, Jira_App SC-1761
High "Delete Personal Queue" Button Missing in Japanese An issue was identified where the "Delete Personal Queue" button was not displayed in the queue management system when using the Japanese language interface. This inconsistency has been resolved, and the button now appears correctly for users accessing the system in Japanese. The program has been corrected. Personal Queue, UI SC-1759
High Short Dump UNCAUGHT_EXCEPTION When Managing TM Releases Under Lock A short dump with error type UNCAUGHT_EXCEPTION occurred when users attempted to add or remove Transport Requests from Transport Management (TM) Releases while Release Management was blocked by another user. After a one-minute wait, the system displayed a correct error message indicating that the TM Releases feature was locked. However, dismissing the message caused the program to crash. This issue has been resolved, ensuring the program remains stable when the lock message is dismissed. The program has been corrected. Release Management SC-1775
High "Type" Field Not Populated During Excel Export A bug was identified where the "Type" field was not populated during data exports to Excel, resulting in incomplete export results. This issue has been resolved, and the "Type" field is now correctly included in all Excel exports. The program has been corrected. UI, Workflow Monitor SC-1794
High Empty Node Displayed for Modifiable Transport Requests In previous versions, empty rows were erroneously displayed in the "Modifiable Requests" tab of the TM Monitor. This issue has been resolved, and empty rows will no longer appear. The program has been corrected. Workflow Monitor SC-1762
Product Synchronization Management
Priority Title Release Note Release Note Solution Components Reference
High Missing Transport Requests in Detail Section When Task List Is Deactivated An issue was identified where Transport Requests were not shown in the detail section of the object view if they were not part of the Task List and the Task List setting was deactivated. This caused incomplete information, affecting the tracking and management of object versions. With this update, the detail section now includes Transport Requests that are not in the Task List when the setting is deactivated. These requests are marked with a red dash status icon for clear identification. The program has been corrected. Customizing, UI, Workbench SC-1705
High Request import did not work Upon attempting to import a transport request, no error message was displayed and the import process did not proceed. The issue was related to the source client of the external transport request being different from target client. Updating the SELECT statements on the relevant tables to ensure that they work in both cases. Synchronization, UI, Workbench SC-1778
Product SmartChange
Priority Title Release Note Release Note Solution Components Reference
High Track-It! Corrections and Enhancements
  • Track-It! Note for released transport requests now includes the program ID and object type of the associated object.
  • Track-It! Note for transport request import now includes the client number. Placeholder <CLIENT> was defined and adjusted in the IMP query.
  • The Track-It! template was updated to incorporate the client number.
  • During transport request import, the SID of the system is now retrieved from the most recent entry in the completed import table.
  • Search help entries no longer show duplicate results.
The program has been corrected. Integration Framework, Track-IT SC-1754
High Extended ITSM Logging Information for JIRA Issues The ITSM log for JIRA issues now includes the following details:
  • Item type
  • Item path
  • System ID
  • Transport level
  • Project
  • Destination
The program has been corrected. Integration Framework, Jira_App SC-1763
High Validation of Project/Destination Assignment for OData Service 'Release' To prevent project/destination assignment errors during the release of transport requests, the OData service TM_GW_SRV has been enhanced with additional checks:
  • The service validates whether the specified project/destination is allowed for assignment, as configured in the development system.
  • If the project/destination is not provided, the service determines the appropriate project/destination for the transport request.
  • If only one project/destination is identified, it is automatically assigned to the transport request before release.
Example API Call:PUT
/sap/opu/odata/RTC/TM_GW_SRV/TR_TO_TMSet(CrudMode='C',TransportReq='MT1K903723',ExternalUser='TestUser')
Payload:
{ 
  "ProjectName": "Realtech",
  "DestName": "default2001",
  "ExternalUser": "user"
}
The program has been corrected to ensure proper validation and automatic assignment of project/destination during transport request releases. Integration Framework SC-1779
High Incorrect Messages in OData QA Check for ToC Release Odata to do the QA check at the release for TOC.The check of ToC destination was corrected.The original transports can be from multiple ToC’s.Call ex./sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TR_RELSet?$filter=Trkorr eq 'MDQK900251,MDQK900184' and Toc eq 'X'&$expand=NavToCritObj,NavToSpecialAspects OData Services SC-1767