Fixed issue allowing the saving of the Inbound Agent File adapter without a required value in the Content Format field #
We are experiencing an issue with the inbound Agent File adapter, possibly caused by saving without any value in the Content Format required field. This may result in an error during processing. The problem has been resolved by adding a default value, ‘SKYVVA Message’.
Resolution of Error in Resizing Columns Table View Inside Agent Control Board #
There was an issue encountered when resizing the columns in the Table View of the Agent Control Board, affecting all functions that call this table view. This led to a pop-up error message: ‘[Cannot read properties of undefined (reading ‘contains’)].’ This issue has been resolved.
Cache Monitor did not display the Cache Record #
We encountered an issue where the cache record was not displayed on the cache monitor of the agent control board when the interface type was null after upgrading the version. This problem has been resolved by enabling the display of cache records of Null within the same main interface type.
Fixed Get Black and Error Pop-Up Screen on Interface Detail Page #
While scrolling up, down, and editing on the interface detail page, an issue was causing a black screen and pop-up screen or displaying an error message: ‘Uncaught Action failed: skyvvasolutions:InterfaceInboundOutboundStep$hidePopover[propover.getElement is not a function].’ We have now resolved this problem.
Resolved Issue with Outbound Processing When Starting Where Condition with Round Brackets #
There is an issue when your query has a WHERE condition starting with round brackets, for example, ‘WHERE (Name <> ‘dd’ OR Name <> ‘test’) AND BillingCity = ‘PP’. It encountered an error in the log of the Outbound Processing Component as shown below:
“V3OutboundUtils.SQLBuiler>reBuildQuery>AfterWhere: WHERE () AND (Id IN :ids)(Name <> ‘dd’ OR Name <> ‘test’) AND BillingCity = ‘PP’reprocess:Eorr-Message: unexpected token: ‘)’ >Detail:(skyvvasolutions)”
This issue has been resolved.
Resolution: Correcting Message Deletion Functionality in Integration and Interface for Outbound Processing using Agent xxx Adapter #
There was an issue when you selected ‘Delete Completed but keep other Messages’ on the interface and ‘Delete Message’ in Integration, despite performing outbound processing using Agent xxx Adapter, the completed message continued to exist in Salesforce. This problem has been resolved by deleting the completed message when this flag is checked.
Resolved: Fixed the Interface Screen’s Continuous Spinner Issue When Adding Event Type Outside of Events Configuration Section #
We encountered an issue when accessing the interface details page, causing a continuous spinner due to adding the ‘Event Type’ field outside the Events Configuration section. This problem has been resolved, allowing you to add any section without encountering errors.
Resolved the Issue of Missing Connection Destination from the Adapter After Cloning the Interface #
There is an issue when you have a cloned interface with an adapter linked to the Connection Destination adapter property. This can result in a lost Connection Destination for the Adapter after cloning the interface. This issue has been resolved.
Fixed Workflow Did Not Set Messages to New While Not Met All Conditions Of the Workflow #
There is an issue when setting the ‘Update Message status to ‘New’’ on ‘Action when all Conditions not Met’ option on the Workflow Settings. When processing a message that does not meet all conditions, the status is not updated to ‘New’ but instead set to ‘Completed’. This issue has been resolved.
Automatically Setting the Sequence for Interfaces after Cloning, Restoring, and Interfaces Sequence Inside the Default Interface Group #
There was an issue where cloning and backing up an existing interface resulted in a duplicate sequence alongside the original. Furthermore, setting the interface sequence within the interface group did not properly establish sequencing. This problem has been resolved by increasing the maximum sequence by one during the cloning, restoration, and sequencing of interfaces within the default group.
Minimize Unnecessary Calls to the Salesforce API for Message Reprocessing by the New Agent in Non-Open Firewall Mode #
There is an issue when a New Agent is using non-open firewall mode; it will automatically use Asynchronous processing. When reprocessing a message, the New Agent will make multiple API calls to Salesforce for message reprocessing unnecessarily. This issue has been resolved by calling only a message update after completing the message reprocessing.
Loss of Agent Connection Destination from Agent xxx Adapter During Destination Name Rename #
When renaming the Agent Connection Destination, all associated Agent xxx Adapters linked to this Destination are lost. This issue has been resolved by ensuring that all Agent xxx Adapter links remain connected to this Connection Destination.
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.
Fixed Issue Agent Retry to Update Message Via Processing with Skyvva CDC #
There is an issue encountered when updating the message and logging the problem during the update process. This issue stems from messages that have not been generated in Salesforce yet, which is why the Agent is unable to effect the update. The New Agent attempts multiple retries to update the message. This problem has now been resolved by transitioning to asynchronous processing using Skyvva CDC and the Agent xxxx adapter. This adjustment ensures that once the message is fully created, Salesforce calls upon the agent to process the data, and the agent calls to update the message.
