3. Bug Fixed

Fix Did Not Get Value Using Streaming API Using Salesforce CDC Event

An error occurred while you were using the Salesforce CDC event streaming API, causing the fields in the records to change. The file did not receive the updated field values. This issue has been resolved by retrieving the values after the field changes in Salesforce.

Fixed Manual Processing is complete with error while Create Batch/Bulk Basket Correctly

There is an issue when processing batch and bulk mode with a manual process. It will raise an error message stating 'Manual processing is complete with errors' with the Agent Database adapter, even though the Batch Basket and Bulk Basket are created correctly. This issue has been fixed by checking the job results correctly.

Fixed Ping Connection for Agent SOAP Adapter

We have fixed the issue that occurred when pinging the connection with a POST operation of the SOAP adapter, which required a request body. However, we no longer ping the connection in that manner. Now, we only check if the domain name is available.

Improved Log Understanding and Response to Update Message Failure During Adapter Processing Error

There is an issue with your adapter's incorrect ConnectURI, Username, and Password after integration. The log currently raises an error: 'ERROR: No messages to be updated,' and the message gets pending. This issue has been resolved by correcting the issue and responding to update the message inside Salesforce.

Fixed Message Completed But Did not Get Any Binary File

The New Agent BinaryDataKey path does not match the salesforce path. This will raise an issue: 'java.lang.NullPointerException: Cannot invoke "com.google.gson.JsonElement.getAsString()" because the return value of "com.google.gson.JsonObject.get(String)" is null.' It receives the completed message without any file. This issue will be resolved by checking only the mapping field for the ContentVersion.

Fixed Various Issues While Consuming SF CDC Streaming API

We have an issue where stopping the consumption of the Salesforce CDC Streaming API on the adapter does not work; it continues to consume and send records.
We encountered a problem: 'Failed to insert the records - ERROR: syntax error at or near “)” position: 13' while inserting records into the database using the Salesforce Streaming API.
Fixed the issue where getValue2__c() is null, resulting in the error: "Cannot invoke Cannot.skyvva.camel.beans.tables.AdapterProperty.getValue2__c() because the return value of java.util.Map.get(sObject) is null." This issue occurred while consuming the Salesforce CDC Streaming API on XML, JSON, and Excel files.
Fixed the issue where the Salesforce CDC Streaming API could not be consumed with a multi-adapter.
Fixed the Salesforce CDC Streaming API consumer support with client_credentials authentication.
Fixed the issue of getting the value but not the file header.

Fixed Issue Regarding Duplicate Adapter Properties on Agent Cache

There is an issue when you have Duplicate Adapter Properties on the Agent Cache. After performing manual processing, it will raise an error: 'Manual Processing is completed with error.' Upon reviewing the log, the issue is identified as: 'query did not return a unique result: 2; nested exception is javax.persistence.NonUniqueResultException: query did not return a unique result: 2.'

Fixed Salesforce Bulk Processing via New Agent Does Not Support OAuth2 Client-Credential Authentication Type

Currently, the New Agent supports only SFDC Bulk API 2.0 with OAuth2 Username-Password Authentication Type. We have now updated it to support both OAuth2 Username-Password and Client-Credential Authentication types.

Fixed Issue with Record Insertion into Database Using 'External Key Management' Insert Operation Mode in Agent Database Adapter

There is an issue when using the New Agent to insert records into the database with the 'External Key Management' Insert Operation Mode in Interface V2 design. It raises an error: 'Failed to insert the record - ERROR: syntax error at or near ")". Position: 13.' This issue has been fixed, and the record insertion is now completed successfully.

Fixed Batch Processing Package Size

We have updated the Interface V2 design to support only the 'Transfer Package Size' field. By default, if the 'Transfer Package Size' field is not set, the package size per batch will be 50 records.
We have updated the Interface V3 design to support the 'Batch Package Size' field. If not set, it defaults to the 'Transfer Package Size' with 50 records per batch.
Both V2 and V3 interface designs support Interface Group and Interface settings. The Interface settings have higher priority than the Interface Group.

Fixed Convert null value as string ‘null’

In the previous version, we had an error converted to 'null' (as a string) instead of a true null value for both file and database adapters of the new agent. This issue has been resolved.

Missing Header Quote for CSV File

In the Agent File adapter, you chose the CSV file type and enabled the 'Has Quotes' option. After exporting the file, the CSV file header did not include the quotes. This issue has been fixed by ensuring the quotes are included in the CSV file header.

Fixed Not Able to Connect Ms Access Using Username and Password

You received a System.HttpResponse [Status=Internal Server Error, StatusCode=500], even though the correct username and password were set in the adapter properties of the Agent Database Adapter to connect to MS Access. This issue has been fixed, and you are now able to connect to MS Access using your username and password.

Fixed Override Option on File Handling Mode of Agent File Adapter

We encountered an issue when exporting files with the Override option in the File Handling Mode of the Agent File adapter. The system would export, append, and duplicate records in the existing file. For XML files, it would duplicate the root element, and for CSV files, it would duplicate the header. This issue has been resolved by properly overriding the old file. As a result, the header for CSV files and the root element for XML files will no longer be duplicated.

Fixed Message Status Not Updating Correctly

There is an issue when you execute the interface in asynchronous mode. The Message Status does not update correctly when processing with the Agent Database Adapter for different operations such as Query, Delete, Update, Upsert, and Insert in both Interface V2 and V3 designs. This issue has been resolved by correctly updating the message status.