Open

In MediationZone 9.1, 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 doesn't contain any spaces before installing.

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.

Latest Oracle JDBC Driver Versions not Supported

Latest Oracle JDBC drivers such as version 21c and 23c are not supported in this release. Ensure to check the https://infozone.atlassian.net/wiki/spaces/MD91/pages/23363786 for information about supported Oracle database version.

Platform Instances and Runtime Data Need to be Removed Post Upgrade

Due to some issues with the Desktop cache, platform instances and runtime data must be cleared from the Desktop Launcher, see https://infozone.atlassian.net/wiki/spaces/MD91/pages/23144693.

Configuration History Loss After Upgrade from MediationZone 8

After upgrading from MediationZone 8, existing configuration history will no longer be available. This issue will be fixed in future releases.

Deleted Configuration History Unavailable After Upgrade from MediationZone 8

After upgrading from MediationZone 8, previously deleted configuration history in MediationZone 8 is no longer accessible in the Configuration Tracer. This issue will be fixed in future releases.

Only the first EC is started when multiple ECs are specified

When specifying multiple ECs during installation using a comma-delimited format (e.g., ec1,ec2,ec3), the installation completes successfully. However, only the first EC (ec1) is started post-installation. The remaining ECs are not started as expected.

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 is 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.

Integer Field Validation Can Be Broken

Inputing integer values outside of the expected range can break the validation in the UI.

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.

Config Locked by Same User

Under some circumstances, a configuration may be locked by the same user on the web desktop. The workaround could be open the legacy desktop to unlock it.

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 new web-native 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 In Web Native UI

The full filter query for Data Veracity is not available for viewing in the web UI. A partial display of the query can be seen in the filter listing under Data Veracity > Filter listing.

Open

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.

Open

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: