Release Update 06/24/2024

Salesforce

Introducing Tree View for Salesforce Components Diff Screen to get a Clear Overview of File Structure and Relationships

The Diff screen in Salesforce task execution displays file changes in a List View, which is sorted based on the Jira Conflict resolution order. While this view offers a structured display, it can become challenging to navigate large projects due to its alphabetical sorting of files within each action category.

To improve the user experience and provide more flexibility, Opsera has introduced a toggle option for switching between two distinct views: List View and Tree View. The Tree View offers a more intuitive way to navigate large projects and understand the relationship between files. By displaying the project’s file structure, users can better visualize the impact of code modifications, especially in complex scenarios. This view enhances comprehension of changes within Jira projects.

Template Management for Task Wizard Selections

A new capability is introduced for users to create and manage templates based on Task Wizard selections. This feature provides a central repository for users to save and reuse their Wizard configurations, enabling them to select and apply templates during task configuration. The main objectives of this capability are to streamline common tasks, promote consistency across the organization, and foster collaboration and knowledge sharing among users.

Users can create and publish new templates by capturing their Wizard selections during task configuration. These templates can then be used to create new tasks, inheriting the pre-configured Wizard selections. To ensure appropriate access levels for different users, you can implement Role-Based Access Control (RBAC) to manage user permissions effectively. For more info, read here.

Note: The templates are currently only available for CPQ Data Transfer tasks.

Enhanced Bundle File Selection for Merging and Pull Requests

Opsera has introduced a new capability to manage modifications in a more efficient and precise way during Salesforce components which are in the bundle format. Earlier, any modification in a file within a bundle required merging or pulling in changes for all files in that bundle, regardless of whether only a few files were actually changed. This process was cumbersome and inefficient for large bundles with hundreds of files.

Now, users can select specific files from the bundles to include as part of the changes pushed to the configured branch. This ensures that only the relevant modifications are incorporated into the target branch, minimizing potential conflicts. The enhanced capability offers users greater control and flexibility in handling modifications, as they can now choose which files to update instead of dealing with all files in the bundle.

Insights

Dynamically Updated Heatmap Based on Copilot License Counts

The heatmap for developer adoption has been updated to be based on the Copilot license counts for an organization. The new heatmap dynamically adjusts its scales according to the Copilot license counts, offering a more accurate view of the data based on the size of the organization. The colour gradient in a heatmap's legend is split into five equal portions, each of which represents a 20% increment in the data.