Release Update 07/18/2025

Platform

New Capability for DataOps Wizard: Automated YAML Codegen, Environment-Aware Parameterization, and IDE Visualization

Opsera’s DataOps Wizard capability offers data engineering teams reduced manual effort, enforced standardization, and accelerated reliable deployments for data workloads.This wizard reduces the risk of errors and makes configuration-as-code accessible, even for teams without extensive YAML knowledge.

Codegen for Configuration Management

A Codegen capability has been implemented in the Wizard to synthesize equivalent YAML (or JSON) configuration files. These files are validated against the DataOps schema before emission and may be automatically committed back to the user’s Git repository.

Key Values:

• The manual effort required to create and maintain YAML files is significantly reduced.

• Migrations to higher environments are facilitated through consistent configuration formats.

• Infrastructure‑as‑code best practices are enabled without requiring deep YAML expertise.

Environment-Aware Parameterization

An enhanced parameterization engine has been incorporated to address environment-specific configuration variations. Placeholders (e.g., ${DB_NAME}, ${CLUSTER_ID}) may now be defined within configuration files. During deployment, these values are automatically supplied by the CI/CD system or can be provided at runtime. This ensures that configurations remain reusable across multiple environments while minimizing the overhead associated with maintaining separate files for each environment.

Key Values:

• A single source of truth for configuration templates is maintained.

• Deployments across DEV, QA, STAGE, and PROD environments are enabled without duplicating files.

• The risk of human error during promotion and deployment is reduced.

• Diverse deployment scenarios can be accommodated with minimal effort.

Integrated IDE Visualization

After Codegen execution, “View YAML Generated File” opens an embedded in‑browser IDE featuring syntax highlighting, auto‑completion based on the DataOps schema, and real‑time validation errors. A side‑by‑side diff view compares regenerated content with any existing edits. Edits made in the IDE may be saved back to Git or exported as standalone YAML/JSON files.

Key Values:

• The generated configuration may be reviewed, validated, and adjusted directly within the IDE view.

• Syntax highlighting and structured formatting ensure that configurations remain readable and error-free.

• Any required edits may be performed before committing the configuration to version control or promoting it to higher environments.

Flexible Runtime Variable Handling

Flexibility has been added through support for multiple methods of supplying variable values. Variables may be embedded within version-controlled configuration files or injected dynamically at runtime through the user interface or pipeline steps. This dual-mode approach ensures that organizational requirements for either centralized control or runtime overrides are met seamlessly.

Key Values:

• Both automated pipelines and manual deployment workflows are supported.

• Better control over variable settings.

Enhanced Notifications for Pipeline Activities

Notifications at Pipeline level are introduced for improved visibility, accountability, and responsiveness through centralized configuration.

1. Pipeline-Level Notification Configuration

Previously, email notifications could only be configured at the individual pipeline step level. With this update, users can now manage notifications directly from the Pipeline Summary view, allowing for:

• Global Notification Settings for the entire pipeline

• Step-Level Overrides within a single, consolidated interface

This eliminates repetitive configuration, simplifies setup, and ensures consistency across pipeline steps.

Key Value:

• Reduces manual effort by eliminating the need to configure notifications per step

• Enhances control and visibility for pipeline administrators

2. Automated Notifications to Pipeline Runners

Pipeline email notifications now include support for notifying the user who manually triggered the pipeline. When the “Notify user who triggered the pipeline” toggle is enabled, an email is automatically sent to the pipeline initiator upon completion—based on the notification level configured in the email notification settings.

Key Value:

• Keeps pipeline initiators informed without requiring them to monitor the UI

• Enables visibility into unattended or scheduled pipeline runs across teams

3. Committer-Based Email Notifications for Salesforce Pipeline Failures

For pipelines that include Salesforce validation, deployment, unit testing, or code analysis, Opsera supports automated email notifications to the committers responsible for failures. When enabled, the system identifies the relevant commits and notifies the associated developers via email.

Failure Attribution Covers:

• Component-Level Failures: Commits that modified the failed Salesforce components.

• Test Coverage Failures: Commits linked to classes that caused test failures or coverage drops

• Code Analyzer Violations: Commits related to files that violated configured quality thresholds

If a valid email is available in the commit metadata, it is used directly. If the address is masked (e.g., no reply emails), Opsera attempts to match the committer with a registered user in the Tool Registry to retrieve the correct email.

Key Value

• Notifies the developers directly responsible for failures

• Speeds up issue resolution by providing immediate context to the right contributors

4. Expanded Pipeline Notifications with GitHub Issues & Azure Boards Integration

Opsera pipelines support automated notifications integrated with GitHub Issues and Azure Boards, enabling seamless end-to-end visibility, traceability, and workflow automation within the tools your teams already use.

GitHub Issues Integration

Pipelines can now automatically create, update, and link GitHub Issues based on pipeline events, using the GitHub Issues REST API.

Key Values

• Real-time issue synchronization: Keep GitHub Issues automatically in sync with pipeline runs.

