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.

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)

ModuleSummaryStatusFix VersionResolutionCause

Version Control

Commits for Fields on Objects are Removing Lines from related Object XML

QA Passed

23.1

Code fix

Configuration

Version Control

Implemented an option to add Reviewers when Creating an External Pull Request

QA Passed

23.1

Code fix

Use case

Version Control

Commit Issue with Custom Page Web Links Deletions

QA Passed

23.1

Code fix

Use case

Version Control

Configure Gated Check-Ins Report for Deployment Validation

QA Passed

23.1

Code fix

Use case

Version Control

Improve Performance of All Metadata Components Screen

QA Passed

23.1

Code fix

Use case

Administration

EBR User Metrics

Done

23.1

Code fix

EBR Change Request

Data Loader

Data Loader Pro jobs not picking up Records

Customer Coordination

23.1

Added Loggers

Use case

29 April 2024

(ARM 23.1.28)

ModuleSummaryStatusFix VersionResolutionCause

Deployments

Getting error on deployments

QA Passed

23.1

Code fix

Use case

CI Jobs

Skip member is not working

QA Passed

23.1

Code fix

Use case

Version Control

EZ-Commits failing

QA Passed

23.1

Code fix

Use case

Version Control

Static resources not identified by ARM SCA

QA Passed

23.1

Code fix

Use case

Version Control

Merge showing as no modifications

QA Passed

23.1

Code fix

Use case

Version Control

Error occurred when the user attempted to upload the conflicted zip file from the local system after manual modifications

QA Passed

23.1

Code fix

Use case

Reports

Inquiries regarding report module

QA Passed

23.1

Code fix

Use case

Deployments

Deployment from Dev Sandbox to B2C2 QA Org by using feature - New Deployment

QA Passed

23.1

Code fix

Use case

CI Jobs

Build did not include second revision

Requires Customer Coordination

Loggers added

Loggers added

CI Jobs

Run test based on changes, noticed issues

Requires Customer Coordination

Loggers added

Loggers added

nCino

IDs of parents/children and records not resolving

QA Passed

23.1

Code fix

Use case

24 April 2024

(ARM 23.1.27)

ModuleSummaryResolutionCause

Version Control

EZ-merges: Successful validations were auto-rejected on 'validate deploy' step

Code fix

Use case

Version Control

Release Label: Package is not preparing

Code fix

Use case

Reports

Weekly Reports tab error

Code fix

Use case

Deployments

Backups not being created for user

Code fix

Use case

Version Control

Code Scan Analysis not showing in AR ARM tool - UI

Code fix

Use case

Version Control

setting default repository

Code fix

Use case

Deployments

ExternalCredentialPrincipalAccess (permissionSet) is ignored on a git revision deployment

Code fix

Use case

Version Control

Unknow error while merging site components

Code fix

Use case

CI Jobs

CI Job does not deploy all components

Code fix

Use case

Admin

SSH connectivity issue

Code fix

Use case

Version Control

request_closure_duration_mins mismatch for the merges

Code fix

Use case

Reports

B2C Prod Code Scan report

Code fix

Use case

nCino

AR issues

Added Loggers

Use case

Dataloader

User Object Requiring ALL Fields for Uploads

Added Loggers

Use case

14 April 2024

(ARM 23.1.26)

ModuleSummaryStatusVersionResolutionCause

Deployments

Org Sync issue with case components

QA Passed

23.1

Code fix

Use case

Deployments

B2C Org sync diff mail notification issue

QA Passed

23.1

Code fix

Use case

CI Jobs, Deployments

Einstein Chatbot Deployments Failing

QA Passed

23.1

Code fix

Use case

Admin

log files are not present

QA Passed

23.1

Code fix

Use case

Deployments

Deployments are not working

QA Passed

23.1

Code fix

Use case

CI Jobs, Deployments

Failed to initiate the deployment

QA Passed

23.1

Code fix

Use case

Version control

Profile commit progress delay

QA Passed

23.1

Code fix

Use case

Admin

Team Administrator modifications creating duplicate Teams and consuming existing licenses

QA Passed

23.1

