Fixed Issue: Incorrect Order of Nodes and Fields in Generated JSON Payload #
You may encounter a problem with the mapping order incorrect, leading to the generation of an incorrect JSON payload. In certain cases, specific fields may be misplaced and end up in the wrong node. However, we have resolved this issue by appropriately enhancing our JSON builder. This ensures the correct order and field population in the JSON payload.
Fixed Issue: Unable to Add Interface to Interface Group #
This issue occurs when attempting to add an interface to an interface group that contains multiple interface records within the integration. It results in an error message alert stating, ‘Please enter the value in Sequence.’ The issue arises during the interface trigger when verifying and validating the source name of the interface. We have resolved this problem by using Type.forName(‘xxxxxxx’) instead of Schema.getGlobalDescribe().get(‘xxxxxxx’). This approach provides faster performance and prevents validation checks during interface updates within the Interface group.
Fixing the Issue of the MessageReprocessPerInterfaceGroup Scheduler #
We have resolved the issue with the MessageReprocessPerInterfaceGroup scheduler that was causing a mix-up between inbound and outbound reprocessing messages that caused an incorrect setting of Processing Package size to outbound.
To fix this issue, we implemented the following solutions:
- Ensured that inbound and outbound processes are not mixed within the same scheduler of the interface group. When the interface group contains only outbound interfaces, the scheduler will execute the outbound worker job (IServiceBatchCallout) to reprocess the outbound messages.
- Similarly, when the interface group contains only inbound interfaces, the scheduler will execute an inbound worker job (IServiceBatchReprocess) to reprocess the inbound messages.
- The issue with the scheduler on the interface group that reprocesses outbound messages with a processing package size greater than 1, even when the Processing Package Size is blank, has been resolved. The issue occurred due to a mix-up in the scheduler’s reprocessing of request/response messages (outbound/inbound messages) within the same group. When the ‘Processing Package Size’ setting is blank, the following default values will apply:
- For outbound message reprocessing, the setting will be 1.
- For inbound message reprocessing, the setting will be 10.
Fixed Various Issues Updated incorrect Message Status #
- We have encountered an issue during the Request and Response process with the SAP CPI Adapter. Specifically, when receiving a failed response, the API message does not update its status from ‘completed’ to ‘Partial Completed.’ This issue occurs when using the invokeCalloutV3 method in various modes such as Future, Queueable, Batch, Auto, and message_only.
- Incorrect Update of API Message: After reprocessing the message, the API Message incorrectly updates as ‘failed’ even though some business messages are completed successfully while others have failed. This issue has been resolved by updating the status to ‘Partial Completed.
- We encountered another issue when calling the ‘SAP CPI’ adapter and performing the ‘Get’ operation without mapping (only querying data for inbound processing) using callout modes such as Future, Queueable, Batch, Auto, and message_only. As a result, both the request business message and API Message remained in a pending status. However, we have resolved this issue by updating the message statuses correctly.
Fixed Error: Handling Multiple-Level Mapping in Raw Upload File of Data Loader Function #
We encountered an issue with the Data Loader where the error message ‘No field name specified on the column for sObject of type skyvvasolutions__IMessage__c’ appears when attempting to upload a file using Raw Upload File with multiple-level mapping. However, this issue has been resolved.
