In MediationZone 9.1, there are the following known issues:
Installation and Upgrade Issues
Installation Is Not Possible if MZ_HOME Path Contains a Folder Name with Spaces
If the MZ_HOME path contains and spaces the installation will fail. Please ensure the MZ_HOME doesn't contain any spaces prior to installing.
Installation Reported as Successful Even if the Platform Fails to Start
In some circumstances during installation the installer may report as successful when the platform has not started.
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.
Cached Instance of Legacy Desktop Generates Error when Logging in After Upgrade
If you try to open the Legacy Desktop using java -jar on http://localhost:9000/launch/desktop/launcher after having upgraded from MediationZone 9.0 to 9.1, the old instance will have been cached generating an error when you log in.
To solve this, you can delete the old instance by right-clicking the instance and selecting Delete in the popup menu
and then create a new instance with the same URL.
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.
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.
New Profile Becomes Read Only on Save
When creating a new profile as soon as it is saved it becomes read only. The user needs to click the edit button in order to continue editing.
Aggregation Inspector Pagination Fails on Very Large Files
With particularly large files the Aggregation Inspector will not scroll through all results. Users will need to use the Legacy Desktop in these cases.
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.
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 behaviour 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.
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.
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 at the filter listing under Data Veracity > Filter listing.
Data Veracity Search & Repair Table Listing's Sorting Does Not Work
The sorting function for the Data Veracity Search & Repair table listing is not working.
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.
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.
Data Veracity View UDR Are Showing Platform Timezone
Date time in View UDR page that we launch from Data Veracity Search or Data Veracity Approve Delete are showing platform timezone instead of client timezone.
Data Veracity New Restricted Fields that was Used for an Existing Repair Rule Not Disabled
If setting a new restricted field that was used in a previously created Repair Rule, it is expected that the rule on the said field should gray out when viewing the saved Repair Rule and ignored when applying repair tasks. However, the rule on the said field still appears to be editable in the old Saved Repair Rule.
Other issues
Logging Issue
When logging out of the legacy desktop desktop_current.log has unnecessary logs added
Error Thrown When SAPCC Agent Not Added With Any Host
In the SAP CC Batch agent, do not add any host, click the Save As button, and you will find the error shown below:
java.lang.NullPointerException: Cannot invoke "String.matches(String)" because "hosts" is null
Inappropriate Validation Handling On Workflow Group Scheduling
In Workflow Group Scheduling, when adding a duplicate execution day plan, it prompts the wrong validation message content and if the user continues to save, scheduling data will be wiped off.
Database Forwarding Agent Validation Message
In Database Forwarding Agent, when we have a field NULL/To UDR, the validation message that prompted is not properly describe the problem.
mzsh topo show pico-view Does Not Dispaly Full Information
The mzsh topo show pico-view does not show the pico names in the output. Picos can be viewed in the Desktops
External References Can Be Removed when a Workflow is Dependent on It
External references of the type Database Properties can be removed even if they are in use. Any workflows using these references will become invalid.
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.
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.
0 Comments