REALTECH SmartChange SP7 HF03
Release 5.7.3.0
Released on Dec 05, 2025
New Feature
Product SmartChange
Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
Encrypted Storage of Client Secret in CTMS Configuration | Client secrets used by cTMS are now encrypted before being stored in the configuration table. The secrets are decrypted only at runtime by the application, ensuring improved protection of sensitive data against unauthorized access. | cTMS | SC-2272 |
Product Transport Management
Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
Remote Function Module for Project and Destination Assignment | A new remote function module (/RTC/TM_ASSIGN_PROJ_DEST) has been introduced to assign a project and destination to a modifiable transport request. The assignment updates database table /rtc/tm_mod_req by internally calling the remote function module /RTC/TM_SET_MODIF_TR. | Eclipse_Plugin | SC-2261 | |
Remote Function Module for Project and Destination List | A new remote function module (/RTC/TM_GET_PROJ_DEST) has been introduced to retrieve the list of projects and destinations for a modifiable transport request. | Eclipse_Plugin | SC-2262 | |
Enhancements for Transport Distribution at Import Using Report /RTC/TM_LD_10 | To enable transport distribution during import using report /RTC/TM_LD_10, table /RTC/TM_LO3 has been enhanced with new fields:
Distribution at approval and distribution at import are mutually exclusive and cannot be active at the same time. | Loaders/Switchers | SC-1270 | |
Status Switcher Allows Wildcard for Project and Destination | The Status Switcher (transaction /RTC/TM_SW) has been enhanced to allow the use of the wildcard character | Loaders/Switchers | SC-2270 | |
SmartChange Reporting Available as OData Service | TM Tools Reporting is now available as an OData service, providing SmartChange reporting data via a standardized interface. The service supports the original input parameters, returns results in JSON format, and includes pagination to efficiently handle large datasets.The OData service allows retrieval of lifecycle data with expandable entities such as Collisions, Documentation, Action Log, Notes, Import History, Attributes, and Objects.Supported filter option IncludeWf:
To retrieve generated HTML output, add Html to the $expand list.Example request URIs:
| OData Services | SC-2224 | |
Enhance SmartChange OData Collision Objects to Include Object Keys | The OData Collision Objects response has been enhanced to include object key details. This allows consumers of the SmartChange OData service to identify and analyze collision objects more precisely based on their specific object keys. | OData Services | SC-2246 | |
Automatic Deletion of Semaphores for Personal Queues | Semaphores created by monitoring or ping actions in personal queues are now automatically deleted, aligning their behavior with system queues. The retention period for automatic deletion can be configured in:Global Settings → Feature → Hours until auto delete semaphore | Personal Queue, Queues/Proposals, UI | SC-1999 | |
Warning Displayed for System Queue Import in Subset Mode When CTC Parameter Is Not Set | A pre-import validation has been introduced for system queue imports executed in subset mode. When the required CTC parameter is not set to the expected value, the system displays a warning indicating that the import cannot proceed. This validation prevents import execution with missing configuration and provides immediate feedback about required settings, reducing import failures and troubleshooting efforts. | UI | SC-253 | |
Warning Message for Package Deletion with Existing Dependencies | When deleting a package that contains Transport Requests with existing dependencies, the system now displays a warning dialog. The dialog informs users about dependent Transport Requests within the package and allows them to decide whether to keep or remove these dependencies before continuing with the deletion process.This enhancement prevents the creation of orphaned dependencies and removes the need for manual, one-by-one dependency handling after package deletion, improving overall operational efficiency. | Workflow Monitor | SC-2199 |
Product Synchronization Management
Priority | Title | Release Note | Components | Reference |
|---|---|---|---|---|
Automatic Adjustment of Tasklist Status After Importing Sync Requests | A new feature has been introduced to automatically adjust the tasklist status of transport requests after importing a Sync Request (SYNCxxxx). When enabled, the system evaluates all transport requests containing synchronized objects and automatically sets the tasklist status to green if all related objects have been successfully synchronized.The feature can be activated via: | Synchronization, UI | SC-769 |
Fixed Bugs
Product Transport Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Mass Revoke Approval only processes first user group | When revoking approvals for multiple transport requests, the mass revoke approval process handled only the first user group. Additional user group approvals were not processed, resulting in incomplete revocation of approvals across all assigned user groups. | The program has been corrected. | Approval, Workflow Monitor | SC-2267 | |
Wrong MT3MT2 Transuser Added to Table /RTC/TM_ALOG | In previous versions, an incorrect import user (MT3MT2 transuser) was recorded in table /RTC/TM_ALOG after a system queue import. As a result, the log entries did not reflect the actual user responsible for the import, leading to misleading audit information. | The program has been corrected. | Log | SC-2271 | |
OData Service “Get TR Object List” Returns Only First Table Key | The OData service “Get TR Object List” returned only the first table key for objects with multiple keys. This behavior was caused by incomplete key handling in the underlying function module /RTC/TM_OBJECT_LIST, resulting in incomplete object data being exposed by the service. | The program has been corrected. | OData Services | SC-416 | |
Short Dump “You Are Not Authorized to Logon to the Target System” in OData Service for Transport Creation and Release | When using the OData service to create or release transport requests, users encountered a short dump with the message “You are not authorized to logon to the target system.” The issue occurred due to missing checks for existing RFC destinations. In addition, during the release process, the client information was not consistently determined. | The program has been corrected. | OData Services | SC-2286 | |
Short Dump When Adding a Note to a Transport Request | After upgrading to a recent version, users encountered a short dump when attempting to add a note to a transport request. The error occurred during the note creation process, causing the system to terminate unexpectedly and preventing the note from being saved. | The program has been corrected. | UI, Workflow Monitor | SC-2264 |
Product Synchronization Management
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Failures in Analysis and BAdI Processing Depending on Logon Language | In Synchronization Management, system analysis and BAdI processing could show failures depending on the user’s logon language. This led to inconsistent analysis results and incorrect status checks across different language settings. | The program has been corrected. | BAdI, Customizing, Objects analysis, UI, Workbench | SC-2288 | |
Transport Request Missing in UMODE Selection Popup During Customizing Import | During Customizing import, the transport request was not displayed in the popup for UMODE selection. As a result, users could not select the required transport request when performing the import process. | The program has been corrected. | Synchronization | SC-2275 | |
Incorrect System Display in Global Settings for Automated Synchronization | In the Global Settings for automated synchronization, systems that were not associated with the selected development client were displayed. This led to inconsistent or incorrect system selection during customization of automated synchronization. | The program has been corrected. | Synchronization, UI | SC-2278 | |
Incorrect Status Display After Import When ENHO and ENHS Are Included | When a transport request contained both ENHO and ENHS objects for the same enhancement, the ENHO object was incorrectly displayed with a red status after transport synchronization. This led to an incorrect representation of the import result despite successful synchronization. | The program has been corrected. | UI | SC-1703 | |
Error When Saving Global Settings Due to User Validation | When saving Global Settings in the configuration module, users encountered an error caused by a validation check against referenced user records that did not yet exist in the system. This validation blocked administrators from saving configuration changes when users were pending creation or had been removed. | The program has been corrected. | UI | SC-2274 |
Product SmartChange
Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
Missing Fields in Table /RTC/TM_BTP_ROUT After Support Package Import | After importing a support package, required fields were missing in database table /RTC/TM_BTP_ROUT. This led to inconsistencies in data processing and unexpected behavior when accessing or updating entries based on this table | The table has been added to a new Transport Request | cTMS | SC-2249 | |
Imported SID Columns Missing When cTMS Configuration Is Active | When the Cloud Transport Management configuration was active, the Imported SID columns were not displayed in the TM Workflow Monitor. As a result, users could not view the system identifiers for imported transport requests. | The program has been corrected. | cTMS | SC-2273 | |
Alternative Function Module to Display Full cTMS Import Message | The function module previously used to display the full cTMS import message log (POPUP_DISPLAY_STRINGS) has been replaced with a HANA-compatible alternative. This change restores full visibility of the cTMS import message log in systems where the original function module is not available. | The program has been corrected. | cTMS | SC-2280 | |
System Queues Not Generated Correctly with Multiple Target Nodes | After approving a transport request, the Transport Management workflow generated only a single system queue even when multiple target nodes were configured. This resulted in incomplete queue creation and inconsistent transport propagation across the system landscape. | The program has been corrected. | cTMS | SC-2282 |
Powered by Automated release notes & reports for Jira