REALTECH SmartChange SP5 HF05

In the latest update, the 'Approve' button is now hidden in the detailed view of the approvals window once all approvals or revokes have been granted, providing a cleaner and more intuitive user experience.

In the latest update, a new ToC configuration option called 'ToC Selection' has been added under SmartChange -> Settings -> Global -> Features. This option empowers users to choose whether a single or multiple transport requests can be selected for the TOC process.

With this new feature, users can now add up to 20 additional columns in the TM Workflow Monitor, 10 of which can be of type text and 10 of type icon. Previously, the limitation was a maximum of 10 columns, with 5 being text and 5 being icon.

In the latest version, the 'Push notifications' option located under SmartChange > Settings > Global > Default User Settings has been renamed to 'Mobile/Web App Notifications'.

In this update, the OData service for creating transport requests has been extended to identify the connection of tickets/changes of the ITSM systems with GUID. For example in ServiceNow: when users create transports from ServiceNow, the GUID is used to identify incidents/changes. The OData service creates a new transport request and also stores the GUID as an SAP attribute for ServiceNow transports.

With the creating or releasing transport requests (TR), all relevant projects and destinations are displayed, with the exception of those intended for fast-tracking.
When fast-tracking was introduced, only fast-track projects were displayed if all objects of the transport are listed in the "Allowlist Objects". This behavior has been changed and the fast track projects are displayed in addition to the other projects and destinations.

In this version, the descriptions for the "Simulate Collisions" options have been updated to enhance clarity and understanding. The changes are as follows:

Simulate collisions (EN):

Kollisionen prüfen (DE):

The checks before TM Destination deletion have been improved. Now, when deleting a logical destination, the system verifies if there are any (released) transport requests in the TM Workflow Monitor. This check has been expanded to include modifiable transport requests as well. This enhancement was essential because when activating the ToC process it is already possible to assign project/destination when creating transport requests

In the latest update, the system now prevents users from assigning transport requests to destinations that are not allowed based on the transport request type. Additionally, error handling for duplicate TRs has been enhanced. Previously, duplicates were initially displayed as valid, but the system now promptly indicates the error status for any duplicate requests.

The TM Integration Framework configuration templates have been enhanced with a new entry for configuring Service Now Change Requests.

New template: TEMPLATE_ SNOW_CHG

With this new feature, TM Integration Framework supports connection to a Jira Data Center server using OAuth 2.0, Authorization Code flow.

In the most recent update, the TM IF configuration was enhanced with three new fields to facilitate the selection of the Authentication Method.

The first field enables users to choose between Basic and OAuth Authorization, while the other two fields are dedicated to OAuth 2.0 Client Profile (for saving Scopes such as WRITE) and OAuth 2.0 Client Configuration Name (for storing Client ID, Client Secret, Token Endpoint, Authorization Endpoint, etc.).

Introducing a new tool for checking printer availability in the latest version. This tool enhances printer management by automating lock/unlock actions based on printer connection status. Systematic logging of changes provides a result list for periodic background jobs. A test checkbox enables users to simulate lock/unlock actions without execution, while the delete option allows for selective removal of entries from the activity log table.

Unable to render embedded object: File (7b189968-3072-42ce-9ba2-8e1ffb5c4fb3#media-blob-url=true&id=c3dc1018-b926-4b65-b994-47057c526c11&collection=&contextId=16425&height=427&width=956&alt=) not found.

Dump may occur during update in the shadow instance when TM is active.

The program has been corrected.

In the latest update, users encountered missing information when performing the transport directory check, especially if changes were not saved in the database.

The program has been corrected.

The tab previously named "Uncritical Objects" has been renamed to "Allowlist Objects" in quality assurance.

The program has been corrected.

Users encountered difficulties when attempting to add new entries to the "Allowlist Objects" section specifically at the system level.

The program has been corrected to enable the creation of new entries within the "Allowlist Objects" section at the system level.

In the previous version, the 'System and Groups' tab allowed case-sensitive creation of groups, leading to duplication when assigning systems. This resulted in new uppercase groups forming alongside empty ones.

The program has been corrected.

When using the 'Maintain client(s)' function in the 'System and Groups' configuration, users encountered an error in the previous version. After maintaining the client(s), the SID disappeared, leaving the clients without an SID. Consequently, the configuration became broken and required redoing.

The program has been corrected.

In earlier versions, the setting 'If import job has an error' in the Default Users Settings tab was initially empty instead of being pre-filled with the default value “Deactivated” when users opened the global settings for the first time.

The program has been corrected.

The report encountered errors due to changes in the included standard code of S4HANA 2023.

The program has been corrected to address the compatibility issues with the updated standard code.

In earlier versions, a dump could occur when creating a transport request via SE10 in the development system and selecting Solution Manager in the ITSM Dialog pop-up. If the "Check" button was pressed without selecting any item, a dump occurred.

The program has been corrected to prevent dumps when the "Check" button is clicked without any item selected in the ITSM Selection Popup.

In the latest version, the report /RTC/TM_FILL_MOD_TR, which retrieves all modifiable transport requests (TRs) for Transport Management (TM), now provides an enhanced output log containing processed data when executed as a background job.

The program has been enhanced to include processed data in the output log for the /RTC/TM_FILL_MOD_TR report when executed as a background job.

Users attempting to add external attributes to transports may encounter an issue where no action is taken without any notification provided. This occurs due to the inability to add external attributes to a transport, leading to confusion among users.

In the latest update, a pop-up message has been implemented to inform users when attempting to add external attributes to transports. This notification will clarify that adding external attributes to transports is not supported, helping users understand the limitation and avoid confusion.

In the Web GUI TM Workflow Monitor, the tree display was readjusted after every action in the initial display, causing inconvenience to users as the column width changed frequently.

The program has been corrected to retain the column width changes for the tree in the current session.

An issue occurred where the OData service for creating transport requests (TRs) allowed the entry of incorrect TM project and destination values. This caused inconsistencies in the TR creation process. To address this, an additional check for TM project and destination validity was implemented in the OData call for transport creation.

If the TmProject and TmDesti are specified this should exist in TM project and shouldn’t be locked.

URL: /sap/opu/odata/RTC/TM_GW_SRV/Transport_RequestSet

HTTP Method: POST

Body:

{"Trfunction":"T",
 "As4text":"Test ODATA",
 "As4user":"USER",
 "Externalattribute":"ITSMid",
 "Externalid":"TicketID",
 "TmProject":"BASIS",
 "TmDesti":"DEFAULT200",
 "Devsystem":"MDD",
 "Client":"200"
}

The OData service now includes an additional check to validate the TM project and destination specified during transport creation. If the TM project and destination provided in the request are not valid or are locked, an error will be returned, preventing the creation of the transport request with incorrect values.
The program has been corrected.