2. Enhancement
Notify connected applications when SKYVVA configuration changes
Connected applications could keep a local copy of SKYVVA settings. When those settings changed in Salesforce, applications outside the existing Agent synchronization process did not consistently receive a notification.
SKYVVA can now notify subscribed applications when supported configuration records are created, updated, or deleted. This includes Integrations, Interface Groups, Interfaces, Mappings, Adapters, adapter properties, connection settings, and connection properties.
To receive these notifications, configure the external application as follows:
| Setting | Value |
|---|---|
| Platform event | skyvvasolutions__Agent__e |
| Subscription channel | /event/skyvvasolutions__Agent__e |
| Event-type field | skyvvasolutions__Type__c |
| Event-type value to listen for | DataChange |
The receiving application must support refreshing its stored settings when a relevant notification arrives. Connected applications can refresh their configuration after changes in SKYVVA, helping prevent processing with outdated settings.
For example, after an administrator changes an interface mapping, a compatible application receives the notification and can reload that mapping before processing the next request.
Retrieve additional pages of records from Sage X3
Previously, the existing Sage X3 adapter did not provide the new Next URL pagination setup for automatically retrieving additional pages.
Now we have enhanced the adapter so customers can configure it to follow the next-page link returned by Sage X3.
For JSON record retrieval, use:
| Field | Selection or value |
|---|---|
| Operation | GET |
| Request Format | application/json |
| Response Format | application/json |
| Pagination | Enabled |
| Pagination Method | Next URL |
| Next URL | The response field containing the next-page link |
| Business Data Field Name | The response field containing the business records, where needed |
The adapter also carries the supplied query, header, and path parameters into subsequent pagination calls. Customers can retrieve the expected records across multiple pages without manually requesting each page. For example, if Sage X3 returns customer records in several pages, SKYVVA follows the supplied next-page links until retrieval finishes.
Guide users through metadata generation
In the previous version, users selected metadata settings on a single screen. It was less clear which settings to use for SKYVVA API, SAP Integration Suite, or SAP Process Orchestration.
Some generated files could also contain unsuitable request structures, and V2 generation could fail when an example value was empty.
Metadata generation now guides users through the required steps.
- Select Application Type: SKYVVA API, SAP BTP Integration Suite (SAP-CPI), or SAP Process Orchestration (SAP-PO).
- Select Interface when starting from an Integration. When starting from an Interface, SKYVVA uses that interface.
- Complete Choose a format file and, for SKYVVA API, choose an API name.
- Click Generate.
The available formats and API choices follow the selected interface. V2 API choices are labelled V2 Integrate and V2 IntegrateSynchronous.
For SAP exports, SKYVVA selects Custom Format for an interface linked to a Message Type, or SKYVVA Format for an interface without a Message Type.
Choose a Structure Format is hidden; customers do not select it manually.
Generated API files also provide more accurate request and response descriptions, Salesforce addresses, authentication information, and examples. Empty example values no longer cause the identified V2 generation error.
Now customers receive a file suited to the selected application and interface, making it easier for their integration team to prepare requests and mappings.
Remove a connection that is still assigned to adapters
In the previous version, users could not remove a connection destination while adapters were still using it. They first had to unlink the connection from each adapter.
Now we have enhanced the Agent Control Board and selected Remove Connection and confirmed with Yes. If adapters still use the connection, a second confirmation window, Connection Destination in Use, displays this warning:
This connection destination is used by one or more adapters. If you delete it, those adapters will no longer have a connection destination, and any integration or processing that uses them will stop until you assign a new connection destination to the adapters. Do you still want to delete it?
Select YES to remove the connection or NO to keep it. So, Administrators can remove an obsolete connection without first editing every linked adapter. The warning explains which processing will be affected before they confirm.
Important note: Assign a replacement Connection Destination to each affected adapter before running its integrations again.