Release Update 02/09/2024

Salesforce

Capability to perform OAuth Authentication and View Tool Connection Details in Tool Creation Wizard

When using OAuth authentication for the Salesforce configurator tool, a new wizard step is added for users to authenticate using the OAuth button. Users can verify if the connection was successful in the same step after authentication. For more info, read here.

Easy Rollback for Salesforce Deployments

Rollback for Salesforce Deployments refers to restoring your Salesforce org to the stable state it was in before your previous deployment.

Users have been able to back up metadata components onto a Git branch using independent Pipeline Steps. Then, a new pipeline orchestration would be needed for the rollback. This would be a time-consuming and tedious process.

Users can rollback to a previous deployment using Opsera's Easy Rollback option by selecting the successful deployment's run count. Opsera will automatically configure the corresponding Back Up branch to fetch the components on the Wizard using the desired run to rollback. With just one click, users can view the components and start the rollback process. A partial rollback is also supported, which allows you to restore only a few components of the deployment. For more info, read here.

Note: The Rollback feature will only be available for upcoming backup deployments and not for the backups that were previously taken.

Support to View Uncovered Lines in Code Coverage Error Report

To display the precise lines of the codes that are not covered, a new column Lines Uncovered has been added to the code coverage error report that is generated when a unit test, deploy, or validate job using Salesforce pipelines fails. This shows the line numbers for every class which is not covered by the test class .

Previously, users were only given information on the Code Coverage warning and the percentage of coverage for each Apex Class component in the report.

Enhanced View for Handling Merge conflicts for Profiles and dependency components when involving multiple Jiras

For salesforce workflows with jira integration enablement, users can handle merge conflicts in a much easier manner.

• According to the configuration chosen for "include dependency" in the wizard, only the components with or without the dependent component for a particular Jira selection will be shown in a merge conflict window.

• For a specific jira selection, the diff window displays the permissions corresponding to the components present in Jira story and its respective feature branch. Furthermore, users will receive a warning message if conflicts for each modified component type is not resolved.

New capabilities for Pipeline Instructions

• Audit logs are available for Pipeline instructions to track their usage and scope. Users can refer to audit logs in organizations where multiple users are working on the same instruction. You can view them by date range, site role, or username for any specific actions performed on the instructions. For more info, read here.

• To track the Pipeline instructions on when it is added or updated, users can refer to the list view of the Instructions. The new columns Created and updated will display the date and time for each instruction, based on when it was added and modified accordingly. For more info, read here.

  

SDLC and DevSecOps

Redshift Pipeline Rollbacks using Tag

Users can roll back changes made to the database based on the specified tag. Users can choose an older version and its associated tag to be rolled back to in the Pipeline step configuration by selecting from a list of more than five Redshift DB pipeline rollback tags. This allows users to add tags quickly rather than searching for and adding them. For more info, read here.

Report Enhancements for Wiz Scan

• A client side vulnerability threshold can be set at step level for Wiz scan pipelines. The supported vulnerabilities are:Critical, High, Medium, and Low. Users can choose the one or all required levels and choose a numeric threshold count. For more info, read here.

  
• Improvements are made for users to get more info using the scan report. Users can view the Fixed Version in the Summary page report. This helps in determining the version that will address the vulnerabilities discovered during the scan. In addition, Package name and version are now combined into a single column labeled as Package.

Pipeline Execution Improvements for Dynamic Parameter Passing

• When running the pipeline, users are prompted with an appropriate error message if they have not configured the repository in the pipeline settings.

• Users can choose repositories from the GitHub Mono Repo tool. This is in addition to the other supported tools: Gitlab, Github, Bitbucket and Azure DevOps.

• The tool name has been changed from Github Mono Repo (Deploy Key) to GitHub Mono Repo. The tool creation field SSH supports SSH based GIT URLs