- Clear Old Value When Click Back Button in Data Loader
- Missing the Category values on Message Type Field Entry
- Get Error “For Job id ‘xxxxxxxxxxxxxx’ :skyvvasolution: Too many query rows: 50001” on Delete Completed Message after Processing
- Not generate dynamic values for the header, query, and path parameters using the InterfaceExecute scheduler through the mapping tool
- Fixed tree messages reprocessing separately between the parents and child messages
- Loading all messages on the message detail screen inside the Root Message
- Missing SKYVVA__MessageId while processing with InterfaceExecute scheduler
- Second Basket Business message not covered by Basket Message
- Fixed Create duplicate child fail messages after reprocessing the outbound tree message
- MessageReprocessPerInterface Scheduler Did Not Pick Up the Message for Reprocessing
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 existing value remained on the screen. This issue has been fixed by clearing the previous value when the back button is clicked.
Missing the Category values on Message Type Field Entry #
To create the message type field entry, there are two ways: manually or by creating an auto-select from IStructure in the repository. This issue occurred while using “Select Field From the Repository” to create the message field entry. It was not taking the category value from the IStructure into the category field of message type field entry. However, this issue has now been fixed.
Get Error “For Job id ‘xxxxxxxxxxxxxx’ :skyvvasolution: 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.
Not generate dynamic values for the header, query, and path parameters using the InterfaceExecute scheduler through the mapping tool #
The users have mapped the header, query, and path parameters using a mapping tool and invoked a callout with the InterfaceExecute scheduler. Therefore, the scheduler will not retrieve the values from the mapping to pass the request header, query, and path parameters.
Fixed tree messages reprocessing separately between the parents and child messages #
An issue occurred while reprocessing outbound tree messages with the Integration scheduler. The scheduler picked the child message records from the message hierarchy and reprocessed them separately from the parent message. However, the following error message was encountered during this process: ‘No outbound adapter to call out >Detail:Class.skyvvasolutions.IServiceBatchCallOut.<init>: line 136, column 1’ in the code. This issue has been fixed.
Loading all messages on the message detail screen inside the Root Message #
There was a problem when attempting to view a specific message, as the whole message tree was displayed on the message details screen. This could be difficult to view and took a long time to load, particularly when there were many messages in a root. However, this issue has been resolved by displaying only fifteen business messages including the select message. The selected message will highlight the green color.
Missing SKYVVA__MessageId while processing with InterfaceExecute scheduler #
An issue occurred during outbound processing with the InterfaceExecution scheduler where the SKYVVA__MessageId was not being generated into the request payload. This issue has since been resolved.
Second Basket Business message not covered by Basket Message #
There is an issue when processing one job with multiple baskets simultaneously. Only a basket message is created to cover a basket, and the other baskets being processed do not receive a basket message to cover them.
Fixed Create duplicate child fail messages after reprocessing the outbound tree message #
An issue occurred while reprocessing outbound failed tree messages with the REST, SOAP, and SAP CPI adapters, resulting in the creation of duplicate failed child business messages. This issue only occurred when reprocessing fail-to-fail messages. However, it has since been fixed.
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.