3. Bug Fixed

Fixed the filter of the License Key

There is an issue when you filter for "Users with active license keys" in the Type of Users, as it also filters out users with invalid license keys. However, this issue has been fixed.

Not able to Export Large Records in the Data Loader

Fixed the issue of encountering the apex job error message ‘First error: skyvvasolutions: Too many query rows: 50001’ while exporting a large number of records using our Data Loader function. This issue has been resolved.

Fixed Created Message Type

If your XML file contains prefix namespaces, the prefix namespaces will be included when creating the message type. However, this issue has been resolved by removing the prefix namespaces during the message type creation process.
If your XML file has many records without a root tag, the import message type will be generated incorrectly. Fixed by adding the message error “XML Parsing Error : This page contains the following errors:error on line x at column x: Extra content at the end of the document Below is a rendering of the page up to the first error.”
In the previous version of importing message types, namespaces were generated for all message type nodes. However, in the current version, namespaces are only generated for elements that have on themselves.

Missing Some Messages After Search Message Again

There is an issue when searching for messages and clicking on 'Show More' to view additional messages. After performing a search and clicking 'Show More' again, some messages are missing. This issue has been fixed.

Error Occurs in Restore Function for Restoring Same Interface with Different Integration

Outbound Mapping Tool Generate Wrong Order Fields

There was an issue with receiving the outbound error message '387, Message: 851 Message :: MyStack, No item' due to an incorrect field order mapping generated by the Outbound Mapping Tool. For instance, if you had to map the same source node to multiple target nodes and an issue was raised, it was not done correctly. However, we have already fixed this issue.

Fixed Generate SObjectType Node for XSD File

We have fixed the generation of message types to include the SObjectType, ensuring that the structure is generated with the SObjectType filling in the node name for XSD generate MetaData. Otherwise, it will use the message type name. For example, if your MessageType type is Salesforce sObject and the SObjectType is 'Account', it will use the 'Account' value to generate the node name. If they are not Salesforce sObject type, the message type name will be used for the node name of the XSD file.

Fixed Error when Re-ordering IWorkflow

An error occurs when the checkbox for re-ordering IWorkflow is selected. As a result, an error message will be displayed: "[Failed to execute 'querySelectorAll' on 'Element': '[data-row-key-value="xxxxxxx (Condition with Break Link) [data-col-key-value="seq-number-1"] > :first-child' is not a valid Selector.]" This error message is triggered when the condition value contains a new line, and that value is utilized as the key to re-order the record on this screen. However, this problem has been resolved by using an ID instead.

Apex Heap Size Issue When Deleting Messages with Multiple Child Messages

You may encounter the apex heap size limit when selecting all messages (10,000 records) that have a large number of child for deletion using the 'Delete' or 'Cancel' buttons in Message Monitoring. This issue has been resolved by stopping the 'BatchGenerateMessage' job to collect messages and pass all messages collected to the 'BatchDeleteCancelAllMessage' job instead of using only one job 'BatchDeleteCancelAllMessage' to query and delete.