Version 5.6.7.0
Date Feb 21, 2025
Description REALTECH SmartChange SP6 HF07
Features 18
Bugs 17

Release 5.6.7.0

Released on Feb 21, 2025

New Feature

Product Transport Management
Priority Title Release Note Components Reference
High Show authorized users for aproval in TM Monitor in the approvals tab even if the authorization are assigned via roles The TM Monitor Approvals tab now displays authorized users for approval, including those assigned via roles, when an approval type is selected. Approval, UI SC-1677
High Consider TM Release in Collisions Check In this new version, users now have the option to ignore collisions depending on TM Release. An additional check has been added to Quality Assurance → Collisions → Check Mode, which functions similarly to the other checks for source system, client, destination and project: Screenshot (699).png Quality Assurance, UI SC-1786
High Enhance Import Job Log In this new version, the import job log has been enhanced to include more specific technical details, including connectivity checks. E.g. Screenshot (704).png Scheduler, UI SC-1668
High Log user which started the import In this new version, the import history log displays the username of the user who initiated the import via the system queue. If system queue is running as job, the user of the running job is displayed. Example:
Workflow Monitor > Request LifeCycle > Import History Screenshot (689).png 		TM Import, Workflow Monitor SC-1842
High Very often TM and necessary tasks are blocked, because of locks by other TM-Users SC-1542
High Problem with multiple clients using /RTC/TM_TRACKING2FILE and /RTC/TM_ADD2PQUEUE The report /RTC/TM_ADD2PQUEUE has been optimized to properly support multiple clients during the transfer of import information to the TM personal queue. Key Enhancements
  • Source/Target Variant Management:
    Users can now create and save a Source/Target Variant, which is stored in a database table for future use.
  • Variant Assignments:
    Each variant defines the mapping of source systems/clients from which transport requests will be added to the target systems/clients' personal queue.
  • Listbox Selection:
    When executing the report, users can easily select a saved variant from a listbox, eliminating the need for manual entry.
  • Toolbar Menu Updates:
    The interface now includes three action buttons for efficient variant management:
    • Create a new Source/Target Variant.
    • Edit an existing Source/Target Variant selected from the listbox.
    • Delete a selected Source/Target Variant from the listbox.
User Instructions
  1. Open the Create a Source/Target Variant screen by clicking the corresponding toolbar button
  2. Enter a Variant Name in the designated input field and press Enter.
  3. Define the Source and Target (SID and Client) assignments for transport requests.
image-20250207-085619.png
  1. To add additional Source/Target assignments, click the Add New Line button
  2. Use the toolbar buttons to delete a line or confirm the variant once all assignments are defined.
  3. When running the report, select a saved variant from the listbox to streamline transport request processing.
  		SC-1841
Product Synchronization Management
Priority Title Release Note Components Reference
High DOT4 - Enhance log information ITSM log infomation was extended with the following data:
  • Item type
  • Item path
  • System ID
  • Transport level
  • Project
  • Destination
 DOT4, Integration Framework SC-1908
Medium SM: Workbench view - show Rollout where syncRequest object is included Synchronization, UI, Workflow Monitor SC-1292
Medium SM: Workbench view - Create new filter for objects in SyncRequests/Rollouts A new filter by Object has been introduced in the Workbench view of Synchronization Management, working the same way as the filter by Object in the Customizing view. This filter allows users to display only requests that include the selected objects in the request tree and can also be saved as a variant for future use. Synchronization, UI, Workflow Monitor SC-1357
High CLONE - Synchronization Transport sequence check (corrections) With this feature, you are now able to see if objects from current transport are synchronized in the right order. If there are previous transports not synchronized for the object, or a newer transport was already synchronized for the object corresponding messages will be displayed:
  • 'Previous TRs have not been synchronized yet. Do you want to continue?'
  • 'Latest version has already been synchronized. Do you want to overwrite?'
 Synchronization SC-1881
Product SmartChange
Priority Title Release Note Components Reference
High Freshservice - Manually entered tickets will not be filtered Tickets entered manually will bypass the filter set in the configuration. Freshservice, Integration Framework SC-1900
High JIRA - Enhance ITSM API Call Messages New placeholders are available for generating a dynamic comment to send to the Jira ticket using an automation rule:
  • <TRKORR>: Transport request number
  • <LEVEL>: Transport request level name
  • <OBJ>: Objects included in the transport request (to be implemented for Track-It)
  • <CLIENT>: System ID
  • <APP_TYPE>: Client
  • <APP_TYPE>: Approval type
  • <USER>: User who granted the approval
  • <ACTION> - Action Name
  • <ACTION_DESC> - Action Description
 Integration Framework SC-1869
High SNOW - Enhance log information ITSM log infomation was extended with the following data:
  • Item type
  • Item path
  • System ID
  • Transport level
  • Project
  • Destination
 Integration Framework, ServiceNow SC-1870
High Track-It! - Enhance log information and Add new placeholders ITSM log was extended with the following information:
  • Item type
  • Item path
  • System ID
  • Transport level
  • Project
  • Destination
 Integration Framework, Track-IT SC-1871