Code fix

Use case

Version control

Issue Retrieving Components

QA Passed

23.1

Code fix

Use case

Version control

Release Label Stuck while building Artifact

Requires Customer Coordination

Loggers added

Deployments

utils.js was not deployed as part of package

Requires Customer Coordination

Loggers added

nCino

Version control record deployments to Salesforce Environments falling off

QA Passed

23.1

Code Fix

Use case

nCino

Lack of Consistency in Filter Functionality Across Feature Management, Deployment History, Commit History, and CI Jobs

QA Passed

23.1

Code Fix

Use case

Version control

Unable to view the Autodraft date and managed package changes dropdown

QA Passed

23.1

Code Fix

Use case

Admin

Super Admin EBR Token Security Enhancement

Done

23.1

Code fix

Internal change request

3 April 2024

(ARM 23.1.25)

ModuleSummaryResolutionCause

Reports, CI Jobs, Deployments, Version Control

ARM overwrites any exclusions set up in CodeScan UI * Requires documentation.

Code Fix

Change Request

Deployments

Single revision deployment taking longer time to retrieve revision

Code Fix

Use Case

Version Control

Org registration issue – resolved by displaying in Logs the exact Salesforce error

Code Fix

Use Case

Version Control

Getting empty revision when performing single revision merge with no modifications

Code Fix

Use Case

Version Control

Unable to create branch with branch name containing "&" through EZ-commit and Modularization

Code Fix

Use Case

nCino

Failure to Display Jobs in Deployment History for Version Control using Salesforce with Single Revision of initial commit

Code Fix

Use Case

nCino

Feature Deployment issue with Salesforce Org Version Control when selecting initial commit as Revision

Code Fix

Use Case

nCino

Version control record deployments to Salesforce environments dropping off

Code Fix

Use Case

27 March 2024

(ARM 23.1.24)

ModuleSummaryStatusVersion ReportedFix Version(s)ResolutionCause

Deployments

Org Sync question on Moderation Rule difference

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to create EZ-Commit for the new user

QA Passed

23.1

23.1

Code Fix

Use Case

Reports

Problem with scheduled code coverage reports

QA Passed

23.1

23.1

Code Fix

Use Case

Deployments

Profile Comparer - Taking too long to deploy

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Issue in Merging

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Incorrect merge status issue

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

The page is taking longer time to load the metadata when selecting to show metadata members.

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Vlocity DataPacks not being baselined

QA Passed

23.1

23.1

Code Fix

Use Case

Admin

Getting stuck in loading when trying to Expand ALM mappings

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

CI Deploy job link throwing pop-up error message

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Loggers added in the SCA log to display whether the baseline branch was selected during the commit and merge process

Customer Coordination

23.1

NA

No Code Fix

Loggers Added

nCino

Data Loader Pro jobs failing for Lead

QA Passed

23.1

23.1

Code Fix

Use Case

nCino

nCino Deployment History - search filter criteria is not working

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unnecessary select all checkbox is showing in added and modified tab

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to view created credentials

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

Returns all CI Jobs History to EBR Data irrespective of active

Done

23.1

23.1

Code Fix

Internal change request in EBR Data Visibility

nCino

Feature Deployment Issue with Salesforce Org Version Control

QA Passed

23.1

23.1

Code Fix

Use Case

Data Loader Pro

Issue with Audit Fields

QA Passed

23.1

23.1

Code Fix

Use Case

Admin, Version Control

Unable to register the same repository twice * REQUIRES FEATURE FLAG: SKIP_DUPLICATE_REPOSITORY_REGISTRATION_CHECK

QA Passed

23.1

23.1

Code Fix

Use Case

20 March 2024

(ARM v. 23.1.23)

ModuleSummaryStatusFix VersionResolutionCause

CI Jobs

nCino CI jobs created are not visible for CI job on successful deployment

QA Passed

23.1

Code Fix

Use Case

Version Control

Regarding unable to approve commit request

QA Passed

23.1

Code Fix

Use Case

Version Control

Very slow commits

QA Passed

23.1

Code Fix

Use Case

Version Control

