3. Bug Fixed

Fixed a few issues regarding Source Definition File Upload

Previously, Source Definition files containing non-English characters, such as é or ü, could display those characters incorrectly after upload.

CSV files could also create incorrect fields when the selected separator did not match the file. For example, if a file used semicolons but a comma was selected, SKYVVA could read the complete header as one field instead of creating separate fields.

SKYVVA now:

Preserves special and international characters during upload.
Checks that the selected CSV separator matches the file.
When the file contains a comma separator and the user chooses a different separator, it will alert the warning, and users can't save it unless they choose the correct separators
Processes the same file again after the separator is changed, without requiring the user to upload it again.

This correction helps users create accurate Source Definitions from XML and CSV files.

Fixed Keep Values in Copied Field for CSV and CSV Fixed-Length

In the previous version, when a user copied a mapping node, SKYVVA searched for the copied field’s value using the original field path instead of the path created for that copy. Because SKYVVA could not find the correct value, the copied field could be blank in the generated CSV or fixed-length payload.

SKYVVA now uses the correct path for each copied field when generating the output.

Now, the copied fields contain their mapped values instead of being left blank, helping prevent incomplete payloads from being sent to the receiving system.

Fixed Database Metadata Retrieval with Agent 3.6.9

In the previous version, when a user wanted to Import Database Metadata, selected the Connection Destination, Database Adapter, and object type—Table, View, or Stored Procedure—and clicked Retrieve Database, SKYVVA could send the request to the older /application/getDBDetails/ API to get the Database Structure information in order to create the Database Structure.

Agent 3.6.9 accepts database requests through the new /agent/v3/getDBDetails/ API. If SKYVVA used the older API, the Agent could not return the requested database information. Users might therefore see an empty list of tables, views, or stored procedures, or no fields for the selected database object.

SKYVVA now checks the connected Agent version and automatically uses the correct API. Requests to Agent 3.6.9 use /agent/v3/getDBDetails/, while older supported Agents continue using their appropriate API.

Now users can retrieve database objects and fields and continue creating Database Structure successfully.

Prevent Duplicate and Conflicting Alert Configurations

In the previous version, users could experience two issues when editing an Alert Configuration:

Changing the Scheduler Name and clicking Save could create another Alert Configuration instead of updating the existing one.
Changing Alerting for sObject from Scheduler to Integration could keep both settings after saving, even though only one should be selected.

SKYVVA now updates the existing Alert Configuration without creating a duplicate. When users change Alerting for sObject, SKYVVA keeps only the newly selected setting. Now each Alert Configuration contains one alert target and can be edited without creating duplicate or conflicting settings.

Restore Pagination Controls Under Salesforce Locker and Lightning Web Security

In the previous version, several SKYVVA record lists used an older jQuery and JavaScript method to display pagination controls.

Salesforce Locker or the Salesforce Session Settings option Use Lightning Web Security for Lightning web components and Aura components could block this older method. As a result, the Previous, Next, and page-number controls could disappear or stop responding. Users could then see only the first page of Interfaces, Messages, or other records.

SKYVVA replaced the older pagination method with controls supported by current Salesforce security requirements.

Now, the pagination controls remain visible and usable, allowing users to navigate through all pages of records without changing their Salesforce security settings.

Fixed Reprocess Large or Partially Failing Outbound Message Sets More Reliably

In the previous version, SKYVVA could attempt to reprocess too many outbound messages at the same time. Large requests could exceed Salesforce limits and fail with errors such as Too many query rows: 50001.

If one group of messages failed, it could also interrupt the remaining work and prevent valid messages from being reprocessed.

SKYVVA now divides large outbound message sets into smaller background jobs. If one group fails, SKYVVA can retry it in smaller groups while allowing other valid messages to continue. Job tracking is maintained throughout the reprocessing flow.

Now the user can reprocess large or partially failing outbound message sets more reliably without one failed group automatically stopping all remaining work.

Close the New Interface Dialog After Successful Creation

The issue occurred when a user opened the New Interface dialog, entered the required information, and created an interface. The interface was created successfully, but the dialog and loading spinner remained open. This could make the user believe that the creation was still in progress and cause them to repeat the action.

SKYVVA now closes the New Interface dialog and stops the loading spinner after the interface is successfully created. The page refreshes only when required by the process from which the dialog was opened. Users receive clear confirmation that the interface has been created and can continue working without closing the dialog manually or refreshing the page.

Restart the Agent Only Once After Saving Properties

The issue occurred when a user changed the Agent Properties Configuration and clicked Save & Restart Service for an Agent in non-open firewall mode.

SKYVVA could send two restart requests from a single click, causing the Agent service to restart twice. The loading spinner could also continue running after the first restart was completed.

SKYVVA now sends only one restart request and stops the loading spinner when the operation is complete. Clicking Save & Restart Service saves the properties, restarts the Agent service once, and returns the configuration page to a completed state.

Return Removed CSV Fields to the Available List

The issue occurred when a user selected Import Metadata, uploaded a CSV file, selected Hierarchical as the Data Structure, and then removed fields from a child structure or deleted a child containing selected fields.

The removed fields did not return to the Available list. Fields belonging to deeper child structures could also remain unavailable, preventing the user from selecting them again.

SKYVVA now refreshes the Available list from the complete CSV field list whenever fields or child structures are removed. This includes fields from all nested child levels. Now, removed fields immediately return to the Available list and can be selected for another child structure without reloading the page or rebuilding the hierarchical structure.

Prevent Repeated File Processing When Keep File Is Enabled

The issue occurred when a user configured an Agent File Adapter, selected Keep File under What to do with the file after Processing?, and clicked Start Consumer, and clicked Start Consumer to continuously check the folder for files.

SKYVVA allowed the consumer to start even though the processed file remained in the folder. The same file could be found and processed again during every check, potentially creating duplicate data.

SKYVVA now checks the After Processing setting before starting the consumer. If Keep File is selected, SKYVVA blocks the action and displays an error. Users cannot start continuous file consumption while Keep File is enabled. They must select another After Processing option before starting the consumer, preventing the same file from being processed repeatedly.