Release Update 08/2024
SDLC
Capability to add Tool Registry Plugin for Job Engine Workflows
Opsera introduces Registry Tool Plugin within the Job Engine Pipeline Workflows. This feature enhances user capabilities by allowing the selection of multiple tools and the registration of environment variables. The plugin enables users to map connection variables from a selected registry tool directly to environment variables. This mapping is crucial for ensuring that jobs are executed with the correct configurations.
New Capabilities for Standard change requests for ServiceNow in Opsera pipelines
The integration of Opsera pipelines with ServiceNow workflows facilitates the creation and management of standard change requests in a streamlined manner. Users can initiate standard change requests directly from their Opsera pipelines.
When an Opsera pipeline is executed, it can reference both existing and new standard change requests logged in ServiceNow. For new change requests, users must select from pre-approved templates during configuration. These templates will then be utilized during the orchestration process within Opsera to create new standard changes efficiently. This cohesive experience enhances operational efficiency by allowing teams to manage changes seamlessly. For more info, read here
Capability to view Approve and Deploy Manifest Details for Pipelines
Opsera provides users with a more comprehensive view of their deployment workflows through the addition of deploy and approve manifests. The new approve manifest feature offers users a detailed overview of the approval status associated with each deployment. This provides context for the approval decision, allowing teams to understand any concerns or requirements that influenced the outcome.
Similarly, the deploy details are now organized in a user-friendly table format that includes essential information of deployment, making it easy for users to access critical deployment details at a glance. This helps to improve operational efficiency and reduce errors during deployment processes. For more info, read here.
Capability to Perform Artifact Scan for Nexus IQ using Opsera Pipelines
A new capability is introduced within Nexus IQ integration that enhances the scanning process for artifacts generated by builds. This capability allows teams to run scans on artifacts generated by builds, such as those from Maven or Gradle, directly within their existing Pipeline workflows.
Users can input specific details related to their source control management (SCM) and the commands linked to their build processes. Additionally, they have the ability to define variables that determine where the results of the scans will be stored and establish naming conventions for the output files created from these scans.
This functionality ensures that every artifact generated during the build process is thoroughly scanned for security vulnerabilities before being deployed into production environments. For more info, read here.
Introducing a New Security Tool Integration with Invicti
Opsera has introduced an integration with Invicti that allows users to create a seamless workflow within Opsera Pipelines, ensuring that security checks are an integral part of the build process.
Users can conduct scans based on their specific configurations set in Scan Profiles. This flexibility allows teams to tailor their security assessments according to their unique requirements and compliance standards. By executing scans through Opsera Pipeline, users also save valuable time by streamlining the process of vulnerability detection. For more info, read here.
Introducing a New Test Tool Integration with AccelQ
The integration of AccelQ into Opsera pipelines, allows users to execute automated tests seamlessly whenever there are changes in the codebase, ensuring that quality assurance processes keep pace with development.
Users can now specify the exact job, environments, and run parameter information directly from Opsera, providing greater control over test executions. The use of AccelQ Job IDs in CI/CD pipelines facilitates automated execution of tests, while the ability to specify an Agent Name enables teams to dynamically run tests across different environments or configurations. This integration ultimately leads to a more efficient continuous testing process. For more info, read here.
Capability to Log for Run Configuration Variables for Job Engine workflows
To create a comprehensive activity log entry for run configuration variables sent to the job engine, a new log entry “Job Configuration” has been added. This log entry encapsulates both the data defined within the pipeline step and any external data sourced from other integrations or configurations. This helps teams to improve troubleshooting and maintain clear visibility into their job executions.
Additional Capabilities
Short-lived token support is added to the Sonarqube tool registration creation setup. Users can switch between User Access tokens and Password, when registering their Sonarqube tool with Opsera. Using the tools configured with short-lived token ensures that the step execution utilizes a unique token, reducing the risk associated with long-lived credentials.
Enhanced dynamic tagging capabilities is added for Docker builds within Jenkins. This feature allows users to create more informative tags for their Docker images by incorporating various dynamic values such as Run count, Date, Timestamp, Commit SHA and Custom Tag during the build process. Users can utilize the Docker Dynamic Tag Name option in the pipeline configuration to populate a dynamic name for the docker.
Salesforce
Opsera’s Job Engine for Salesforce Task Workflows
Opsera has introduced its Job Engine as a replacement for Jenkins in the workflow for Salesforce tasks. This shift eliminates the need for users to select Jenkins as a tool during task configuration and instead requires them to provide SCM account details for task setup. The Job Engine offers a more streamlined and efficient approach to automating these tasks, allowing developers to manage different versions of their metadata effectively.
This capability is currently supported for Salesforce Bulk Migration and Salesforce Branch Structuring tasks.
Opsera extends support to OmniStudio Metadata
The following Omnistudio components can be used in the Pipelines, Tasks and other wizards for Salesforce workflows created in Opsera.
These components are crucial to the Business Rules Engine and OmniStudio's functionality, as they help define business logic, manage data flow, and improve user experience within Salesforce applications.
ExpressionSetDefinition
ExpressionSetMessageToken
ExpressionSetObjectAlias
ExplainabilityMsgTemplate
DecisionMatrixDefinition
Last updated