...
In MediationZone 9.3, there are the following known issues:
| Table of Contents |
|---|
Installation and Upgrade Issues
Unable to Change Platform Database After Installation
...
If the MZ_HOME path contains spaces the installation will fail. Please ensure the MZ_HOME does not contain any spaces before installing.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8655 Installation isn't possible if MZ_HOME path contains a folder name with spaces |
...
To avoid encountering this error during installation or upgrade, you should use an absolute path instead of a symlink for the MZ_HOME directory. This is no longer required as of 9.3.1.0.
| Page Properties | ||
|---|---|---|
| ||
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.
| Page Properties | ||
|---|---|---|
| ||
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.
...
| hidden | true |
|---|
...
Issues with HTTP Batch after Upgrading
When upgrading from MediationZone 8 to MediationZone 9, there are the following issues with the HTTP Batch agent:
In MediationZone 8, the HTTP Batch agent has a non-standard way to configure keystore information where instead of referencing a file on disk, the full file content is kept in the configuration. Currently there is no way to configure this in the same way in MediationZone 9.
If you configure a keystore in MediationZone 8, either in the profile or in the agent, the certificate handling will be completely disabled, and all server certificates are accepted. This is different compared to the REST client agent where the profile/keystore is used as both keystore and truststore.
| Page Properties | ||
|---|---|---|
| ||
External Reference Profile Datalist Can Be Altered in Read-Only Mode
...
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.
| Page Properties | ||
|---|---|---|
| ||
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.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9054 [Vaadin] 8872 |
External Reference Profile
...
Login Web UI Will Go To Last Page That Last User Accessed
...
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.
| 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.
9054 [Vaadin] External Reference Profile edit values in read only mode |
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.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8968?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 GUI Vaadin - Typ Assigned indication not shown in MIM browser, 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 | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8968?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 GUI Vaadin - Typ Assigned indication not shown in MIM browser, Edit Filename Template |
Idle Timeout Only Warns the User Once
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/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 | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8973?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 After 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 |
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.
...
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.
| Page Properties | ||
|---|---|---|
| ||
Data Veracity New Restricted Fields That Were Used For An Existing Repair Rule Is Not Disabled
...
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.
| Page Properties | ||
|---|---|---|
| ||
...
| Page Properties | ||
|---|---|---|
| ||
Other issues
Logging Issue
...
Monitoring Tab with Unused Configurations
Monitoring tab configurations were included into the agent, but without any actual implementations. To be removed.
| Page Properties | ||
|---|---|---|
| ||
Other issues
Logging Issue
When logging out of the legacy desktop desktop_current.log has unnecessary logs added
...
| Page Properties | ||
|---|---|---|
| ||
Keystore Information Is Gone After Imported Notification Workflow From MZ8.3
...
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.
| Page Properties | ||
|---|---|---|
| ||
Overwrite After Collection Disabled in Workflow Table of Workflow Properties
Users might encounter this issue when using a workflow configuration that uses SFTP Agent exported from MediationZone versions prior to MediationZone 9.3.0.4. This impacts SFTP Agents configured with the Default Collection Strategy and with the After Collection option set to either Move To or Rename. This issue occurs for workflow configurations that have not been modified since import.
To resolve this, edit the workflow configuration (e.g. move an agent slightly) and then save the configuration. The Overwrite After Collection workflow property will now be configurable.
| Page Properties | ||
|---|---|---|
| ||