Version 5.6.8.0 Date Mar 31, 2025 Description REALTECH SmartChange SP6 HF08 Features 8 Bugs 11

Release 5.6.8.0

Released on Mar 31, 2025

New Feature

Product SmartChange

Priority	Title	Release Note	Components	Reference
	Dynamic Mapping of External Users to SAP Technical Users via BAdI /RTC/TM_IF_BD_MAP_EXT_USER	A new BAdI implementation, /RTC/TM_IF_BD_MAP_EXT_USER, has been introduced to dynamically determine the SAP technical user based on the external user of the connected ITSM system (e.g. Jira or ServiceNow). This is particularly relevant when actions are triggered from the ITSM system and executed in SAP via the SAP Cloud Connector. The enhancement enables accurate user mapping and supports proper authentication and authorization during integration.	BAdI, Log, OData Services	SC-1916
	Enhanced Navigation and Issue Retrieval for ITSM DOT4 Configuration	With this feature, the configuration for ITSM DOT4 has been updated to include the following actions: J2S (Jump to Ticket): Allows navigation to a DOT4 ticket using its URL. Can be configured with a tenantId as sub-item path. GET (Search for Issues): Retrieves the list of open DOT4 tickets. Can be used with or without the filter '?$orderby'.	DOT4, Integration Framework	SC-1645
	Enhanced DOT4 Template with GET and J2S Actions for Improved Data Retrieval and Reassignment	The DOT4 template has been updated to include the GET and J2S actions along with their respective fields in the ITSM systems configuration. This enhancement improves the integration framework by allowing more comprehensive data retrieval and reassignment capabilities. Template name: TEMPLATE_DOT4	DOT4, Integration Framework	SC-1768
	New DOT4 Integration Framework Template in TM Workflow Step Configuration for GET Actions	A new DOT4 template has been added to the TM Workflow step configuration for GET actions AFTER_WF_A, CREATION, and REASSIGN. This enhancement allows users to streamline their workflow processes by utilizing the predefined DOT4 template for these specific actions. Template name: TEMPLATE_DOT4	DOT4, Integration Framework	SC-1863
	Enhanced Filtering by "Reassign" Action in Jira Templates for SAP Integration Framework	In this new release, we've enhanced the templates for Jira Cloud and Jira DC to support filtering by the “Reassign” action filter (REALTECH Settings in Jira), which will take effect in SAP if the reassign feature is enabled. This is achieved by using the filter query. {{issue.property[tmFilter_REASSIGN].content ~ {PROJECT_KEY}}}. The placeholder {{{PROJECT_KEY} }} will be dynamically replaced with the current project if the transport request being reassigned is associated with a project.	Integration Framework, Jira_App	SC-1555
	External User Parameter Introduced in OData Services for Authorization and Logging via SAP Cloud Connector	All relevant OData entity sets in the RTC/TM_GW_SRV service have been enhanced to support an external user parameter, enabling seamless integration between an ITSM system (e.g., ServiceNow) and the SAP backend via the SAP Cloud Connector.This enhancement introduces a new mechanism to support user mapping: the external user—representing the actual end user from the ITSM system—is now passed to the SAP system and can be mapped to a corresponding SAP user using a newly provided BAdI. This ensures that authorization checks and logging are performed using the mapped SAP user, not the technical communication user.The external user parameter is now consistently available across the following entity sets: /sap/opu/odata/RTC/TM_GW_SRV/TR_ApproveSet /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet /sap/opu/odata/RTC/TM_GW_SRV/$batch /sap/opu/odata/RTC/TM_GW_SRV/TR_ReassignSet /sap/opu/odata/RTC/TM_GW_SRV/TR_TO_TMSet /sap/opu/odata/RTC/TM_GW_SRV/TOC_StartSet /sap/opu/odata/RTC/TM_GW_SRV/TR_AttributeSet /sap/opu/odata/RTC/TM_GW_SRV/TM_LicenseSet /sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TR_RELSet /sap/opu/odata/RTC/TM_GW_SRV/QA_TM_TRSet /sap/opu/odata/RTC/TM_GW_SRV/CTS_ProjectSet /sap/opu/odata/RTC/TM_GW_SRV/Proj_DestiSet Functional Highlights: All OData entity sets now support a standardized external user parameter. The external user represents the initiating ITSM system user (e.g., from ServiceNow). A new BAdI enables customizable mapping of the external user to an SAP user. All authorization checks are executed using the mapped SAP user. Logs and audit trails reflect the mapped SAP user. Enhances compliance, security, and traceability in hybrid SAP-ITSM system landscapes.	Integration Framework, OData Services	SC-1915
	Integration Framework Log with External User Info	External User field was found to be redundant, therefore it has been removed from the Integration Framework Log Report.	Integration Framework	SC-1940
	Enhance Integration Framework Log data for action "Move to History"	The Integration Framework's logging has been improved to now include details on the transport level , workflow project, workflow level and workflow destination when a transport is added to WF history.	Integration Framework, Log	SC-1941

