3. Bug Fixed

Fixed: Browser Crashes Due to Large History Baskets on the Batch Control Board

There is a problem with the History Baskets having many records on the Batch Control Board, causing the browser tab to crash when it takes a long time to load. This issue has been fixed by adding pagination.

Resolution of JSON Payload Generation Issue When Copying Nodes with the Same Name

There was an issue where the JSON payload was generated incorrectly when copying a node with the same name in the mapping tool. This resulted in duplicate object payloads in the JSON. This issue has now been fixed by ensuring that only an array object covering different records is generated.

Reprocess a Single Message

In the previous version, you could not reprocess a single message; you could only reprocess the root message, which triggered the reprocessing of all messages within that root message. Now, we have enhanced the system to allow reprocessing of individual messages.

Fixed issue Backup and Restore IMapping Records

The issue concerns the incorrect Full_Source_Path__c, Full_Target_Path__c, and Source_Path__c fields of Source and Target after restoring a backup. This occurs when a user backs up only the IMapping record and restores it to another Org. This issue has now been resolved.

Fixed Issue on Message status remains 'New' during Request and Response processing in synchronous mode

There is an issue with Request and Response processing in synchronous mode. While all message requests and responses are marked as 'Completed', the root Agent Message remains in a 'new' status. This issue has been fixed, and the Agent Root Message has been updated correctly.

Fixed Issue on Import SAP Metadata Function

When you use the 'Import SAP Metadata' function from SAP ERP, the message type field entry is not generated. This issue has now been fixed.

Fixed Some Issues for Alert Feature

• There is an issue with the Agent Scheduler not running on the Agent side. The alert will trigger and update the comment on the Agent Scheduler on the Salesforce side. It will send the agent scheduler cache to the cache table. In this case, we have been fixed by not sending the cache to the Agent anymore to avoid unexpected errors.
• Fixed an issue with the agent inbound scheduler. Previously, the logic was to create InterfaceControlRunTime only after the scheduler had executed at least once. To avoid the problem where InterfaceControlRunTime is not created if the scheduler crashes on its first run and never triggers the alert feature, we have changed the process to create InterfaceControlRunTime when starting the scheduler.
• When you stop the Agent scheduler on the Salesforce side, it updates the comment to 'Stop by Admin' and triggers an alert feature. We have fixed this by preventing the alert from being triggered when the scheduler is  'Stop by Admin'.