Missing Some Value2__c Adapter Database Properties When Cloning/Restoring the Interface Linked to This Adapter #
There is an issue when using the clone/restore function to replicate the interface that links to the Agent Database. After cloning, the adapter loses value2__c of the connectionURI and hostname properties, which can lead to problems when processing interfaces with that adapter. This issue has been resolved.
Resolved various issues related to ‘Import Database IStructure’ within the Creation Interface Step #
There are some issues concerning the ‘Import Database Structure’ within the Creation Interface Step as follows:
- Fixed the issue of losing the initial Source Name selection after clicking the cancel button on the Import Database Structure screen
- Resolved the issue of the ‘Import Database Structure’ button remaining enabled even after exiting the Agent Database Adapter from the interface creation step.
- Fix the issue of losing the initial Operation Type selection after clicking the cancel button on the Import Database Structure screen.
- An issue was identified with ‘Import Database Structure’. When creating an interface, an IStructure was generated. Subsequently, creating another interface on the same page without clearing the existing IStructure caused it to be retained in the cache. This caused the new interface to also inherit the previous IStructure. The issue has been resolved by clearing the IStructure cache when creating a new interface on the same page.
Fixed ‘Object Type’ Filter for Cache Monitor #
An issue arises when you apply a filter for Object Type set to ‘All’ in Cache Monitor, resulting in a loss of caches for objects such as Integration, Interface, and InterfaceGroup. This problem has been resolved by displaying all objects without missing any objects.
Resolved the issue of Duplicate Interface Records in the ‘Where to Use Inside’ Option of the Adapter #
There was an issue with the ‘Where to Use’ function in the Adapter for searching the interfaces that use this adapter. However, if a space was inadvertently typed, the screen might display duplicate interface records. This issue has been resolved.
Fixed Cannot Edit Adapter and Stop Consumer of Agent Adapter File #
An issue was identified during the integration backup involving the interface link to the Agent File Adapter. Specifically, when starting the consumer from one organization and restoring it to another organization for the Agent Adapter File, users were unable to edit or stop the consumer of the Agent File Adapter after the restore.
This issue has been resolved. Now, after the restore, the agent connection destination is removed, and the consumer of the Agent File Adapter is automatically stopped when restoring it to the other organization. Additionally, we have implemented a solution to prevent cloning an interface that is already linked to the Agent File Adapter during the start of the consumer process.
Fixed Cannot Edit Adapter and Stop Consumer of Agent Adapter File #
An issue was identified during the integration backup involving the interface link to the Agent File Adapter. Specifically, when starting the consumer from one organization and restoring it to another organization for the Agent Adapter File, users were unable to edit or stop the consumer of the Agent File Adapter after the restore.
This issue has been resolved. Now, after the restore, the agent connection destination is removed, and the consumer of the Agent File Adapter is automatically stopped when restoring it to the other organization. Additionally, we have implemented a solution to prevent cloning an interface that is already linked to the Agent File Adapter during the start of the consumer process.
Fixed Issue: Delete All Batch Basket and History Basket inside the Batch Control Board #
There is an issue when clicking the ‘Delete All’ button in the Batch Basket Control Board; the action also deletes all Bulk Baskets. This issue has been resolved by updating the function to delete all batch baskets without affecting the bulk baskets. Additionally, we have fixed the screen responsiveness for ‘delete all history baskets’ confirmation on the batch control board, which was previously unresponsive on the screen.
Fixed Connection Name filter for Adapter Records on Agent Control Board #
The Connection Name filter in the Adapter Records section of the Adapter Tab on the Agent Control board shows the connection Name of the Old Agent Connection. This issue has been fixed by filtering only the New Agent Connection Name.
Fixed Filter Message on CDC Control Board #
The message in Message Monitoring on the CDC Control Board was not displayed in the ‘All’ mode when requesting and responding with CDC processing covered by the API Message. In such instances, filtering the message with all modes enabled on the CDC Control Board did not display the CDC message. This issue has been resolved by allowing the display of the CDC message under the API Message and showing only the CDC message covered by the API Request/Response Message.
Fixed Issue: Select Baskets with Multi-Processing Type #
The message in Message Monitoring on the CDC Control Board was not displayed in the ‘All’ mode when requesting and responding with CDC processing covered by the API Message. In such instances, filtering the message with all modes enabled on the CDC Control Board did not display the CDC message. This issue has been resolved by allowing the display of the CDC message under the API Message and showing only the CDC message covered by the API Request/Response Message.
Resolution of Cache Clearing Issue During Interface Switch From Agent to Non-Agent Adapter #
The associated cache was not cleared when the interface was switched from the Agent to a non-agent adapter. This issue has been resolved by removing the caches related to that interface within Salesforce and the agent, except for the Adapter, Properties, Integration, and Interface Group caches.
Fixed Agent File Adapter Screen When Selecting ‘Binary’ as the File Type #
There was an issue when selecting the File Type as Binary, Binary File, Binary Folder, and Reference Field, along with properties inside the create and edit Agent File Adapter screen. This problem has been resolved by removing those properties from the screen, as they are not used when the Agent File Adapter is set as a Binary File Type.
Remove Response Message When Request Does Not Find Any Records #
There was an issue encountered during the request and response processes with the Agent Database. Queries were executed in the request interface to fetch records, and the resulting responses were utilized for upserting, inserting, or updating in Salesforce. When no records were found in the request, a ‘pending’ response message was triggered due to asynchronous processing. However, in synchronous requests where no records were found, it would create a ‘failed’ message with the comment ‘Please check response payload and inbound Interface!’ was issued. This problem has been resolved by ensuring that if the interface request does not return any records after the query, the response interface will not generate any additional response messages.
Resolved Missing Cache Issue in Request and Response Interfaces in Asynchronous Mode #
We have resolved the interface cache issue related to your request and response in asynchronous mode. If the interface cache is not sent in the correct order at the interface level chain, some sub-interfaces may be missed. This could impact processing when these caches are not available.
Fixing Missing Initial Property in All Adapter Types #
There was an issue during the creation of the adapter where initial properties like Username, Certificate Name, OAuth 2.0 flow, or API Key Name were not displayed as expected. This problem has been resolved by adding back these properties.
Resolved the Stored Procedure of Agent Database Processing Issue with Request and Response #
There was an issue encountered while processing the Agent database using the ‘Stored Procedure’ operation type with the request and response interface. After processing the response, the agent encountered an error with the root message being ‘New’ because no response was received after the request. This issue has been resolved by ensuring the response is processed correctly.
Resolved Query Editor to Execute Records for Outbound Manual Process #
We encountered an issue where the user intended to perform Outbound Processing manually using the ‘Manually select the sObject using the Query Builder?’ option. When the user added an additional WHERE condition after executing the query statement by clicking the ‘Execute SOQL’ button, an error message was triggered, indicating an ‘unexpected token’ and ‘Where’ twice. This problem has been resolved by preventing the addition of an extra WHERE condition when executing the SOQL button.
Resolved Issue: Reset Start Index to 0 When No Records in Response #
There is an issue with the Start Index not being set to 0 when requesting data with no records in response from Sage 100. Subsequently, when the scheduler runs again, the user is unable to retrieve the most recent update record and gets only the last Index record. To address this, we have implemented a fix where, after the last request and no records in the response, the ‘Start Index’ will be automatically set to 0.
Resolved Issue: DoAlert Scheduler Limiting Selection of Failed Messages #
There is an issue when using the DoAlert feature to fetch failed messages for email alerts. This problem can occur when a significant number of failed messages are present, leading to an error in the apex job with the message: ‘Scheduler: failed to execute scheduled job: jobId: xxxxxxxxxxxxxxx, class: common.apex.async.AsyncApexJobObject, reason: Apex heap size too large: xxxxxxx’, consequently causing the scheduler to halt. To tackle this issue, the problem has been resolved by restricting the selection to only 1000 failed messages to avoid hitting the limit.
Resolved Multiple Issues with Query Editor for Using V4/Query #
There are various fixed issues inside the Query Editor for use with V4/Query as follows:
- Fixed the issue of not loading the sObject field while appending the tree node inside the Query Editor.
- Resolved the problem of losing the sObject tree node and field when selecting the interface name inside the Query Editor.
- An issue occurred when a query contained a parameter within the WHERE condition, for instance, Name = {!param}. Clicking the “Execute SOQL” or “Test SOQL / Count Records” button resulted in an error message stating “Error! Unexpected token.” This problem has been addressed by introducing a dialog screen to provide a parameter value for executing the query.
- Corrected the problem of saving the query statement in the incorrect location in the Database Query, rather than the Query field. It has now been rectified to save in the Query field.
- A problem was identified in the Query Editor Tool for inbound V4/Query, where the WHERE condition did not consider the Where-Expression field of the Query Template from the message Type. However, it was retrieved from the sObject when using the query editor for the first time. This has been resolved by considering the field from the Where-Expression of the Query Template.
- Fixed the issue of missing the query (Select field1, field2, xxxx From sObject) and only obtaining {!__SKYVVA__WHERE-Clause} in the Query Editor upon loading. The Query Editor now retrieves all query statement values when loading.
Resolved Payload Issue in Agent Rest Adapter with sObject Structure Mapping #
In the previous version, during inbound processing or the Agent File and Agent Database Adapter with External Mapping involving flat mapping in Interface V3 design, mapping the root node of the sObject Structure was necessary. Failure to map this would result in processing errors. To address this, adjustments have been made to the flat mapping of the External Mapping in the Interface V3 design. Mapping the sObject root node is no longer required, except for use cases where mapping is hierarchical. It is important to note that the Agent Database supports only flat mapping with External Mapping.
Fixed Issues in Manual Processing Across Various XXXX Control Boards #
When you have only one inbound or outbound interface selected and attempt to process it using the ‘Manual Process’ button, an alert message appears: ‘Warning: You can not process Inbound and Outbound Interface at the same time. Please select only Inbound or Outbound Interfaces.’. This issue occurred across various XXXX Control Boards, such as the Amazon and Oracle Control Boards, and others. This issue has been resolved by removing the warning message when selecting the same direction for interface processing. Now, proceed by selecting only one direction, which is now functioning correctly.
Resolved Issues: Scheduler Settings for Oracle and Amazon Control Boards #
The following issues have been fixed:
- There was an issue when accessing the Scheduler tab in the Oracle and Amazon Control Boards. An error message appeared: “Error: Attempt to de-reference a null object.” This issue has been resolved by generating the scheduler settings, and the error message no longer appears.
- Additionally, an issue where the Scheduler in the Oracle and Amazon Control Boards did not work with the Scheduler per Integration and per Interface Group has also been fixed.
Resolved Issues: Importing Database IStructure in the Create Interface Screen #
The following issues have been fixed:
- When the Agent Database Adapter was removed from the Adapter field, the Import Database IStructure button remained on the Create New Interface screen. This issue has been resolved, and the button is no longer displayed after the adapter is removed.
- When canceling Import Database IStructure and returning to the ‘Create New Interface’ screen for the Outbound direction, the Source (Select or Enter) field no longer remains set. This issue has been resolved.
- There is an issue when you use “Import Database IStructure” inside the Create New Interface Screen for the inbound interface. After import database Istructure, it will return to the “Create New Interface Screen, then the Operation Type of Interface will turn to defalut value and will not exist with the selection value. This issue has been fixed.
Fixed Issue Where No Business Response Records Were Created for Agent Database Adapter #
There was an issue when performing an outbound request to query records from the database and processing the response for inbound handling. Although the database returned records, the response contained no records. As a result, failed messages were created for synchronous processing, and records were left pending for asynchronous processing without business message records. This issue has been resolved by ensuring that no messages are created when there are no business messages to return.
Fixed Issue with Custom Format with Agent File Adapter with Non-Open Firewall #
There was an issue during outbound processing with the Agent File Adapter (Content Format = Custom and Custom Processing Class) in non-open firewall mode. It faced difficulties creating a custom message without a business message and an agent message. This problem has been resolved to prevent the duplication of root messages and ensure the creation of only a Custom Message to cover the business message.
