Comment on page
Release Notes 23.1
September 2023
Version 23.1 – New Features, Enhancements, and Improvements
1. Automatic Merge after Successful CI Build
We know that understanding and managing version control can sometimes be a challenge. ARM offers the flexibility to cherry-pick branch revisions for merge or deployment. Now you can automate this process of cherry-picking the revisions in CI Jobs as a post-deployment step.
The 'Run Merge process on successful deployment' feature keeps track of builds in source branches and merges them into a designated destination branch if they meet the configured criteria (for example, if the build is successful). Rather than requiring manual effort, upstream merges may now be automated by the Salesforce Release Manager using revision numbers that were determined as part of a build cycle in CI jobs.
Users will be notified via email of the success or failure of the automated merge process.
2. Create and Install an Unlocked Package Version from a Version Control Branch
Use ARM CI intelligence to create a package version, build using the SFDX project structure in a Version Control branch, and install the same in the destination org of your choice—all from the same page.
You can now generate an unlocked package version automatically through the CI job, and as part of the deployment, it is deployed in the same build cycle. Until the 22.2 version, it picked the latest package version that was already successfully created in ARM.
When users create a CI job using this option, ARM checks the Version Control. If there is a change, it builds a new version on top of the packages. Once the package is created, then the deployment is triggered automatically.
3. Create Connected Apps
ARM now gives access to users to create and maintain their OAuth credentials. Users can set up the Connected Apps for Jira OAuth and register the credentials with ARM.
You can add, edit, and delete your Jira login credentials instead of contacting AutoRABIT to manage the connected apps. Once created, simply provide us with the connected app details like Client ID and Secret Keys.
We use these details to connect as an ALM and test the connection.
4. RESTricted Emails
The new RESTricted Emails section on the Notifications page of the Admin module helps ensure that ARM-related emails are not sent to deactivated users.
Admins can either add users to this list manually or deactivate the respective users from the Users page of the Admin module, and they will be automatically added to this list. These users will not receive ANY emails including deactivation, forgotten password, reset password, jobs executed in the application, etc. Admins can also use the same two methods to reactivate a user and remove them from this list.
There is also a provision for an Admin to remove all users from the RESTricted Emails list at once.
5. Dependency Analyzer
Dependency Analyzer helps you understand the dependencies among various components in your Salesforce org. It allows you to analyze the relationships among objects, fields, classes, triggers, and other metadata components.
With Quality Gates, ARM helps Salesforce developers run multiple checks to understand if and how their commits can break a Salesforce org. Currently, we enforce the following gates:
- SAST, SSPM, and AST (Static Code Analysis, Salesforce Security Posture Management, and Application Security Testing)
- Deployment Validation
- File Change Footprint
- Peer-to-Peer Code Review
With the introduction of the Dependency Analyzer, we can offer a fourth gate, Dependency Check, which will allow users to see what they are missing due to Salesforce specificity.
We have introduced the Dependency Analyzer in CI Jobs for now, and this is just a start at bringing this functionality to the remaining modules soon.
Users now have the option to ‘Run Metadata Dependency on Failed Deployments’ to view the results of failed metadata components with their dependencies and download them in Manifest and XML formats.
6. ServiceNow – ALM Management
The ARM–ServiceNow integration automatically posts updates to ServiceNow tickets. It makes tracking the status of your user stories and support tickets faster and easier. Tasks can be organized by project, allowing an organization to track issues within projects transparently.
ServiceNow will make information more easily accessible and workflows more streamlined, reducing the time and effort required to manage and resolve service requests. Additionally, the integration will allow teams to work more effectively, improving collaboration and communication.
- 1.Salesforce Spring (API 57.0) & Summer (API 58.0) Support AutoRABIT supports the most recent API 57.0 & API 58.0 versions in this release to keep our product updated with Salesforce updates. The most recent API version is intended for customizing and developing tools to manage the metadata model.
- 2.Exporting Selected User Details Users with Admin access can now choose the fields they want to include while exporting users' details to a CSV file. While selecting the Export option, the list of available fields is displayed. Admins can select and deselect the required fields by clicking the corresponding checkbox. Some of the fields are selected by default for ease of use. Admins can always deselect these fields if they are not required. Thus, based on the teams with whom they will be shared, Admins can customize the fields in the list.
- 3.More Info on CI Jobs and Info Users are now able to view the CI Jobs they created in the CI Job List screen to date inside ARM. The list is displayed in chronological order with the most recent jobs listed at the top.
- 4.'Created and Requested by' in Deployment UI Users are now able to view the ‘Created by’ and ‘Triggered by’ fields in the Deployment home screen without scrolling through multiple screens for this info, enabling monitoring of the deployment’s real-time progress. Read more
- 5.Self-Service Connected App Setup for Jira OAuth in ARM We've introduced a self-service feature allowing users to set up Jira OAuth-connected apps in ARM autonomously. With guidance from our user manual's Connected App guide, users can effortlessly create and register their app credentials, eliminating the need for support team assistance. Users can quickly establish a robust connection by inputting the generated Client ID and Server Key into ARM's settings.
- 6.Unified Admin Roles We’re excited to introduce a streamlined and more efficient Admin experience. We’ve consolidated the roles of Super Admin and Registered Admin into a single empowered Admin role. This change means Admins now have a unified set of tools and permissions, streamlining tasks and creating a more user-friendly Admin experience.
- 7.CI Jobs List and Results: Filter and Export Option We've enhanced the platform with a user-friendly quick filter and export feature in response to user feedback. This functionality empowers administrators, release managers, and users to efficiently organize and analyze data by alphabet or date, facilitating faster insights and informed decision-making.
- 8.Create Artifact: Release label more than 180 days In the Create Artifact section, users can now generate a Release Label and have the flexibility to choose an extended timeframe of over 180 days for retrieving comprehensive commit history data. This enhancement offers users a broader historical perspective, facilitating more in-depth analysis and tracking of commits for their projects.
- 9.Enhanced security and user experience. (NEW) The new features focus on enhancing security and user experience. They include a single-user session control to prevent multiple active sessions under the same username, automatic logout for inactivity to bolster security, and support for multiple tabs or pages in the same browser, improving user productivity and maintaining the environment's integrity.
This update has implemented significant performance upgrades to enhance the tool's efficiency and responsiveness. These enhancements encompass optimized queries and leveraging newer technologies, collectively resulting in a smoother and faster user experience.
September 2023
Version 23.1 – Streamlined CI/CD and Enhanced Control
We're thrilled to introduce a series of exciting enhancements to elevate your nCino experience. Get ready for:
1. Precision Deployment: Define your baseline revisions and effortlessly trigger builds for new revisions, enabling delta deployments. Package multiple commit revisions together for swift Record-Based Configuration (RBC) deployments.
2. Multi-Sandbox Mastery: Seamlessly deploy nCino CI builds to multiple target sandboxes, with the flexibility to choose up to 5 organizations per job. Say goodbye to redundant job creations for the same deployment across multiple Orgs.
3. Effortless Job Management: Our revamped CI job flow guides you directly to the ‘Job List’ page, streamlining your experience. A simple ‘Run’ button on this page empowers you to initiate jobs effortlessly.
4. Rollback Assurance: Take control of your nCino RBC deployments with our rollback feature. Capture snapshots before deployment and confidently revert your Org to its prior state if needed.
5. Access + Validation: We've renamed 'Applied Mappings' to 'External ID Mapping' for clarity. Plus, enjoy peace of mind with automated validation, ensuring your access to objects and essential external ID fields.
6. Post-Deployment Insights: Keep a finger on the pulse of post-deployment activities. The ‘Post Deploy Details' section provides consolidated updates for multiple Orgs. Dive deeper with 'View Details’ to explore orgs and their records effortlessly.
(ARM v 23.1.10)
Module | Summary | Fix Version(s) | Resolution | Cause |
|---|---|---|---|---|
Admin | Issue adding user mapping | 22.3, 23.1 | Code Fix | Use Case |
Deployments | Full org:org deployment failing with no proper reason | 23.1 | Code Fix | Use Case |
Admin | Issue with registering new branch in the repository | 23.1 | Code Fix | Use Case |
Reports | ARM and CodeScan integration EZ-Commit validation issue | 23.1 | Code Fix | Change Request |
Reports | New branch created CodeScan issue | 23.1 | Code Fix | Use Case |
Deployments | Destructive package is not generated properly when deploying from git revisions | 23.1 | Code Fix | Use Case |
Admin | nCino View Object Failing | NA | No Code Fix - Added Loggers | Data |
Deployments | Org sync not completing | NA | No Code Fix - Added Loggers | Data |
Dataloader | Corrected a spelling mistake in ARM steps. | 23.1, 22.3 | Code Fix | Use Case |
Dataloader | Corrected data seeding error preventing upsert | 23.1, 22.3 | Code Fix | Use Case |
Reports | Getting ‘cannot invoke "String.length()" because of "text" is “null”’ error when performing the ‘Get latest reports’ in Weekly reports | 23.1 | Code Fix | Use Case |
Reports | When navigating to Static Code Analysis screen from Reports module, getting the “comparison method violates its general contract!” error. | 23.1 | Code Fix | Data |
Version Control | On DX branch release label artifact execution, on deleted components, the destructive changes artifact preparation is not generated. | 23.1 | Code Fix | Use Case |
nCino | On-premise testing: CI Job with template option failed due to "data and metadata retrieval failed” error | 23.1, 22.3 | Code Fix | Use Case |
CI Jobs | Failed to deploy destructive changes though CI jobs. | 23.1 | Code Fix | Use Case |
(ARM v 23.1.9)
Module | Summary | Fix Version(s) | Resolution | Cause |
|---|---|---|---|---|
Admin | Branching baseline issue | 23.1 | Code Fix | Use Case |
CI Jobs | The new feature of merging only revision in the CI job build is not working | 23.1 | Code Fix | Use Case |
CI Jobs | CI job filter not working properly | 23.1 | Code Fix | Use Case |
Version Control | Commit not getting detected | 23.1 | Code Fix | Use Case |
Version Control | Rejecting a commit is merging the changes | 23.1 | Code Fix | Use Case |
Admin | Unable to save Pull Request Plugin config | 23.1 | Code Fix | Use Case |
Version Control | AR commit File Diff process is failing with errors | 23.1 | Code Fix | Use Case |
Version Control | Merge auto-rejected but CI job triggered | 23.1 | Code Fix | Use Case |
Admin | Changing role from Dev to Admin shows orgs and branches in New EZ- Commit without mapping under profile | 23.1 | Code Fix | Use Case |
Version Control and Deployment | Release Label Artifact not including code for a commit | 23.1 | Loggers Added | Data |
Dataloader | Dataloader Pro jobs causing huge threads pileup | 23.1 | Enhancement | Use Case |
CI Jobs | Data Retention – CI Jobs - Observing 'java.lang.NumberFormatException' error in the CI Retention process log when processing the string '2023-08-26.' Please check the date formatting to ensure it is being treated as a string and not causing the exception. | 23.1 | Code Fix | Use Case |
Version Control | While submitting the ALM commit with these “<ALM Issue ID>“, “{ALM Issue ID}” ALM patterns, unable to submit the commit | 23.1 | Code Fix | Use Case |
Deployments | Sub-user - Deployment History - While changing the date range filter, getting "Cannot invoke "String.equalsIgnoreCase(String)" because the return value of "com.autorabit.entity.deployment.DeploymentHistory.getCreatedBy()" is null" error | 23.1 | Code Fix | Use Case |
Version Control | With Release label deployment, the flow-meta.xml retrieval issue both constructive and destructive | 23.1 | Code Fix | Use Case |
Module | Summary | Fix Version(s) | Resolution | Cause | Enabled by default? | Feature Flag Name |
|---|---|---|---|---|---|---|
Version Control | Branch Protection Policy enforced and behavior of EZ- merge | 23.1 | Code Fix | Use Case | NO | GIT_LOGGEDIN_USER_AS_COMMIT_USER |
Version Control | Issue while creating feature branches in EZ - Commit screen | 23.1 | Code Fix | Use Case | | |
Version Control | Upload File option not available during EZ- commit with Option package manifest | 23.1 | Code Fix | Use Case | | |
(ARM v. 23.1.8)
Module | Summary | Fix Version | Resolution | Cause |
|---|---|---|---|---|
Deployments | Deployment tab - Redeploy/Promote issue | 22.3, 23.1 | Added Loggers | Data |
Dataloader | Optimize the Dataloader Pro job logs in the rabit cs log | 23.1 | Code Fix | Use Case |
nCino | Unable to create Feature Migration Template on Debt Schedule object | 22.3, 23.1 | Code Fix | Use Case |
All Modules | Invalid Email ID | 22.3, 23.1 | Code Fix | Use Case |
CI Jobs, Deployments, Version Control, Admin | Org Sync diff report differs for the same source org compared to different orgs. | 23.1 | Code Fix | Use Case * |
Dataloader | Urgent: AutoRABIT is down | 23.1 | Code Fix | Use Case |
Version Control | Issue with Block button during Merge Conflict | 23.1 | Code Fix | Use Case |
CI Jobs | CI job deployment failing: Restriction rules deployed as moderation rule and made the deployment bugged | 23.1 | Code Fix | Use Case |
CI Jobs | Urgent: Rollback of specific components - Issue | 23.1 | Code Fix | Use Case |
CI Jobs | Unexpected behavior when disabling component category on rollback destructive changes. | 23.1 | Code Fix | Use Case |
SFDX | Error while using Scratch Org Management tab | 23.1 | Code Fix | Use Case |
All Modules | ARM<>ULP Integration Issues | 23.1 | Code Fix | Use Case |
Version Control | Auto-reject on commit validation for SCA & Auto-reject setting in Merge | 23.1 | Code Fix | Use Case |
Module | Summary | Fix Version | Resolution | Cause |
|---|---|---|---|---|
CI Jobs | CI Job is not picking up changes committed on the branch, indicating "No modifications made." | 23.1 | Code Fix | Use Case |
Deployments | Org Synchronization – constructive & destructive changes are not working together | 23.1 | Code Fix | Use Case |
Admin | Sync error between ARM and GIT | 23.1 | Code Fix | Use Case |
Version Control | Deployment validation not working correctly during new EZ-Merge | 23.1 | Code Fix | Use Case |
CI Jobs | Merging only revision in the CI job build not working | 23.1 | Code Fix | Use Case |
(ARM v. 23.1.7)
Module | Summary | Fix Version(s) | Resolution | Cause |
|---|---|---|---|---|
Deployments | During Org Sync, file names are being repeated as part of the deployment results. | 23.1 | Code Fix | Use Case |
Deployments | User is unable to see the Deployment History. | 23.1 | Code Fix | Use Case |
CI Jobs & Deployments | User is unable to deploy static resource. | 23.1 | Code Fix | Use Case |
Reports | Scheduled Code Coverage Reports are running at the wrong time. | 23.1 | Code Fix | Use Case |
nCino | User is unable to create Feature Migration Template on Debt Schedule object. | 22.3, 23.1 | Code Fix | Use Case |
Dataloader | User is unable to upload files and update records; system logs user out instead. | 23.1 | Code Fix | Use Case |
Version Control | User is getting timeouts in merge screen. | 23.1 | Code Fix | Use Case |
(ARM v. 23.1.6)
Module | Summary | Fix Version(s) | Resolution | Cause |
|---|---|---|---|---|
All Modules | SF CLI version upgrade to 2.14.6 | 23.1 | Code Fix | Enhancement |
Environment Provisioning | View environment provisioning templates | 22.3 & 23.1 | Code Fix | Enhancement |
Admin | Branching baseline is not picking all components from production | 22.3 & 23.1 | Code Fix | Use Case |
Deployments | Help with destructive change | 22.3 & 23.1 | Code Fix | Use Case |
Version Control | Merge request is failing due to validation credentials | 22.3 & 23.1 | Code Fix | Use Case |
CI Jobs, Deployments | Issues with a release – related to Feature Flag - not automatically deployed: STANDARD_VALUE_SET_DELTA | 22.3 & 23.1 | Code Fix | Data |
Version Control | Approval button is not visible after successful merge validation | 22.3 & 23.1 | Code Fix | Data |
Version Control | Create artifact: not completed | 23.1 | Code Fix | Data |
Admin | AutoRABIT login not working | 23.1 | Code Fix | Use Case |
Version Control | Error pop-up during merge type selection as Commit Label in EZ-Merge | 23.1 | Code Fix | Data |
CI Jobs | AutoRABIT AccelQ Integration/ bhg-inc.com | 23.1 | Code Fix | Use Case |
CI Jobs |
Developer API for CI Jobs History not returning latest results. | 23.1 | Code Fix | Use Case |
nCino | Ability to trigger nCino CI jobs using REST API | 23.1 | Code Fix | Customer Request |
CI Jobs | For run test automation scripts job: More than one cycle is not displayed in the individual job history | 23.1 | Code Fix | Use Case |
Version Control | Unable to delete feature branch under merge request, getting internal server error | 23.1 | Code Fix | Use Case |
Version Control | Unable to view the entry of recently created merge request in the merge request history screen | 23.1 | Code Fix | Use Case |
Version Control | Criteria met ALM's not getting fetched under merge request | 23.1 | Code Fix | Use Case |
nCino | Instead of POST methods need to change the GET | 23.1 | Code Fix | Customer Request |
(ARM v. 23.1.5)
This was a maintenance release. The following items were enhanced, fixed, or added:
- Loggers were added to Reports and Dashboard modules in versions 22.3 and 23.1 due to a data error in which users were unable to fetch a Salesforce code coverage report.
- An enhancement was made by a code fix applied to the Deployments and Org Synchronization modules in versions 22.3 and 23.1 enabling users to change deploy text for validations.
- A code fix was applied to the CI Jobs module in version 23.1 identified by use case to enable validation CI Job comments to be visible on the Bitbucket PR.
- A code fix was applied to the Admin module of version 23.1 due to a use case in which modification logs were needed for Version Control mapping setup.
- A code fix was applied to the Version Control module of version 23.1 related to a use-case error in which External Pull Requests, when expanding the files in the diff, content was not visible and showing as undefined.
- A code fix was applied to the Version Control module of version 23.1 related to a use-case error in which External Pull Requests, when expanding files in the diff, show duplicate content.
- A code fix was applied to the nCino module of versions 22.3 and 23.1 due to a use-case scenario during dataset creation with saving only user info in Json that is relevant to current dataset.
- A code fix was applied to the Version Control module of versions 22.3 and 23.1 due to a use-case error with an AR merge failing.
- A code fix was applied to the Version Control module of versions 22.3 and 23.1 due to a use-case error in which the incorrect removal of Custom Application type in package.xml on EZ-Commit via AR occurred.
- A code fix was applied to the Version Control module of versions 22.3 and 23.1 in which two external pull request issues were occurring.
This was an interim maintenance release. The following items were enhanced, fixed, or added:
- A Code Fix was applied to the Deployments module due to the Deployment initiated using Org Synchronization failing caused by a use case with a fix applied to versions 22.3 and 23.1.
- A Code Fix was applied to the Version control module due to a Validation Error requiring Feature Flag: VALIDATE_DEPLOY_PICK_FILECHANGES_FROM_DIFF caused by a use case with a fix applied to versions 22.3 and 23.1.
- A Code Fix was applied to the Reports module due to the Weekly Code/ Test Coverage Report taking a long time caused by a use case with a fix applied to versions 22.3 and 23.1.
- A Code Fix was applied to the Admin module due to an SSO Error as of Sept 25 caused by a use case with a fix applied to versions 23.1.
- A Code Fix was applied to the Admin module due to an AutoRABIT Login Issue caused by a use case with a fix applied to versions 23.1.
- A Code Fix was applied to the Version Control module due to validation/merge errors after latest release caused by a use case with a fix applied to versions 23.1.
- A Code Fix was applied to the Dataloader module due to the download button not working caused by a use case with a fix applied to versions 23.1.
22 October 2023
(ARM v. 23.1.4)
This is a maintenance release. The following items were enhanced, fixed, or added.
- Performed a code fix to version 23.1 affecting the Reports module resulting from a use-case error with code coverage report emails missing test class errors in the subject.
- Applied a code fix to version 23.1 for the Deployments module resulting from a use-case scenario with user unable to see deployment history.
- Instituted a code fix to version 23.1 for the CI Jobs module resulting from a use-case error with the org management page.
- Implemented a code fix to versions 22.3 and 23.1 affecting the CI Jobs module due to a use-case issue to SFDX/CI jobs with package version installation key.
- Performed a code fix to versions 22.3 and 23.1 affecting the Version Control module for a use-case issue related to custom label translation file.
- Applied a code fix to versions 22.3 and 23.1 related to the Deployments module for a use-case error with previous deployment label 'add members' option not working.
- Performed a code fix to version 23.1 affecting the Admin module due to a use-case error with MyProfile not redirecting properly and showing the profile icon after clicking on the 'profile' button.
- Implemented a flow center change to versions 22.3 and 23.1 for the Dataloader module due to a use-case error with the download button not working.
This interim release consisted of the following:
- Performed a code fix to versions 22.3 and 23.1 affecting the Version Control module for a use-case issue with a custom label translation file.
(ARM v23.1.3)
AutoRABIT provided the API 59.0 changes as part of its weekly fixes on both 22.3 and 23.1. This is available only for ARM modules, not for Dataloader or nCino. For DL and nCino, API 59.0 changes will be available next week as part of the Wednesday fixes deployment.
This is a maintenance release. The following items were enhanced, fixed, or added.
- Instituted an enhancement via code fix to versions 22.3 and 23.1 affecting all ARM modules, applying Salesforce v.59 upgrade for Winter 2024.
- Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the CI Jobs module concerning a package directory issue.
- Applied a code fix to versions 22.3 and 23.1 due to a use-case scenario pertaining to the Environmental Provisioning module with users not able to generate a migration template using the migrate custom setting data module.
- Issued a code fix to versions 22.3 and 23.1 for a use-case error in the Version Control module with a custom label translation file.
- Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the Deployments module concerning bugs in deployment with multi-packages and static resource.
- Applied a code fix to version 22.3 resulting from a use-case error affecting Dataloader returning an 'invalid cross reference id' error for ProcessInput and ProcessingInputCondition objects.
- Implemented a code fix to version 23.1 for a use-case error to the Version Control module, in which duplicate commits were being created.
- Performed a code fix to version 23.1 for a use-case error to the Version Control module pertaining to Deployment history, with the deployment status not being visible.
- Performed a code fix to version 23.1 relating to a use-case error affecting the nCino module in which users are unable to deploy nCino feature (RBC), instead returning a 'malformed query' result.
- Performed a code fix to version 23.1 relating to a use-case error to the Version Control module with users unable to perform new pull request commit due to commit template permission.
- Executed a code fix to version 23.1 relating to a use-case error affecting the Version Control module with users continually getting a login redirect error when trying to create a branch through an EZ-Commit.
- Performed a code fix to version 23.1 relating to a use-case error in the Version Control module with users unable to create a commit label, continually getting a login redirect error.
- Performed a code fix to version 23.1 relating to a use-case error affecting the Admin module, particularly a SuperAdmin user, not getting any response to the scheduler's service registration button without expanding the selection.
- Initiated a code fix related to a use-case scenario in version 23.1 affecting the Version Control module with release labels getting failed after restarting the agent.
- Applied a code fix related to a use-case scenario affecting version 23.1 in the nCino module, when parallel CI jobs limit was reached, the job was not added to the queue.
- Performed a code fix to correct a use-case error in version 23.1 related to the nCino module for a merge missing changes.
- Performed a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the Version Control module, in which users were unable to create/append a revision to an existing label for a sub-user.
- Implemented a code fix to version 22.3 relating to a use-case error in the Version Control module in which the user was getting empty error pop-ups under the ALM management screen for a sub-user, not displaying the ALM items.
- Performed a code fix to version 23.1 relating to a use-case error affecting the nCino module with a job deployment issue.
- Applied a code fix to version 23.1 relating to a use-case error affecting the nCino module for a CI job build getting failed.
- Initiated a code fix to versions 22.3 and 23.1 relating to a use-case error affecting the nCino module for a 'no modifications status' displayed for a version control BR job.
- Performed a code fix to versions 22.3 and 23.1 related to a use case scenario affecting the Version Control module related to ALM tickets being bugged after using the ALM sync refresh.
- Performed a code fix to version 23.1 related to the Deployments and CI Jobs modules affecting a use-case error being issued during CI Deployment for property 'userLicense' not valid in version 57.0.
This is a maintenance release. The following items were enhanced, fixed, or added.
- Performed a code fix to versions 22.3 and 23.1 for a use-case error affecting the Admin module relating to code coverage issues.