Fixed tree messages processing separately between the parents and child messages #
There was an issue when reprocessing outbound tree messages using the Integration Scheduler. The Scheduler selected the child message record of the message hierarchy and attempted to reprocess them separately from the parent message. However, an error occurred with the message ‘No outbound Adapter to callout >Detail:Class.skyvvasolutions.IServiceBatchCallOut.<init>: line 136, column 1’ in the code. This issue has since been fixed.
Fixed Create duplicate child fail messages after reprocessing the outbound tree message #
There is an issue when reprocessing the failed tree message using the REST, SOAP, and SAP CPI adapter. This results in the creation of multiple duplicate failed child business messages when attempting to reprocess those failed tree messages again.
MessageReprocessPerInterface Scheduler Did Not Pick Up the Message for Reprocessing #
An issue occurred while reprocessing the message with the MessageReprocessPerInterface scheduler. When the scheduler started, it did not pick up the message for reprocessing. However, this issue has now been fixed.
The Child Unlink Parent Business During Reprocess Message #
We experienced an issue with the ‘Delete Completed but keep other messages’ interface setting during message reprocessing when the parent business message was partial completed, with some child messages completed and some failed. When reprocessing, if all child messages are completed, the parent business message is marked as completed, and any failed child messages are also marked as completed. However, if child messages were completed before being unlinked from the root message, they are not deleted. This issue has been resolved.
Fixed Response Message does not contain all business response messages #
There is a problem while attempting to reprocess the request message which has a response message. After reprocessing the request successfully, it will respond to the response message back. Some business messages are not inside the API Response Message.
Get Error “For Job id ‘xxxxxxxxxxxxxx’ :vskyvvasolution: Too many query rows: 50001” on Delete Completed Message after Processing #
This issue occurs when the ‘delete completed’ flag is set on an Integration with a large number of completed messages, and the integration attempts to delete all completed messages at once. This causes an error message to be raised, specifically: ‘For Job id ‘xxxxxxxxxxxxxx’ :vskyvvasolution: Too many query rows: 50001’. However, this issue has been resolved by deleting only specific completed messages that were processed per transaction, rather than selecting all completed messages per integration for deletion.
Backup the Formula Mapping did not work on multiple lines #
If you backed up mapping records that contained a formula field with multiple lines, the backup function did not capture all the values in the formula field. However, this issue has been fixed.
Source Object Generates Wrong the Inbound Interface While Update Interface Name #
There is an issue when an inbound interface is designed as V3 without specifying a message type in the Interface setting on Interface API Version = V3. The structure mapping generates a sObject hierarchy, typically with the source object represented as a sObject node map. However, changing the interface name also changes the source object to the current interface name, which can cause integration data to become incorrect.
Clear Old Value When Click Back Button in Data Loader #
In the previous version, when you clicked the back button in the Data Loader and then clicked the Next button to proceed to the next step, the current value remained on the screen. This issue has been fixed by clearing the previous value when clicking the back button.
Incorrect Level Displayed in Mapping #
Our mapping did not display the correct level hierarchy for the mapping record. For example, ‘Account’ is the first level, and ‘Contact’ and ‘Contract’ are child of ‘Account’. However, ‘Contract’ was displayed incorrectly and appeared under ‘Contact’ instead of ‘Account’. This issue has been resolved.
Fixed Check Syntax of Mapping Formula and Expression #
An issue has been identified with checking the syntax of the field and sObject in Formula and Expression mapping on the outbound interface. For example, the expression VLOOKUP(Account, Name, Name, Name) has the correct syntax for the field and sObject, but it was displaying an error message stating that ‘Field Account is invalid.’ This issue has now been fixed.
