Fixed Cache Issue When Deleting Integration and Interface #
We encountered a pending cache issue after you deleted the integration and interface. This issue has been resolved: when the integration and interface are deleted, all associated caches and child caches are also removed.
Fixed Restore Wrong Value on Source Field of IMapping Record #
We encountered a problem while restoring the IMapping record. It retrieved the old source value into the Source field, which could cause issues during integration. This issue has now been resolved, and the correct value has been restored as expected.
Outbound Scheduler Delayed Several Seconds For Next Scheduler #
We encountered an issue during rescheduling that caused several seconds of delay for the entire Skyvva scheduler. To address this, we have changed from using DateTime.now(), we now store the previous time and the next scheduled time in the InterfaceControlRuntime__c object. By utilizing the ‘SchedulerSubmittedTime’ field rather than DateTime.now(), we aim to prevent delays of several seconds for the next scheduler run.
Import Database Message Type for Inbound Processing #
We currently have a database template for outbound database processing. Now, we need to create an inbound message type for the inbound database message template for the V3 processing. This requires us to consider our adapter for a generation. If the outbound adapter is chosen, we will keep the existing database template message type. If an inbound adapter is selected, we will generate two levels of messages: one being the Database Table Template and the other being the table name with the ‘Database Table’ type. Additionally, we will use an indicator under the name of the adapter to show whether it is inbound or outbound, making it easier for users to identify their adapter.
Resolution of Error: ‘Invalid Decimal’ Message in Interface Creation Due to Accidental Space Entry #
While creating a new interface with bulk mode and input space, an error occurred due to an accidental space entry in the Bulk Package Size field, resulting in the message ‘Invalid decimal:’. This issue has been resolved by eliminating the space before creating the interface.
Enhance Support Import Database Metadata for Non-Open Firewall #
In the previous version, the Import Database Metadata feature only supported open firewalls. In the latest update, we have enhanced this functionality to also support non-open firewalls for creating the Database Message Type on the Salesforce side.
Fixed Preventing Automatic Creation of IStructures from Filter Field Queries in Cases of Manually Created Old IStructures Using Database Adapter #
In the previous version, during outbound processing, users were able to add a Salesforce query to the Filter field. This action resulted in the generation of the query field and IStructure in the outbound interface due to the manually created column field in the table database on IStructure Interface. However, if confusion arose during the mapping of this field for agent database processing, it led to errors indicating invalid columns on the table during post-processing. To address this issue, a prevention mechanism has been implemented to prevent the creation of IStructure in the interface from the query for the outbound interface of the Agent Database.
Fixed Duplicate Id Issue in List: xxxxxxxxxxxxx in Mapping Tool, When Saving the Mapping #
We are currently encountering an issue with the existing mapping for outbound processing. The user is mapping a source node to a multi-target node. After remapping and saving the configuration, an error occurs: ‘Error while saving mapping 194 >> System.ListException: Duplicate Id in List: xxxxxxxxxxxx’. This problem arose as we attempted to create an unnecessary sub-interface. Fortunately, this issue has now been resolved.
Fixed Outbound Processing Issue with “Apex heap size too large: xxxxxxxxxxx” and got Exception: Read timed out #
We have observed an issue occurring in the Business Message without Agent Message during Outbound Agent Database Processing, manifesting as ‘Apex heap size too large: xxxxxxxxxxx’ and resulting in the exception ‘Read timed out’. This problem arises when querying messages for processing in the Agent Database. If the root message’s Agent Message is null, and an attempt is made to fetch the child message’s sObject Message using rootMessageId = null, all messages are retrieved for reprocessing. Consequently, this process decelerates gradually, leading to timeout errors and heap size issues. To address this issue, we are implementing a validation check to ensure that the sObject Message ID is utilized in place of the root message when it is absent.
Fixed Missing Label Name Connection Tab of Connection Destination Configuration #
We are missing label names for steps four and five in the Agent SAP ERP and Agent SAP S/4HANA Connection Types. Without these labels, you might skip steps four and five and see only ‘Agent->’ and ‘->Agent’. We have rectified this by adding ‘Agent -> SAP ERP’ and ‘SAP ERP -> Agent’ for SAP ERP, and ‘Agent -> SAP S/4HANA’ and ‘SAP S/4HANA -> Agent’ for Agent SAP S/4HANA.
Fixed Various issues on the Configuration Tab of the Agent Control Board #
- In the Agent Connection Destination section, we can switch between Username-Password OAuth2 and Client-Credential OAuth2, so the previously saved data remains on the screen. When the user switches the Authentication Type, they must input the new values. However, the cache and agent properties do not delete the username and password after saving values with the OAuth2 Client-Credential Authentication Type. This issue has been resolved by requiring the user to input new data while switching and delete the necessary cache after switching.
- When pinging the Agent to Salesforce, the request payload for the ping is missing proxy values such as proxyUse, proxyUsername, proxyPassword, proxyHost, and proxyPort. This issue has been addressed by including these values in the payload while the user is using the New Agent 3.06.01.
- Update the mandatory input fields, proxyUsername and proxyPassword, to be optional inputs, and move them below proxyHost and proxyPort.
Fixed Issue Cache While Outbound Request and Inbound Response Link Together #
An issue arose during the design of the outbound request interface and the link response interface to the outbound request interface. The Response Interface did not cache to the Agent Cache. This issue has been resolved. While the user is linked with the Ref Field, we will send all cache-related data from the parent and child cache records.
Fixed A few Issues. Reprocess Message with Max Number Of Retry #
- There was an issue where the failed message did not reprocess despite the Max Number of Retry setting on the integration. This problem has been resolved by querying ‘RootMessage__r.Integration__r.Max_Number_Of_Retry__c’ during the ReachMaxRetry check. Now, the messages are processed as expected.
- The root message that incorrectly counted retries has been fixed. The Retry Counter no longer needs to be counted in the root message. It will now count business messages on its own.
Fixed Interface Cache Not Ordered into Agent Cache #
There was an issue when saving mappings, updating the cache, or rebuilding the cache with the interface hierarchy. The interface cache was unordered, leading to problems. This issue has been resolved.
Enhanced Salesforce Reprocess Event Message with New Agent 3.06.01 #
In the previous version, the event message did not support reprocessing. However, in Salesforce, we have enhanced it to include support for the reprocessing feature with New Agent 3.06.01.
Fixed Incorrect Warning Message during Manual Processing while the Interface Type is not Main-Interface #
There is an issue where the interface type is not set to Main-Interface, and a warning message stating ‘Interface not found. Id: (xxxxxxxxxxxxxxx). Please make sure your interface is in Deployed mode.’ appears, despite the interface already being in Deployed mode. We have now updated the alert warning to ‘Interface Id: (xxxxxxxxxxxxxxxx) is not set as the Main Interface’.
