Release Update 09/02/2024

Salesforce

Capability in Jira Integration Workflow to manage destructive changes in Salesforce Merge Tasks

Opsera's new capability improves Jira integration workflows by allowing users to mark components for deletion directly from both the Branch and the Salesforce Org, easing component management and reducing potential conflicts during execution.

This capability helps to prevent users from accidentally selecting the same component for both deletion and deployment in a single execution run. Users can either upload a destructive package XML file to mark components for deletion, or manually select components through the wizard interface. The wizard will retrieve and display all currently available components within the Org, enabling users to easily identify which components are eligible for removal.

New Capabilities Introduced for Jira integrated Salesforce workflows

New Salesforce Policy to enable release ticket selection and ticket validation

A new Salesforce policy setting “Enable Release Ticket Selection” is implemented to enhance the user experience by governing the visibility and validation of Jira tickets based on Customer preferences. This allows users to customize their interface according to their specific needs.

• In the Git to Git Merge Sync task creation workflow, users will now have access to the ‘Release Ticket’ field once the relevant policy setting is enabled. By default, this field is hidden in the task configuration interface. When activated, users can select required tickets from a dropdown menu, significantly reducing the likelihood of accidental selections.

• A validation check is introduced to prevent users from inadvertently selecting the same ticket for both “Jira Tickets” and “Release Tickets”. Upon enabling this policy, if a feature ticket has already been selected as a Jira ticket, it will now be displayed in a disabled state within the Release Ticket field. This capability ensures that users cannot make duplicate selections, thereby reducing errors and improving clarity in ticket management.

Platform

Capability to manifest details for Opsera Pipeline workflows

Opsera Pipelines extends the support for additional pipeline steps to display static code manifest offering an detailed overview of information related to the scan performed in the workflow. The manifests generated by Opsera Pipeline are presented in a table format, including the details such as scan status, message, step start and end time, threshold level and quality gate level.

The static code manifests are supported for the following scan tool steps: Coverity, Sonar, Blackduck, Wiz, Grype, Aquasec and Twistlock.

Additional Capabilities

Access Updates for Security Manager Role

Users with Security Managers roles will be able to view connection details across all tools without restrictions. In addition to the Connection tab, read-only access has been granted to all other tabs within the Tool Registry. This ensures that Security Managers can monitor and review configurations and settings without the ability to modify them, maintaining security integrity while providing necessary oversight.