Popular Search how tohow to useagenthowdatarestformulacustombatchstore
View Categories

3. Bug Fixed

Fixed Various Issues on the Bulk Control Board #

  • The batch job limit is set to 5 by default, which means that even if you select multiple baskets, only 5 baskets can be processed at a time. We encountered an issue where we selected these 5 baskets with separate pagination. The system will process the selected baskets within the current pagination. This issue has been resolved.
  • We have also addressed the issue of missing some baskets when the organization reaches its storage limit. The job was still completed successfully, even if the storage limit had been reached and some baskets remained uncreated that is why the missing basket was even the apex job was completed. This issue has been fixed.
  • Furthermore, we have resolved the issue where it was not possible to ‘Delete All’ baskets in the Processing Baskets section and ‘Delete All’ history baskets in the Processed Baskets section.

Incorrect Message Structure and Message Status CallOut Using SAP Business One Adapter #

There is an issue when making a callout with Future and Queueable mode from the invokeCalloutV3() method using the SAP Business One Adapter. The outbound message structure relation is not being established, and the status is incorrect due to the error message ‘Update failed. First exception on row 0; first error: MISSING_ARGUMENT, Id not specified in an update call: []’. This issue has been resolved, and now the message structure and status are correct.

Fixed the DoMaintenance scheduler only Delete ISERVICE_LOG4I.txt Log File Name #

The DoMaintenance scheduler is used to delete messages, logs, and basket history. We encountered an issue while deleting logs because it only deleted logs with the file name ISERVICE_LOG4I.txt, while other logs with different names were not being deleted. However, this issue has been resolved by allowing the deletion of all logs.

Fixed Generate Incorrect Request URL of Microsoft OneDrive Adapter  #

There was an issue when making a request to retrieve files. Unfortunately, the API call generated an incorrect request URL by adding double slashes (‘//’). As a result, the log displayed an error message: ‘Resource not found for the segment ‘root’:”. However, this issue has been resolved.