Release Notes 23.1

ARM Release Notes 23.1

September 2023

Version 23.1 – New Features, Enhancements, and Improvements

Supports Provar Current Version: 2.10.1

Supports Apex PMD Current Version: 7.0.0

New Features

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.

Enhancements

  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.

Improvements

This update has implemented significant performance upgrades to enhance the tool's efficiency and responsiveness. These enhancements encompass optimized queries and leverage new technologies, collectively resulting in a smoother, faster user experience.

31 July 2024

ARM 23.1.40

  1. A code fix was applied to the CI Jobs module of versions 23.1 and 24.1 related to a use-case error causing the CI Jobs History report to not generate. Support ticket #116943

24 July 2024

ARM 23.1.39

  1. A code fix was applied to the Version Control module in version 23.1 related to a use-case error in which the merge completion was taking too long. Support ticket #113102

  2. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which an issue was occurring with the system administrator lite. Support ticket #117297

  3. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to see the metadata through the single revision deployment. Support ticket #116919

  4. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to deploy the Einstein Prediction builder. Support ticket #116909

  5. A code fix was applied to the Admin module of versions 23.1 and 24.1 due to a use-case error with users losing access. Support ticket #111830

  6. A code fix was applied to the Version Control module of versions 23.1 and 24.1 due to a use-case error requiring multiple revisions on an ALM work item. Support ticket #117810

  7. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error with the new profile compare feature. Support ticket #117309

  8. A code fix was applied to the Deployments module of version 23.1 due to a use-case error with 'add additional member' showing duplicates when expanding the toggle. Internal request.

  9. A code fix was applied to the Version Control module of version 23.1 due to a use-case error with users getting an error for a commits tab external pull request using Bit bucket repo. Internal request.

17 July 2024

ARM 23.1.38

  1. A code fix was applied to the nCino module in version 23.1 related to a use-case error in which Data Loader Pro was not fetching the child object. Support ticket #115313

10 July 2024

ARM 23.1.37

  1. A use-case error identified in version 23.1 required a code fix, which was applied in versions 23.1 and 24.1 to the Deployment and Version Control modules, to correct a scenario in an org-to-org full-profile deployment where it was not capturing package visibility and permissions. Support ticket #110760

  2. A use-case error identified a code fix needed to the Reports module of version 23.1 to fix a product test class in which the weekly scheduled job failed. Support ticket #115654

  3. A code fix was applied to versions 23.1 and 24.1 due to a use-case error identified in version 23.1 where commits were failing with a 'no credentials mapped' error in the Version Control module. Support ticket #116704

  4. A code fix was applied to the Admin module in version 23.1 related to a use-case scenario that required additional support to create the ARM instance from scratch. Support ticket #117015

  5. A code fix was applied to the Deployment module in version 23.1 due to a use-case error in which the user was unable to get the popup while deploying using package.xml as the source. Support ticket #116967

3 & 7 July 2024

ARM 23.1.36

  1. A use-case scenario identified an error in version 23.1 with metadata retrieval from the repository failing in the Deployment module, which was resolved in versions 23.1 and 24.1. Support ticket #115818

  2. A code fix identified in version 23.1 was applied to correct a use-case error in the Version Control module of version 23.1 related to commit templates. Support tickets #116124, #116138

  3. A code fix identified in version 23.1 by internal request ticket was applied to the Admin and CI jobs modules in versions 23.1 and 24.1 to upgrade v61 (Beta) to v61.

  4. A use-case error in version 23.1 required a code fix to version 23.1 Deployment and Version Control modules due to an org comparison not showing diff results. Support tickets #112752, #116025

26 June 2024

ARM 23.1.35

  1. A data error reported in version 23.1 with the Version Control module that resulted in version control being deleted was resolved in both 23.1 and 24.1 through adding loggers. Support ticket #114503

  2. A use-case error reported in version 23.1 with the Version Control module in which the user was unable to use an existing conflicted file, which resulted in reraising merge requests, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115084

  3. A use-case error reported in version 23.1, which resulted in an issue with the Data Loader module in which the software was not inserting the correct record type, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #114076

  4. A use-case error reported in version 23.1 with the nCino module in which rollbacks were only partially being completed was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115204

