Fixed Flat Interface of Bulk Processing #
When utilizing Skyvva Bulk Processing, an issue arises with a flat interface if the Bulk Package Size is not set. This can lead to the creation of a bulk basket containing a single record. Dealing with a large number of records may lead to multiple bulk baskets being created, which can result in resource waste. However, this issue has been resolved by a dedicated bulk basket capable of storing up to 1000 records, when the Bulk Package Size does not set.
Resolving the Issue of the New Agent being Unable to Cache Batch Mode Field Value #
When utilizing Skyvva Bulk Processing, an issue arises with a flat interface if the Bulk Package Size is not set. This can lead to the creation of a bulk basket containing a single record. Dealing with many records may lead to multiple bulk baskets being created, which can result in resource waste. However, this issue has been resolved by a dedicated bulk basket capable of storing up to 1000 records, when the Bulk Package Size does not set.
Fixed Alert Message Error “Manual Processing is complete with errors” while successful push Basket #
There was an issue when integrating using batch, bulk, and auto switch modes, where the baskets were successfully created, but an error message would appear stating, “Manual Processing is Complete with errors.” I’m pleased to inform you that this issue has been resolved by eliminating this error alert message.
Resolving Persistent Ping Connection Failure Despite Correct Agent Credentials #
There was an issue when attempting to establish a ping connection from Salesforce to the Agent, even after inputting the correct Agent credentials. This problem occurred due to the firewall blocking the port. However, we are pleased to inform you that this issue has been resolved, and you should now be able to establish a successful ping connection.
Resolving Null Pointer Issue in IService.Login during V2 Bulk Processing #
You may encounter a problem with V2 Bulk Processing, which can lead to an issue where IService.Login becomes a null pointer due to the login not being assigned to SFService. I’m pleased to inform you that this issue has been resolved.
Fixed Missing Some Fields Streaming API to Agent Database #
We have an issue with streaming API while we have to do outbound processing Salesforce to Database it will miss some fields that we have mapped on the mapping. This issue has been fixed.
Database Did Not Delete Records While the Salesforce Already Delete Using Streaming API #
We encountered an issue with the Streaming API and SQL database adapter when configuring the ‘Notification For Operation = Deleted’ and ‘Operation Deleted = Hard Deleted’ settings. The problem arose when records were deleted from Salesforce but remained undeleted in the associated database. However, This issue has been resolved. Now, regardless of whether you set Hard Deleted or Soft Deleted, when records are deleted in Salesforce, both Salesforce and the associated database will perform synchronized deletions.
Fixed Null Pointer V3 Setting on Interface API Version Without Message Type #
The New Agent encountered an issue when integrating with the V3 setting on the Interface API Version without specifying the Message Type, which resulted in a Null Pointer error. I am delighted to inform you that this issue has been fixed.
Fixed Not able to Cache on Bulk Package Size Field #
We encountered an issue while caching the Bulk Package Size field because the request body and the Salesforce cache table had different values. We are pleased to inform you that this issue has been resolved by changing BATCH_SIZE to ‘Batch_Package_Size’ and BULK_SIZE to ‘Bulk_Package_Size’.
Fixed Error That Is Not Able To Process Binary File In SFTP and FTP Protocol #
There was an issue encountered during the processing of Binary Files using the SFTP and FTP protocols. An error message, ‘Error in ProcessBinary,’ would appear in the log due to the absence of conditions for sending files to Salesforce via FTP and SFTP. I’m pleased to inform you that this issue has been resolved.
CSV Payload Contains Special Source Encoding #
The error occurred due to a special source encoding in the CSV payload. Importing the payload from the New Agent into Salesforce may result in an error. However, this issue has been resolved by supporting the CSV source encoding.