Fixed Bugs

Product Transport Management

Priority	Title	Release Note	Release Note Solution	Components	Reference
	Transports Released Without Being Added to TM Still Appear in TM	Previously, when a transport release to a selected target route failed (e.g. due to technical errors or inactive/missing objects), the transport entry — including the selected project and destination route — was incorrectly retained in the /RTC/TM_BAD01 table.	The issue has been addressed, ensuring that any entry flagged in the /RTC/TM_BAD01 table is deleted when the transport is released without being added to TM.	BAdI, Loaders/Switchers	SC-1931
	Inconsistent Destination Order in Switcher Log Affecting Usability and Reliability	Users have reported inconsistencies in the Switcher log, specifically regarding the order of destinations. This issue affects the reliability and usability of the log, potentially leading to confusion when reviewing switching operations. The incorrect ordering of destinations may impact the ability to accurately track and analyze system behavior, causing difficulties in troubleshooting and maintaining system integrity.	The program has been corrected. The ordering logic for destinations in the Switcher log has been refined to ensure consistent and reliable tracking of switching operations.	Loaders/Switchers, UI	SC-1946
	Inconsistent Owner Assignment for Transport Requests	Users reported an inconsistency in the assignment of owners for automatically created Transport Requests in certain scenarios. This issue occurred specifically for Transport Requests that reached their destination system in later stages of a multi-step route. As a result, some Transport Requests were overlooked in process workflows due to view restrictions, while others were forwarded under incorrect user names.	The program has been corrected.	Loaders/Switchers, UI	SC-1947
	Incorrect User Shown for Released Transport Request in REALTECH Action Log	The action log for Transport Requests previously displayed an inconsistency where the same user was shown as both the creator and the releaser of a Transport Request, even when these actions were performed by different users. This issue has been resolved to ensure that the correct user information is displayed for each action.	The program has been corrected. The action log now accurately reflects the distinct users for the creation and approval of Transport Requests.	UI	SC-1906

Product SmartChange

Priority	Title	Release Note	Release Note Solution	Components	Reference
	J2S and J2O actions doen't consider the subpath of configuration	In previous versions, when clicking on a ticket ID in the TM monitor, the URL did not include the sub-item path configured for item types J2O and J2S.	The program has been corrected.	DOT4, Integration Framework	SC-1944
	Incorrect Action Log Displayed Due to Duplicate 'Release' Trigger in TM Workflow	The integration framework update action 'Release' was triggered a second time after adding a transport request to the TM workflow, resulting in an incorrectly displayed action log.	The program has been corrected. The action log display issue has been resolved by ensuring that the ‘Release' action is only triggered once per transport request. When adding transport request to the TM Workflow Monitor, the action “ADD2WF’ will be displayed.	Integration Framework, Log	SC-1864
	Centralized Placholder "Revoke Approval" for ITSM API Calls	In the previous version, when revoking an approval, automation placeholders were not populated correctly. Additionally, a new UPD action called “REVOKE_APP” has been introduced to distinguish between granting and revoking an approval.	The program has been corrected.	Integration Framework	SC-1936
	Double/Triple Execution of APPROVAL Action in TM Integration Framework	The APPROVAL action was executed multiple times in the TM Integration Framework instead of just once, resulting in multiple log entries.	The program has been corrected.	Integration Framework, Log	SC-1937
	ITSM System Fails to Update After Importing Multiple Transport Requests	The ITSM system was not being updated when multiple transport requests were imported simultaneously. This occurred due to missing transactional consistency after processing the imports.	The program has been corrected.	Integration Framework	SC-1950

Product Synchronization Management

Priority	Title	Release Note	Release Note Solution	Components	Reference
	Incomplete Display of Released Rollout Requests Due to Timeframe Filtering Issue	In the previous version, not all relevant released rollout requests were displayed according to the settings for the last number of days to display released rollout requests. This issue occurred when the system failed to filter and show the requests correctly based on the specified timeframe, leading to incomplete or missing entries in the display.	The program has been corrected.	Synchronization, UI	SC-1402
	Automatic Update to TM Fails After Synchronisation Management Synchronization Due to Event Linking Issue	When "Automatic synchronization" is set in TM Global settings in the TM Server it is created: the event 'Z_TM_SA_UPD_SYNCH'  an event trigger based job with same name 'Z_TM_SA_UPD_SYNCH' calling report /RTC/SC_TM_SYNC_FROM_SYM The Event being called has been corrected to use the “Z_TM_SA_UPD_SYNCH”.	The program has been corrected. The event 'Z_TM_SA_UPD_SYNCH' is now correctly linked to ensure automatic updates to TM after synchronization on SyM.	Synchronization, UI	SC-1949