Unable to create branch with '&' character getting Exception Error

QA Passed

23.1

Code Fix

Use Case

Version Control

Issues after Branching Baseline

Requires Customer Coordination

Added Loggers

No Code Fix

Reports

Static Code Analysis fails with timeout error

Requires Customer Coordination

Post fix awaiting customer confirmation.

Code Fix for SF CL timeout configuration.

Admin

Observing that after the 7th file, RabitCS and Agent logs are not being created or generated. From the 8th file, they are being overridden from Existing files 1 to 7.

QA Passed

23.1

Code Fix

Use Case

CI Jobs, Deployments

Identified below nCino CI Job "related to VC Source job type" displaying issue in CI jobs and Deployments

QA Passed

23.1

Code Fix

Use Case

Flow Center

Enable SSL for the Kafka used to communicate with FlowCenter.

QA Passed

23.1

Code Fix

Use Case

nCino

nCino Feature deployment failed with a “malformed query” error, Feature deployment and Ci Job. nCino CI jobs the customer has run failed with an exception, and the failed records column shows zero.

QA Passed

23.1

Code Fix

Use Case

Data Loader Pro

[ARM-QAN5,7] The job is currently running in progress, but the Success Record Count is showing in the Failure Count.

QA Passed

23.1

Code Fix

Use Case

13 March 2024

(ARM v. 23.1.22)

ModuleSummaryFix VersionResolutionCause

Deployments

Profile Comparer was taking too long to deploy

23.1

Code Fix

Use Case

CI Jobs

When the agent is external, DevHub authentication was not properly validated in CI Jobs for DX unlock and install-type CI job

23.1

Code Fix

Use Case

Admin

Signup account creation email not received by respective created-by owner

23.1

Code Fix

Use Case

Deployments

packExport is not failing when selecting data packs

23.1

Code Fix

Use Case

CI Jobs

Status Check API working incorrectly on UI

23.1

Code Fix

Use Case

CI Jobs

Issue when deploying the release to the master branch

23.1

Code Fix

Use Case

Version Control

Issue when creating commit labels with dots (.) post upgrade * Feature Flag required (not enabled by default): INCLUDE_DOT_IN_SFDX_COMMITLABEL_NAME

23.1

Code Fix

Use Case

Version Control

Intermittent issue with the Merge screen

23.1

Code Fix

Use Case

Version Control

Commit Labels within EZ-Merge no longer sorted by latest Commits

23.1

Code Fix

Use Case

Reports

CodeScan analysis discrepancies in APAC Prod * Requires documentation update

23.1

Code Fix

Use Case

Version Control

Territory metadata type is not fetched as destructive changes during EZ-Commit.

23.1

Code Fix

Use Case

Dataloader

Dataloader Pro was not copying over Contact fields when migrating data

23.1

Code Fix

Use Case

Dataloader

When updating the data using a CSV file, the update operation in Dataloader was failing with the error MISSING_ARGUMENT: ID is not specified

23.1

Code Fix

Use Case

Dataloader

The latest record was not being fetched in the single Dataloader

23.1

Code Fix

Use Case

nCino

Deployment History - search filter criteria was not working

23.1

Code Fix

Use Case

Dataloader

Problem loading ContentVersion object

23.1

Code Fix

Use Case

CI Jobs

Deployment stuck

23.1

Code Fix

Use Case

6 March 2024

(ARM v. 23.1.21)

ModuleSummaryVersionResolutionCause

ARM

Not fetching merges when trying to create a release label for Vlocity components.

23.1

Code Fix

Use Case

Deployments

Org Sync issue

23.1

Code Fix

Use Case

Admin

Unable to Log in to AutoRABIT via Okta

23.1

Code Fix

Use Case

Version Control

EZ-Merge - User Approval Setting is not working as expected

23.1

Code Fix

Use Case

Version Control

EZ-Commit Salesforce Org Authors not completed

23.1

Code Fix

Use Case

CI Jobs

Dashboards and reports were overwritten after the deployment to PROD

23.1

Code Fix

Use Case

Admin

Suggestion-SF org UI

23.1

Code Fix

Use Case

Reports

