4. Enhancement
Migrate Bulk Delete Processing from Bulk API 1.0 XML to Bulk API 2.0 REST/JSON
Updated bulk delete message processing to use Salesforce Bulk API 2.0 REST/JSON instead of the legacy Bulk API 1.0 XML endpoint. The new flow creates a Bulk API 2.0 ingest job, uploads record IDs as CSV, and marks the job as UploadComplete for Salesforce processing. This improves compatibility with current Salesforce bulk processing behavior and updates response/error handling from XML parsing to JSON/HTTP status handling.
Added Advanced Search on Browse Logs File, Prevented Deletion of Backup Log Files from the Agent, and Added Clickable Breadcrumb Navigation
Added Advanced Search on the Browse Logs File screen. Users can now filter loaded log entries by Created Date or Modified Date, making it easier to find specific log files. Also improved the delete behavior for Backup Logs File and System Backup Logs File. The system now deletes only the related Salesforce ContentDocument records and no longer calls the Agent log-file delete endpoint. This prevents backup log deletion in Salesforce from accidentally deleting log files directly from the Agent. The breadcrumb path is now clickable, allowing users to jump directly to a parent folder instead of repeatedly clicking Up. Advanced Search date filtering was also corrected so records within the selected To Date minute are included in the search result.
Enhanced Support for Large Data in Agent Async Outbound Processing
In previous versions, Agent Async Outbound Processing could hit Salesforce governor limits when processing large parent-child data structures. For example, if one parent record, such as an Account, has many Contact child records and deeper child levels, Salesforce limits such as Apex heap size, CPU time, SOQL rows, SOQL queries, or DML rows could be exceeded. We have optimized Agent Async Outbound Processing to handle large chained data more safely. SKYVVA now splits large parent-child record trees into smaller parts and processes them across multiple Agent calls using hasMore and nextCursor. The process keeps the parent-child relationship, continues from the last processed position, and avoids missing or duplicating records. This optimization is supported only for Agent Async Outbound Processing.
Enhance Transport Route to Support Client Credentials OAuth2
This enhancement allows Transport Route to connect through Salesforce External Client Apps without using the username-password flow. It provides a more secure authentication method for server-to-server integration because no Salesforce user password needs to be stored or used during the connection.
With this update, customers can configure Transport Route to authenticate by using the OAuth client credentials flow from a Salesforce External Client App. This helps align the integration with Salesforce’s recommended OAuth-based authentication approach and improves security for automated connections.
Added a new Properties Configuration section under the Setup tab in the Agent Control Board.
Users can now load, review, edit, and save SKYVVA Agent application properties directly from the Agent Control Board. After saving changes, users can also restart the Agent Service from the same screen to apply the updated configuration.
This enhancement makes Agent property management easier because users no longer need to manually access or update the Agent configuration file on the server for supported properties.
The feature supports both connection modes:
- Direct Agent API calls
- Non-Open Firewall event action mode
Interface Group Handling Improvements
Enhanced Interface Group handling so users can clean up old or duplicate default Interface Groups from the UI. In some upgraded orgs, incorrect default groups could appear like system default groups and prevent users from correcting the setup. Real system default Interface Groups remain protected, while incorrect or duplicate defaults can now be renamed, corrected, or removed. This helps keep Interface Group data clean and supports a more consistent Agent Scheduler setup.
Improved the Interface screen so the Interface Group lookup only shows groups that match the Interface direction. This helps users avoid assigning an Inbound Interface to an Outbound Interface Group, or an Outbound Interface to an Inbound Interface Group. The update also protects existing Interface Groups from unsafe direction changes when they already have linked Interfaces.
Add Pagination support for existing Microsoft Azure Databricks Adapter
Previously, the existing Microsoft Azure Databricks outbound adapter could process only the first response page when the Databricks API returned data in multiple pages. For large result sets, this could cause incomplete processing because additional pages were not automatically requested.
This enhancement adds pagination support to the Microsoft Azure Databricks adapter. The adapter now supports Limit + Offset, Token Based, and Cursor Based pagination. SKYVVA can now continue requesting and processing additional result pages based on the selected pagination method.
This helps integrations handle larger Microsoft Azure Databricks responses more reliably and reduces the need for manual workarounds or custom logic to retrieve all available records.
Add Pagination Support for existing Microsoft Graph API Adapter
Previously, the Microsoft Graph API outbound adapter could read only the first page of data from the Microsoft Graph API. If Microsoft Graph API returned more records on additional pages, those records were not processed automatically.
This enhancement adds pagination support to the Microsoft Graph API adapter. SKYVVA can now continue reading the next pages by using Top + Skip or Next Link pagination. With this update, integrations can process larger Microsoft Graph API result sets more completely, without needing extra custom logic to fetch the remaining records.