5. Bug Fixed

Fixed to Handle the Correct Message while the Wrong Operation Type

When an incorrect Operation type is selected on the outbound Interface to process the Outbound Agent Database adapter, an error message appears: 'Response code: 200, Response Payload: {"response": {}}'. This message comment is unclear. To address this issue, we have added a comment to the message: 'Response code 500, Response Payload: {"statusCode": "Failed:", "Message": "ERROR Unsupported Operation:xxxxxx, "success": false, "messageStatus": "Failed"}' to get better understanding.

Retry to the Data Source while No Connection Before and After Processing with the Agent Database

When unable to connect to the Data Source, issues may arise if the agent is installed on Server A and the database is on Server B, leading to connectivity challenges. To resolve this, the system will attempt to reconnect to the Data Source based on the configured Max Number Of API Retry and Retry Time Interval fields within the Interface, interface group, and integration settings. By default, the retry count is set to five if not specified in these three sObjects.

Resolved Issue of Null Value in 'Max Number of API Retry' Field for File Protocols FTP, SFTP, and FTPs

There was an issue with your interface, interface group, and integration settings where the 'Max Number of API Retry' value was not defined for processing with the agent for file protocols SFTP, FTP, and FTPs. Consequently, the processing would fail, resulting in the error message: 'Cannot invoke "java.lang.Long.intValue()" because the return value of "com.skyvva.camel.beans.interface.getMax_number_of_api_retry()" is null.' This issue has since been resolved.

Omitting the External ID Field from the 'Set' Clause When It's Inside the 'Where' Clause

We encountered an issue while performing an outbound interface with the operation type set to 'update.' This operation involved including the external ID in the 'set' clause for updating it. For example, generating a database query like: 'update tablename set extidfield = ‘id1’, field1 = ‘Acc001’ Where extidfield = ‘id1’. This problem could potentially lead to business issues as the 'extidfield' is typically a non-editable and unique field in the database. To resolve this, we have removed the 'extidfield' from the 'set' clause. Since this field is already specified within the WHERE condition clause, setting it again is unnecessary.

Resolved Issue: Agent Cache Incorrectly Updating 'created_date' and 'last_modified_date ' Field

There was an issue with updating and creating the Agent Cache in the PostgreSQL database, where the 'created_date' and 'last_modified_date' fields were being created incorrectly. This problem has been resolved to ensure that these fields are updated correctly.

Resolving Missing Records Issue in Inbound Processing with Excel Files Using Interface V2 of Agent File Adapter

There was an issue when importing data from an Excel file using the Agent File adapter for inbound processing. Some records were being missed during inbound processing with the interface v2 design. This issue has been resolved. The Excel file now imports correctly, and there are no more missing records.

Various Issues with Agent Adapter with XML File Type

• There was an issue with Inbound processing using External or Hybrid Mapping with an XML file type in the Agent File Adapter. The inbound processing was not functioning correctly. This problem has been resolved by extending support for all types of mappings, including normal, External, and Hybrid mappings.

• Resolved the issue with importing an XML file containing the root of data and processing it with sObject mapping in the v3 interface design of the Agent File Adapter. This issue has now been fixed.

Linking Request and Response Messages in the Root Agent Message Using Agent Rest and Agent Soap Adapters

We were processing requests and responses via the Agent Rest and Agent Soap adapters. However, the request and response messages were not linked within the Agent Message. This issue has been resolved by linking the request and response together into the Root Agent Message.

Resolved Issue with Request and Response Processing Using Message Type Rest and Soap Template Structure

We encountered an issue when users utilized the Message type Rest and Soap template structure via the Agent Rest and Soap adapter. An error message appeared: 'Response code: 500 Problem processing the request: Cannot invoke “org.json.JSONArray.iterator()” because “msgOutbound” is null.' This issue has now been resolved.

Fixed Issues on Inbound SQL Query Editor for Agent Database Adapter

• Resolved an issue with complex queries involving functions like TOP, GETDATE(), and table joins.
• Rectified response errors from the database.

Resolved Issue with Requesting and Responding in Sync Mode of Agent Rest Adapter with Request Format set to 'application/xml'

When requesting and responding to sync mode with the Agent Rest Adapter, an issue arises when the request format is set to ‘application/xml’. After processing, this triggers an error message in the agent log java.util.HashMap.get(Object)" because "this.property" is nullCannot invoke "java.util.HashMap.get(Object)" because "this.property" is null'. This issue has been resolved.