...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| Page Properties | ||||
|---|---|---|---|---|
| ||||
|
...
|
...
|
Release 5.6.7.0
Released on Feb 2127, 2025
New Feature
Product Transport Management
| Priority | Title | Release Note | Components | Reference | |||
|---|---|---|---|---|---|---|---|
 | Show authorized users for aproval in TM Monitor in the approvals tab even if the authorization are assigned via roles | The TM Display of Authorized Users for Approval in TM Monitor Approvals Tab | The TM Monitor Approvals tab now displays authorized users for approval, including those assigned via roles, when an approval type is selected. This enhancement ensures that all users with the necessary roles are visible in the approvals tab, improving transparency and ease of use in the approval process. | Approval, UI | SC-1677 | ||
| | Consider New Functionality to Ignore Collisions Based on TM Release in Collisions Check In this new version, users now have the option Quality Assurance Checks | A new functionality has been introduced that allows users to ignore collisions depending based on TM Release. An additional check has been added to under Quality Assurance → Collisions → Check Mode, which functions functioning similarly to the other existing checks for source system, client, destination, and project: | Quality Assurance, UI | SC-1786 | |||
| | Enhance Enhanced Import Job Log In this new version, the with Detailed Technical Insights for Improved Troubleshooting | The import job log has been enhanced to include more specific technical details, including such as connectivity checks. E.g. | Scheduler, UI | SC-1668 | |||
| | Log user which started the import Import History Log Displays User Who 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 the system queue is running as a job, the user of the running job is displayed. Example: Workflow Monitor > Request LifeCycle > Import History | TM Import, Workflow Monitor | SC-1842 | |||
| | Very often TM and necessary tasks are blocked, because of locks by other TM-Users | SC-1542 | | Problem with multiple clients using /RTC/TM_TRACKING2FILE and /RTC/TM Improved Multi-Client Support and Variant Management in /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
| Tools | SC-1841 |
Product Synchronization Management SmartChange
| Priority | Title | Release Note | Components | Reference | ||||
|---|---|---|---|---|---|---|---|---|
| DOT4 - Enhance log information | Extended ITSM Log Information with Additional Data Fields | ITSM log infomation was information has been extended with the following data:
| DOT4, Integration Framework | SC-1908 |  | SM: Workbench view - show Rollout where syncRequest object is included | Synchronization, UI, Workflow Monitor | SC-1292 |
| | 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 | ||||
| | 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:
| Synchronization | SC-1881 |
Product SmartChange
| Priority | Title | Release Note | Components | Reference | |||
|---|---|---|---|---|---|---|---|
| | Freshservice - Manually entered tickets will not be filtered | Tickets entered manually will bypass the filter set in the configuration. | Freshservice, Integration Framework | SC-1900 | |||
| | 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:
| Integration Framework | SC-1869 | |||
| | SNOW - Enhance log information | ITSM log infomation was extended with the following data:
| Integration Framework, ServiceNow | SC-1870 | |||
| | Track-It! - Enhance log information and Add new placeholders | ITSM log was extended with the following information:
| Integration Framework, Track-IT | SC-1871 | |||
| | Centralized Placeholder Handling for ITSM API Calls 2 | Manually Entered Tickets Bypass Automatic Filtering Rules in Freshservice | Manually entered tickets in Freshservice will now bypass the filter set in the configuration. This new functionality ensures that tickets created by users are not subjected to the automatic filtering rules, allowing for greater flexibility and control in ticket management. | Freshservice, Integration Framework | SC-1900 | ||
| | Dynamic Comment Placeholders for Jira Ticket Automation in Transport Requests | New placeholders are available for generating a dynamic comment to send to the Jira ticket using an automation rule:
| Integration Framework | SC-1869 | |||
| | Enhanced ITSM Log Information with Additional Tracking Fields for Improved Analysis | The ITSM log information has been extended to include additional data for improved tracking and analysis. The following fields have been added:
| Integration Framework, ServiceNow | SC-1870 | |||
| | Enhanced ITSM Log with Additional Placeholders for Improved Tracking and Analysis | The ITSM log has been extended to include additional information for better tracking and analysis. The new placeholders added are:
| Integration Framework, Log, Track-IT | SC-1871 | |||
| | Centralized Placeholder Data Retrieval for ITSM API Calls | A new class has been introduced to centralize the retrieval of placeholder data for ITSM-related API calls. This class ensures consistent and efficient handling of placeholders across various actions within the ITSM process.The following placeholders are now available:
| Integration Framework | SC-1882 | |||
| | New Custom F4 Search Help for POC users Custom Users Enhancing User Experience | A new custom F4 search help was created for POC User | Integration Framework | SC-1889 | has been created specifically for POC users. This functionality enhances the user experience by providing a tailored search help option, improving efficiency and ease of use for POC-related tasks. No additional configuration is required to enable this feature. | Integration Framework | SC-1889 |
| | Jira Automation Webhook - authentication with client secret All Rules Enhanced with Incoming Webhook Trigger | A new feature has been introduced for Jira automation rules containing an incoming webhook trigger. These rules will begin to now be routed through a different endpoint. A Additionally, 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 | HTTP Header can be maintained in view /RTC/TM_IF_WHEAD | Integration Framework | SC-1891 | |
| TM Integration Framework - Get TM attributes values | New Method for Selecting TM Attributes in Transport Requests via Sync Report | 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
| , enhancing the TM Integration Framework by allowing users to efficiently retrieve and manage TM attribute values associated with their transport requests. This new functionality aims to streamline the process of synchronizing transport request data with TM attributes, ensuring better data consistency and management. | Integration Framework | SC-1910 |
Product Synchronization Management
| Priority | TitleRelease Note | Release Note Solution | Components | Reference | | Translations needed for tasklist status details for Japanese | The program has been corrected. | Customizing, UI, Workbench | SC-1810 |
|---|---|---|---|---|---|
| | 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 |
| | New Filter by Object Functionality in Workbench View of Synchronization Management | 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 |
Fixed Bugs
Product Synchronization Management
| Priority | Title | Release Note | Release Note Solution | Components | Reference | ||||
|---|---|---|---|---|---|---|---|---|---|
| | 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. Missing Japanese Translation for Tasklist Status Details in Task Management Module | Users encountered issues with tasklist status details not being translated into Japanese. This problem occurred in the task management module, where status details were displayed in English instead of Japanese, causing confusion for Japanese-speaking users. The issue was due to missing translation entries in the language pack for Japanese. | The program has been corrected. Missing translation entries in the language pack for Japanese have been addressed. | DOT4 Customizing, Integration Framework, Jira_App, ServiceNow UI, Workbench | SC-1902 1810 | |||
| | 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 TM Workflow Synchronize Button Causes Short Dump Due to APCRFC_TRANSFORMATION_ERROR | Pressing the 'Synchronize' button in the TM Workflow previously caused the TM to terminate with a short dump. This issue occurred due to incorrect handling of synchronization parameters, resulting in an ABAP programming error. The specific runtime error was APCRFC_TRANSFORMATION_ERROR, and the short dump was generated in the ABAP Program /RTC/SAPLSA. | The program has been corrected. The handling of synchronization parameters has been fixed to prevent the APCRFC_TRANSFORMATION_ERROR short dump. | Integration Framework Synchronization | SC-1785 | | 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 issue1897 |
Product SmartChange
| Priority | Title | Release Note | Release Note Solution | Components | Reference |
|---|---|---|---|---|---|
| | Deletion of TM Release Does Not Update ITSM System Data | An issue was identified where the IT Service Management (ITSM) system was not updated when a TM Release was deleted from a transport request. While the system correctly updated upon release assignment, it failed to reflect deletions. | |||
| Priority | Title | Release Note | Release Note Solution | Components | Reference |
| | Transport request created with wrong ITSM name using Odata Service | The program has been corrected. | Integration Framework, Track-IT | SC-1839 |
Product Transport Management
| A trigger has been added to the deletion process to ensure the ITSM system receives the necessary updates when a release is deleted from a transport request. | DOT4, Integration Framework, Jira_App, ServiceNow | SC-1902 | ||||||||||
| | Incorrect ITSM Names in Transport Requests Due to Unconfigured ITSM ID Attribute in TM | Users were allowed to create transport requests from ITSM , using an ITSM ID attribute which that was not configured in TM. This resulted in transport requests being created with incorrect ITSM names. | The program has been corrected. Integration Framework, OData Services Transport requests will no longer be created using unconfigured ITSM ID attributes, preventing incorrect ITSM names. | Integration Framework, OData Services | SC-1315 | |||||||
| | 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! Incorrect Message Displayed During Ticket Assignment When RFC Destination is Missing | When the RFC destination is not found, users encountered an incorrect message during ticket assignment. This issue occurred because the system failed to properly handle the missing destination scenario, leading to confusion among users. The error has now been corrected to display an appropriate explanatory message, ensuring clarity during the ticket assignment process. | The program has been corrected. Integration Framework, Track-IT The system now properly handles missing RFC destination scenarios and displays an appropriate explanatory message during ticket assignment. | Integration Framework | SC-1801 1785 | ||||||
| | 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. 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, ServiceNow, Synchronization Track-IT | SC-1901 1801 | ||||||
| | 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 | | 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 Missing Integration Framework Log Entry for Track-It! During Authentication Failure | An Integration Framework log entry was not created for Track-It! during an authentication issue. This problem occurred when the system failed to authenticate user credentials, resulting in no log entry being recorded to indicate the authentication failure. This made it difficult to diagnose and troubleshoot authentication problems effectively. | The program has been corrected. Integration Framework now logs authentication failures for Track-It! to facilitate troubleshooting. | Integration Framework, Track-IT | SC-1839 |
| | Inconsistent Retrieval of Transport Requests by Ticket ID in ITSM Synchronization Report | 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. This issue occurred due to an error in the search algorithm, which did not account for all possible Ticket ID formats. | | Propsal job is deleted | The program has been corrected | Loaders/Switchers | SC-1909 | 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 search algorithm has been updated to accommodate all possible Ticket ID formats. | Integration Framework, ServiceNow, Synchronization | SC-1901 |
Product Transport Management
| Priority | Title | Release Note | Release Note Solution | Components | Reference | |||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| | Project and Destination Fields Missing in ITSM After Transport Request Release | 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. Queues/Proposals . The Project and Destination fields now display correctly in the ITSM system after releasing the Transport Request. | Jira_App | SC-1448 1877 | |||||||||||||||
| | 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 | | 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 Status Switcher Handling with Wildcard | 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. | UI Loaders/Switchers | SC-1887 1909 | ||||||||
| 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 | Unable to Change Priority in Quality Assurance/Collisions Settings | Users were unable to change the priority of the exceptions in the Quality Assurance/Collisions settings. Although the priority selection was displayed, it did not allow modifications. This issue occurred due to a missing update in the user interface logic that failed to register the changes made by users. | The program has been corrected. | SC-1896 | | 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 | | Priority cannot be changed | Users were unable to change the priority of the The user interface logic has been updated to allow modifications to the priority of exceptions in the Quality Assurance/Collisions settings. The priority selection was displayed but did not allow modifications. The program has been corrected. | Quality Assurance | SC-1904 | | 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 | Proposal Conflict Leading to Job Deletion When Scheduling Simultaneous Proposals | Users experienced an issue when creating two proposals scheduled for the exact same time, which resulted in a single job being generated for both. If one of the proposals was deleted, the associated job was also removed, causing the remaining proposal to lose its scheduled job. | The program has been corrected. The scheduling logic for proposals has been updated to ensure that multiple proposals can coexist without conflict. | Queues/Proposals | SC-1448 | |||||||||||||||
| | Short Dumps When Calling Function Module /RTC/TM_CHANGE_LICENSE_KEY in SC2015 System | Users experienced short dumps when calling the function module /RTC/TM_CHANGE_LICENSE_KEY in the SC2015 system. The issue occurred in a mixed landscape, where adding a 2015 system with System * Groups was impossible. The dump was caused by incorrect handling of system group parameters during the function module call. | The program has been corrected. The handling of system group parameters during the function module call has been fixed to prevent short dumps. | Security | SC-1896 | |||||||||||||||
| | Loss of Non-ITSM Attributes During Transport Request Reassignment in TM | Previously, when a modifiable Transport Request (TR) had additional attributes besides ITSM attributes, these attributes were lost during the reassignment process in Transport Management (TM). This issue occurred because the reassignment function did not properly handle the preservation of non-ITSM attributes, leading to data loss. | The program has been corrected. The reassignment function now properly preserves non-ITSM attributes during the Transport Request reassignment process. | TM Attribute, Workflow Monitor | SC-1905 | |||||||||||||||
| | RFC Connection Errors Due to Missing Function Module /RTC/TM_IF_GET_RFC_DEST in Mixed Landscape Environment | The function module /RTC/TM_IF_GET_RFC_DEST was called with RFC in a mixed landscape environment including both 2019 and 2015 systems. The function module does not exist in the 2015 system, causing the call to be ignored and resulting in connection errors. | The program has been corrected. The function module call has been adjusted to handle mixed landscape environments more effectively, preventing connection errors. | TM Connectivity | SC-1913 | |||||||||||||||
| | Incorrect Error Flagging in Transport Environment Check Due to Locked or Unavailable Systems | 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. This issue caused confusion as it did not accurately reflect the status of each system. The error occurred in the transport environment check process, leading to incorrect error messages and misidentification of system statuses. | The program has been corrected. The transport environment check process has been updated to accurately reflect the status of each system, preventing incorrect error flagging for subsequent systems when one is locked or unavailable. | UI | SC-1887 | |||||||||||||||
| | Error Saving Modified TM Attributes for Modifiable Transport Requests Due to Action Log Failure | An error occurred when saving the modified TM attributes for modifiable Transport Requests (TRs). The action log was not saved, which prevented the changes from being recorded properly. This issue was identified during the modification process, causing inconsistencies in the attribute data. | The program has been corrected. The action log saving mechanism for modified TM attributes in Transport Requests has been fixed to ensure proper recording of changes. | SC-1899 |
Powered by Automated release notes & reports for Jira