Fixed A few Issues Reprocess the 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 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 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.
Added new ISINTEGER(text) Formula #
We have introduced a new formula called ‘ISINTEGER(text).’ This formula verifies if a given string can be converted into a valid integer. If the conversion is successful, it returns true; otherwise, it returns false. For example, ISINTEGER(’12’) returns true, while ISINTEGER(‘ABC’) returns false.
Fixed the Restore Wrong Value on the Source Field of the 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.
The Running Scheduler did not run anymore after rebuilding the Cache #
We encountered an error while the Agent Scheduler was running, and you clicked ‘Rebuild Cache’ under Cache Monitor on the Agent Control Board. This action deletes the old cache and upserts the Agent caches in the Postgres Database. The quartz job details will be removed during this process of deleting the scheduler agent cache. The scheduler will not run and raise the scheduler comment “Agent Response: The Scheduler with id: xxxxxxxxxxxxxxx is not running.”. In this scenario, we will forego deleting the cache after clicking ‘Rebuild Cache’ and only upsert the cache instead.
Resolved Issue: Invalid Type ‘Report’ and Message Monitor Accessibility with ‘High Assurance Session Required’ Enabled #
There is an issue related to the ‘IExportController’ class when calling the Skyvva API. Within the class, there is a variable named ‘public IntegrationAdminTab admin’. Although the ‘IntegrationAdminTab’ class includes a method that queries the Report object, this method is never invoked during the integration process, and the user is also not able to access message monitoring. This limitation arises when the user enables the ‘High Assurance Session Required’ Salesforce feature. To address this issue, we have implemented solutions for both enabling and disabling the ‘High Assurance Session Required’ setting.
