Fixed various issues regarding Log Configuration on the Agent Control Board #
- There is an issue while you have updated the Log profile. It will alert the message The log profile Name already exists. This issue has been fixed by allowing to update.
- Allow to remove inactive profile while you have updated profile.
Do Not Allow Missing ‘numberOfTree’ Parameter in IntegrateWithIMessage API #
In the previous issue, when you pushed an IMessage to the batch basket via the IntegrateWithIMessage API without the ‘numberOfTree’ parameter or ‘numberOfTree’, it was null. This caused the processing of the batch basket to get stuck. However, this issue has been resolved by returning an error while pushing the batch basket without including ‘numberOfTree’ or ‘numberOfTree’ as null.
Prioritize Retrieving the Old Basket for Processing First on the Bulk Control Board #
We are encountering an issue with multiple baskets on the Bulk Control Board, consisting of both old and new baskets. The old and new baskets contain the same data. Our scheduler processing prioritizes the new baskets over the old ones. This leads to a problem with corrupted data, as the new data gets overwritten with the old data. This issue has been fixed by selecting the old basket processing first.
Fixed Issue Regarding Use of Auto-Switch Mode #
An issue arises when Use Auto-Switch Mode is enabled. In cases where the interface has a batch basket, it will not display and will not provide the scheduler for running the basket processing. This issue has been resolved by implementing an interface filter and Batch Interface scheduler for that option.
Fixed Selection Options for Batch, Bulk, and Use Auto-Switch Modes #
We have added validation for the batch, bulk, and auto-switch modes. Now, each interface can only have one of these modes enabled. If you attempt to enable more than one, an error message will be triggered, stating: ‘Batch, bulk, and auto-switch modes are not allowed per interface’.
Invalid Query While to Export Data From Data Loader #
An error is encountered when the outbound interface query is invalid while using the Data Loader to export data. However, an error alert message is displayed: ‘Unexpected Token: “xxxxxxxxx”.’ This alert message makes it difficult for us to fully understand the issue. The problem has been resolved with a new error message: ‘Invalid SOQL: unexpected token, Interface ID: xxxxxxxxxxxxxxxx, Query: query statement.’
Fixed Not Change Parent Development Status of Interface #
The development status of the parent interface does not change from Green to Partial when the child interface is ‘Development’. However, we have resolved this matter by updating the parent interface to partial whenever this situation arises.
Fixed Issue Exporting CSV Files with Data Loader including the special character ‘#’ hash #
We encountered an issue when exporting the CSV file that contains the ‘#’ symbol within the data. This was causing errors, resulting in an incorrect format and missing data. Fortunately, this issue has been resolved. #
