4. Enhancement

Load and Refresh SKYVVA Settings in SAP Integration Suite

The adapter kept a local copy of SKYVVA settings, called a cache, so it did not need to retrieve the same settings from Salesforce for every message. However, changes made in SKYVVA could leave the adapter using older settings until the cache was cleared or the runtime restarted. Now, when you enter Integration and Interface names in the receiver configuration and deploy the iFlow, the adapter retrieves their settings from SKYVVA and stores them locally for reuse. If the configured integration or interface cannot be found, startup reports an error. This startup check is skipped when either field is empty, or its value is supplied dynamically. The adapter also supports configuration-change notifications from SKYVVA. When a supported notification arrives, it clears the affected local settings. The next processing request retrieves the updated settings automatically. Supported configuration areas include Integration, Interface, Mapping, Adapter, Property, and CPI Setting.

Example

You configure Integration A and Interface B, then deploy the iFlow.
The adapter loads their settings and reuses them for subsequent messages.
You change Interface B in SKYVVA.
SKYVVA sends a supported change notification to the adapter.
The next request loads and uses the updated settings.

The adapter reduces repeated requests to Salesforce and can apply updated SKYVVA settings without restarting the iFlow, provided it receives the supported change notification.

Compatibility and Upgrade Note

Use SKYVVA version 2.51.20 with SKYVVA Salesforce Adapter 1.3.0 and redeploy the iFlow after upgrading. The adapter then refreshes affected cached settings when it receives configuration-change notifications from SKYVVA.

Add Integration and Interface fields to V2 receiver configuration

The Integration and Interface fields were available only when Skyvva API Version was set to V3. Users could not enter these names in the V2 receiver configuration. Now the receiver displays Integration and Interface for V2 processing as well.

In the receiver’s Processing tab, select:

Field	Selection
Processing Type	Skyvva
Operation	Integrate
Skyvva API Version	V2

Enter the target Integration and Interface names alongside the existing Skyvva API and Apex Method settings. Now the customers can enter and review the target SKYVVA integration and interface directly in the V2 receiver configuration, making these settings easier to maintain.

Added Standard Salesforce API Support to the Receiver Adapter

Previously, the receiver adapter focused on SKYVVA integration and did not provide standard Salesforce API processing options.

The new Processing Type picklist now offers two options:

Salesforce
SKYVVA

When Salesforce is selected, the Type picklist provides the following options:

REST
REST Bulk
REST Bulk 2.0
REST Place Order
Event Processing
Apex Call

The available Operation and configuration fields depend on the selected Type.

When SKYVVA is selected, the adapter displays the SKYVVA integration settings.

Users can now choose either a standard Salesforce API or a SKYVVA integration path within the same receiver adapter. For example:

Select Salesforce → REST to perform a standard Salesforce object operation.
Select SKYVVA → SKYVVA Integration to process data through a configured SKYVVA integration.

New Operation Selection for SKYVVA Receiver Processing

Previously, the receiver provided SKYVVA integration settings for sending data to Salesforce, without a dedicated Operation picklist for choosing between integration processing, event publishing, and data retrieval.

A new Operation picklist under Processing Type = Skyvva brings together the existing integration capability and two new operations:

Skyvva — Existing: Send data from the iFlow to a configured SKYVVA integration and interface using the selected processing mode.
Platform Event - Publishing — New: Publish a Salesforce Platform Event directly from the iFlow using JSON or XML data, without calling a SKYVVA API. Configured subscribers can receive the event and perform the corresponding business action.
Query — New: Retrieve Salesforce data through SKYVVA, including related records such as Accounts and Contacts, and return the results to the iFlow for mapping or further processing.

Customers can select Integrate to send business data through SKYVVA, Platform Event - Publishing to publish events directly to Salesforce, or Query to retrieve Salesforce records through SKYVVA.

Add Structure Format selection for V3 data processing

The receiver did not offer a Structure Format selection for V3 processing. Customers had to prepare their data using the existing supported structure.

A new Structure Format picklist lets customers choose how their JSON data is organized.

In the receiver’s Processing tab, select:

Field	Selection
Processing Type	Skyvva
Operation	Integrate
Skyvva API Version	V3

Then select the appropriate Structure Format:

Skyvva Format: Use the existing structure containing the business object and, optionally, integration and interface. Values supplied in the payload take priority over the receiver settings. This remains the default selection.
Custom Format: Send business data without the legacy wrapper. Complete Integration and Interface in the receiver settings to specify where the data should be processed.

For example, Skyvva Format can contain:

{
  "integration": "Customer Integration",
  "interface": "Account Inbound",
  "Account": [
    { "Name": "ABC Company" }
  ]
}

With Custom Format, customers can send:

[

  { "Name": "ABC Company" }
]

For this example, enter Customer Integration in Integration and Account Inbound in Interface. The interface’s source mapping must match the Account data.

Customers can send simpler JSON data and maintain the destination settings in the receiver configuration. Existing integrations can continue using Skyvva format.