• Dynamic status updates: Reflect pipeline execution status directly in related issues.

• End-to-end traceability: Link code changes, builds, and deployments back to tracked work items.

Azure Boards Work Items Integration

Opsera now supports native integration with Azure Boards, enabling automated creation and updates of work items such as tasks, bugs, and user stories directly from pipeline events like builds, deployments, and failures. This enhancement brings work tracking and DevOps execution into a unified flow, improving visibility, accountability, and team coordination.

Key Values

• Easily configure pipelines to create or update Azure work items—such as tasks, bugs, or user stories

• Assign ownership immediately with Primary Assignee and link related work using Parent Ticket.

• Fine-tune who gets notified and when by setting the Notification Level (e.g., All Activity, only failures), ensuring the right stakeholders are kept in the loop—reducing noise and improving response time.

Advanced Webhook Pattern Matching for Pipeline Triggers

Webhook trigger configuration for pipelines has been enhanced and simplified. Users can now define custom URL patterns to control when a pipeline is triggered based on incoming webhook events.

Key Values:

• Pattern-Based Triggering: Pipelines trigger only when webhook URLs match user-defined patterns (e.g., my-service/events/*).

• Simplified Configuration: The previous requirement to select multiple secondary branches has been removed—pattern matching alone is now sufficient.

Insights

Custom Date Ranges for Enhanced Data Analysis in Copilot Reports

Custom date ranges are supported, enabling users to analyze data over any specified period rather than being limited to preset intervals. This enhancement overcomes previous restrictions like the 90-day maximum view in the Contribution Report and the absence of custom range options in the Dashboard and User Usage Report, resulting in greater flexibility and more precise insights.

Support for Custom Date Range Selection

Users can now select custom date ranges across the following modules:

• Overall Copilot Dashboard

• Copilot Contribution Report

• Copilot User Usage Report

Enhanced Copilot Impact Chart with Dynamic Sum and Average Calculations

A new dropdown has been added to the Copilot Impact Chart, enabling users to switch between “Sum” and “Average” modes. This allows for automatic aggregation of data across all three tabs within the selected time period, replacing the previous manual counting process.

• Sum Mode: Automatically calculates the cumulative total count for all tabs over the chosen time frame.

• Average Mode: Computes the average value across the tabs for the selected period.

Change Request KPI Integration in Devex Dashboard

Opsera’s Devex Dashboard includes comprehensive Change Request metrics that enhance visibility into change management, track resolution efficiency, and identify trends. This integration equips DevOps teams with actionable insights to optimize change workflows and reduce operational risks.Users gain a unified view of how change requests impact delivery timelines, project stability, and developer productivity.

Key Highlights:

• Proactive Risk Mitigation: Early identification of high-risk or long-duration change requests to minimize delays.

• Efficiency Optimization: Utilize resolution time metrics to refine workflows and improve process automation.

• Resource and Capacity Planning: Align CR volume trends with team capacity for optimized resource allocation.

Enhancements for Sonar Code Coverage KPI

The enhancement to the Sonar Code Coverage KPI is aimed at providing deeper insights and improved customization options for better analysis of code quality metrics.

• Additional Columns Added: The following new columns have been added for more comprehensive reporting:

  • NCLOC (Non-Comment Lines of Code)

  • CLOC (Comment Lines of Code)

  • Quality Gate Name

  • Quality Gate Status

  • Cyclomatic Complexity

  • Cognitive Complexity

  • Unit Tests Count

• Average Overall Coverage Percentage: The KPI now directly displays the average overall coverage percentage, allowing quick assessment of code coverage health.

• Customizable Column View: Users can now show or hide specific columns, tailoring the KPI view to their needs for a focused reporting experience.

Enhancements to Sonar Ratings KPI

The enhancements to the Sonar Ratings KPI deliver greater value by enabling users to quickly locate relevant reports through date-based filtering and gain focused insights by separately tracking security, reliability, and maintainability ratings, thereby improving decision-making and accelerating issue resolution.

• Dynamic Ratings Columns: In the drill-down report, selecting the Security, Reliability, or Maintainability tab dynamically displays the corresponding ratings as a dedicated column, supporting focused analysis on the chosen quality attribute.

• “Created By” Date Filter: A new filter option, Created By, is available for the reports table. Users can filter report details by selecting a specific date, streamlining the process of viewing reports created on or after the specified date.

Additional Enhancements

Clearer "Total Closed Alerts" Metric Replaces Percentage in GitHub Advanced Security Dashboard

The previously inconsistent percentage metric in the "Overall Security" metric on the GHAS Dashboard has been replaced with Total Closed Alerts (Timeframe). This change aligns the metric with absolute alert counts for the selected timeframe, improving clarity and consistency.

Role-based access control in NX 01 has been strengthened to enforce restrictions by default:

• Tools & Mappings: Users with Auditor or Security Manager roles can no longer create, edit, or delete mappings.

• Dashboards: Users with Auditor or Security Manager roles are restricted from creating, editing, or deleting dashboards.