12 June 2024

ARM 23.1.34

  1. A code fix was performed due to a use-case error related to the CI Jobs module in which nCino CI Jobs were not triggered by metadata CI Jobs on success. Support ticket #113887

  2. A code fix was performed due to a use-case error related to the Version Control module in which the API response from CodeScan returned a page not found (404) error in ARM. Support tickets #108895, #115120, #114434

  3. A code fix was performed due to a use-case error related to the Deployment module in which the Deployment button was not enabled in AutoRABIT after validation. Support ticket #107108

  4. A code fix was performed due to a use-case error related to the Deployment module in which the user was unable to deploy a Bot from a Branch to a sandbox. Support ticket #11497

  5. A code fix was performed due to a use-case error related to the Version Control module in which an ALM work item was not displaying in the merge. Support ticket #113626

  6. A code fix was performed due to a use-case error related to the Admin module in which a user was unable to implement ARM and Zoho desk integration with JWT.

  7. A code fix was performed due to a use-case error related to the Version Control module in which a user was unable to perform EZ-Commits. Support ticket #114441

  8. A code fix was performed due to a use-case error related to the Version Control module in which the previously validated commit label showed to add a date instead of the label dropdown. Support ticket #115249

  9. A code fix was performed due to a use-case error related to the Reports module that required us to fix recursive errors.

  10. A code fix was performed due to a use-case error related to the Data Loader module in which the master-child relationships were not being applied when loaded through Data Loader Pro. Support ticket #111780

  11. A code fix was performed due to a use-case error related to the nCino module in which the CI job was not updating templated objects and object record count when the checkout was not taken from version control. Support ticket #112704

  12. A code fix was performed due to a use-case error related to the nCino module wherein CI Jobs for nCino RBC feature migrations were failing. Support ticket #114991

  13. A code fix was performed to the Admin module as a result of a change request related to users being unable to log in to AutoRABIT. Support tickets #115392, #113300

5 June 2024

ARM 23.1.33

  1. A code fix was applied to all modules prompted by an internal change request in preparation for support of the Salesforce Summer '24 release. This will require updates to internal documentation.

  2. A code fix was applied to the Deployments module resulting from an internal request to correct a use-case error in which a deployment failure and document discrepancy were encountered, with subsequent deployment attempts unsuccessful.

  3. A code fix was applied to the Version Control module initiated by a use-case error in which the team encountered an ALM commit issue related to the label name when testing a user story. Support ticket #113308

  4. A code fix was applied to the Version Control module related to a use-case error occurring when processing merge conflicts. Support ticket #113606

  5. A code fix was applied to the Admin module related to a data error in which the branching baseline was not updating the LWCs in the branch. Support ticket #113174

  6. A code fix was applied to the Data Loader module related to a configuration error causing Data Loader to not work as expected. Support ticket #113575

  7. A code fix was applied to the ARM module related to a use-case audit logging API error with start time and end time issues occurring when fetching logs. #113739

29 May 2024

