Versions Compared

Old Version 4

changes.mady.by.user REALTECH Automation AI

Saved on

compared with

New Version 5

changes.mady.by.user REALTECH Automation AI

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated by Automated release notes for Jira

...

Bugs

PriorityKeySummaryStatus
Medium SC-174 Issue:
If a new level and status is selected, the TRs are displayed for the selected level, but for previous status.

Root cause:
Programming error; the filter for new status is not performed.

Solution:
The program has been corrected. 		Done
Medium SC-171 Issue:
The e-mails are also sent to users of User Groups where the approver of the previous step is included.

Root cause:
Programming error;the User Group where the current user is included was not taken into consideration.

Solution:
The program has been corrected. 		Done
Medium SC-169 Issue:
Errors 'UUID for Object not found'should notoccur.

Root cause:
Programming error

Solution:
The program has been corrected. 		Done
Medium SC-168 Issue:
Too many lines in Collect Job log of IQ LIB for the same object

Root cause:
All errors are displayed for an object key.

Solution:
The program has been corrected. The modification will prevent a log with too many information for an object and will only display the first error for the object, because following errors are usually dependent on the first error. 		Done
Medium SC-164 Issue:
The Object Comparison display is not working for CDS View objects.

Root cause:
The report to display the differences could not be found,because it was searched with object type instead of data pointer.

Solution:
The program has been corrected. 		Done
Medium SC-65 Issue:
The Object Comparison (Expert Mode) is not working for CDS View objects.

Root cause:
The structure with object information is not found.

Solution:
The program has been updated. 		Done
Medium SC-62 Issue:
In Import Scheduler, when the button 'Select System Queue(s)'is pressed, not all SID and transport levels are displayed.

Root cause:
This was due to a program error.

Solution:
The program has been corrected. 		Done
Medium SC-61 Issue:
The import of the transport request terminates with short dump DBIF_DSQL2_OBJ_UNKNOWN, for program /RTC/SA_SWITCH_TO_UNICODE.

Root cause:
This was due to a program error.

Solution:
The program has been corrected 		Done
Medium SC-60 Requirements:
To be able to sort ascending/descending after SIDs/TM Levels

Issue:
Currently, the users cannot sort in Import Scheduler window after SID/TM Levels.

Root cause:
Functionality not implemented

Solution:
Two new buttons were added to the ImportScheduler window, in order to sort ascending/descending after SIDs/TM Levels. 		Done
Medium SC-31 Requirements:
Starting with SAP NW 7.4 EHP7, there is an available function in SE10, 'Simulate Release', which performs all checks prior to a release, without performing the actual release.

Issue:
New functionality added by SAP, not handled in TM

Root cause:
The standard BADI Before Release is executing during the checks,and TM functionality is executed, inserting the corresponding TR entry in table /RTC/TM_BAD01, even though the TR will not be released.

Solution:
The program has been adjusted. 		Done
Medium SC-29 Issue:
The personal queue display is stuck after finishing the import, due to an automatic refresh of the screen.

Root cause:
If personal queue contains more than 50 entries, the screen is stuck after finishing the import.

Solution:
The program has been corrected by eliminating the automatic refresh. The user has to refresh the queue manually. 		Done
High SC-21 Issue:
The transport with object type VARX will change the original system from DEV to MAINT at synchronization.

Root cause:
The object cannot be found in the original system.

Solution:
The program has been corrected. 		Done
Critical SC-2 Requirements:
In TM, at Content Approval, the notification mail should be sent to all users which are authorized to perform the Technical Approval (next step).
Issue:
In TM, if the user which performs the Content approval has also authorization for technical approval, notification mails will not be sent.

Root cause:
Spam e-mails are avoided if current user has authorization to perform the next step.

Solution:
A new field has beenadded to table /RTC/TM_OPT named SEND_ALL_MAILS. In order to activate the feature request the value for this field should be set to 'X'. 		Done

...