Fixed the ‘Select Field’ function for Node to support systems that call the IntegrateWithIMessage #
In the previous version, using the ‘Select Field’ function for Node did not support payloads as IMessage. This issue has now been resolved for both Raw Payload and IMessage Payload. Additionally, we have disabled the display of parent fields that are selected, so they no longer appear in child message data.
Fixed Not Able to Callout with V2 Interface API Version While Using Agent xxx Adapter #
In the previous version, using the Interface API Version would raise a ‘No implementation for the outbound interface with name = xxx and adapter type = Agent xxx’ issue. This has now been fixed by the Agent xxx adapter, which enables v3 outbound processing support with the V2 Interface API Version.
Agent Rest Adapter Does Not Return Salesforce Id Into the Response #
There was an issue with setting the ‘Return Salesforce Id in the response’ option under the Salesforce Id Handling property adapter of the Agent Rest Adapter. It did not return the Salesforce ID in the message response. This issue has now been resolved, and it correctly returns the ID in the message response.
Fixed Issue Delete Message with Bulk Delete #
When you set ‘Enable Bulk Delete?’ and click ‘Delete All’ with more than 500 records, the deletion did not occur because Skyvva uses a Lightning component/LWC to get the session Id via UserInfo.getSessionId(). The Lightning component/LWC did not work, raising a Batch Apex job issue: ‘First error: Refresh token has been deleted.’ This issue has now been fixed.
Removed Default Skyvva Namespace on XML Root Tag Namespace for Outbound Adapter #
In the previous version, the namespace was generated as the Skyvva default namespace when the user did not set the namespace for the ‘XML Root Tag Namespace’ outbound adapter. Now, we have removed the Skyvva default namespace. If you do not set it, the ‘XML Root Tag Namespace’ will remain empty.
Fixed Reprocess Messages While Setting the ‘Delete Completed but Keep Other Messages’ Option #
There was an issue when reprocessing 500 – 5000 failed messages using the ‘Delete Completed but Keep Other Messages’ mode. The total batches differed from the batches processed. For example, if the total batches were 50, the batches processed might be 52. This meant that not all records were reprocessed, leaving some records in message monitoring. This issue has now been resolved, and all messages are reprocessed and deleted as expected when ‘Delete Completed Messages’ is checked.
