In MediationZone 9.3, there are the following known issues:
Installation and Upgrade Issues
Unable to Change Platform Database After Installation
It is not possible to change platform database after the installation is completed which used to be a feature that available since 8.x. This issue will be fixed in future releases.
Installation Is Not Possible if MZ_HOME Path Contains a Folder Name with Spaces
If the MZ_HOME path contains spaces the installation will fail. Please ensure the MZ_HOME does not contain any spaces before installing.
Installation is Reported as Successful Even if the Platform Fails to Start
In some circumstances during installation the installer may report as successful when the platform has not started.
Warning Messages Displayed During Installation
When the user performs “setup.sh prepare”, a warning message “setSecurityManager will be removed in a future release" is displayed. This does not impact functionality of MZ 9 installation and will be handled in future versions of MZ.
Error Occurs When Performing Multiple Installations on a Host with Different UNIX User IDs
The /tmp/syslog/syslog-debug.log file is created when a host machine contains an MZ 9 installation. This file will be overwritten by any subsequent MZ 9 installations that are performed on the same host machine with a different UNIX user ID. However, the attempt to overwrite this file will fail and cause errors to the subsequent installations.
To solve this issue, modify the platform.xml file setting by using the mzsh topo open platform command. Edit the platform.xml file, and change the directory to use another directory using the following command: <property name="mz.syslog.debuglogfile.filedir" value="[the directory]"/>.
Unable to Upgrade When Using a Symbolic Link as MZ_HOME
Users are encountering issues with symlinks when using them as MZ_HOME during an installation or upgrade due to the java.nio.file.FileAlreadyExistsException error.
This issue arises from a bug reported under [JDK-8294193] Files.createDirectories throws FileAlreadyExistsException for a symbolic link whose target is an existing directory - Java Bug System (openjdk.org) and has been fixed in JDK 20.
To avoid encountering this error during installation or upgrade, you should use an absolute path instead of a symlink for the MZ_HOME directory.
User Interface issues
New Desktop Issues
Database Agent Assignment Tab Value Are Not Cleared
When Value Type is set to "To UDR" or "NULL", the Value column are not cleared.
Database Agent MIM Browser Need To Click Twice To Close It
The MIM browser open from database agent, need to close it by hitting twice on cancel button or the X button to close it.
External Reference Profile Datalist Can Be Altered in Read-Only Mode
When certain procedures are made, it is possible to alter the data list found in the external reference profile while the read-only mode is used. This causes a system-wide DRRCPException to be thrown.
Login Web UI Will Go To Last Page That Last User Accessed
User A log out from web UI, and User B login, it will automatically go to the page last accessed by User A.
Type Assigned Indication not Shown in MIM Browser
This can be viewed in the Legacy Desktop if required.
Idle Timeout Only Warns the User Once
Inactive users will be logged out after a configurable period, following a warning to that effect. If a user is active after the warning they won't be logged out, but if they are inactive again then they will be logged out with no warning.
Cannot Login to Multiple Platforms
It is not currently possible to login to multiple separate platforms using the new UI in one browser. Users can use different browsers, incognito modes, or the Legacy Desktop if this is required.
Data Veracity Repair Jobs Show in One Line
When viewing the repair jobs in the new UI they are displayed in one line which is hard to read.
Accessibility Issues
The new web-native desktop aims to be fully accessible, but there are currently some outstanding issues regarding this. These include:
In some interfaces, the keyboard navigation doesn't follow the ideal order or convention
Incorrect behavior of radio buttons
Code Editor Issues
The code editor in the desktop provides code completion and syntax highlighting there are some known issues with syntax highlighting not being correct, it is not possible to add tabs to code and code completion cannot be activated on a Mac if multiple keyboard layouts are enabled.
When attempting to use the code completion function in agents or profiles, for example, the Analysis agent, the built-in keyboard shortcut of Command + Space on a Mac computer will not trigger the code completion dialog box.
Known Differences Between Desktops
There are some known, minor issues with differences between the two Desktops.
Data Veracity issues
Data Veracity Search Filtering For Some Fields Are Case-Sensitive
The filtering for the source_node and message fields in the Data Veracity Search & Repair table are case-sensitive.
Data Veracity Filter's Full Query Is Not Available on Desktop
The full filter query for Data Veracity is not available for viewing on the Desktop. A partial display of the query can be seen in the filter listing under Data Veracity > Filter listing.
Adding an Empty Query Group With A Parent Condition In Data Veracity Search & Repair Filter Will Result In An Error
Attempting to add an empty query group with a parent condition will cause an error to be thrown upon clicking OK. A sample of the query setup is shown below.
Importing Old Data Veracity Collection Agent Workflow Configurations Returned Validation Errors
If you have an old Data Veracity Collection Agent Workflow configuration from version 8.x, it is possible that validation errors about invalid Analysis Agents may occur.
Example error during import:
|
Example error when viewing the invalid workflow Analysis Agent configuration:
|
To resolve this, you will need to re-add the Data Veracity UDR for Analysis Agent input UDR Types or use the Set To Input button if applicable. After adding the appropriate Analysis UDR Types, save the workflow configuration.
Data Veracity Filters Are Not Refreshed Automatically
The Filter page is not always the latest, after creating a new Filter from the Data Veracity Search page, you may need to click the Refresh button to view it.
Data Veracity New Restricted Fields That Were Used For An Existing Repair Rule Is Not Disabled
If setting a new restricted field that was used in a previously created Repair Rule, it is expected that the rule on the said field should be grayed out when viewing the saved Repair Rule and be ignored when applying repair tasks.
This is not the case as the rule on the said field still appears to be editable in the old Saved Repair Rule.
Duplicate UDR issues
Duplicate UDR Inspector Stuck Loading When Attempting To Delete Records
When a Duplicate UDR profile is being used by a running workflow, attempting to delete any records for that profile in Duplicate UDR Inspector would cause the Inspector to be stuck loading.
System Log Shows Unknown User On Deleting A Record In Duplicate UDR Inspector
After deleting any records in Duplicate UDR Inspector, the log message in the System Log, will show the Username as <Unknown>.
Duplicate UDR Inspector Allows To Delete Records Without Profile Locking
Currently, when executing a workflow using the Duplicate UDR profile, the profile remains unlocked, allowing for the deletion of records from the Duplicate UDR Inspector.
Duplicate UDR Inspector Didn’t Return Records Properly
With certain search date criteria in Duplicate UDR Inspector, some records are not returned.
Duplicate UDR MIMs Shows 0
Duplicate UDR Inspector shows these MIMs as 0 even when there are Duplicate UDR caught.
Dup_UDR_1.dups UDRs
Dup_UDR_1.Inbound UDRs
Dup_UDR_1.Outbound UDRs
Dup_UDR_1.r_3 UDRs
Incorrect Handling When Duplicate UDR Process Old Data With System Arrival Time
With the SQL Storage Duplicate UDR profile set to use System Arrival Time, UDRs with dates older than the system time on the Platform will not be handled properly. The Duplicate UDR Inspector will not display any data despite the UDRs being processed.
When using File Storage Duplicate UDR profile with System Arrival Time as well, you might see Records and Duplicates as 0 in the legacy desktop Duplicate UDR Inspector.
Duplicate UDR Inspector Table Header Row Count Is Not Updated When Records Found Is 0
When searching a profile that has no records after previously searching with a profile that has any records, the table header would still display previous row count.
Rename Duplicate UDR Profile Doesn’t Auto Reflect In Duplicate UDR Agent
When renaming a Duplicate UDR profile in the configuration browser, the Duplicate UDR agent that is using this profile is does not refresh with the new name automatically. This does not affect the workflow when executing with the profile.
Exception Thrown When Truncating Previous Tables After Changing DB Profile In Duplicate UDR Profile
Upon saving a copy of Duplicate UDR profile A to another Duplicate UDR profile. Changing the DB profile to a different schema and clicking on Yes at the confirmation message to truncate previous tables would lead to an exception error.
File Directory Is Not Empty When Delete Duplicate UDR File Storage Profile
When deleting a Duplicate UDR File Storage profile and choosing Yes to delete relational data, the system will fail to empty the File Directory.
Reference Data Management
Reference Data Management Table Shows No Data And All Functions Are Locked
After searching in Reference Data Management with any number of results on the table, navigate away from Reference Data Management to another page.
Navigate back to Reference Data Management and click on Get Started.
Once the Query dialog is opened, refresh the page, and click on Query to select the same profile and table and the apply, you would find that table is now empty, and all functions are locked.
Import/Export Ongoing Process Are Not Aborted When Navigating Away From Reference Data Management
Running import/export processes are not aborted when navigating away from the Reference Data Management page.
SAPCC Rest Agent
Unable To Post Through Istio
Currently posting to SAPCC Rest API through SAPCC Rest agent will gets backend error.
Unable To Add Additional Parameter In Desktop Online Workflow Page
In Desktop Online Add/Edit Workflow page, click on the Add button for Additional Parameters field, we will see the pop up missing Key and Value fields, so currently user is unable to add Additional Parameters in Workflow page. However, user can add Additional Parameters in Legacy Desktop.
Workflow Unable To Rollback To Default Values
Set agent fields to Default in Workflow Properties, and enter some data into let’s say a textfield and save it. Then edit again to remove data in this textfield, workflow template will throws validation error that the workflow is invalid. This happened to checkbox and some other fields as well.
Other issues
Logging Issue
When logging out of the legacy desktop desktop_current.log has unnecessary logs added
Error Thrown When SAPCC Agent Not Added With Any Host
In the SAP CC Batch agent, do not add any host, click the Save As button, and you will find the error shown below:
java.lang.NullPointerException: Cannot invoke "String.matches(String)" because "hosts" is null
Inappropriate Validation Handling On Workflow Group Scheduling
In Workflow Group Scheduling, when adding a duplicate execution day plan, it prompts the wrong validation message content and if the user continues to save, scheduling data will be wiped off.
Database Forwarding Agent Validation Message
In Database Forwarding Agent, when we have a field NULL/To UDR, the validation message that prompted does not properly describe the problem.
External References Can Be Removed when a Workflow is Dependent on It
External references of the type Database Properties can be removed even if they are in use. Any workflows using these references will become invalid.
Incorrect HTTP Status Code in Error Response in Operations REST API Workflow
In the error response, the HTTP status code displayed in the “status” field is incorrect. You are required to refer to the “detail” field for the correct error code.
In the example above, the correct error in the workflow is “HTTP 404 Not Found” and not “500”.
Keystore Information Is Gone After Imported Notification Workflow From MZ8.3
System Import Notification Workflow from MZ8.3, found that Keystore information in the SAP CC Notification agent is gone.