ARM 23.1.32

  1. A code fix was applied to the Version Control module to resolve a use-case error in which the user cannot approve or reject a Merge Request when the label name contains a "+" symbol. When the merge label contains unsupported characters, the merge label is not submitted as expected and the validation message displays the supported characters. Support ticket #112715

  2. A code fix was applied to the Admin module related to a use-case error occurring when modifying the Team Administrator, it created duplicate Teams, consuming existing licenses. Support ticket #109457

  3. A code fix was applied to the CI Jobs module due to a use-case error in which a Checkmarx scan was not matching up and breaking the build. Support ticket #105217

  4. A code fix was applied to the CI Jobs module due to a use-case error occurring when multiple CI jobs run on GitHub PRs, AutoRABIT reports incorrectly that the jobs were successful. * Issue requires updated documentation. Support ticket #111955

  5. A code fix was applied to the Version Control module related to a use-case error in which Mock Deployment criteria check lines were not logged in the UI during the Prevalidation Deployment refresh, but they do appear after auto-rejection and subsequent refresh.

  6. A code fix was applied to the Deployment module to correct a use-case error occurring when selecting and deselecting ApexClass and CustomField metadata types, the Deploy pop-up incorrectly displayed "All components are selected" for ApexClass instead of the list of selected components.

  7. A code fix was applied to the Version Control module to correct a use-case error displaying unwanted characters, such as different language letters, like “— in the message: "Please wait†when a compare and commit is in progress."

  8. A code fix was applied to the Version Control module due to a use-case PrevalidationMerge error occurring when the user was trying to approve a Merge Label through an API with an auto-rejected label, the status changed from "Auto-reject" to "Commit."

  9. A code fix was applied to the Version Control module after a user observed three gaps/issues in Commit Templates: 1) Data Table Change in the Commit Template under the 'All Metadata' tab should also sync across all three places, like Deployments, VC Commit, and Commit Template under the 'All Metadata' tab for data table changes. 2) Folder-Related Members Visibility: Folder-related all members are not visible when selecting the folder. This does not sync with EZ Commit All Metadata, from new commit all members. When selecting the folder, all respective folder-related members are visible but not included in the Commit Template when selecting the same Salesforce org. 3) Input Search Dropdown Missing for selecting Folders.

  10. A code fix was applied to the Data Loader module concerning a use-case error in which the user was unable to create a project journey with a BIC__c field using "LookUp via" feature. Support ticket #110111

22 May 2024

(ARM 23.1.31)

  1. A code fix was applied to the Version Control module due to a use-case error related to EZ-Commits and EZ-Merges not taking the master branch, even when Baseline Branch "master" is selected. #107151

  2. A code fix was applied to the Version Control module due to a use-case error in which reverting a commit failed. #112094

  3. A code fix was applied to the Version Control module due to a use-case error related to the system failing to select multiple reports. #112381, #112812

  4. A code fix was applied to the Deployment module due to a data error in which the org sync was not completing. #111545

  5. A code fix was applied to the Deployment module due to a data error in which there was a problem in component selection during deployment. #111892

  6. A code fix was applied to the Deployment module due to a data error in which the selected items tab was now showing the selected components, as well as the search filter not always being visible. #112095

15 May 2024

(ARM 23.1.30)

  1. Code fix applied to Deployments module due to user receiving error message: INVALID_LOGIN: Invalid username or password or security token or API version or user locked out. #111008

  2. Code fix applied to Version Control module due to user not being able to see the merge request label name in BitBucket after merging. This required a feature flag, MERGE_STRATEGY_ENABLE_NON_FF, which is not enabled by default and must be enabled. #110541

  3. Code fix applied to the Deployments module related to user experiencing Redeploy/Promote hanging if previous deployment used specified tests. This requires a feature flag, AR_33697_ENABLE_APEX_TEST_GET_CALL, which is not enabled by default and must be enabled. #110764

  4. Code fix applied to Deployments module related to email templates of type Visualforce not being added to the package.xml when deploying. #110762

  5. Internal - Code fix applied to Version Control module due to DX Package Directory Selection lists not being visible when configuration changes from Vlocity SF org and Vlocity repo to DX Repo.

  6. Code fix applied to Version Control module related to an auto-rejected merge label being pushed to a remote repository. #112244

7 May 2024

(ARM 23.1.29)

29 April 2024

(ARM 23.1.28)

24 April 2024

(ARM 23.1.27)

14 April 2024

(ARM 23.1.26)

3 April 2024

(ARM 23.1.25)

27 March 2024

(ARM 23.1.24)

20 March 2024

(ARM v. 23.1.23)

13 March 2024

(ARM v. 23.1.22)

6 March 2024

(ARM v. 23.1.21)

28 February 2024

(ARM v. 23.1.20)

21 February 2024

(ARM v. 23.1.19)

12 February 2024

