Content Comparison

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

...

Page Properties
hidden true id versionDesc
Version 5.6.9.0 Date May 05, 2025 Description REALTECH SmartChange SP6 HF09 Features

...

3 Bugs 11

Release 5.6.9.0

Released on May 05, 2025

New Feature

Product Transport Management SmartChange

Priority	Title	Release Note	Components	Reference
	Integration Framework UPD action with no ticket assignment	In this updated version, the Skip UPD Actions When No Ticket Assignment Exists Across ITSM Types	The Integration Framework has been enhanced to skip UPD actions when no ticket assignment exists, across all ITSM types. This new functionality ensures that unnecessary updates are avoided, improving system efficiency and reducing processing time. No additional configuration is required for this feature, and it is automatically applied to all relevant processes.	Integration Framework	SC-1968
Error while releasing a transport	Enhanced Authorization Checks for External Users in TR_AssignReleaseSet	Authorization checks for /sap/opu/odata/RTC/TM_GW_SRV/TR_AssignReleaseSet have been refined to validate permissions against an external user. This enhancement ensures that external users are properly authenticated and authorized before accessing the TR_AssignRelease functionality, improving security and access control.	OData Services, Technical User Mapping	SC-1964

Product Transport Management

Priority	Title	Release Note	Components	Reference
Image Added	Improved Release Process for Transport Requests with Critical Object Checks in SmartChange Panel	A new functionality has been introduced to improve the release process of transport requests via the SmartChange Panel in SmartITSMIn this new version, when . When the 'Check Critical Objects' or 'Check Special Aspects' flags are set in transaction /rtc/tm_badi, attempting to release a transport request from ITSM containing these flagged objects does not trigger no longer triggers an error message anymore. If the release is performed directly in SAP, the QA Check screen appears will appear as usual, without errorany errors.	OData Services, Quality Assurance	SC-1952	Image Removed	Very often TM and necessary tasks are blocked, because of locks by other TM-Users	SC-1542	Image Removed	Enhance Odata service with External User for TR_AssignRelease	In this enhancement, authorization checks for /sap/opu/odata/RTC/TM_GW_SRV/TR_AssignReleaseSet have been refined to validate permissions against an external user.	SC-1964

Fixed Bugs

Product Transport Management

Priority	Title	Release Note	Release Note Solution	Components	Reference
	Short Dump at TR release related to critical objects At release of the Release request a shortdump is generated at critical objects checkPERFORM_PARAMETER_MISSING During Critical Objects Check When Releasing Transport Requests	Users experienced short dumps when releasing Transport Requests related to critical objects. The short dump occurred during the critical objects check due to incorrect parameters being submitted. This issue was identified in the program responsible for the critical objects validation, leading to runtime errors and preventing the successful release of Transport Requests.	The program has been corrected. The critical objects validation logic has been updated to handle parameters correctly, preventing short dumps during Transport Request releases.	Customizing, Quality Assurance	SC-1970
	TOC Log Double Entries	In previous versions, the Duplicate Entries in ToC Log	The ToC log contained duplicate entries in previous versions, causing confusion and difficulty in tracking changes accurately.	The program has been corrected.	Log, ToC	SC-1932
	Odata Service TR_Attribute is not working for modifiable requests when Trkorr is used in the filter	In previous versions, the OData Service TR_AttributeSet could not process modifiable requests via the GET method when the transport request was passed in the filter instead of being used as a key.	The program has been corrected.	OData Services	SC-1956	Image Removed	Desti and Project have the name fields iregular.	In the latest version, the short text field in the Project Management and Destination tabs has been extended to 60 characters.	UI	SC-1945	Image Removed	Wrong user assigned at TR creation with project/destination assignment using technical user	Bug: Incorrect User Logged for Project/Destination Assignment in Transport Request Creation using Technical User	When a Transport Request (TR) is created and both a project and destination are assigned during creation, the user recorded for the project/destination assignment is incorrect.Solution: Now, was incorrect. This issue occurred because the system was incorrectly logging the technical system user instead of the actual user who created the TR. The fix ensures that the user associated with the project/destination assignment will match now matches the user logged in the creation log, not the technical system userproviding accurate user tracking.	The program has been corrected.	Log, Technical User Mapping	SC-1961
	Odata Service to OData Service Fails to Retrieve CTS Projects Due to Inactive RFC Destinations	The OData service to retrieve CTS projects return returned an error , if when SC2015 systems are were connected to the latest version of SmartChange ControllerIf . This issue occurred if one of the RFC destinations is was not working THE Odata throws an error, The Odata is changed not to , causing the OData service to fail. The service has been updated to handle such scenarios gracefully, ensuring that it does not display an error and to show instead shows the CTS projects for all reachable DEV systems that can be reached.	The program has been corrected. The OData service now handles RFC destination failures gracefully, allowing retrieval of CTS projects for all reachable DEV systems without displaying an error.	OData Services, TM Connectivity	SC-1977
