...
In MediationZone 9.1, there are the following known issues:
| Table of Contents |
|---|
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 feature issue will be available in 9.2 releasefixed in future releases.
| Page Properties | ||
|---|---|---|
| ||
DOC: Known Issue |
...
| Page Properties | ||
|---|---|---|
| ||
Latest Oracle JDBC Driver Versions not Supported
Latest Oracle JDBC drivers such as version 21 21c and later 23c are not supported in this release. Ensure to check the System Requirements for information about supported Oracle database version.
| 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
...
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.
| Page Properties | ||
|---|---|---|
| ||
External Reference Profile Datalist Can Be Altered in Read-Only Mode
...
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 Removing Instances and Runtime Data.
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.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9054 [Vaadin] External Reference Profile edit values in read only mode |
Login Web UI Will Go To Last Page That Last User Accessed
...
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-8712 when changing user you are logged into the last page used by the previous user |
Integer Field Validation Can Be Broken
...
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.
| Page Properties | ||
|---|---|---|
| ||
XE-8980 Web UI Integer field breaks with values going over integer limits |
Type Assigned Indication not Shown in MIM Browser
This can be viewed in the Legacy Desktop if required.
| Page Properties | ||
|---|---|---|
| ||
XE-8968GUI Vaadin - Typ Assigned indication not shown in MIM browser, Edit Filename Template |
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.
| Page Properties | ||
|---|---|---|
| ||
XE-7883 Idle timeout notification doesn't warn twice |
Cannot Login to Multiple Platforms
...
https://digitalroute.atlassian.net/browse/XE-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-8712 when changing user you are logged into the last page used by the previous user |
Integer Field Validation Can Be Broken
Inputing integer values outside of the expected range can break the validation in the UI.
| Page Properties | ||
|---|---|---|
| ||
XE-8980 Web UI Integer field breaks with values going over integer limits |
Type Assigned Indication not Shown in MIM Browser
This can be viewed in the Legacy Desktop if required.
| Page Properties | ||
|---|---|---|
| ||
XE-7549 Vaadin seems to break when two platforms are running simultaneously |
Data Veracity Repair Jobs Show in One Line
...
8968GUI Vaadin - Typ Assigned indication not shown in MIM browser, Edit Filename Template |
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.
| 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
...
7883 Idle timeout notification doesn't warn twice |
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.
| Page Properties | ||
|---|---|---|
| ||
XE-8973After collection radio buttons have incorrect behaviour |
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.
...
7549 Vaadin seems to break when two platforms are running simultaneously |
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.
| 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 | ||
|---|---|---|
| ||
| Page Properties | ||
XE-8988 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.
8973After collection radio buttons have incorrect behaviour |
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.
| Page Properties | ||
|---|---|---|
| ||
XE-8936GUI Vaadin - Agent Configuration - Logged MIMs not presented as a header.8988 Analysis agent code completion doesn't work on a Mac XE-7196 CSV DB profile Displayed in Config Selection Dialog in WebUI Encrypted profiles lacks key icon as in old Desktop |
Legacy Desktop Issues
...
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 | ||
|---|---|---|
| ||
XE-8934 Exception when logging into the desktop |
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 |
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.
...
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
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-8271 Vaadin DV > Search/Filter > Not displaying query |
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.
...
8109 DV vaadin source_node and message field filtering is 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.
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-82748271 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.
Example error during import:
|
Example error when viewing the invalid workflow Analysis Agent configuration:
|
/Filter > Not displaying query |
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.
...
| 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.
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 Filter Are Not Refresh 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 Not Disabled
...
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-9240 Vaadin DV - New Restricted Fields that was Used for an Existing Repair Rule is still Editable when Editing Repair Rule |
Other issues
Logging Issue
When logging out of the legacy desktop desktop_current.log has unnecessary logs added
...
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 |
SAP CC Notification Agent TLS Feature Not Working
The fields in SAP CC Notification Agent Configuration for configuring TLS connection are, Enable Secured Connection, Keystore Path, and Keystore Password. These fields should not be enabled and used for now as it will cause the agent to fail to connect to the SAP CC server.
| Page Properties | ||
|---|---|---|
| ||
https://digitalroute.atlassian.net/browse/XE-10946 SAP CC notification TLS is not working |
The Aggregation Inspector Does not Work with Aggregation Profiles Using External References
...
The Aggregation Inspector Does not Work with Aggregation Profiles Using External References
If you have an Aggregation profile using External References, the session data will not be visible in Aggregation Inspector. To solve this, you can update the Aggregation profile to not use External References once the session data has been made available, the data will then be visible in Aggregation Inspector.
| Page Properties | ||
|---|---|---|
| ||
File Storage Aggregation Data not Removed when Modifying Profile
If you have an Aggregation profile with File storage selected and select to change the Storage Host or the Directory, or change to a different storage type, you will have to manually remove data. However, if this is done in the Legacy Desktop, data will automatically be removed.
| Page Properties | ||
|---|---|---|
| ||
Open API Incorrectly Validates Request Body
Users are encountering an issue with request body validation when using a schema file that includes discriminator and oneOf keywords in the same schema object. This issue arises due to a limitation in the library implementation.
There is an existing ticket logged on this issue, see https://bitbucket.org/atlassian/swagger-request-validator/issues/771/discriminator-is-not-working-with-oneof. To work around this issue, you can disable request validation for requests containing the schema object.
| Page Properties | ||
|---|---|---|
| ||
File Storage Aggregation Data not Removed when Modifying Profile
...
Data Hub Workflow Aborts With “NoClassDefFoundError”
Users might encounter a “NoClassDefFoundError” in Data Hub Forwarding agent in MediationZone9.1.1. This is caused by an unintentional removal of a library dependency. To resolve this, the change will be reverted in the subsequent service pack release of MediationZone 9.1.
| Page Properties | ||
|---|---|---|
| ||