4. Bug Fixed

Cache Adapter Properties Issue in Non-Open Firewall Mode

There was an issue when changing the XML Root Tag to a blank value using a non-open firewall mode connection. The cache did not update the blank value for the xmlRootTag column in the adapter_properties cache table. This could lead to issues when retrieving the XML Root Tag with existing input for the XML file export. However, this problem has been resolved by synchronizing the cache's blank value for the XML Root Tag from the Salesforce adapter property to the xmlRootTag in the adapter_properties cache table.

Outbound Database Operator Interface Upsert With Special Character

There is an issue when data containing special characters is sent to the database via the Agent Database. For example, 'D'Cruz' will result in an error during SQL operations. We have resolved this by handling values with special characters.

Clean up skyvva_application.properties

In Agent Version 3.06.01, we no longer require certain properties in the skyvva_application.properties file. We have cleaned it up to display only the essential information needed.

Do not update the Message Status while using Request and Response for Agent Rest Adapter

An issue occurred while performing Request and Response for the Agent Rest Adapter behind a non-open firewall. While data retrieval was successful, the message request and response were not updated. This issue has been resolved, and now they have been updated.

Resolved Insert/Upsert Error: Invalid Column name on Child Record, Including Table Name in Agent Database Adapter

An issue was encountered while setting up the V3 interface design for upserting/inserting records in a hierarchy. Specifically, an error occurred when attempting to insert a child record with an invalid column name. The problem stemmed from including the table name in the column during insertion. This issue has been resolved by omitting the table name from the column.

Resolved Issue: Stored Procedure Fails to Update Message Status in V3 Interface Design When Using Asynchronous Processing Mode

When utilizing a stored procedure within the V3 interface design in Asynchronous Processing Mode, an issue arises where the message fails to update upon completion of processing. This problem occurs due to a lack of response from the Agent to update the message in Salesforce, consequently keeping it in the 'New Message' state. This issue has been resolved by ensuring the Agent responds to update messages.

Resolved Issue Related to Retrieving All Records in Database When Getting Null Values in the 'where' Clause for Outbound Query Operations

When querying records using the request outbound interface with the 'where' clause of Agent Database, an issue arises when the clause receives a null value, resulting in all records being queried from the database. This problem has been resolved by selecting records where the column in the clause is null.

Fixed: Cannot run Flyway While Having a Postgres Password with Special characters during Installation

There is an issue if you have a special character in the PostgreSQL password, which can cause problems when running Flyway during the installation of a New Agent. This issue has been resolved by ensuring that Flyway can handle passwords with special characters by using double quotes around the PostgreSQL password in the Running Flyway script.

Fixed Issue: Did Not Get Response Interface with External Key Management in Asynchronous Processing Mode

We observed that in Synchronous Processing Mode, the outbound requests and responses support Internal Key and External Key Management. However, in Asynchronous Processing Mode, only Internal Key management is supported for requests and inbound responses. We have enhanced our New Agent to support both internal key management and external key management for requests and responses in Asynchronous Mode, aligning it with the capabilities of Synchronous Mode.

Fixed Get All Response Completed Message While Outbound Request Message Failed

There was an issue encountered when calling an API with multiple records, where some were processed successfully while others failed, leading to all responses being marked as completed. We have resolved this problem by ensuring that only the response message corresponds to the request's completion message status. For instance, if a business message request consists of ten records, with seven successfully processed and 3 failing messages, the inbound response will now include only the 7 completed messages.

New Agent Did Not Create Business Log While Doing Inbound Integration Processing with Database Adapter

In the previous version, the New Agent did not generate the business log during inbound processing with the Database Adapter. This issue has been addressed by reinstating the creation of the business log.

Clean Up Code for Session Management and Refactor Code in the Same Class and Method

• Clean-up session management for calling the Salesforce API entails logging in to Salesforce to obtain the session ID. In older versions (v1, v2), the Agent always logged in to Salesforce to acquire an access token before making API calls for integration (sending payloads). An enhancement involves checking if the session ID exists in the agent property; if the execution fails, indicating that the current session has expired or is invalid, the system should log in again to obtain a new session and retry the integration.
• Refactor the code within the same class and method to address duplicate code related to processing interfaces for API versions v1 (blank) and v2. Since these are older integrations with identical processing steps, the approach involves removing duplicates and consolidating any differences.

Fixed Various Issues with File Adapter

• Get a duplicate header with a CSV File Adapter in Append File Handling Mode while doing outbound processing to create the CSV file. This issue has been resolved.
• Fixed issue regarding “No such file” with SFTP protocol with Append and Override File Handling with support /folder and \folder.

Fixed Various Issues with Platform Event With New Agent

• Fixed issue regarding no sObject related to the message while processing with streaming with the Platform event, and raised an issue with "java.lang.NullPointerException: Cannot invoke "String.equals(Object)" because the return value of "com.skyvva.camel.beans.OutBoundRecords.getRecordId()" is null”. This issue has been resolved.
• Resolved the issue with 'Java.lang.StackOverflowError: null' that occurred when the event message lacked the Agent Message to encompass the event message with business data.

Fixed Retry Normal Integration

There was an issue with retrying the normal integration, as it was not functioning as expected. This problem has been resolved based on the Interface, Interface Group, and Integration. The priority order for resolution is Interface first, followed by Interface Group, and then Integration.

Fixed Various issues with Update Message, Generate Message, and Agent Database Adapter

• We have resolved the issue where messages were not updating correctly when the upsert child fails during outbound interface processing with the Agent Database Adapter for the upsert operation.
• Fixed delete operation does not update the child message
• An issue occurred during the request and response process with the Agent Database Adapter, leading to the generation of a duplicate root message response. This issue has been resolved.
• The issue of generating incorrect SQL in the child table for the update operation in the outbound process from the Agent Database has been fixed.