2. Enhancement

Enhanced Administration APIs

Administrators can now view and update the Agent’s application properties and restart the Agent service remotely through new APIs. This removes the need to log in to the Agent server for these tasks, making configuration changes and routine maintenance easier.

Optimize Generate PFX validation and SSL redirect URL handling

Enhanced the Generate PFX File process with the following improvements:

• Validate the uploaded certificate file and show a clear error if the certificate content is invalid.
  
• Validate the uploaded Bundle/CA file and show a clear error if the bundle content is invalid.
  
• Validate the password field in real time and show an inline error when spaces are entered.
  
• Clear old file validation messages after users select a valid file.
  
• Warn users earlier when the uploaded certificate is close to expiry before generating and applying the PFX file.
  
• Improve SSL redirect URL generation for wildcard certificates.
  
• Prevent wildcard values such as *.customer.com from being used as a literal URL host.
  
• Use localhost as the generated URL host when the wildcard certificate does not match the Agent server hostname.

These improvements help users identify SSL input issues before generating the PFX file and prevent incorrect HTTPS redirect URLs after SSL configuration.

Add Logging for Agent Local Web App Actions

Previously, some actions performed in the Agent Local Web App were not logged in enough detail. This made it harder for administrators and support teams to troubleshoot user actions such as login, registration, connection management, PFX file generation, ping, edit, delete, subscribe, unsubscribe, and resubscribe.

We have added logging for major Agent Local Web App actions so user operations can be traced more easily during troubleshooting. Sensitive values are masked in debug logs, including passwords, client secrets, security tokens, and proxy passwords.

This enhancement improves supportability while keeping credential information protected.

Separate Logs by Integration, Interface, and Pub/Sub connection

Previously, many Agent logs were mixed together, especially in the system or integration log files. This made troubleshooting difficult because users had to search through large mixed logs to find messages for a specific interface or Pub/Sub connection.

Enhanced Agent logging so logs are now separated more clearly:

• Integration logs are kept per integration.
  
• Interface logs are written into a dedicated interface-logs folder.
  
• Pub/Sub connection logs are written into a dedicated pubsub-connection-logs folder.
  
• Log context is set and cleared more safely so logs are written to the correct file.
  
• Active log upload now supports integration, interface, and Pub/Sub connection logs.
  
• Backup/archived log listing now includes interface and Pub/Sub log archives where appropriate.
  
• System backup log handling was corrected so SYSTEM-LOG archives stay in the proper system archive location.
  
• Upload retry handling was improved to avoid creating duplicate Salesforce log files.

This enhancement makes log troubleshooting easier because users can review logs by the exact integration, interface, or Pub/Sub connection instead of searching through one mixed log file.

Add specific Automatic Log Cleanup for backup log files

The Agent already had global log cleanup/rollover behavior from the active Log Profile, but it did not provide separate cleanup control for each generated backup log type. After adding more log files, such as System logs, Business/Integration logs, Interface logs, and Pub/Sub logs, old backup/archive files could grow over time and require manual cleanup.

Added a specific Automatic Log Cleanup housekeeping job for backup/archive log files. Administrators can now configure cleanup separately for:

• System logs
  
• Business/Integration logs
  
• Interface logs
  
• Pub/Sub connection logs

Users can enable or disable the cleanup job, choose the retention unit, set the maximum files cleaned per run, and define retention values for each log type. A retention value of 0 disables cleanup only for that specific log type.

This cleanup only removes eligible backup/archive log files. The active log file is not deleted. If Automatic Log Cleanup is disabled, the Agent continues using the existing global log configuration from the active Log Profile.

The enhancement also adds cleanup settings support in the Agent UI, REST API, and non-open-firewall platform-event flow, and fixes Yearly archive path generation for log cleanup.

Improved Agent logs for outbound polling mode with non-open firewall Agent connections.

In outbound polling mode, the Agent sends a request to Salesforce/Skyvva to get the mapping result before processing the data. Previously, when an issue happened during this step, the log did not show enough details about the request payload or the response returned from Salesforce/Skyvva. Because of this, it was difficult to understand the real cause of the issue, especially when the Agent could not get the expected response back. With this improvement, the Agent now writes more useful information in the log during outbound/Salesforce processing, including request details, response status, response body, and reprocessing batch size. This helps support teams investigate what the Agent sent, what response was returned, and why outbound polling mode processing may have failed. This change does not change the business processing logic. It only improves log details for troubleshooting.

Support More JSON Mapping Structures for Agent REST Adapter in V3 Outbound Processing

Enhanced the Agent REST Adapter for V3 JSON outbound processing. Previously, the Agent REST Adapter supported JSON mapping correctly only when using a REST Message Type Template. It did not fully support other JSON mapping structures, such as sObject structure or plain/custom Message Type structure.

With this enhancement, the Agent REST Adapter now supports API V3 JSON mapping for the following structures:

• sObject structure
  
• Plain Message Type structure
  
• REST Message Type Template structure

This gives customers more flexibility when configuring outbound REST integrations with JSON payloads in V3 Outbound Processing.

Added a New Keep and Lock File Option for File-Based Processing

Before, users could process files with options such as Delete or Move/Backup after processing. There was no option to Keep File and no option to Lock File.

This made it difficult for users who wanted the agent to process a file but keep the original source file in the same folder, or mark the file as processed without deleting or moving it to backup.

After this enhancement, two new file processing options are available:

• Keep File: The agent reads and processes the file, then keeps the original file in the source folder unchanged.

• Lock File: The agent reads and processes the file, then locks/renames the processed file in the same folder so users can identify that it has already been processed.

Additional protection was added for Keep File. Because keeping the file unchanged can cause Start Consumer to process the same file repeatedly, the agent now blocks Start Consumer when After Processing = Keep File.

This gives users more control over how source files are handled after processing.

Add File Locking to Prevent Concurrent Processing

The Agent now locks a file before starting processing. Once a file is locked, other adapters and processing jobs cannot claim or process the same file at the same time. This prevents duplicate processing when multiple adapters monitor the same folder or when scheduled and manual jobs run concurrently. The locking mechanism applies to local files and FTP, SFTP, and FTPS connections. After processing, the Agent performs the configured action, such as keeping, moving, or deleting the file.