...
In MediationZone 9.2, there are the following known issues:
| Table of Contents |
|---|
Installation and Upgrade Issues
Unable to change platform database after installation
...
| Page Properties | ||
|---|---|---|
| ||
Unable to Upgrade When Using a Symbolic Link as the MZ_HOME
When a symlink is used as the MZ_HOME during an installation or upgrade, this will cause the operation to fail with the java.nio.file.FileAlreadyExistsException error.
This issue is caused by a bug as reported in [JDK-8294193] Files.createDirectories throws FileAlreadyExistsException for a symbolic link whose target is an existing directory - Java Bug System (openjdk.org). This bug is only fixed in JDK20.
To work around this issue, use the absolute path during an installation or upgrade and avoid using a symlink.
| Page Properties | ||
|---|---|---|
| ||
User Interface issues
New Desktop Issues
Database Agent Assignment Tab Value Are Not Cleared
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8712 when changing user you are logged into the last page used by the previous user |
Type Assigned Indication not Shown in MIM Browser
This can be viewed in the Legacy Desktop if required.
...
| Page Properties | ||
|---|---|---|
| ||
XE-8409 DV Repair Jobs > Repair Rule displays in 1 long string 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
| Page Properties | ||
|---|---|---|
| ||
XE-8973After collection radio buttons have incorrect behaviour |
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.
| Page Properties | ||
|---|---|---|
| ||
Analysis agent code completion doesn't work on a Mac GUI Vaadin - Analysis agent - vaadin - synchronized and internal functions not highlighted in APL Editor |
Known Differences Between Desktops
There are some known, minor issues with differences between the two Desktops.
| Page Properties | ||
|---|---|---|
| ||
GUI Vaadin - Agent Configuration - Logged MIMs not presented as a header. CSV DB profile Displayed in Config Selection Dialog in WebUI Encrypted profiles lacks key icon as in old Desktop |
Legacy Desktop Issues
In the Legacy Desktop an exception may occur when you first log in to the Platform. If you log in again the exception is not shown.
| Page Properties | ||
|---|---|---|
| ||
Exception when logging into the desktop |
Data Veracity issues
Data Veracity Search Filtering For Some Fields Are Case-Sensitive
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8274 Vaadin DV > Search > Add a rule with a empty group > Error |
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.
...
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.
| Page Properties | ||
|---|---|---|
| ||
Data Veracity New Restricted Fields That Were Used For An Existing Repair Rule Is Not Disabled
...
| Page Properties | ||
|---|---|---|
| ||
Other issues
Logging Issue
When logging out of the legacy desktop desktop_current.log has unnecessary logs added
...