- Not possible to update the message after message reprocessing is done
- Fixed Rest Adapter with SOAP XML Format
- The asynchronous call got the error "null input to JSON parser" with mode "Batch Apex"
- Always remove the manual query while saving the outbound mapping
- Fixed V3 inbound processing while the response payload has an empty node
- Generate Node without mapping request body of Rest Adapter
- Auto Mapping parent reference field
- Get message error "Error:skyvvasolution: Too many query rows: 50001" on delete/cancel/ reprocess message function
Not possible to update the message after message reprocessing is done #
We got an issue while the user did the reprocessing message. Therefore, the message does not update the status due to the duplicate message id in the list during the update. This issue has been fixed.
Fixed Rest Adapter with SOAP XML Format #
There is an issue with the rest adapter sending the SOAP XML format e.g. soap envelope in XML syntax is used exclusively in the soap adapter and not in the rest adapter. Fixed this issue by sending and receiving with pure XML (Pure Business Data).
The asynchronous call got the error “null input to JSON parser” with mode “Batch Apex” #
There is an error that occurred when the user pushed the record containing more than 131072 lengths with the Asynchronous call of Batch Apex Mode. The message’s data is too long. Therefore, It will write the records into the ContentVersion. The problem happens when the message’s data cannot be read from the file and it raises an error message “First error: null input to JSON parser” on the apex job. This error has been fixed.
Always remove the manual query while saving the outbound mapping #
Got a problem removing the manual query while after saving the outbound mapping. Now we have fixed this by merging manually added with an auto-generated query from the mapping.
Fixed V3 inbound processing while the response payload has an empty node #
Inbound v3 processing gets an error message “Failed inbound processing, Please check the response and inbound interface!” because some systems will respond with an empty node array while the fields did not have any value field map. This issue has been fixed by not creating the message for the node empty anymore.
Generate Node without mapping request body of Rest Adapter #
There is a problem when the user does not map the source node to the target side message type request body in the Rest adapter and it still was generating the root node using the source object of the outbound interface. Therefore it was creating problems when we are sending requests using the GET protocol. The issue has been resolved.
Auto Mapping parent reference field #
This issue occurred while auto-mapping with the parent note reference field of the child. Therefore, it will generate an extra node and fields for the mapping. This problem has been resolved.
Get message error “Error:skyvvasolution: Too many query rows: 50001” on delete/cancel/ reprocess message function #
This error happened when you processed records by Dataloader or Basket, and you will get a few message root messages containing too many child business messages. Therefore, you will get an error message “Error:skyvvasolution: Too many query rows: 50001” while you try to use the delete, cancel, reprocess function. This issue has been fixed.
Note: if your hierarchical messages are more than 10000 records, it will take only 10000 records to reprocess per batch in per transaction.