Suggestion to display a notification if a label has already been created for the same branch previously.

23.1

Code Fix

Use Case

Admin

Expose API for Super Admin Token Authentication to Test Registered Agents' Connections

23.1

Code Fix

Use Case

Version Control

Added metrics in ARM DB

23.1

Code Fix

Use Case

nCino

Post Deployment Org Details need to be displayed on CI Job Info pop-up

23.1

Code Fix

Use Case

nCino

CI Jobs Build Page - Pagination displayed as "undefined"

23.1

Code Fix

Use Case

nCino

nCino CI jobs - Date Literals Value not being populated

23.1

Code Fix

Use Case

nCino

When the Source Org is deleted, scheduled CI Job is not triggered from the queue

23.1

Code Fix

Use Case

nCino

[API Upgrade v59.0] Attachments Object Failed due to "Index 1 out of bounds for length 1" error

23.1

Code Fix

Use Case

Dataloader

Unable to migrate related EmailMessage records of Case

23.1

Code Fix

Use Case

CI Jobs

Unable to view API 59 version in CI configuration under API version dropdown.

23.1

Code Fix

Use Case

28 February 2024

(ARM v. 23.1.20)

ModuleSummaryResolutionCauseFeature Flag

Admin

Login Error

Code Fix

Use Case

Ci Jobs

CI Jobs build date sorting is not functioning as expected for non-Admin users

Code Fix

Use Case

ARM

SF CLI version upgrade to 2.28.6 for ARM 23.1 instances

Code Fix

Change Request

Version Control

Able to approve auto-rejected merge from email

Code Fix

Use Case

Version Control

PersonAccount AutoRABIT bug

Code Fix

Use Case

CI Jobs

It is not possible to run several CI Jobs in parallel when jobs are scheduled.

Code Fix

Use Case

SFDX

Error on create package version and install type of job.

Code Fix

Use Case

AR_33235_SKIP_UPDATE_PACKAGE_COMMAND

Dataloader

CPQ Dataload in Developer Sandbox - Errors

Code Fix

Use Case

nCino

nCino CI Job issue

Code Fix

Use Case

Dataloader

Invalid CSV file. Please check for blank columns.

Code Fix

Use Case

Dataloader

CSV file does not reset when you go back to the previous step in a single data loader

Code Fix

Use Case

Version Control

Getting Undefined Error for target branch in External Pull request

Code Fix

Use Case

Version Control

Unable to resolve conflicts in release label merge.

Code Fix

Use Case

Flow Center

Search & Substitute rules are not applied in the pipelines.

Code Fix

Use Case

21 February 2024

(ARM v. 23.1.19)

ModuleSummaryResolutionCause

VS Code extension Version Control

Cannot set up VS Code Extension

Code Fix

Use Case

Ci Jobs

CI Job and code coverage not running at correct times

Code Fix

Use Case

Version Control

EZ-Commit & EZ-Merge SCA validation issue

Code Fix

Use Case

All Modules

Support for Salesforce Spring ‘24 * Requires Documentation

Code Fix

Change Request

Version Control

Unable to commit the action overrides in service appointment object.

Code Fix

Use Case

Version Control

Quick Merge shows below pop-up

Code Fix

Use Case

Version Control

Unable to add the reviewer's name when using an external pull request

Code Fix

Use Case

Version Control

EZ-Merge Validation Failing: "Metadata package is empty"

Code Fix

Use Case

Admin

Branching baseline for main branch not bringing all components from production. * Feature Flag: METADATA_API_TO_DX_CONVERSION

Code Fix

Use Case

Version Control

Unable to commit a profile

Code Fix

Use Case

Version Control

Release label throwing InvalidFilterExpression error

Code Fix

Use Case

nCino

Error message when attempting to clone a feature template: ‘Request parameters are empty/null.'

Code Fix

Use Case

Dataloader

Dataloader Pro issue while triggering the job

Code Fix

Use Case

Version Control

Add additional metrics in ARM DB.

Code Fix

Use Case

nCino & Dataloader

nCino - Support for Salesforce Spring ‘24

Code Fix

Use Case