(ARM v. 23.1.18)

7 February 2024

(ARM v. 23.1.17)

28 January 2024

(ARM v. 23.1.16)

21 January 2024

(ARM v. 23.1.15)

14 January 2024

(ARM v. 23.1.14)

7 January 2024

(ARM v. 23.1.13)

17 December 2023

(ARM v. 23.1.12)

10 December 2023

(ARM v. 23.1.11)

3 December 2023

(ARM v 23.1.10)

26 November 2023

(ARM v 23.1.9)

22 November 2023

19 November 2023

(ARM v. 23.1.8)

15 November 2023

12 November 2023

(ARM v. 23.1.7)

5 November 2023

(ARM v. 23.1.6)

27 October 2023

(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.

25 October 2023

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.

18 October 2023

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.

15 October 2023

(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.

11 October 2023

  • 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.

8 October 2023

(ARM v23.1.2)

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.

  • Applied a code fix to versions 22.3 and 23.1 related to a use-case error in the Deployments module concerning a flow component missed in the deployment.

  • Implemented a code fix to versions 22.3 and 23.1 for a use-case error related to a specific customer’s fields for redeployment.

  • Applied a code fix to version 23.1 for a use-case error affecting the Deployments module related to metadata production and a deployment issue.

  • Integrated a code fix to version 23.1 affecting the Deployments and CI Jobs modules for a deployment issue running all test classes.

  • Performed a code fix to the nCino module in version 23.1 pertaining to Salesforce Orgs not showing as source orgs for nCino feature management deployments.

  • Applied a code fix to the nCino module in versions 22.3 and 23.1 pertaining to [arm-qan] no modification status displayed for version control BR job.

  • Added loggers to versions 22.3 and 23.1 to correct a use-case error in the Deployments module pertaining to a deployment bug occurring with multi packages and static resources.

1 October 2023

(ARM v23.1.1)

This is a maintenance release. The following items were enhanced, fixed, or added.

  • A code fix was applied to the version control module in releases 22.3 and 23.1 due to a use-case error with a user being unable to create a new commit.

  • A code fix was performed in the 23.1 release to the version control module for a use-case error when merging destructive changes.

  • A code fix was instituted to the CI Jobs module in version 23.1 to address when a CI job has two different package directories. Changes were failing under one package when the analysis was completed in CodeScan.

  • A code fix was performed for release versions 22.3 and 23.1 to the deployments module for a use-case error resulting in a buggy deployment with multi packages and the static resources being bugged as well.

  • A code fix was applied to the version control module in releases 22.3 and 23.1 concerning a use-case error for an EZ-Commit, where the user was unable to view the 'deleted components' tab for the commit template when unchecking the 'skip mappings' checkbox.

  • A code fix was implemented to versions 22.3 and 23.1 to correct an error with the deployments module due to a deployment initiated using org synchronization failing.

  • A code fix was applied to releases 22.3 and 23.1 due to a use-case error in which the registration date of the repository was not correct in the version control repository (created date in AutoRABIT).

  • A code fix was performed to versions 22.3 and 23.1 due to a data error in the version control module preventing ALM working items from loading.

  • A code fix was initiated for versions 22.3 and 23.1 due to a data error affecting the reports module, which occurred when executing a static code analysis (CodeScan) report.

  • A code fix was performed to version 23.1 in the version control module resulting from a data error on the commit history screen.

  • A code fix was implemented in versions 22.3 and 23.1 to the version control module related to a use-case error wherein the baseline job has modified the Salesforce folder structure in GitHub.

  • Loggers were added in the version 23.1 release due to a data error in the version control module causing duplicate commits to be created.

  • A code fix was implemented to the nCino module for versions 22.3 and 23.1 for a data error in which the records count was not being updated in the object sidebar for the version control baseline revision job.

24 September 2023

(ARM v23.1) This is a maintenance release. The following items were enhanced, fixed, or added:

  • A code fix was applied to the Deployment module due to a data error concerning an Org difference pulling changes from the managed packages.

Last updated