2. Enhancement

Enhancement: Simplified V3 Message Processing for SAP BTP Integration Suite and the New SKYVVA Agent

SKYVVA has enhanced the /createNewMessage and /processMessage APIs to support the V3 request format used by SAP BTP Integration Suite (SAP CPI) and the new SKYVVA Agent.

Previously, the APIs already supported multiple messages, but messages had to be placed inside SKYVVA’s previous request structure. For message creation, the request separated the message information from the business data. For reprocessing, the request required additional status and processing-mode information and was limited to 200 messages.

Now, the SAP CPI and the new SKYVVA Agent can send messages using a simpler list-based format.

/createNewMessage accepts a list of prepared message records. The message information and business payload are included in each record.
/processMessage accepts a list of existing SKYVVA message IDs.
V3 reprocessing always runs as a background batch job.
The previous 200-message reprocessing limit does not apply to V3 requests.
SKYVVA returns a job ID so the background job can be tracked.
Invalid message IDs are reported to the calling system.

This enhancement makes large-volume message processing easier for SAP CPI and the new SKYVVA Agent. It reduces request preparation, requires fewer API calls for large reprocessing workloads, and allows Salesforce to manage the work through background batch processing.

Note: The existing integrations can continue using the previous request format without changes. The new list-based format is available specifically for SAP BTP Integration Suite and the new SKYVVA Agent.

Configure Separate Automatic Cleanup Settings for Each Log Type

Previously, automatic log deletion was controlled by a general setting in Global Configuration. This existing setting remains available and continues to work as before.

Now SKYVVA Agent generates a few more types of logs, including Interface Logs and PUB/SUB Logs. Because each log type may need a different retention period, a single general cleanup setting may not meet every operational need.

To provide more control, a new Automatic Log Cleanup section has been added to Log Configuration. This is an additional configuration option and does not remove the existing setting from Global Configuration.

Users can now:

Continue using the existing automatic log deletion setting in Global Configuration.
Set a separate retention value for each supported log type in Log Configuration.
Enter 0 to disable automatic cleanup for a specific log type.

If the connected Agent version does not support the new automatic log cleanup controls, SKYVVA hides the settings or displays a warning to prevent users from applying an unsupported configuration.

Create IStructure for V2 of Source Definitions from JSON Files

Previously, users could not upload a JSON file to create a Structure Payload from Source Definition. They had to create the structure manually or convert the JSON file into another supported format.

Users can now upload a valid .json sample file, and SKYVVA automatically creates the Source Definition.

Nested JSON fields are converted into usable field paths.
For JSON arrays, the first item is used to create the structure.
Invalid JSON files are rejected with an error so users can correct them.

This feature reduces manual configuration and helps ensure the Source Definition matches the actual JSON message structure.

Add Keep File and Lock File Controls for File Adapters

Previously, users could not select Keep File or Lock File when configuring what should happen to a source file after processing.

The following options are now available in the File Adapter configuration:

Keep File: Keeps the original source file after processing.
Lock File: Protects the file during processing to help prevent another process from using the same file at the same time.

These options give users more control over source files and help prevent files from being removed or processed by multiple processes unexpectedly.

Highlight Job Warnings, Failures, and Comment Agent Schedulers When Not Run

In the previous version, job warnings, failures, and scheduler comments (When the Agent Scheduler Does Not Run) were displayed as normal comment text. Users could easily miss important problems when reviewing a long list of jobs.

SKYVVA now uses colors to make these conditions easier to identify:

Yellow: The process completed with a warning.
Red: The process failed, and the scheduler has not run since the displayed time.

Now users can quickly identify jobs and schedulers that require attention without viewing full information

Add SOAP, Named Credential, and Legacy Payload Options for SAP BTP Integration Suite

When configuring SAP BTP Integration Suite, users select the Protocol and Authentication Type on the Connection Destination and select the Payload Format on the Adapter.

Previous limitation: The configuration provided HTTP with Basic, OAuth 2.0, or Certificate authentication. Outbound messages used the V3 payload format. Users could not select SOAP, use a Salesforce Named Credential, or keep an older SAP PI/PO payload structure when moving an integration to SAP BTP Integration Suite.

Enhancement: SKYVVA has added:

SOAP as a Protocol option. HTTP remains the default.
Salesforce Authentication Provider as an Authentication Type. Users provide a value in Named Credentials, which manages the endpoint and authentication.
A Payload Format field with these options:
- V3 Payload Format — the existing and default format.
- SAP-PO Payload Format — keeps the payload structure used by SAP PI/PO.
- SFDC2SAPI Payload Format — keeps the older SFDC-to-SAP PI XML structure and requires SOAP.

Users can connect to SAP BTP Integration Suite through HTTP or SOAP and choose an authentication method appropriate for their environment. Customers moving from SAP PI/PO can keep the payload structure expected by their existing SAP mappings. Existing configurations continue using HTTP and V3 unless the user selects different options.