...
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 |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-5535 Installation is reported as successful even if the platform fails to start |
...
| Page Properties | ||
|---|---|---|
| ||
Error Occurs When Performing Multiple Installations on a Host with Different UNIX User IDs
...
| Page Properties | ||
|---|---|---|
| ||
Unable to Upgrade When Using a Symbolic Link as MZ_HOME
...
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 | ||
|---|---|---|
| ||
...
Issues with HTTP Batch after Upgrading
When upgrading from MediationZone 8 to MediationZone 9, the upgrade process will result in numerous unused service contexts remaining from the previous installation. To clean up these unused contexts, use the following mzsh topo command to remove the redundant pico instances:
| Code Block |
|---|
mzsh topo unset ..../psc1
mzsh topo unset ..../sc1
mzsh topo unset ..../zk1 |
For more information on, refer to Removing Pico Configurations.
...
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 | ||
|---|---|---|
| ||
User Interface issues
New Desktop Issues
Database Agent Assignment Tab Value Are Not Cleared
...
| Page Properties | ||
|---|---|---|
| ||
Database Agent MIM Browser Need To Click Twice To Close It
...
| Page Properties | ||
|---|---|---|
| ||
External Reference Profile Datalist Can Be Altered in Read-Only Mode
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9054 [Vaadin] External Reference Profile edit values in read only mode |
...
| 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 | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8968?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 GUI Vaadin - Typ Assigned indication not shown in MIM browser, Edit Filename Template |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-7883?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 Idle timeout notification doesn't warn twice |
...
| Page Properties | ||
|---|---|---|
| ||
XE-7549 https://digitalroute.atlassian.net/browse/XE-7549?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 Vaadin seems to break when two platforms are running simultaneously |
...
| 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 |
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 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.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8109 DV vaadin source_node and message field filtering is case sensitive |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8271 Vaadin DV > Search/Filter > Not displaying query |
...
| 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
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9240?search_id=2d941f83-64ff-4eea-9e1d-be70c19b1049 Vaadin DV - New Restricted Fields that was Used for an Existing Repair Rule is still Editable when Editing Repair Rule |
...
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.https:
| Page Properties | ||
|---|---|---|
| ||
Duplicate UDR Inspector Didn’t Return Records Properly
...
| Page Properties | ||
|---|---|---|
| ||
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 | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8994?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 desktop_current.log spammed with exceptions when trying to disconnect from platform. |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8221 vaadin and swing > Duplicate execution day plan validation handling is inappropriate |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8932 Database Collection Agent - Validation Error message sounds weird |
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-8904?atlOrigin=eyJpIjoiMjBhNWIzMmFjMjdiNGE1YzhhZTE4YmM0ZjA0MDM4ZWYiLCJwIjoiZXhjZWwtamlyYSJ9 External Reference does not check if the key is used for all types |
Missing <Agent> - 5G <Field> Parameters in Workflow Table and Workflow Instance Table
The HTTP2_Server_1 - 5G - 5G Profile, HTTP2_Server_1 - 5G - Primary NRF Address, and HTTP2_Server_1 - 5G - Secondary NRF Addresses parameters in version 8.3.2.X are missing from the Workflow Table and workflow instance table when upgrading from version 8.3.2.1 onwards to MediationZone 9.
...
The '<agent> - 5G - <field>' parameters in version 8.3.2.X
This is because the three parameters are classified under a different sub-category, the '5G Support' as HTTP2_Server_1 - 5G Support - 5G Profile, HTTP2_Server_1 - 5G Support - NRF Address, and HTTP2_Server_1 - 5G Support - Secondary NRF Address.
...
The '<agent> - 5G Support - <field>' parameters in MediationZone 9
If the existing workflow contains these parameters from the older version, users are required to configure them under the new '5G Support' sub-category.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9275 Known Issue Documentation for 5G Primary & Secondary NRF Backward Compatibility in MZ9 & PE |
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”.
| Page Properties | ||
|---|---|---|
| ||
Keystore Information Is Gone After Imported Notification Workflow From MZ8.3
...
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”.
| Page Properties | ||
|---|---|---|
| ||
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.
| 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 | ||
|---|---|---|
| ||