ToC returnes wrongly the error, that request has a different ticket ID, after ticket reassigning	TOC Returns Incorrect Error After Ticket Reassignment: Request Still Assigned to Old Ticket ID	Users experienced an issue while reassigning Transport Requests to a different ticket within the workflow management system. Although the reassignment appeared successful — with the updated ticket ID correctly reflected in the workflow monitor and attributes — an error occurred while creating a TOC. The system incorrectly reported that the Transport Request was still linked to the previous ticket ID.	The program has been corrected.	ToC	SC-1979
Image Added	Irregular Display of Destination and Project Name Fields Due to Inconsistent Field Length Handling	The name fields for Destination and Project were displaying irregularly, causing confusion for users. This issue occurred due to inconsistent handling of field lengths, leading to misalignment and truncation of names.	The program has been corrected. Field length handling has been standardized.	UI	SC-1945

Product SmartChange

Priority	Title	Release Note	Release Note Solution	Components	Reference
	Ticket GUID is displayed instead Displayed Instead of Ticket ID for ServiceNow in the Integration Framework Log for ServiceNow Tickets	Issue: The Integration Framework Log displayed the Ticket GUID instead of the Ticket ID for ServiceNow tickets. This is not the optimal way to visualize the ticket information.Solution: issue occurred when users accessed the log to review ticket information, leading to confusion and inefficiency. The log has been updated to display the Ticket ID, as it is already done aligning with the visualization method used for other ITSM systems.	The program has been corrected. The log now displays the Ticket ID instead of the Ticket GUID for ServiceNow tickets, reducing confusion for users.	Integration Framework, Log	SC-1942
	Short Dump GENERATE_SUBPOOL_DIR_FULL During Transport Request Creation in SAP Due to F4 Search Help fails to show more than 1000 results While Limitations with Jira Issues	Users experienced a short dump while creating a transport request in SAP , following short dump appears when using the F4 search help to look up the Jira Issue Number. The problem occurs issue occurred when there are were more than 1800 Jira issues available. For creating dynamic tables , SAP has a This problem is due to SAP's limitation of 36 subroutine pool generation limit in the create_dynamic_table method.	The program has been corrected.	Integration Framework	SC-1954
Image Added	OData Service 'TR_Attribute' Fails for Modifiable Requests When Trkorr Is Used in Filter	The OData Service TR_AttributeSet could not process modifiable requests via the GET method when the transport request number (Trkorr) was passed in the filter instead of being used as a key.	The program has been corrected.	OData Services	SC-1956

Product Synchronization Management

Priority	Title	Release Note	Release Note Solution	Components	Reference
	SYM: Maintenance view status not changed after import	Bug: Even after refreshing the screen, the object status TOBJ remained unchanged, leading to confusion about Maintenance View Status for TOBJ Not Updating Post-Import	The maintenance view status for the object TOBJ did not update after import, even when the screen was refreshed. This caused confusion regarding the actual import state. Fix: The The issue has been resolved, and the maintenance view now properly accurately reflects the updated status post-import without requiring manual intervention.	The program has been corrected.	Objects analysis, Synchronization, UI, Workbench	SC-1824
	TM/SYM: Mark as SYNC in TM when TR is not available in SyM Maint	Allow a transport to be marked as synchronised in TM only if there exists only one pair and the transport is Transport Synchronization Fails When Single Pair Marked as Finished in TM Tasklist	Users were unable to mark a transport as synchronized in TM if the transport was not available in SyM Maintenance. This issue occurred when there was only one pair, and the transport was marked as Finished in the tasklist in Synchronization Management. The system failed to recognize the transport status correctly, preventing synchronization.	The program has been corrected. The transport status recognition in Synchronization Management has been improved to allow marking as synchronized even when the transport is not available in SyM Maintenance.	Synchronization, UI	SC-1948

...