Fixed Agent SOAP Adapter without Response #
There was an issue with processing requests and responses using the Agent SOAP Adapter, resulting in the response not coming back. This issue has been resolved on the Salesforce side, specifically regarding the actionDoIntegrate being set to false during the request and response. In this case, you will receive an Agent message with a status of ‘New’ and a corresponding request business message marked as completed, without updating the Agent Message. The issue has been addressed by setting actionDoIntegrate to true; thus, the response interface will be executed, and both the request and response will be processed, allowing the message to update correctly.
Fixed Cache Issue When Deleting Custom Interface Group #
There is an issue when you delete a custom group that contains an interface used with the New Agent. In this case, the cache for this interface group is not deleted, nor is the interface cache updated to link back to the default group. This can cause problems while processing the interface group. This issue has been resolved by deleting the interface group cache and updating the interface cache to link back to the default group when a custom group is deleted and is being processed with the new agent.
Fixed Agent Rest Adapter without Response while Response Format is XML #
We encountered a problem when making requests in JSON format while receiving responses in XML format with the Agent REST Adapter. This issue has been resolved on the Salesforce side, specifically regarding the actionDoIntegrate being set to false during the request and response. You will not receive a response message, and the Agent Message will have a status of ‘New,’ while the Business Request message is marked as completed. This issue has been resolved by ensuring that the response is properly handled, creating the appropriate business response message, and updating the Agent correctly.
Fixed Now() formula without format #
Currently, the Skyvva NOW() formula function supports both usages:
- Without parameters, which uses the default format: dd.MM.YYYY HH:mm:ss.
- With parameters, where the parameter explicitly defines the date/time format, for example: dd.MM.yyyy HH:mm:ss.
The issue you encountered happens only when the function is used without parameters. In this case, the default format uses YYYY (ISO week-based year). During the last days of December, if a date falls into ISO week 1 of the following year (for example, between 29.12.2025 and 04.01.2026), YYYY will resolve to the next year, even though the calendar date is still in December. This issue has been fixed by using yyyy instead of YYYY.
Fixed Remaining New Message Root When Workflow Sets ‘Delete Message’ on ‘Action When All Conditions Are Not Met’ #
There was an issue when the workflow was set to ‘Delete Message’ under ‘Action When All Conditions Are Not Met.’ When the business message did not meet all conditions of the workflow, it would be deleted; however, the root message covering the business message would remain in a ‘New’ status and would not be deleted. This issue has been resolved by including the deletion of the root message.
Fixed Various Issues Regarding the Queue Monitor in Agent Control Board #
There are a few issues regarding the Queue Monitor in the Agent Control Board that have been fixed as follows:
- Fixed the issue where the text overlaps with the Queue Name freeze column while scrolling to view the queue records on the left side.
- Resolved the issue that prevented the deletion of the selected queue due to the queue record ID not being passed for deletion.
Fixed Various Issues Regarding the Interface Group #
Several issues related to the Interface Group have been fixed as follows:
- Fixed the issue where some interfaces linked with an adapter, while others were not linked or were in development. When performing Group Processing on the Interface Detail page, all interfaces would fail to execute. This issue has been resolved, allowing only interfaces linked with the adapter and in the deployed status to execute.
- Resolved an issue with reordering interfaces within the Interface Group on the Detail page. Previously, after entering a value for the interface sequence and saving it, the sequence value was not retained. This issue has been addressed by redesigning the input method, enabling proper reordering of the interface sequence.
Fixed Various Issues Regarding the Query Editor Tool #
Fixed a few issues related to the Query Editor as follows:
- There was an issue when using the Agent Database Adapter for inbound interfaces in a non-open firewall mode. Opening the Query Editor resulted in a continuous spinner. This issue has now been resolved by stopping the spinner and successfully loading the Query Editor Tool.
- There was an issue when using the Agent Database Adapter for inbound interfaces in Initial Mode. After processing the data record from the Query Editor Tool, the Initial Mode was not unchecked. This issue has been resolved by ensuring that Initial Mode is unchecked after processing.
Fixed Issue with Response Based on Interface Processing Mode When Using Dynamic Switch based on record size of Batch Mode #
An issue occurred when the “Batch Mode” flag and the Dynamic Switch based on record size were enabled. When the message size is less than the Record Size To Be Switched setting, and the messages are processed immediately, the response is returned in synchronous mode instead of reflecting the selected interface processing mode. This issue has been resolved by ensuring that the response is returned according to the specified interface processing mode (synchronous or asynchronous).
Fixed Issue TransportRoute on MetaData Provider, Message Type, and Repository #
There were issues with the TransportRoute related to Metadata Provider, Repository, and Message Type records, which prevented you from sending these records to another organization via TransportRoute. This issue has now been resolved, enabling you to send these records through TransportRoute.
