4. Bug Fixed
Fixed Message Reprocess of SOAP Adapter
There is an issue occurred while the users reprocess the outbound message of the SOAP adapter, and it will create a new API message and business message after the reprocessing. Fixed this issue by updating the existing one.
Fixed several issues on Message
- We fixed to added the checkbox for the first child business message
- There is an issue when the user sets the mode Delete Completed but keeps another Message. All completed business messages (child's message) will be deleted, but it keeps only the basket message (parent message) due to the status partial completed is not updated after doing this mode. This issue has been fixed.
- In the previous version, the user only filters on the parent/root message. Now we fixed to allow message filter both child message and parent/root message.
- Fixed message reprocessing from the child business message failed to fail again, but the parent message (basket message) updated to partial completed. This issue has been fixed.
Error ENTITY_IS_DELETED on Bulk Basket
Got an error message "caused by: System.DmlException: Update failed. First exception on row 0 with id a8R67000000LB8DEAW; first error: ENTITY_IS_DELETED, entity is deleted: []" on baskets of bulk processing. The issue is the overlapping running of the processing and reprocessing job with the same basket. This issue has been fixed.
Missing the message response
In the previous version, the message responses responded only to the root message of v3 inbound processing. This issue has been fixed by implementing the logic response whole tree message for all statuses.
Skyvva Data Loader faced an issue with Salesforce limit parsing Data
There is an issue that occurred while the user imported the CSV file with a large amount of data. Therefore our Data Loader does not import the data and gets a non-stop spinner due to an issue with Salesforce limit parsing Data. This issue has been fixed by splitting data into small amounts in order to avoid this error happening.