If you’ve ever tried to sync Salesforce metadata, manage test class coverage, or debug a failing pull request at 5 p.m. on a Friday, you know the difference a well-timed product update can make. That’s why we’re rolling out a series of enhancements focused on clarity, control, and developer experience. No fluff, no “digital transformations”, just updates designed to make your day a little easier.
Here’s what’s new
Let’s start with visibility where it counts: merge sync workflows. Whether you're syncing Salesforce to Git or Git to Git, Opsera now surfaces code scan vulnerabilities right in the diff view. A bug icon shows up next to any risky lines. Click it, and you’ll get everything from the exact line number to severity, category, and remediation suggestions. Just make sure code scan is turned on in your workflow.
On top of that, manually edited files now get a checkmark, making it easy to distinguish between automated syncs and human intervention. For teams managing approvals or compliance reviews, this tiny icon is a time-saver.
We’ve simplified reviewer and file selection on the merge confirmation screen. If there are no conflicts to resolve, you can now skip the editor and go straight to confirmation, just click “Proceed to Confirmation” after selecting your files. This option is intended for clean merges only, not as a shortcut.
The PR Validation Summary has a cleaner UI and better debugging support. Errors now include direct links to console logs or reports. We also added dynamic job status capture, which tracks validation progress in real time with deployment IDs and success or failure checkpoints.
Bonus: If validation fails because no deployable components were found, the pipeline status now says “Aborted” instead of vaguely “Failed.” And if a user stops it manually, it’s marked as “Stopped.” Accuracy matters.
Map Apex test classes to Apex classes to implement Autoinclude test classes on your pipelines and PR validation. This removes the need to specify test classes for each individual apex class at run time and can be managed centrally.You can bulk upload mappings via CSV, and for each class.
Managing Apex test coverage monitoring used to be tedious. So we built a centralized Apex Test Matrix Dashboard. It maps classes to test classes automatically, using naming patterns, dependency checks, and metadata relationships. Even better, when you run a pipeline and a class doesn’t have a test mapped, we highlight it and give you a one-click link to fix it right from the wizard. No more hunting through orgs to patch holes in test coverage.
Need to run Salesforce pipelines more often? You can now schedule them every 15 or 30 minutes. If a task is still running when the next one is due, the system queues it automatically and executes it as soon as possible. No skipped automations, no overlap chaos.
We’ve added proactive protected branch checks to the bulk migration flow. Before any components are selected, Opsera checks if the branch is protected and surfaces warnings immediately. This prevents wasted cycles on long-running jobs that were doomed from the start.
We upgraded the Salesforce Code Analyzer engine to v5.1. Here’s what that gets you:
All of it adds up to faster, cleaner, and more accurate scans, especially for Salesforce development.
We’ve redesigned our Salesforce pipeline and validation reports for faster insight. Now they:
Supported across Deploy, Quick Deploy, Unit Tests, and PR Validation reports. It’s everything you need to debug and document your pipelines without wasting time.
We’re building tools that make Salesforce deployments, GitOps workflows, and DevOps automation easier to manage, easier to trust, and easier to scale. These updates are live now in your Opsera environment.
You’ve got code to ship. We’ve got your back.