High Centralized Placeholder Handling for ITSM API Calls 2 A new class has been introduced to centralize the retrieval of placeholder data for ITSM-related API . This class ensures consistent and efficient handling of placeholders across various actions within the ITSM process.The following placeholders are now available:
  • <TRKORR>: Transport request number
  • <LEVEL>: Transport request level name
  • <OBJ>: Objects included in the transport request (to be implemented for Track-It)
  • <CLIENT>: System ID
  • <APP_TYPE>: Client
  • <APP_TYPE>: Approval type
  • <USER>: User who granted the approval
  • <ACTION> - Action Name
  • <ACTION_DESC> - Action Description
 Integration Framework SC-1882
High F4 Help for POC users Custom F4 search help was created for POC User Integration Framework SC-1889
High Jira Automation Webhook - authentication with client secret All Jira automation rules containing an incoming webhook trigger will begin to be routed through a different endpoint. A new view has been created to maintain the HTTP header and new placeholders are available for generating a dynamic comment to send to the Jira ticket. Integration Framework SC-1891
High TM Integration Framework - Get TM attributes values A new method has been developed to select TM attributes for a list of Transport Requests. This method will be triggered by the Sync report Integration Framework SC-1910

Fixed Bugs

Product Synchronization Management
Priority Title Release Note Release Note Solution Components Reference
High Translations needed for tasklist status details for Japanese The program has been corrected. Customizing, UI, Workbench SC-1810
High Short dump when using 'Synchronize' in TM workflow In the previous version, pressing the 'Synchronize' button in the TM Workflow caused the TM to terminate with a short dump. The program has been corrected. Synchronization SC-1897
Product SmartChange
Priority Title Release Note Release Note Solution Components Reference
High Deletion of TM Release doesn't update ITSM system data Users have reported an inconsistency in the automatic updating of the IT Service Management (ITSM) system when managing Transport Management releases. While the ITSM system is successfully updated when a release is assigned to a transport request, it fails to update when a release is deleted from a transport request. The program has been corrected. DOT4, Integration Framework, Jira_App, ServiceNow SC-1902
High Display wrong message at ticket assignment, if destination is not found If the RFC destination is not found, an explanatory message is displayed during ticket assignment. The program has been corrected. Integration Framework SC-1785
High Integration Framework log entry is not created for Track-It! during an authentication issue An Integration Framework log entry is recorded for Track-It! in during an authentication issue. The program has been corrected. Integration Framework, Track-IT SC-1839
Product Transport Management
Priority Title Release Note Release Note Solution Components Reference
High Transport request created with wrong ITSM name using Odata Service Users were allowed to create transport requests from ITSM, using an ITSM ID attribute which was not configured in TM. The program has been corrected. Integration Framework, OData Services SC-1315
High Modifiable transport requests is deleted without a Note in Track-It! When a TR is deleted from SE10, a new note is created in Track-It! The program has been corrected. Integration Framework, Track-IT SC-1801
High ITSM Synchronization report doesn't retrieve all transport requests when searching by 'Ticket ID' Users experienced inconsistencies when using the ITSM Synchronization report to retrieve Transport Requests. The report failed to display all associated Transport Requests when searching by Ticket ID, leading to incomplete data retrieval. The program has been corrected. Integration Framework, ServiceNow, Synchronization SC-1901
High Project and Destination fields missing in ITSM system after update from Release or Change of Modifiable Transport An issue was reported where the Project and Destination fields did not appear in the IT Service Management (ITSM) system after releasing the Transport Request. However, once the Transport was transferred in TM, the fields displayed correctly in the ITSM system. The program has been corrected. Jira_App SC-1877
High Status Switcher Translation and Handling Users encountered difficulties when configuring project destinations in the Status Switcher. The system required individual entry of all target paths in a project, which was time-consuming and prone to errors. In the new version, this limitation has been removed, users can now use '*' for the destination, ensuring all destinations are automatically considered. The program has been corrected Loaders/Switchers SC-1909
Medium Propsal job is deleted Users experienced an issue when creating two proposals scheduled for the exact same time. Results in a single job being generated for both. If one of the proposals is deleted, the associated job is also removed. The program has been corrected. Queues/Proposals SC-1448
High At reassignment of modifiable TR's the additional attributes are lost Previously, when a modifiable TR had additional attributes besides ITSM attributes, these attributes were lost during the reassignment process in TM. The program has been corrected. TM Attribute, Workflow Monitor SC-1905
High System and Groups check shows wrong info Users have reported inaccuracies in the System and Groups check. During the transport environment check, if a system is locked or unavailable, all subsequent systems are incorrectly flagged as errors. The program has been corrected. UI SC-1887
High The shortdump occurs at call of FM /RTC/TM_CHANGE_LICENSE_KEY in SC2015 system Issue: In a mixt landscape, adding a 2015 system with System * Groups was impossible. The program has been corrected. SC-1896
High Error at saving of modifiable attributes Error in saving the modified TM attributes for modifiable TR’s.The action log wasn’t saved. The program has been corrected. SC-1899
High Priority cannot be changed Users were unable to change the priority of the exceptions in the Quality Assurance/Collisions settings. The priority selection was displayed but did not allow modifications. The program has been corrected. SC-1904
High call FM /RTC/TM_IF_GET_RFC_DEST connection error not handled The FM /RTC/TM_IF_GET_RFC_DEST is called with RFC in a mixt landscape 2019 with 2015 and the FM doesn’t exist in 2015 and will be ignored. The program has been corrected. SC-1913

 

Powered by Automated release notes & reports for Jira