Release Update 05/17/2024

Salesforce

Capability to Modify Package XML files from Past Runs in Salesforce Tasks

In Salesforce Tasks, users can trigger the task workflow and utilize the upload XML or Past Run’s XML option. This new capability empowers users to efficiently manage and customize their tasks by providing them with the ability to edit and fine-tune package XML files from past runs according to their unique requirements.

Support for new Salesforce Components in Opsera Workflows

• The Salesforce components DigitalExperienceBundle and DigitalExperienceConfig are now supported for Opsera’s Salesforce workflows. These components can be used to provide more functionality and flexibility for developers building digital experiences.

• The components Audience, SalesAgreementSettings and MessagingChannel are now supported for Opsera’s Salesforce workflows. The components can be used for improved customer segmentation, sales agreement management, and multi-channel communication. For more info, read here.

Additional Enhancements

A sparse checkout logic has been implemented in the Salesforce Create Package Step within Jenkins workflow, optimizing the process for improved performance and speed

SDLC & DevSecOps

Support to select images in Nexus docker registries for Argo Deployments

Users can utilize custom images from Nexus repositories. This process pulls in the most recent build’s tag information during the creation and subsequently pushes it into a Nexus repository or other similar repositories. By implementing this approach, organizations can effectively manage and control versions of Docker images within their CI/CD pipeline.

In addition to choosing images only from Amazon Web Services (AWS) and Azure registries, support for Nexus has been added. For more info, read here.

Integration of Opsera with Google Cloud Platform for Terraform Infrastructure as Code (IAC) Pipeline Workflow

Opsera supports Google Cloud Platform (GCP) as one of the Cloud Providers for the Terraform Infrastructure as Code (IAC) pipeline workflow. This integration allows for IAC resource creation from Opsera’s terraform pipeline in GCP, with Opsera managing the terraform state in GCP buckets

This integration aims to enable quicker time-to-market for applications or services running on GCP infrastructure managed by Terraform via Opsera pipelines. For more info, read here.

Enhancements for Jira Notifications

Sprint Name is set to be optional for Jira Notification Setup

When configuring Pipeline Step Notifications for Jira, users who do not have sprints set up for their storyboard or project can leave the sprint name box blank or disregard it. This flexibility enables teams and users that do not employ a sprint-based approach to seamlessly integrate notifications into their Jira workflow without having to comply with sprint-related restrictions.