You can now view all available permissions and assign or revoke them for existing users directly from the Backoffice. Access to this feature requires the permission:read permission.

You can now check for CVEs and export SBOMs for all on-prem container images provided by Quickwork before installation, directly from the self-managed installation portal. While you may continue to pull images to your own repository for scanning and signing, Quickwork regularly scans these images using Trivy and highlights identified vulnerabilities, their severity, and the versions in which fixes are available. SBOMs are generated in SPDX 2.3 format and can be exported for independent verification and further security analysis.

Quickwork now offers easy-to-use network troubleshooting tools directly from the Backoffice to simplify testing connectivity between your on-prem Quickwork instance and external systems such as databases, API endpoints, and other microservices. With appropriate permissions, users can run Telnet, HTTP checks, Traceroute, DNS lookups, Ping, and more, making it faster to diagnose and resolve network connectivity issues.

Quickwork now lets you create, update, and delete tags centrally from the Backoffice with appropriate permissions, helping standardize tagging across resources such as Users, Connections, Journeys, and more. These tags are exclusive to Backoffice users and do not impact the Quickwork iPaaS runtime. You can also search across all assets using tags for faster discovery and management.

Quickwork now automatically collects custom health metrics for core dependencies in self-managed (on-prem) installations, no additional configuration required. Simply enable the custom metrics job from your deployment settings to start monitoring standard and custom metrics. For advanced observability, you can also install Quickwork’s open-source exporter to convert these metrics into Prometheus-compatible format, allowing them to be scraped by your preferred monitoring tool.

Quickwork now displays the total time taken by each transaction directly on the History page, making it easier to identify performance at a glance. Detailed, step-level timing continues to be available within each transaction’s History detail page.

Transaction durations are color-coded to help quickly spot latency patterns:

Gray: Under 10 seconds

Yellow: Between 10 seconds and 5 minutes

Dark Orange: Over 5 minutes

These indicators do not signify failures or errors; they are intended solely as a quick visual aid to identify potential latency.

You can now add comments to every workflow version created during updates. This helps document what changes were made and provides valuable context for collaborators reviewing the workflow. These comments also make upgrades and rollbacks in release management easier by allowing quick identification of version history and intent.

You can now visualize how resources depend on one another with interactive, drag-and-drop dependency graphs. These graphs allow you to explore dependencies across assets—drilling down infinitely to understand relationships in precise detail.

Select any resource from the dropdown to view its full dependency chain, or explore dependencies for a specific Journey directly from its Journey page. A convenient “Go to Asset” button lets you navigate to any referenced asset with a single click.

Users can now include additional team members in Journey failure notification emails, allowing stakeholders across the workspace to stay informed alongside the account owner. Only users who are part of the workspace team can be added, and if a team member is removed from the workspace, they will be automatically removed from the notification settings as well.

We have streamlined the connector deployment experience for on-premise environments using Quickwork’s proprietary serverless compute stack. Administrators can now access the full library of apps directly from the Backoffice portal and deploy, scale, upgrade, and patch connectors—all from a single, unified interface complete with telemetry and logs for each connector.

Every connector is also distributed with its own signed SBOM, security scan reports, and publisher certification, ensuring transparency, security, and trust for on-premise installations.