Bug Fixes (4.2.1)
4.2.0
Version | Case ID | Internal ID | Components | Summary |
|---|---|---|---|---|
4.2.0 |
| XE-5393 | Ultra | Description Currently, {{targetNameSpace}} property is always added to target locations. In case {{targetNameSpace}} is null, then schemaLocation is completely ignored. Resolution A new system property called {{mz.ultra.xml.schemalocation.newparsing}} is added. If set to true, it will give precedence to {{schemaLocation}} (if available) and {{targetNameSpace}} will be ignored. In case property is not available (or set to false), then the default behaviour is backward compatible. |
4.2.0 | 44663,44765 | XE-8934 | Desktop Launcher | Description Unable to log in using a local user ID when the IP address of the IDP is unreachable. Resolution The issue has been fixed by introducing a 5-second connection timeout when retrieving the IDP Configuration. This will prevent the launcher from getting stuck in a prolonged waiting state. |
4.2.0 | 44245 | XE-10021 | System Import/Export | Description Workflow Packages can only be downloaded to Legacy Desktop. Resolution It is now possible to download Workflow Packages to Desktop as well. |
4.2.0 | 39011, 40350, 41464 | XE-10946 | SAP CC | Description SAP CC notification TLS is not working due to a bug in SAP CC library API that is used by the SAP Notification Agent. Resolution SAP has provided a fix that as of writing is only available for SAP CC version 2020 SP2 Patch 5 and SAP CC version 2023 FPS1. A code fix is required and is done for SAP Notification Agent to implement the fix from SAP which resolved the SAP CC notification TLS issue. Expecting more SAP CC versions to get this fix moving forward, you can check with SAP on availability of this feature for other SAP CC version. |
4.2.0 | 00042894 | XE-11407 | Prometheus | Description Desktop does not allow the Prometheus forwarding agent renaming as there was no way to enable it to happen. Renaming of the agent from the Legacy Desktop is still allowed. Resolution An interface has now been added to the Prometheus Forwarding agent to enable users to rename it from the Desktop. |
4.2.0 | 43140 | XE-11669 | RCP | Description The security token sent in clear text over the network is insecure. Resolution Make sure to delay sending of auth packet containing the credentials until TLS has been properly negotiated. |
4.2.0 | 43158 | XE-11885 | Database Profile | Description After the property “postgresql.connectionpool.maxlimit” in the Database Profile is updated, the old connections in the connection pool are not properly removed. This leads to a connection leak in Database Forwarding Agent and sqlExec APL function. Resolution This issue has been fixed for Database Forwarding Agent and sqlExec APL function. |
4.2.0 | 43674 | XE-12287 | Radius | Description When configuring a secret key for the Radius agent, it is visible in plain text both in the agent configuration and in the workflow table. Resolution This problem has now been fixed and the secret key is not visible in plain text anymore. |
4.2.0 |
| XE-12670 | Documentation | Description The option, File System Profile, was missing from the list of agent profiles where External References can be defined. Resolution The option, File System Profile, has been added to the list of agent profiles where external references can be defined. |
4.2.0 | 44190 | XE-12883 | Workflow Table | Description This issue only happens in Legacy Desktop Workflow Editor. When sorting on the Name column in the Workflow Table and double-clicking an external reference cell in another column to edit, a random external reference name of another cell is displayed instead. If no change is done, the cell will now be set to the incorrect random external reference name. Resolution The issue is fixed and the correct external reference name will remain when clicking to edit. |
4.2.0 |
| XE-12934 | SFTP | Description Older workflow that involves SFTP agents will assume that the cipher mode is enabled in advanced security settings. However, this feature is not available in the older MediationZone versions. Resolution The fix includes version validating and disabling the “Enable Advanced Security Settings” checkbox if it is a version older than MediationZone 7.3.4.0. |
4.2.0 | 44400 | XE-12953 | HTTP APL Functions | Description HTTP Client Functions may crash an EC when a timeout and Response are received simultaneously. Resolution Deprecated thread-stopping functions are refactored to respond with timeout without crashing the EC. |
4.2.0 | 44401 | XE-13214 | Workflow Engine | Description Due to rounding errors in the Queue Throughput calculations, the value is misreported as too large in System Statistics. Resolution The calculation has been fixed to be as exact as possible (given that it is reported as an integer value). |
4.2.0 | 44510 | XE-13215 | Aggregation | Description In the documentation for Aggregation Profile, the documentation for parameter {{Enable Separate Storage Per Workflow}} was incorrect. It contained information from the corresponding parameter in Duplicate UDR Profile. Resolution The documentation has been corrected. |
4.2.0 | 44620 | XE-13307 | Realtime Batch | Description When forwarding more than 1000 UDRs with Disk Forwarding, some are lost in the process. Resolution This issue has now been fixed and the user can now send more than 1000 UDRs without losses. |
4.2.0 | 44670 | XE-13384 | Workflow Table | Description Workflow ID added on Desktop would not reflect on Legacy Desktop. Resolution Legacy Desktop will now get the next number from the current max workflow ID. |
4.2.0 | 44674 | XE-13487 | SSO | Description When SSO users are part of a group called *All* they cannot login and an exception is thrown. Resolution This problem has now been fixed and SSO users belonging to an *All* group can login as expected. |
4.2.0 | 44724 | XE-13500 | Core | Description For a Workflow Configuration using Dynamic Fields, validation can become extremely slow if you have many rows in the workflow table. This is due to failures in field type lookup causing a large amount of synchronous requests to be sent from the UI process to the platform. Resolution The issue has been fixed and the unnecessary lookup attempts have been eliminated. |
4.2.0 | 44877 | XE-13629 | JSON Decoder | Description The jsonFormat() APL Function uses a Gson object to format the UDR. The same object is also used by the jsonEncodeUdr() APL function. Depending on the order of which the methods are called, the Gson object will be initialized with different parameters. This causes the jsonFormat() APL Function to have inconsistent output. Resolution Initialize a new Gson object with the correct parameters jsonFormat() is called. |
4.2.0 | 44999 | XE-13710 | Ultra | Description Previously we have not supported global named attributes. If you tried to define such an attribute a parsing exception was thrown. Resolution Global named attributes, or named attributes at the root level are now supported and can be used from other non-root attributes with the ref argument. |
4.2.0 | 45012 | XE-13733 | JSON Decoder | Description Due to an old version of the JSON schema parser and validator being used, only very old versions of the JSON schema standard are supported. Resolution The validator has been upgraded to the latest version, and JSON Schema versions up to and including 2020-12 should now be supported. |
4.2.0 |
| XE-13835 | Core | Description The CVE-2021-47621 is present in classgraph library. Resolution This CVE is resolved by upgrading the classgraph library. |
4.2.0 | 45082 | XE-13843 | Inter Workflow | Description When the Realtime Inter Workflow Forwarding agent loses network connection to a remote storage service, the error handling is poor and the workflow can often not recover and aborts unnecessarily. Resolution The error handling has been improved. The workflow will now always try to find a new storage reference and reconnect and will also retry a number of times to avoid problems with short lived issues and support the remote storage EC shutting down and the storage being restarted on a different EC. |
4.2.0 | 45077 | XE-13921 | External References | Description In some situations, configurations in Workflow Packages that uses an External Reference Profile may not work due to the profile not being found at runtime. This is due to the system will instead try to look for the External Reference Profile outside the workflow packages, which happens for example for Archiving. Resolution The lookup of the profile has now been fixed to use the correct workflow package. |
4.2.0 |
| XE-13984 | Core | Description ECs that were registered as running a workflow at platform shutdown, but are unreachable at platform restart are handled incorrectly by System Statistics. This can cause many incorrect log entries in the system log until the ECs reconnect or are unregistered. Resolution System Statistics will no longer try to contact unreachable ECs. |
4.2.0 | 45168 | XE-14018 | Workflow Properties | Description The workflow configuration of User Defined Throughput MIM in Workflow Properties is not correctly validated. Resolution This configuration parameter is now properly validated as part of the normal workflow validation. |
4.2.0 | 45232 | XE-14062 | Encoder | Description Regardless if skipEncoding is checked or not, the validation will always check to ensure the Encoder is not empty. Resolution When skipEncoding is checked, it should allow the Encoder to be empty. |
4.2.0 | 45272 | XE-14138 | APL | Description NullPointerException occurs when logging MIM values in the System Log. Resolution Try to check each of the MIM values and see if it is NULL. Just return an empty string if it is NULL, do not call the toString() method. |
4.2.0 | 45272 | XE-14139 | Workflow Properties | Description Unable to edit Logged MIMs items when Abort after one cancel batch is selected in Desktop. Resolution Created a separate VerticalLayout for Logged MIMs so that it is always editable. |
4.2.0 | 45331 | XE-14147 | Archiving | Description The Archive Cleaner does not handle Archive Profiles located in a workflow package. Resolution This has been resolved, so the Archive Cleaner will handle all Archive Profiles. |
4.2.0 | 45034 | XE-14262 | Alarms | Description The Alarm Detection documentation contains a description on the states of alarms in versions 9.0 and above where the Alarms are now stateless. Resolution Documentation has been updated to reflect the change in versions 9.0 and above. |
4.2.0 |
| XE-14855 | User Management | Description Added documentation on how to reset locked mzadmin user for PE Resolution |
4.2.0 | 46065 | XE-15062 | Documentation | Description *Description:* The documentation for creating an External Reference in Helm Chart is missing an important warning about the required label, {{app.kubernetes.io/component: "extref"}}. Without this label, the created ConfigMap will not work. *Resolution:* A warning message has been added to the documentation advising that the ConfigMap will not work if created without this label. Resolution |
4.2.0 | 44096 | XE-15117 | Devkit | Description The descriptions of the osgi and exportpackages options are incorrect in the DTK documentation. Resolution The documentation has now been updated. |
4.2.0 | 48663 | XE-18562 | Codeserver | Description The default value for the oracle.pool.maxlimit property described in the documentation is “-1” while the actual default value is 10 for the platform and 50 for the ecd. Resolution The documentation has now been updated to state the correct default value. |
4.2.1
Version | Case ID | Internal ID | Components | Summary |
|---|---|---|---|---|
4.2.1 | 45731 | XE-14692 | Diameter | Description When using the Diameter Stack agent in workflows in a Kubernetes environment, the pod IP is sent out as Host_IP_Address in Capabilities-Exchange-Request/Answer which causes a mismatch between sender IP and Host_IP_Address. Resolution A new field has been added to Diameter Stack to enter the Load balancer Service name that is used for external communication. Diameter then adds the external IP of the Service to the list Host_IP_Address in Capabilities-Exchange-Request/Answer. |