ARM Release Notes

ARM 25.2.9 Release Notes

Release Date: 15 June 2025

Overview

This release introduces support for Salesforce API 64 (Summer ‘24) and adds compatibility for new metadata types. Key improvements include bug fixes for CI Job execution, Profile Compare deployments, permission retrieval, and DX-based destructive changes in EZ-Merge.

Salesforce API 64 Support

Module: Metadata Compatibility

Added support for the following new metadata types:
- LightningTypeBundle (supported for Non-DX only)
- ExtlClntAppMobileSettings
- ExtlClntAppMobileConfigurablePolicies
- ExtlClntAppNotificationSettings
- ExtlClntAppPushSettings
- ExtlClntAppPushConfigurablePolicies
Also validated existing metadata types (e.g., Objects, Fields, Profiles, Permission Sets) with API 64, and confirmed that they work as expected.

Issue: Newly created CI Jobs were not getting triggered upon pull request creation in a specific branch. CI jobs for other branches in the same repository were functioning correctly.

Fix: The logic was updated to properly retrieve the base branch name when fetching credentials from the database. This now ensures the correct CI job is triggered for all branches.

Module: CI Jobs

Issue: When updating object permissions using the Profile Compare feature, the changes appeared to reflect correctly in the UI but were not applied during deployment. The mismatch was due to inconsistent node names in the backend.

Fix: Standardized object permission node names across the UI and backend to align with Salesforce's profile XML structure, ensuring accurate deployment of user selections.

Module: Profile Compare

Issue: Profiles with special characters in their names were not being retrieved properly. This was due to URL decoding and formatting that altered the original profile name, preventing matching and retrieval.

Fix: Removed unnecessary decoding and now presents the profile name in the exact format received from Salesforce, ensuring such profiles are correctly processed.

Module: Admin → Salesforce Settings → Profiles and Permissions

Internal Enhancement

Issue: Destructive changes related to static resources were not working properly for DX-format deployments in EZ-Merge.

Fix: Destructive change logic for static resource metadata was implemented for DX format, making it consistent with non-DX behavior and ensuring successful validation and deployment.

Module: EZ-Merge

ARM 25.2.8 Release Notes

Release Date: 8 June 2025

Overview

This release brings critical improvements and feature enhancements across multiple modules, including Environment Provisioning, CI Jobs, Admin, EZ-Merge, and Metadata handling. The updates aim to improve system flexibility, performance, and metadata deployment consistency.

Bug Fixes and Improvements

1. Fix / Improvement

Issue: In Environment Provisioning, the Remote Site Settings template was failing to update the URL in the destination org when the user applied alphabetical sorting. This caused deployment inconsistencies.

Fix: Now, the template can update remote site settings correctly regardless of alphabetical sorting. Sorting by Remote Site Name or Remote Site URL no longer blocks the update process. Validation has been completed in the integration branch.

Module: Environment Provisioning

2. Fix / Improvement

Issue: Customers could not edit SSO domain changes directly from the platform, leading to manual intervention.

Fix: Users can now update their SSO domain name via the SSO Configuration page. Once the domain name is changed, an automated email informing all users of the update is triggered.

Module: Admin → My Account → SSO Configuration

3. Fix / Improvement

Issue: While attempting to delete static resources and their .meta files through EZ-Merge, no destructive changes package was being generated, even when the "Run Destructive Changes" checkbox was selected. This caused validation failure during merge.

Fix: Destructive logic has been implemented in EZ-Merge for both DX and non-DX formats, ensuring static resource deletions are correctly handled and packaged.

Module: EZ-Merge

4. Fix / Improvement

Issue: CI Job deployments were failing with a 504 Gateway Timeout error, blocking staging environment activities and causing delays in deployment pipelines.

Fix: Optimized the CI Job execution logic by improving how API timeouts are handled. This ensures better performance and avoids timeout-related failures during large or slow deployments.

Module: CI Jobs

5. Fix / Improvement

Issue: While running test classes in the Admin section, unrelated Apex test classes were being auto-populated.

Fix: The auto-population logic was revised to ensure only relevant Apex classes are retrieved and saved. Unrelated classes are now excluded from test jobs.

Module: Admin → My SF Org Management

6. Fix / Improvement

Issue: During CI Job deployments involving Search and Substitute rules, changes were not being applied to the destination org, even though the deployment was marked successful.

Fix: Provided Fix and also Extended support to apply substitution logic to the following metadata types: AutoResponseRule, CustomLabel, CustomMetadata, CustomObject, CustomSite, Dashboard, DashboardFolderShare, Network, NamedCredential, PermissionSet, Portal, Queue, RemoteSiteSetting, Report, ReportFolderShare, SamlSsoConfig, SharingCriteriaRule, SharingOwnerRule, and Workflow.

Module: Search and Substitute

7. Fix / Improvement

Issue: When performing a destructive change (e.g., deleting a ProfileSearchLayout) and deploying via Single Revision, the system failed to identify the change correctly, expecting the metadata to be present instead.

Fix: The Retrieve Metadata screen now correctly classifies added/modified ProfileSearchLayout changes under "ALL ITEMS" and does not falsely tag them as missing. For Non-DX Deployments and CI Jobs, ProfileSearchLayout changes now appear as constructive updates and deploy successfully.

Behavior Limitation: If a Custom Object contains only a single ProfileSearchLayout node and that node is deleted, the change will not be picked up during deployment, as ProfileSearchLayout is not a standalone metadata type.

Module: Deployment / CI Jobs

Release Notes 25.2.7

Release date: 1 June 2025

Overview

This release improves metadata handling and deployment type consistency and enhances support for Vlocity and Permission Set delta deployments. Several critical fixes have been addressed across the Deployment, CI Jobs, and EZ-Commit modules to improve reliability and reduce deployment anomalies.

Bug Fixes and Improvements

Fix/Improvement 1

Issue: When deploying a new profile search layout for the Case object, the deployment unintentionally removed all other existing profile search layouts in the org, causing a loss of metadata settings for other profiles.
Fix: The logic in the deployment backend (CustomObjectController.java) has been refactored. It now compares layout differences in an additive manner, ensuring that new layouts are added without deleting existing ones.
Impacted Module: Deployment

Fix/Improvement 2

Issue: The “Enable Delta on Permission Sets” checkbox is designed to ensure only changed permissions are committed or deployed. While it did not work correctly for CI Jobs, object permissions were still getting removed even when the checkbox was enabled.
Fix: The delta behavior is now standardized across both CI Jobs and Deployments. A back-end code fix ensures that object permissions are preserved in deployments sourced from version control (SCM) and delta logic is honored properly.
Impacted Modules: CI Jobs, Deployment

Fix/Improvement 3

Issue: During Vlocity SF Org-to-Org deployments, YAML files failed to handle Calculation Matrix fields with comma-separated values that included spaces. This broke deployments and made the downloaded DataPacks unusable.
Fix: The YAML generation process was enhanced to support such field values. Now, comma-separated Calculation Matrix components are parsed and deployed correctly to the target org. YAML downloads are also displayed properly.
Note: This fix currently applies only to Org-to-Org Vlocity deployments. Support for Vlocity deployments via Version Control is under R&D.
Impacted Module: Deployment (Vlocity SF Org-to-Org)

Fix/Improvement 4

Issue: While configuring ScheduleApexClassesMonthly templates in the Environment Provisioning module, all default user fields were incorrectly set to Analytics Cloud Integration User, regardless of what the template intended.
Fix: The back-end logic for template value assignment was fixed. It now correctly pulls in the actual default values specified in the template configuration.
Impacted Module: Environment Provisioning

Fix/Improvement 5

Issue: A customer was performing a merge using a commit that contained only destructive changes. Even though the "Destructive Changes" checkbox was enabled, the merge failed during the Validate Deploy stage.
Fix: Salesforce expects both a postdestructivechanges.xml and an empty package.xml file for validation to pass. The fix ensures that an empty package.xml file is now automatically added to the package folder, along with destructive changes, making the validation step successful.
Impacted Module: EZ-Merge with Validate Deploy

Fix/Improvement 6

Issue: While using a previously validated commit label to perform a new EZ-Commit, customers were unable to see the RecordType component under the “All Metadata Components” tab.
Fix: The component filtering logic was corrected to ensure that RecordType and similar metadata types are displayed when using commit templates, improving usability and completeness of the commit UI.
Impacted Module: EZ-Commit

Release Notes 25.2.6

Release Date: 25 May 2025

Overview

This release focuses on stability, reliability, and enhanced usability across core modules like CI Jobs, EZ-Commit, and Release Management. Key improvements address long-standing issues such as CI job queue blocks, premature status transitions during aborts, metadata filtering inconsistencies, and usability fixes in user management.

We’ve also added support for Provar v25.2.1, improved error handling and logging, and ensured a smoother experience for EZ-Commit users leveraging custom metadata and commit labels.

Bug Fixes and Improvements

1. Release label Abort Stuck Status

Issue: When a user aborts a release label, the system prematurely sets the release status to "Failed" while the abort request to the agent is still pending. If the abort request isn’t successfully sent, the status gets stuck, causing confusion in monitoring and troubleshooting.

Fix: The system now updates the release status to “Failed” only after the agent successfully triggers and acknowledges the abort request. Extra logging has been added to help trace abort scenarios and ensure proper state transitions.

Impacted Module: Release label Management

2. EZ-Commit Metadata Filter with Reused Labels

Issue: When performing an EZ-Commit using the SCA > CodeScan option and enabling “Only newly added supported metadata types,” the commit wasn’t functioning properly if the user reused a previously used commit label.

Fix: Metadata filtering logic has been updated to support commit label reuse, ensuring seamless functionality with Auto Draft.

Impacted Module: EZ-Commit

3. CI Jobs Stuck in Queue

Issue: Some CI jobs were getting stuck in the queue due to:

Unhandled exceptions
Git commit failures where no revision was generated

Fixes:

Prevented downstream processes when Git fails to generate a revision
Improved handling for null messages and unexpected errors
Added enhanced logging to support better troubleshooting

Impacted Module: CI Jobs

4. Admin User Creation Validation

Issue: Fields like Phone Number, Zip Code, and State were mandatory during user creation, restricting onboarding in certain cases.

Fix: These fields are now optional in the Admin module, streamlining user creation.

Impacted Module: Admin (User Management)

5. Fieldset Translation Removal During Commit

Issue: When committing CustomField and CustomObjectTranslations, valid Fieldset translation nodes were unintentionally removed.

Fix: Translation node handling has been refined to preserve valid entries and prevent data loss in multilingual configurations.

Impacted Module: EZ-Commit

6. Credential-Based CI Job Failures

Issue: CI Jobs were failing inconsistently when using existing credentials, with causes difficult to trace.

Fix: Improved logging at credential validation points to isolate issues and aid future debugging.

Impacted Module: CI Jobs

7. Provar v25.2.1 Compatibility Support

Request: Compatibility needed for Provar version 25.2.1 to support automated test execution.

Update: Provar v25.2.1 is now supported and available on demand for integration with ARM workflows.

8. Branch Name Case Sensitivity in Release Labels

Issue: Sub-users could not view their own release labels due to a mismatch in branch name casing logic.

Fix: The filtering logic now respects case sensitivity, ensuring correct visibility of release labels.

Impacted Module: Release Label Management

Release Notes 25.2.5

Release Date: 18 May 2025 Overview

This release includes key bug fixes and improvements focused on enhancing CI Job stability, deployment reliability, and metadata diff accuracy. It addresses critical issues encountered in Salesforce-to-Salesforce deployments, destructive change logic, permission set handling, and package creation workflows. Additionally, customer-requested upgrades such as Provar support enhancements have been implemented.

Bug Fixes and Improvements

1. CI Job: Destructive Changes Handling

Issue: The “Prepare Destructive Changes” option was not selected during initial CI Job creation but was unexpectedly selected during re-runs.

Impacted Modules:

Deploy a package from Salesforce to Salesforce
Deploy a package from Salesforce to Salesforce and back up to Version Control

Fix: Resolved inconsistencies in destructive change logic. The system now retains the correct state of the “Prepare Destructive Changes” flag across CI Job executions.

2. Permission Set FLS Diff Missing

Issue: When attempting to commit FLS changes for a new field within a permission set, the changes were not captured in the diff report, resulting in missing commits.

Fix: Enhanced logic to correctly capture FLS changes by appending Task and Event objects for the Activity object when the Global Permissions option is selected in EZ-Commit.

3. Deployment Abort Functionality

Issue: When performing a Single Revision Deployment, even after aborting it (a confirmation popup showing a successful cancellation), the deployment continued and was marked as successful.

Fix: Fixed the abort logic within the deployment module to correctly halt execution and reflect the accurate status post-abortion.

4. Unlocked Managed Package CI Job Failure

Issue: Customer experienced failures when triggering a CI Job to create and install an unlocked managed package from a version control branch.

Fix: Improved JSON handling during CI Job execution, ensuring compatibility with both internal and customer-specific JSON structures. Now, even in case of exceptions during package creation, the system attempts fallback version creation instead of complete failure, similar to the existing SFDX module behavior.

5. Provar Upgrade Request

Request: Customer requested support for Provar v25.2.1

Update: Support for Provar version 25.2.1 has been added to ensure compatibility with automated test execution workflows. This version will be available on a demand basis.

Release Notes 25.2.4

Release Date: 11 May 2025

Overview

This release introduces feature enhancements and key bug fixes to improve deployment flexibility, metadata handling, CI job stability, and user experience. The update includes enhanced error handling for CI and Apex jobs, metadata recognition updates, and refined UI behavior in merge and licensing workflows.

Bug Fixes & Improvements

CI Job Includes Unsupported Metadata Despite Exclusion Configuration A customer reported that certain metadata types (CallCenterRoutingMap, CallCtrAgentFavTrfrDest) were deployed despite being explicitly excluded in the deployment configuration.

Upon investigation, the data related to CallCenterRoutingMap was retrieved and verified successfully. However, data for CallCtrAgentFavTrfrDest could not be validated.

These metadata types are associated with Salesforce Service Voice features, which require full integration with a compatible telephone system. Currently, such an integration is unavailable in our environment, limiting our ability to validate the issue fully.

Fix: Few metadata types are officially supported and recognized correctly in deployments.
Impacted Module: CI Jobs

Repository URL Migration A customer-requested repository URL migration has been completed.

Fix: Migration was successful, and no further issues were reported.
Impacted Module: Repo Management

Profile Comparison Error: “Salesforce Org Doesn’t Exist” An error occurred when comparing profiles across 2 or 3 environments.

Fix: UI logic for diff loading has been refined to handle multi-org comparisons.
Impacted Module: Metadata Comparison

CI Job Fails When All Standard Value Sets Are Excluded CI Jobs failed to run if standard value sets were excluded from selection.

Fix: Job logic updated to handle scenarios where standard value sets are excluded.
Impacted Module: CI Jobs

Failure in Scheduled Apex Test Runs for Production Orgs Daily scheduled Apex test executions failed due to an issue handling multiple concurrent jobs.

Fix: Logic in ApexTestClassesSchedulerJob refined to support multiple scheduled jobs.
Impacted Module: Apex Test Scheduling

Text Change in Merge Screen UI The label was changed from “Skip all three prevalidation criteria” to “Skip all prevalidation criteria” for better clarity.

Impacted Module: Merge UI

Known Issues

License Upload Not Visible for Expired On-Premise Servers When the license expired, the option to upload a new key was not visible before login.

Fix: The pop-up visibility issue was resolved; users can now upload the license before logging in.
Impacted Module: Licensing (On-Prem)
Issue Type: UI Bug

Release Notes 25.2.3

Release Date: 4 May 2025

Overview

This release of AutoRABIT ARM introduces key bug fixes and stability improvements to deployment label handling, CI job webhook executions, and user management across regions. Notably, a critical internal issue affecting metadata filtering during full deployments has been addressed. Additionally, issues related to saving users for countries without state-level details and CI job webhook failures have been resolved.

Bug Fixes and Improvements

Issue with Full Deployment - Previous Deployment Label Type

A defect was identified when performing a full deployment using the “Previous Deployment Label” type, which inadvertently included all metadata members from the source organization, rather than only those associated with the selected label.

Fix: Updated deployment logic now ensures that only metadata within the selected label is included in the deployment. Impacted Modules: Deployments

Webhook Execution Failures in CI Jobs

Webhooks were not being executed during CI job runs due to limitations in DynamoDB.

Fix: Webhook invocation logic has been revamped to ensure reliable webhook execution in CI pipelines. Impacted Modules: CI Jobs

User Creation Failure – Countries Without States

An issue was reported where creating or editing users with countries that do not have states (e.g., Singapore, American Samoa, Andorra) failed to save the user details.

Fix: Validation logic has been updated to treat the state field as optional for applicable countries, ensuring successful user creation. Impacted Modules: User Management

Release Notes 25.2.2

Release Date: 27 April 2025

Overview

This release introduces significant enhancements to AutoRABIT’s ARM platform, focusing on enhanced metadata support, improved deployment accuracy, and optimized performance across CI workflows. Previously unsupported metadata types are now fully recognized in DX-based branching and deployment. Issues with redundant code coverage reports and performance bottlenecks in ALM item loading have been resolved. Significant improvements also include full profile permission coverage in EZ-Commit and enhanced metadata exclusion logic.

Bug Fixes and Improvements

Support for New Metadata Types in DX Repo CI Deployments Previously unsupported metadata types are now included in deployments created through DX repo-based branching. These include: ApplicationSubtypeDefinition, BusinessProcessTypeDefinition, ConvIntelligenceSignalRule, ExplainabilityActionDefinition, ExpressionSetDefinitionVersion, ForecastingGroup, and PathAssistant. Impacted Modules: CI Jobs (DX Branching & Deployments)

Code Coverage Report Duplication Fixed Resolved an issue where multiple code coverage reports were generated for the same sandbox. The back-end logic has been updated to ensure that only one report is created per sandbox. Impacted Modules: Code Coverage Reports

Improved ALM Item Load Time in Commit/Merge Modules Addressed severe performance lag when loading Azure ALM items after sprint selection. Switched to batch API calls for fetching work item data and states, reducing calls from thousands to single digits. Load time dropped from ~6 minutes to ~4 seconds for large sprints. Impacted Modules: Commit/Merge (ALM Integration with Azure)

Full Profile Commit – Object Permissions & Tab Visibility Fixes Fixed missing object permissions (Documents, Push Topics) and tab visibilities (Reports, Dashboards) in full profile commits during EZ-Commit. The package.xml generation logic now correctly includes all necessary metadata members. Impacted Modules: EZ-Commit, Profiles

Metadata Exclusion Logic Improved – ExpressionSetDefinitionVersion Corrected behavior in which ExpressionSetDefinitionVersion metadata was included in deployments, even when excluded. This enhancement enables precise control over metadata exclusions, particularly for workflows that require separate deployment flows (e.g., OmniStudio jobs). Impacted Modules: CI Jobs, Deployment

nCino + Data Loader Release Notes 25.1.4

Release Date: 27 April 2025

Refer to the latest release notes published for nCino + Data Loader at .

ARM Release Notes 25.2.1

Release Date: 20 April 2025

Overview

This release brings meaningful enhancements that improve reliability, accuracy, and visibility across ARM workflows. Backup CI jobs now consistently capture StandardValueSet changes, ensuring more complete metadata tracking. Improved metadata classification prevents deployment errors, while CustomObjectTranslation handling in EZ-Commit for DX repos is now more precise. Custom settings deploy smoothly through Environment Provisioning, reducing manual effort. File comparisons are clearer with restored full diff visibility, aiding better change reviews. Updates to Search and Substitute and managed package exclusions streamline CI deployments. Audit trails now display correct timestamps, enhancing reporting accuracy.

Bug Fixes and Improvements

StandardValueSet Metadata in Backup Jobs Backup CI jobs now correctly detect and retrieve changes made to StandardValueSet metadata. Previously, these changes were not captured automatically, although manual commits through EZ-Commit functioned as expected. This enhancement ensures StandardValueSet changes are included in automated daily backups. Impacted Modules: CI Jobs backup to VC. Support Case: #132829

Metadata Type Detection for Custom Metadata Labels Improved handling of custom metadata with labels starting with "profile" or "permissionset" by validating based on their file paths instead of label names. The system now checks for profiles/ and permissionset/ in metadata paths to accurately categorize them during commit, merge CI jobs, and deployments. This resolves previous misclassification issues. Impacted Modules: All Modules.

CustomObjectTranslation Handling in DX Repositories Improved the EZ-Commit process to correctly handle CustomObjectTranslation metadata in DX repositories. Previously, some nodes were unintentionally removed, and unrelated changes like validation rules appeared in the compare changes section. The commit process now includes only selected components, matching the behavior of non-DX repositories. Impacted Modules: EZ-Commit while selecting 'customobjecttranslation' [DX/NonDX].

Custom Settings Deployment in Environment Provisioning Resolved an issue where custom settings were not being deployed through the Environment Provisioning module. Although no errors were shown on the history page, specified changes were not applied. This enhancement ensures that custom settings are now correctly deployed as part of the provisioning process. Impacted Modules: Env Pro -> migrate custom settings.

File Difference Display in Comparison Dialog Fixed an issue where the comparison dialog box did not consistently display full file differences for all metadata types. Previously, the UI showed only a limited number of lines without offering a "Load More" option, while the downloaded file revealed additional differences. The "Load More" functionality has been restored, now loading up to 200 lines per click to ensure complete visibility of metadata changes. Impacted Modules: Compare Metadata in Deployment Module.

Search and Substitute for Workflow Alerts in CI Jobs Resolved an issue where applying Search and Substitute rules on Workflow Alerts in SFDX repositories caused CI jobs to fail. The error was due to a logic fault, which has now been corrected. Common code has been refactored and moved to the pipeline to ensure consistent execution across jobs. Impacted Modules: CI Jobs, Deployment, and Pre-Validation Commit.

Exclusion of Managed Components in SFDX CI Job Deployments Fixed an issue where managed components were not properly excluded during SFDX CI job deployments, despite selecting "Ignore installed packages" and configuring exclusions under the Skip Members section. The deployment logic has been corrected to ensure managed components are now accurately excluded as intended. Impacted Modules: Deployments & CI Jobs.

Date and Time Accuracy in Audit Trails Corrected the logic used for date and time conversion in the UI of the Reports Audit Trail. Previously, the created and modified dates were displayed inaccurately. This enhancement ensures that audit timestamps now reflect the correct values. Impacted Modules: Audit Report.

ARM Release Notes 25.1.4

Release Date: 17 April 2025

Overview

This release focuses on streamlining the deployment process and improving reliability across the platform. OmniStudio deployments now handle dependencies more intelligently with Max Depth -1, ensuring a smoother experience from retrieval to deployment. Conflict resolution has been made more precise, avoiding issues like content bleed between files, and users can now seamlessly retry failed merges without losing progress. Improvements to Org Sync and Admin settings make it easier to spot differences and manage roles in real time, while enhancements to file comparison and commit labeling bring greater clarity and control to the deployment workflow.

Bug Fixes and Improvements

Max Depth -1 Support for OmniStudio Deployment Deployments using Max Depth -1 now correctly retrieve and include all dependent components such as IntegrationProcedure, DataRaptor, Document, and VlocityUiTemplate. The retrieved dependencies are now properly reflected in the UI and included in the deployment to the target org. Impacted Modules: Deployment (org → org).
Improved Conflict Resolution Accuracy Resolved an issue where content from previously resolved files was being incorrectly appended to other files during conflict resolution. This fix ensures each conflicted file is processed independently, preventing errors such as duplicate labels during deployment. Impacted Modules: EZ-Merge → Conflicts.
Retry Commit for EZ-Merge After Failure The "Retry Commit" option is now available when a merge fails due to incorrect or unmapped credentials. The system correctly updates the merge status to "CommitPending," enabling users to retry the commit. This fix applies to new merges created after this release. Impacted Modules: EZ-Merge, Dry run merge.
Enhancement: Accurate Filtering in Org Sync The 'Exists in Source Only' filter in Org Sync now accurately reflects the actual number of differing metadata groups. With this fix, both the group count and displayed results are consistent and reliable. Impacted Modules: Org Sync.
Immediate Visibility of 'Skip Org Mapping' Option The 'Skip Org Mapping' permission is now immediately visible in the Roles tab after enabling 'Skip Mappings' on a user’s profile. Previously, a page refresh was required for the option to appear. This enhancement ensures the setting is saved and reflected instantly without additional user actions. Impacted Modules: Admin.
Whitespace Differences in File Diff View The File Diff tab now displays whitespace-only changes when comparing Apex Class files. Previously undetected space differences are now identified and shown, ensuring accurate comparison between source and destination files. Impacted Modules: Org Sync and Deployments.
Vlocity Commit Label Filtering Commit labels associated with Vlocity metadata can now be filtered correctly using the commit label name in the merge screen. Previously created labels without commit type are also supported following a back-end migration fix. Impacted Modules: VC → Change labels → Commit labels.
Support for Initial Commit in Revision Range Deployment Salesforce metadata changes from the initial commit are now included in the retrieve metadata screen when selected as the "From Revision" in a revision range deployment. This ensures changes from both the initial and target revisions are accurately reflected and deployed. Impacted Modules: Custom Deployments - Revision range, single revision.

ARM Release Notes 25.1.3

Release Date: 06 April 2025 This release introduces significant new capabilities and key enhancements across the ARM platform. A major new feature enables multi-level deployment approvals by Org, offering structured release governance with customizable approval groups. Architecture improvements include enhanced global workspace management to handle deleted or missing branches more gracefully. The release also strengthens security with encrypted installation key handling. Core functionality has been optimized, including improved commit revision sorting and faster loading of standard value sets.

1. New Feature

Multi-Level Deployment Approval by Org A two-level deployment approval process has been introduced to provide better control over releases. Each approval level supports group-based approval, allowing any member within the group to approve the deployment. Email notifications are sent to approvers with a link to ARM for approval actions. This approval process can be configured based on Org name. Admins can select applicable orgs and assign separate approvers or approver groups for each. Note: Approval Process support is now limited to Direct Custom Deployment only. It is not supported via Org Sync or Profile Management.

2. Feature Enhancements

Secure Handling of Installation Key in Unlocked Packages CI Job The installation key used in the Unlocked Packages CI Job is now masked and encrypted for improved security. Additionally, a view/hide eye icon has been introduced to toggle the visibility of the installation key.
Clear Status Indicators for Merge Pre-validation Outcomes The "Merge Prevalidation Process" logs now provide clearer visual indicators based on the outcome of the validation. A green checkmark ( ✓) is shown only when the process completes successfully, while a red X clearly indicates when the pre-validation has failed or resulted in auto-rejection. This improvement ensures better visibility into validation outcomes for both merge and commit workflows.

3. Architecture Improvements

3-Tier Architecture for ARM – Separate and Load the UI and Backend Services Individually The ARM UI can now be compiled and run independently from the backend. Based on configurable endpoints, the UI communicates with any designated backend server, defaulting to localhost. All UI components load locally, and API calls are routed according to the configured backend endpoint.
Resilience in Global Workspace Management for Optimized Workspaces A backend fix has been implemented to ensure stability in global workspace creation when the default branch is missing or deleted in the repository. When the default branch no longer exists in AutoRABIT or the remote repository, the system will now automatically update the global workspace and repository configuration to use the last valid branch. This prevents version control operations—such as commit, merge, or revision listing—from being blocked due to a broken global workspace.
A UI enhancement to allow users to change the default branch directly in the VC Repos module will be introduced in an upcoming release to fully resolve the issue.

4. Bug Fixes and Improvements

Reliable CI Job Queue Handling Resolved an issue where CI jobs were stuck in the queue due to mismatched build numbers between CIJobInfo and CIJobHistory tables. The system now handles these cases correctly, ensuring jobs progress without blocking subsequent builds. Impacted Modules: CI Job abort and Queue flows, Release Label abort and Queue flows.
CustomNotificationType Support in Destructive Commits Destructive commits now support the CustomNotificationType metadata. Impacted Modules: Commits, Merges, Release Label Artifact execution, CI Jobs, Deployments while performing the Custom Notifications type destructive changes flow.
Package Key Handling in Deployment Module Resolved an issue where deployments failed due to a null package key during package version installation. The key preparation logic for dependent packages has been corrected, and a migration has been implemented to fix existing invalid keys. Impacted Modules: Unlocked packages, Deployments.
LWC API Check Support in CodeScan Analysis Files with .js-meta.xml suffixes are now included in the CodeScan analysis, enabling proper API checks on Lightning Web Components (LWC) from ARM. This ensures more accurate validation during the scan process. Impacted Modules: ARM CodeScan integration.
Accurate File Name Display in Review Artifact The Review Artifact UI now correctly updates the file name when switching files, ensuring clarity while reviewing changes. Impacted Modules: EZ Commit -> Review-Artifact -> Edit In IDE -> File Names in editor view.
Commit Revisions Sorted by Committed Timestamp Commit revisions in the Commit module are now displayed based on the committed timestamp, aligning with GitHub's behavior. Previously, revisions were shown using the author timestamp, causing confusion. The backend logic has been updated to ensure commits are sorted and displayed consistently. Impacted Modules: New Deployment, New CI Jobs, New Merge, VC Repositories, Release Labels.
Support for Special Characters and Extended Name Lengths in User Profiles User profile fields now support special characters in first and last names. Additionally, the character limits have been extended—first names now allow 3 to 40 characters, and last names allow 1 to 80 characters. Impacted Modules: Admin, My Profile.
Support for Priority 4 Rules in Apex PMD Static Code Analysis Static Code Analysis now includes Priority 4 rule violations in Apex PMD reports. The minimum PMD priority has been updated from Medium (3) to Low (5), allowing visibility into lower-priority issues without affecting CI Job validations configured to fail only on higher priority errors. Impacted Modules: All static code analysis running with Apex PMD.
Optimized Loading of Standard Value Sets in Commit Improved performance and visibility of Standard Value Sets in the EZ-Commit module by minimizing repeated Salesforce API calls. The system now retrieves enabled services during org registration and stores the cloud org type in the database. For existing orgs, the cloud type is updated during retrieval and used for subsequent requests, significantly reducing load times and ensuring correct metadata visibility—especially for Financial Services Cloud orgs. Impacted Modules: EZ-Commit, Commit Templates, Branching Baseline, Deployments, CI Jobs.
Provar Plugin Name Edit Handling Editing the Provar name in the Admin module no longer triggers an invalid notification pop-up when a key file is already uploaded. A response check ensures smoother and more accurate user feedback. Impacted Modules: My Account plugins (Provar).

nCino + Data Loader 25.1.3 Release Notes

Release Date: 6 April 2025

See the for nCino + Data Loader improvements.

ARM Release Notes 25.1.2

Release Date: 09 March 2025

This release introduces Checkmarx One Integration, enabling users to perform security scans within ARM using Checkmarx One alongside existing Static Code Analysis tools.

Additionally, we have addressed multiple bug fixes and enhancements, including improved support for PLATFORMEVENTCHANNELMEMBER in destructive commits, enhanced merge conflict detection for layouts, and more reliable duplicate resolution for profiles. Security and stability improvements include fully hiding API tokens after creation, ensuring correct project mapping for CodeScan in CI jobs, and providing consistent permission set deployments in Commit Label deployments.

New Feature

Checkmarx One Integration
Users can now integrate Checkmarx One as a Static Code Analysis tool within ARM. This allows security scans to be performed using Checkmarx One alongside other existing tools, providing a scalable and fully managed security solution for cloud-native and DevOps teams.

Bug Fixes and Improvements

Improved Support for PLATFORMEVENTCHANNELMEMBER in Destructive Commits
ARM supports the destructive commit of PLATFORMEVENTCHANNELMEMBER metadata, ensuring seamless deletion and replacement of platform events without file diff errors. Impacted Modules: Destructive changes, VC, Deployments, CI Jobs.
Enhanced Merge Conflict Detection for Layouts
ARM reliably detects merge conflicts for layout metadata, including files with special characters in their names, ensuring a smoother and more accurate merge process. Impacted Module: EZ-Merge.
Improved Duplicate Resolution for Profiles
ARM ensures stable conflict resolution for profiles by preventing errors caused by commented code on a new line. Users can click on files in the resolve duplicate screen without encountering IndexOutOfBounds exceptions. Impacted Module: EZ-Merge duplicates resolution scenario.
Improved Security for API Tokens
API tokens are now fully hidden after their initial creation and display, ensuring they are no longer exposed in network requests. This enhances security by preventing unauthorized access through browser developer tools. Impacted Module: API Token creation.
Correct Project Mapping for CodeScan in CI Jobs
ARM ensures that CodeScan projects are correctly linked to the scanned Salesforce org in CI jobs. The mapping issue causing a null project name has been resolved, ensuring accurate project creation and association. Impacted Module: CI Job Build Logs.
Improved Commit Label Deployment for Permission Sets
ARM ensures consistent and accurate deployment of permission sets during Commit Label deployments. The Ignore Missing Visibility setting behaves as expected, and redeployments correctly generate a new deployment package instead of reusing the initial one. Impacted Module: Commit Label.

nCino + Data Loader Improvements

Release Date: 9 March 2025

See the for nCino + Data Loader improvements.

ARM Release Notes 25.1.0

Release Date: 23 February 2025

The ARM Release 25.1.0 introduces key upgrades, new features, and critical fixes to enhance security, compatibility, and overall performance. This release includes updates to third-party libraries, improved error handling, and several bug fixes to ensure a seamless user experience.

Upgrades and Enhancements

Third-Party Library Updates: OpenJDK, Tomcat, Salesforce CLI, Sonar Scanner, and Local DynamoDB have been updated to their latest versions for improved performance, security, and compatibility.
Salesforce API Version 63.0 Support: ARM now fully supports Salesforce API version 63.0, ensuring compatibility with the latest Salesforce features and functionalities.

Deprecated Features

Picklist to ValueSet Migration: The Picklist feature in the VC Repo section is now deprecated, as Salesforce has discontinued support for it starting from API version 39.

Bug Fixes and Improvements

Clearer Error Messages: Improved UI messages provide more precise and actionable feedback, making troubleshooting easier.
Tag Deployment Fix: Previously, deploying a tag would always result in the same changes, even when those changes were not present in the specified tag or branch. Tags now deploy the correct updates as expected. Impacted Modules: Custom Deployments.
Flow Access & LoginFlows Retrieval: Users can now retrieve and compare Flow Access and LoginFlows seamlessly. Previously, LoginFlows were not visible during change comparisons. Impacted Modules: EZ-Commit with validate deploy, Merge with validate deploy , Profile duplicates.
EZ-Merge Report Accuracy: The EZ-Merge report CSV now includes missing details, such as dates and L1/L2 review statuses, improving tracking and transparency. Impacted Modules: Weekly Report, EZ-Merge report.
CI Job Stability: Resolved issues causing CI job failures and deployment errors for AccelQ tests. Test results now display the correct status and test counts in the Test Summary Report. Impacted Modules: AccelQ CI Jobs.
Deployment Rules Visibility: Deployment rules are now consistently displayed in the Deployment Submit popup window across all deployment types. Impacted Modules: Custom Deployments.
Lightning Email Templates Retrieval: Fixed an issue where Lightning Email Templates were not retrievable across multiple ARM modules, including EZ-Commit, EZ-Merge, Release Label Artifact Preparation, Org-to-Org Deployment, Org Sync, Auto-draft, Commit Template, and Branching Baseline. Impacted Modules: EZ-Commit.
Review Artifact Enhancement: The "Review Artifact" option now correctly displays the package.xml and its corresponding data for commits, deployments, and merges. Additionally, SearchCustomization now functions as expected for both SFDX and non-DX environments, supporting merging, CI jobs, and deployments. Impacted Modules: EZ-Commit, Merge.
SFDX Package Naming Support: Special characters such as @ and . can now be used in SFDX package version names, resolving previous naming limitations. Impacted Modules: SFDX, Unlocked Packages.

Upgrades and Enhancements

Third-Party Library Updates: OpenJDK, Tomcat, Salesforce CLI, Sonar Scanner, and Local DynamoDB have been updated to their latest versions for improved performance, security, and compatibility.
Linux Upgrade: The underlying Linux environment has been upgraded, strengthening security and optimizing system performance.

nCino Improvements

Release Date 23 February 2025

See the for nCino + Data Loader improvements.

ARM Release Notes 24.4.5

Release Date: 19 January 2025

With this release, we have implemented the following enhancements and support fixes to improve features and functionality and streamline the user experience.

Security Improvements

Email and Username Validation

Registration processes now enforce unique email addresses and usernames, ensuring each email is linked to only one active account. Added email verification confirms ownership, enhancing security and preventing duplication. Impacted Modules: Admin - User Registration, Subscription Management.

Enhanced XSS Protection

Implemented robust measures to prevent XSS risks, including validation of untrusted data, HTML sanitization, and Content Security Policy (CSP). These updates safeguard data and prevent script-based attacks. Impacted Modules: All Modules.

Support

Improved Remote Site Settings Updates

URL updates now run seamlessly in the destination org. A new mechanism ensures tests proceed smoothly, even if individual cases fail. Impacted Modules: Environment Provisioning.

Consistent Merge Validation

The merge validation process now handles internal folder references accurately. Files in helper folders are fully validated, ensuring consistent results across merges and deployments. Impacted Modules: EZ-Merge with validate deployment.

SharingRules Metadata Visibility

SharingRules metadata is now visible and selectable for deployment and commit operations. Child metadata exclusions were adjusted to ensure proper visibility. Impacted Modules: All Modules.

Support for GenAiPromptTemplate

ARM now supports the GenAiPromptTemplate component, ensuring compatibility with Salesforce updates and enhancing functionality. Impacted Modules: VC, Deployment, CI Jobs.

Aligned Branching Baseline Behavior

Branching Baseline now matches EZ-commit behavior for Default manageable state metadata. Excluded Default metadata, such as Account.object-meta.xml, is no longer committed. Impacted Modules: Branching Baseline.

Faster CI Job Assignment

Agent assignment during CI jobs has been optimized, and a new feature flag allows streamlined verification using repository and username data, reducing delays. Impacted Modules: CI Jobs using Version Control.

Reliable Backup CI Jobs

Backup CI jobs now handle DX metadata exclusions and dashboard queries correctly, ensuring successful scheduled backups. Impacted Modules: CI Jobs, Deployments, EZ-Commits.

Merge Validation for Short Metadata Names

Merge validation now properly handles metadata names shorter than 9 characters. Improved logic ensures accurate validations without failures. Impacted Modules: EZ-Merge, EZ-Commit with validate deployment.

Commit Label Preservation

Commit labels are now retained even when associated pre-validation labels are removed, ensuring labels remain accessible and visible. Impacted Modules: EZ-Commit, Commit Label EZ-Merge, Commit Label Deployment.

Issue Resolution

Optimized Merge File Processing

The VALIDATINGSALESFORCEXML performs a single file check during branch-to-branch merges. Merged file data is stored uniquely, improving performance by preventing duplicate validations. Impacted Modules: EZ-Merge.

ARM Release Notes 24.4.4

Release Date: 15 December 2024

With this release, we have implemented the following enhancements and support fixes to improve features and functionality and streamline the user experience.

Enhancements

TAF Sunset Feature Flag

We introduced a feature flag to support the gradual phase-out of TAF functionality in AutoRABIT. This flag allows controlled activation or deactivation of TAF at the customer account level, enabling a seamless transition without disrupting existing workflows. Automated testing and monitoring have been implemented to ensure functionality operates correctly and customer environments remain stable during the transition. Affected customers will be notified with detailed timelines, guidance, and alternative solutions to support their migration. Impacted Modules: TAF, CI Jobs, Reporting

Protection Against CSV Injection

We strengthened protection against the potential for a security vulnerability related to CSV injection, where malicious formulas embedded in CSV files could execute commands when opened in spreadsheet applications. User-generated data is now thoroughly sanitized, and special characters are omitted to prevent formula execution. This enhancement ensures that exported CSV files are safe to open, enhancing security against attempted cyberattacks. Impacted Modules: Org Sync History, Users, CI Job History, Reports, CI Job List

Unique Email Enforcement for User Registration

We eliminated the possibility for users to register using multiple email accounts for the same email ID, preventing potential confusion and security risks. The registration process now includes strict validation checks to ensure each email address is linked to only one active account. Email verification has also been implemented to confirm ownership and prevent unauthorized registrations, improving data privacy and system integrity.

Asynchronous Deployment Processing

We implemented an update to the deployMetadata SOAP service within the Deployment module, which now enables the process to run asynchronously in the background when initiating a Full Deployment. Previously, the service remained in a "pending" state until the deployment job completed. With this enhancement, the deployment process is more efficient, allowing the service to proceed without blocking user actions while the deployment completes in the background. Impacted Module: Deployments

ARM API Integration with Supported SIEM Systems

AutoRABIT introduced a new API endpoint in the audit logs service to provide structured access to CEF audit logs. The API allows querying audit events based on a specified time range and maximum results, returning a detailed JSON response that includes event metadata, such as timestamps, event types, user actions, and outcomes. This enhancement replaces the previous plain-text log format with a structured system with query capabilities, enabling easier integration and analysis of audit data. Impacted Module: API Audit Log Event

Fixed Redirect for Unsupported Types in Org Sync Report

We corrected an issue in which clicking "Here" in the Org Sync Report failed to redirect to the Unsupported Types Salesforce screen. The href attribute spelling has been corrected, ensuring users are properly redirected to the relevant page for unsupported metadata types. This fix improves navigation and user experience within the Org Sync Report. Impacted Module: Org Sync

Support

Improved Stability for Commit and Merge Operations

We resolved an issue causing failures in commit and merge operations due to corrupted global workspaces. The global workspace handling mechanism has been enhanced to ensure stability, even when the OPTIMIZED_WORKSPACE feature flag is disabled. This fix eliminates runtime exceptions during clone operations, improving the reliability of EZ-Commit and EZ-Merge processes. Impacted Modules: EZ-Commit, EZ-Merge, Deployment & CI Jobs, Repo & Branch Registration.

Accurate Reporting for a CodeScan SCA with a Large Number of Violations

We corrected an error occurring in which a CodeScan code analysis with more than 500 violations displayed incorrect results in the UI and incomplete data in downloaded reports. The fix ensures that all scanned violations are accurately reflected in the UI and included in the downloaded Excel files, providing a complete and reliable report for large code scans. Impacted Modules: CodeScan SCA Execution Reports, CI Jobs, Deployments, Commits, and Merges.

Improved Grouping for Salesforce Scanner Violations

We resolved a mismatch issue between Apex PMD and Salesforce Scanner results. Violations in bundle or static resource subfolders are now correctly grouped under their respective metadata types instead of being displayed as separate components. This fix ensures accurate and consistent results, improving the clarity of scanned violations across all file types, including .JS files. Impacted Modules: SCA Execution for both DX and Non-DX.

ToRevision Included in Scheduled CI Jobs

We fixed an issue in which the ToRevision parameter was missing in scheduled CI jobs. This issue caused jobs to fail by incorrectly using the baseline revision instead of the incremental revision. The fix ensures that ToRevision is consistently included, enabling accurate and reliable execution of CI jobs. Impacted Module: CI Jobs.

Accurate Metadata Selection in AutoRABIT Build Deployments

We resolved an issue in which AutoRABIT Build deployments failed to pick all metadata components when certain components were excluded. The deployment process now ensures that all remaining metadata is correctly included, even after exclusions. This fix addresses issues with missing data-table rows, ensuring complete and accurate metadata deployment. Impacted Module: Deployments.

Accurate Revision Handling in Incremental CI Jobs

We corrected an issue in which manually triggered incremental CI jobs were skipping the previous revision. The build process now ensures accurate handling of "From" and "To" revisions, preventing gaps in deployed commits. This enhancement guarantees that all relevant changes are included during incremental builds, maintaining consistency and reliability in deployment workflows. Impacted Module: CI Jobs.

Improved Handling of Managed Package Components in CI Jobs

We have resolved an issue causing CI job deployments to fail by including managed package components in destructive changes, despite the "Ignore Installed (Managed) Components" setting being enabled. Logic has been added to exclude installed components from destructive changes in both custom deployments and CI jobs. This enhancement ensures successful deployments without errors related to managed package components. Impacted Modules: CI Jobs, Deployments [DX, Non-DX, and Org-to-Org Deployments].

Resolved Deployment Error for DigitalExperienceBundle

We corrected an issue during org-to-org deployments in which DigitalExperienceBundle components were not found in the zipped directory, resulting in deployment failure. The logic handling Digital Experience bundles has been corrected to account for scenarios where excluded components exceed 50. This enhancement ensures successful deployments are completed without errors related to missing DigitalExperienceBundle components. Impacted Module: Custom Deployments with Digital Experience bundles.

Accurate Package Version Updates in sfdx-project.json

We resolved an issue where AutoRABIT failed to commit the latest package version to the sfdx-project.json file. When a new package version is created, it is now correctly updated and committed in the sfdx-project.json file, ensuring consistency between the project configuration and the deployed package versions. Impacted Module: CI Jobs.

ARM Release Notes 24.4.4.1

Release Date: 22 December 2024

Patch to fix bugs in the nCino Query Validation module.

ARM Release Notes 24.4.3

Release Date: 24 November 2024

The following enhancements and support fixes have been implemented with this release to improve features and functionality and streamline the user experience.

Enhancements

Special Character Support in Commit Comments

The EZ-Commit workflow now supports special characters in commit comments, including German characters (ä, ö, ü) and punctuation marks (colon [:], semicolon [;], slash [/]). These characters are correctly displayed in commit messages, and the commit process completes without errors when they are used. Impacted Module: EZ-Commit.

Duplicate Detection for Layout Metadata Subnodes

The system now supports duplicate detection for all subnodes in Layout metadata, ensuring consistent layout configurations and preventing errors during deployment. Duplicate detection functionality has been extended to include the following subnodes:

Header
RelatedLists
Sections
QuickActionList
RelatedContent
EmailDefault
MiniLayout
PlatformActionList

Users will be prompted with clear, actionable messages when duplicates are detected in any of these subnodes, allowing them to resolve issues efficiently. This enhancement builds on existing duplicate detection for <layoutItems>, <layoutColumns>, and <layoutSections>. Impacted Module: Back End.

Support

Digital Experience Metadata Type Improvements

Accurate Metadata Selection in Profile Deployment

When deploying a profile via the CI Job build, only the selected profile is now included in the deployment. The issue in which Digital Experience metadata was incorrectly included has been resolved, ensuring that deployments contain only the metadata explicitly chosen by the user. Impacted Modules: Every module that uses Digital Experience Bundle Metadata type.

Delete Support for DigitalExperience Metadata

Users can now delete DigitalExperience metadata in the EZ-Commit module. Additionally, support for managing DigitalExperience metadata has been extended across all modules. Impacted Modules: EZ-Merge, Custom Deployment, CI Jobs, Prevalidation Deployments, and Release Labels.

Subscription Extension via Super Admin

Super Admin users can now successfully extend subscription counts for active accounts. The issue causing an empty notification pop-up when attempting to increase subscriptions has been resolved. Impacted Module: SuperAdmin - Extend Customer tab. Found in QA.

Vlocity Deployment Visibility in Deployment History

The Vlocity deployment process has been updated to address issues with visibility and interaction:

Deployment History Display:
- Vlocity deployments now appear correctly in the deployment history, ensuring users can track and review their deployments without issues.
UI Interaction Fix:
- Resolved the issue where Vlocity components failed to expand when toggled. Users can now expand and view Vlocity components seamlessly in the deployment history UI.

These improvements enhance the usability and reliability of Vlocity deployments in ARM. Impacted Module: Vlocity Deployments.

Accurate Notifications for Scheduled Code Coverage Report Changes

The notification system for scheduled code coverage reports has been improved to accurately reflect changes in settings.

Test-Level Changes:
- When the test level is altered for a scheduled code coverage report (e.g., weekly schedule), the notification now correctly indicates the change instead of displaying "no changes detected."
Other Configuration Changes:
- Modifications to parameters such as test classes or email lists also trigger accurate and relevant notifications.

This enhancement eliminates misleading messages, ensuring that users receive correct feedback on configuration updates. Impacted Module: Admin-Code coverage report → Reports.

Automatic Mapping of JIRA Credentials

The JIRA credentials mapping process has been improved to eliminate the need for manual workarounds. Credentials using application tokens are now automatically populated in the ALM Mapping section of the profile, without requiring modifications to the default credentials in the ALM Management admin section. This enhancement simplifies the mapping process and ensures seamless integration with JIRA. Impacted Modules: VC Repos, Modularization, EZ-Commit, My Account, SF Org Management.

Improved Handling of Empty Metadata in Release Label Deployment

The release label deployment process has been enhanced to prevent failures caused by empty metadata. When no deployable changes exist and the package.xml is empty, the system now accurately reflects the absence of metadata in both the UI and back end, ensuring consistency and preventing deployment errors. Impacted Module: Release Labels.

Notification Emails for New User Creation

The issue in which notification emails were not being sent to new users upon creation in ARM has been resolved. New users now receive a notification email in their mailbox immediately after being created by an admin, ensuring consistent communication and a smoother onboarding process.

ARM Release Notes 24.4.2

Release Date: 10 November 2024

Enhancements

Salesforce API Version 62 Support

ARM now supports Salesforce API Version 62 for all functions, allowing users to utilize the latest metadata types and capabilities introduced by Salesforce. This upgrade includes comprehensive integration across all ARM functions, including the Data Loader, ensuring alignment with Salesforce's Winter '25 release. ARM Admins can set the global API to version 62, ensuring consistent functionality across all features.

Support

Accurate Metadata Count for Repeated Deployments

ARM now ensures accurate tracking of metadata counts across multiple deployments using previous deployment labels. The request node sent for deployment has been corrected in the front end, ensuring that when performing a follow-up deployment with a prior label, all specified components are included. This enhancement resolves issues in which subsequent deployments using previous labels reflected only a partial count of metadata components, providing a consistent and complete deployment experience across repeated operations.

Confirmation for Destructive-Only Deployments

A new confirmation prompt has been added to notify users when a deployment includes only destructive changes and no constructive changes. This enhancement helps clarify deployment contents, reducing potential confusion for users who may expect other metadata components to be included.

Inclusion of Destructive Changes File in Deployment Backups

The backup.zip file now includes the destructiveChanges.xml file, allowing users to access destructive change data for potential rollback scenarios. This enhancement provides a more comprehensive backup package to support safer and more flexible deployment management.

Improved Commit Label Search Functionality

Enhancements have been made to the commit label search feature to address two user concerns:

Accurate Filtering with Special Characters: The search functionality on the Commit Labels screen now retains all special characters in commit labels, allowing for precise search results even with special characters.
Consistent Label Retrieval Across Screens: The commit label creation and retrieval processes have been standardized across the EZ-Commit and Commit Labels screens. This ensures accurate search results by aligning label keys, resolving prior issues with locating commit labels by revision.

These improvements enhance usability and consistency within the Version Control module, providing a more reliable experience for commit label management.

Corrected Revision Display in EZ-Merge Confirmation

An update has been made to ensure proper display of revision numbers in EZ-Merge confirmations. Previously, certain revision formats containing the character "e" were misinterpreted as exponential values, causing them to display incorrectly as "Infinity" or scientific notation.

This issue has been resolved by adjusting the response handling, allowing revisions to appear as intended without conversion errors. This enhancement improves the accuracy and reliability of revision details displayed during merges, especially for branches with specific revision formats.

Quick Deploy Auto-Population for Deployment Label and Asynchronous ID

An improvement has been made to the Quick Deploy feature to ensure the Deployment Label Name and Asynchronous ID fields auto-populate after a validated deployment. This update addresses issues in which these fields were previously blank, preventing users from completing Quick Deploy without manually reentering data.

This enhancement improves efficiency and consistency for custom deployments, particularly for users working with single revision DX deployments.

Stable Permissions View for Newly Created Teams

An update has been implemented to ensure stable loading of the Permissions View in the Admin module for newly created teams under Subscription Management. Previously, permissions were not displayed due to an incomplete setup for new users created via the "Create Team" option.

Now, the releaseNotify setting for new users defaults to "true," and additional checks have been added to handle null values during data conversion. This enhancement ensures permissions load reliably, enhancing usability for subscription-based team management.

Improved CI Job Editing with Null Check for Checkmarx Configuration

A fix has been implemented to prevent blank pages from displaying when editing CI jobs. Previously, attempting to edit CI jobs with no rules configured for Checkmarx would result in an unresponsive, blank screen.

This enhancement includes a null check, ensuring CI jobs are editable even if no rules are set for Checkmarx configurations. This update improves stability and usability for managing CI jobs in ARM.

Improved Tag-Based Deployment

An update has been made to ensure successful deployments when using tags in the deployment module. Previously, deployments initiated with tags would sometimes fail with a "No Changes are found in the package" error due to issues with file copying during tag-based deployments.

This enhancement ensures accurate file handling for tag-based deployments, providing stable and reliable performance for both DX and non-DX branches.

Accurate Error Messaging for CI Jobs and Deployments

An update has been implemented to improve the accuracy of error messages displayed in CI job logs and deployments. Previously, CI jobs that encountered baseline revision failures or exceeded file limits displayed misleading error messages. Additionally, deployment failures were showing unrelated errors, such as "Invalid Login," instead of indicating the true cause, such as reaching Salesforce file limits or the need for reauthentication.

This enhancement ensures that CI job and deployment errors reflect the actual underlying issues, providing users with clearer, more actionable information for troubleshooting.

Direct Commit Support for Profiles and Permission Sets

An update has been applied to the direct commit process to ensure that both profiles and permission sets are committed together when selected. Previously, when committing Field-Level Security (FLS) for profiles and permission sets in a single direct commit, only profile FLS was committed, while permission sets were excluded.

This enhancement aligns direct commit functionality with pre-validation commits, allowing selected metadata types—including profiles, permission sets, and custom fields—to be consistently committed as intended. This update improves accuracy and flexibility for version control management within ARM.

Improved Merge Conflict Resolution Status

An update has been applied to ensure accurate status updates during merge conflict resolution in EZ-Merge. Previously, after resolving a conflict, the status was sometimes incorrectly set to "Commit," even when additional conflicts remained. This led to repeated merge conflict prompts after refreshing the page.

With this fix, the merge status will correctly display as "In Progress" when unresolved conflicts are pending, and actions will show as "Check Details" instead of "Commit." This enhancement ensures clearer guidance during conflict resolution, streamlining the merge process in EZ-Merge for better user experience.

Optimized Inline Comment Retrieval in Large File Diffs

An improvement has been made to reduce "Network Connection Interrupted" errors when expanding large files under the "Files Changed" tab in EZ-Merge. Previously, each line in files exceeding 3,000 lines triggered an individual API call to fetch inline comments, leading to network interruptions and interface freezes, particularly for files with 15,000 lines or more.

With this enhancement, a single API call now retrieves all inline comments at the file level, significantly improving performance and stability when working with large files. This update prevents excessive network calls and enhances usability during merge and commit actions.

Accurate Component Inclusion for Reused Commit Labels

An update has been made to the "Re-use Previously Validated Commit Labels" functionality to ensure that only selected components are included in the commit. Previously, when reusing a validated commit label, additional, unintended changes (such as Profiles and Permission Sets) could appear in the "Files Changed" tab during the approval stage, even if only specific components were selected initially.

This enhancement corrects the commit process so that only the selected components are retained and displayed in the commit, providing more reliable control and accuracy over component selection in EZ-Commit. This improvement applies to both DX and non-DX formats and supports all commit types, including manual selection, auto-draft, commit templates, and package uploads.

ARM Release Notes 24.4.1

Release Date: 27 October 2024

Enhancements

Manageable-State Selection for Branching Baseline A new option has been added to select the Salesforce org's manageable state when initiating or re-running a branching baseline. This option is available only when the retrieval type is set to Salesforce, ensuring greater control over the data types included in the process.

Consistent Manageable-State Dropdown Across Modules The manageable-state dropdown is now consistently available across several modules, streamlining the user experience. It can be found in the following areas:
- Branching Baseline
- CI Job (Org to Org deployment)
- EZ Commit
- My Account (Save Global Settings for Admins)
- Static Code Analysis
- Org Synchronization History
Global Settings Migration for Manageable State Global settings for manageable state, previously configured in the "My Account → Admin" section, are now automatically retrieved and applied across relevant modules, ensuring consistency across the platform.
Database Support for Manageable State The database schema has been updated to support the manageable-state dropdown in CI Job, EZ-Commit, and Branching Baseline modules. This ensures that user selections are properly saved and retrieved, maintaining data integrity across sessions.

Conditional Abort Functionality for Branching Baseline The "Abort" button is now only clickable when the branching baseline process is actively in progress. The abort functionality behaves as follows:

If the process is in the retrieval stage, clicking "Abort" will stop the operation.
If the process is in the committing stage, clicking "Abort" will cancel the process.
If the revision has already been generated or committed, the "Abort" button will be disabled to prevent unnecessary actions.

Enhancement: Updated Actions in Branching Baseline The actions available for each branching baseline iteration now include "Run," "Abort," and "Delete," providing clear and accessible options based on the process state.
Enhancement: Combined Revision and Info Section in Iterations The "Revision" and "Info" columns in the branching baseline iterations section have been merged into a single "Revision Info" column. This section is now a clickable hyperlink, allowing users to view detailed information for each specific revision easily.

Improved Abort Functionality with Interrupt Method (Internal) The abort functionality has been enhanced across the application by implementing the recommended interrupt method, significantly improving reliability and preventing potential thread-related crashes. This update ensures a smoother and more stable abort process.

The enhanced abort functionality has been applied to the following areas:

Admin
CI Jobs
Version Control Release Labels

Thorough internal QA checks have been performed to ensure the stability of this new approach.

Enable the “Trigger Build On Commit” option when creating a CI Job Users can now enable the “Trigger Build On Commit” option when creating a CI Job, allowing automated builds triggered directly by commits. Upon selecting this option, a webhook setup will become available, ensuring that every new change in the version control system triggers an update to the CI Job. Builds will only initiate for commits made in the feature templates folder.

Support

Accurate Merge Status Display

Customers reported receiving expiry email notifications with a misleading status of "MERGED," even though the merge was still pending approval or awaiting changes to be committed. This confusion has been addressed by updating the merge status in the expiry email. Now, the system retrieves the status from the SCM History table, ensuring the actual state of the merge is reflected. Users will no longer see "MERGED" unless the merge has been fully completed, providing clearer communication on the status of their merges.

Profile Comparison Layout and Behavior Fixes

The following issues in profile comparison have been resolved by adding the "Person Account" column dynamically when person accounts are enabled:

Record Type Column Fix: The Record Type section in new profile comparisons now displays only two columns, as expected. The third column, "Person Account Default," will only appear in the downloadable report if person accounts are enabled.
Layout Fix: The layout issue where five columns were displayed instead of six during profile comparisons has been addressed.
Default and Visible Field Fix: The issue where users could check 'Default' without checking 'Visible' and could not uncheck 'Default' once selected has been fixed.

These changes ensure a more accurate and dynamic display in profile comparisons, improving the overall user experience.

Select All Behavior Correction in Deployment Tab

A UI bug in the Deployment tab has been fixed where unchecking a metadata member under the "All Metadata" tab did not update the "Select All" option as expected. The condition for deselecting "Select All" has been corrected based on metadata types in the front end, ensuring that when individual metadata members are unchecked, the "Select All" option now responds accurately and reflects the correct selection status. This fix improves the consistency and usability of the deployment process.

Apex Test Class Live Status Fix

The issue where the Live status for the Apex Test Class was not populating under the SF Org Management section has been resolved. The fix involved changing the response data type from text to JSON, allowing the Live status to be fetched and displayed correctly for Apex Test Classes. This update ensures accurate status reporting for users.

Vlocity Deployment Failure Fix

A code fix has been implemented to resolve the issue where Vlocity deployments were failing during VC incremental deployments. The failure occurred because the CI job picked a different dependency, specifically the contentVersion dependency, which was not included in the release label deployment. The fix removes non-Vlocity components during CI deployments, ensuring that only relevant dependencies are picked, resulting in consistent and successful Vlocity deployments.

Board Type Selection Fix in Release Label Merge

An issue where the board type was automatically changing from Vlocity to Salesforce during release label merges has been resolved. The problem occurred because the board type was not being explicitly set to Vlocity during the merge operation, causing Salesforce to be selected by default. This fix ensures that the correct board type, Vlocity, is maintained during the merge process.

Unrelated Changes in EZ-Merges Fix

A fix has been implemented to address the issue of unrelated changes being pulled into EZ-Merges. To prevent this, the system now cross-checks the remote head revision against the local revision before allocating the workspace, ensuring the workspace is properly synced with the remote repository.

Additionally, loggers have been added to track and identify the root cause should this issue recur in the future. These updates ensure a more reliable and controlled merge process, reducing the chance of unintended changes being included in EZ-Merges.

Manual Deployment Destructive Changes Fix

An issue was identified during manual deployments using AutoRABIT Build, where clearing all pre-destructive changes did not exclude them as expected. This occurred when deploying via the Metadata.zip option in non-DX custom deployments, where destructive changes were still included despite being deselected.

A code fix has been implemented to ensure that when pre-destructive changes are cleared during deployment, they are properly excluded from the process. This update ensures that all selected components are correctly deployed, without any unwanted destructive changes being included.

Review Artifact Screen Icon Display Fix

An issue on the Review Artifact screen where icons were not displaying correctly during keyword searches (Ctrl + F) has been resolved. Users previously saw only box icons, leading to confusion about the functions of each icon.

The fix involved correcting the file path for font icons and updating the CSS to ensure proper loading. Icons now display correctly, providing clear visual guidance for each action on the screen. Support Case #123456

NamedCredential Search and Substitute Fix

An issue was identified where the "Search and Substitute" feature was not working for the NamedCredential metadata type. The problem occurred because the metadata type was misspelled as "NamedCrendential" in the configuration file.

The root cause has been addressed by correcting the spelling of "NamedCredential" in the JSON file that maintains supported metadata types and their subnodes.

Deactivated User Deletion Error Fix

An issue where an error pop-up appeared when attempting to delete deactivated users has been resolved. While the user was successfully deleted after a page refresh, the error caused confusion.

The fix involved correctly reading the JWT token during the deletion process, ensuring that inactive users can now be deleted without triggering an error message. This update streamlines the user deletion process and eliminates unnecessary pop-ups.

Validation Job NullPointerException Fix

An issue causing validation CI jobs to fail with a java.lang.NullPointerException has been identified. The problem occurred intermittently when the customer changed the baseline revision, with the workaround only providing temporary relief.

A fix has been implemented to address the root cause of the null pointer error. This ensures that validation jobs now run consistently without failure, eliminating the need for manual interventions or workarounds.

Workspace Error in EZ-Commit Delete Tab Fix

An issue where users encountered a "Workspace does not exist" error in the Delete tab of EZ-Commit has been resolved. The error occurred because the system did not check whether the workspace was optimized before throwing a custom exception when the workspace was not locked.

A fix has been implemented by adding a condition to ignore optimized workspaces when checking for locks. This ensures that users no longer see the error pop-up when navigating to the Delete tab in EZ-Commit, improving the overall functionality. Support Case #124537Improvements

Optimized Selective Deployments Selective deployments have been optimized to utilize pre-prepared artifacts, eliminating the need for additional Git operations. This enhancement allows users to perform component selection directly on the pre-prepared artifact, ensuring faster deployment times and reducing the risk of errors associated with manual Git interactions.

Lazy Loading for EZ Commit Data Tables The EZ Commit process now includes lazy loading for metadata components when using the Auto Draft functionality. Initially, only necessary data is loaded, with additional data fetched as the user scrolls or navigates through the table. This ensures a more efficient and responsive experience.

Lazy Loading in Package Manifest and Commit Template Lazy loading has also been implemented in the Package Manifest and Commit Template screens and the Selected and Deleted tabs, enhancing performance and responsiveness across these areas.

A visual indicator has been added during the loading process, ensuring users are informed while additional data loads, without any noticeable delays or interruptions to the user experience.

Third-Party Library Upgrades Third-party libraries have been upgraded to ensure the latest enhancements and fixes from external libraries, improving overall stability across the platform.

By streamlining the selective deployment process, this improvement enhances efficiency and contributes to a more reliable release management workflow.

ARM Release Notes 24.2

Release Date: 25 August 2024

Improved Reporting Features and Enhancements

New Features

The new merge report is now included in the downloaded reports.
Failure/Auto-reject reasons have been added to the reports for merge, commits, deployment, and CI build jobs, ensuring that if any jobs fail, the reason is included in the reports.

Enhancements

Extra fields have been correctly added to the current report.
The name of "Latest Reports" has been changed to "Refresh Reports View."
Users are now restricted from downloading more than six months of data.
Post-download, headers, alignment, and naming conventions in Excel have been checked for readability and usability.

Exclude Metadata in the Branching Baseline Users can now customize their baselines by excluding specific metadata. When selecting the "New Branching Baseline" option, a pop-up appears with available fields. A new "Exclude Metadata" checkbox allows users to choose what metadata to include or exclude from a scrollable or searchable list, with individual checkboxes for each item. Options to "Check All" or "Uncheck All" are available in both sections. Once selections are made, users can click "OK" and then "Run" to execute the process.
Detailed Status Messages for Branching Baseline Process To improve transparency and usability, the branching baseline process now provides specific status messages for different failure scenarios. If some metadata members fail to commit, the status will display as "Partial Success" or "Failed." Users can download the files of the failed batch metadata XML files for better feasibility and view failure reasons, reducing troubleshooting time and improving overall efficiency.
Updated UI and Pagination The UI for EZ-commit, deployments, and commit template screens has been updated with pagination for metadata-type tables. Users can now adjust the number of entries displayed per page.

Pagination Availability:

VC Commit: Components selection screen.
Commit Template: Components selection screen.
Deployments: Retrieval screen and "Additional Metadata" section.

Improvements

In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability.
SOAP to REST services were upgraded.
Third-party libraries were upgraded.

ARM Release Notes 24.1

June 2024

Version 24.1 – Enhancements and Improvements

Enhancements

Perform Validation Deployment for Multiple Orgs In this release, we're thrilled to introduce an enhanced Validate Deployment feature, responding to a key user request. Users can now choose multiple orgs simultaneously, enabling a forward-looking validation process as they promote from one sandbox to the next and eventually to production. This time-saving enhancement allows users to select up to three organizations from a convenient multi-picklist, and the subsequent summary screen provides a consolidated view of the deployment results for each selected organization. The implementation ensures a seamless experience by allowing users to toggle between different org validations. The introduction of this feature in the EZ-Merge and EZ-Commit options streamlines deployment validations, contributing to a more efficient and informed deployment workflow.
Incorporated Checkbox to Skip Prevalidation Criteria In this release, we're excited to introduce the ability for developers to skip all prevalidation criteria specifically for back merges from designated branches. This enhancement offers a streamlined approach to the back merge process, empowering developers to improve efficiency and simplify code migration upstream. To leverage this feature, developers can configure the branch type in VC Repos → Branch settings, where a new checkbox option allows you to enable skipping prevalidation criteria for a particular branch during back merges. This capability enhances flexibility and productivity, reducing unnecessary steps in the code migration workflow. With the skip option, developers have greater control over the back merge process, ensuring a smoother and more agile development experience.
Revamped Static Code Analysis View We’ve revamped our static code analysis UI to enhance the user experience. Now, errors are conveniently displayed under selected files, streamlining issue identification and resolution across various tools.
Streamlined EZ-Commit Editing This release significantly enhanced the EZ-Commit workflow to empower developers. The introduction of an integrated Compare Changes option in the Review Artifact screen allows for seamless viewing, editing, and visualizing of Salesforce metadata changes in a single, user-friendly interface. Developers can now effortlessly navigate and understand their code edits with color-coded differences, eliminating the need to toggle between multiple screens. This streamlined process enhances the user experience and addresses a crucial blocker in the journey towards CI/CD, providing a more efficient and intuitive path for developers.
Enhanced SCA Label Scheduling In this release, users can now enjoy enhanced control over SCA label scheduling with the introduction of the ability to edit/update schedules. This feature provides greater flexibility, allowing users to modify scheduled times for SCA labels, contributing to a more seamless and user-friendly experience in managing job schedules.
New Email Templates Implementation In this release, a significant enhancement has been made by implementing new email templates that align with current visualization standards. This update reflects our commitment to maintaining high standards in user interface design and enhancing overall user engagement.

Improvements

This update improves the tool's efficiency and responsiveness and leverages new technologies, collectively resulting in a smoother, faster user experience.

In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability.
SF CLI Version upgrade to 2.41.8
SOAP to REST services upgrade: Upgrading from SOAP to REST services improves performance by reducing overhead with lightweight JSON payloads and enhances security through stateless communication and simplified implementation of HTTPS.
By merging SalesforceDxHub into SalesforceOrg, it effectively reduces redundancy in data storage. Users can now register once from SalesforceOrg, with the added capability to specify a registered org as a Dev hub. When a production org is registered as a Dev hub, it appears on both screens, streamlining data management and enhancing user workflow. This release optimizes data storage, improves user experience, and simplifies registration processes, ultimately enhancing overall system efficiency.
Upgrade of third-party libraries
Salesforce integration credentials (Client ID & Secret) are now encrypted for improved security. Existing tokens are also migrated to the new format. This enhances protection against unauthorized access.
Log-leveling: Dynamically modify log levels for specific logger categories to enhance monitoring and troubleshooting.

Changelogs

The following weekly fixes were implemented.

31 July 2024

ARM 24.1.7

A code fix was applied to the CI Jobs module of version 24.1 related to a data error that caused a CI Job to be unable to be built manually. Support ticket #117587
A code fix was applied to the Admin module of version 24.1 due to a data error that caused Salesforce orgs to not be displayed as mapped to the repository even after enabling them under the profile. Support ticket #117542
A code fix was applied to the nCino module of version 24.1 due to a use-case error identified internally in which rollback failed for inserted records.
A code fix was applied to the nCino module of version 24.1 due to a use-case error in which Data Loader jobs were automatically being deleted. Support ticket #117577
A code fix was applied to the CI Jobs module of versions 23.1 and 24.1 due to a use-case error causing the CI Job History report to not generate. #116943

24 July 2024

ARM 24.1.6

A code fix was applied to the CI Jobs module of version 24.1 due to a typo in the ARM CI Jobs creation screen. Support ticket #116616
A code fix was applied to the Deployments module of version 24.1 due to a use-case error in which the 'add member' option was not working. Support tickets #116545, #117480
A code fix was applied to the Admin module of version 24.1 to correct a use-case error in which test class mappings were missing. Support tickets #116984, #117737
A code fix was applied to the Admin module of version 24.1 to correct a use-case issue with log visibility in the branching baseline for admin users. Support ticket #117485
A code fix was applied to the Admin module of version 24.1 from an internal ticket identifying a use case in which the user was getting an 'unauthorized 401' error during a new account signup registration.
A code fix was applied to the Admin module of version 24.1 identified by internal ticket a use case in which the user was unable to log in via the default SSO login page; also, the build version and revsion information were not displaying.
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
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
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
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
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
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
A code fix was applied to the nCino module of version 24.1 due to a use-case error in which Data Loader jobs were being automatically deleted. Support ticket #117577
A code fix was applied to the CI Jobs and Deployment modules of version 24.1 due to a use-case error causing the rollback functionality to not work properly. Support tickets #117512, #118316
A code fix was applied to the CI Jobs module of version 24.1 due to a use-case error in which CI Jobs were experiencing a build issue, which is awaiting QA verification from the customer. Support ticket #118301
A code fix was applied to the CI Jobs module of version 24.1 due to a use-case error identified by internal ticket in which a CI Unlocked package installed CI build failing with Hub connection failure, even though Hub connection was successful.
An internal ticket identified an EBR change request required to the EBR module of version 24.1 to correct EBR plugins.

17 July 2024

ARM 24.1.5

A code fix was applied to version 24.1 as a result of a data error encountered in the CI Jobs module related to CI Jobs not triggering. Support ticket #116677
A code fix was applied to the Version Control module in version 24.1 related to a data error causing the WebLink deletion feature to not work. Support ticket #115994
A code fix was applied to the CI Jobs module in version 24.1 due to a data error identified internally with the CI Edit edit mode where the "Do you want us to update the test classes" feature is not saving.
A code fix was applied to the nCino module in version 24.1 related to a use-case error in which Data Loader Pro was not fetching the child object. Support ticket #116928

10 July 2024

ARM 24.1.4

A use-case error identified in version 23.1 required a code fix 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 in which package visibility and permissions were not captured. Support ticket #110760
A code fix was applied to versions 23.1 and 24.1 due to a use-case error identified in version 23.1 in which commits were failing with a 'no credentials mapped' error in the Version Control module. Support ticket #116704
A code fix identified in version 24.1 was applied to the Admin module in version 24.1 due to a use-case error identified by internal ticket in which the on-premises server was not starting up after migrating from 23.1 to 24.1 build.
A use-case error in the Version Control module identified in version 24.1 by internal ticket required a code fix to version 24.1 to correct an instance in which the user was unable to create a release label.

3 & 7 July 2024

ARM 24.1.3

A use-case error identified in version 24.1 required a code fix to the CI Jobs module, applied in versions 23.1 and 24.1, to correct instances where configuration changes were not being saved to the CI job. Support ticket #116047
A code fix identified in version 24.1 by an internal ticket was implemented in version 24.1 to correct a use-case error in which the Version Control module’s Validate and Merge button was not being reflected immediately after changing the EZ-Merge validation criteria in MyAccounts.
A code fix identified in version 24.1 by an internal ticket was applied to version 24.1 due to the minimization feature not working in the Version Control module.
A code fix identified by an internal ticket in version 24.1 was applied to the Version Control module in version 24.1 due a use-case error where ‘Path View’ section highlighting is occurring when toggling from the ‘File Changes’ screen to the ‘Path’ view, then back to the ‘File Changes Path’ view.
A code fix identified in version 24.1 by an internal ticket was initiated to the EBR Change module in version 24.1, prompted by a change to the EBR plugin info.
A use-case error identified in version 24.1 by an internal ticket required a code fix to the Version Control module in version 24.1 due to the commit history screen getting stuck loading when the repo name has a special character in it (e.g., plus sign [+]).
A use-case scenario identified in version 24.1 by an internal ticket required a code fix to the CI Jobs module in version 24.1 for the time-frame window to be added for the ARM admin API to fetch data.
A use-case error identified in version 24.1 by an internal ticket required a code fix applied to the nCino module in version 24.1 to correct where the option "automap user/owner data" is disabled by default for CI jobs created in 23.1.x versions.
A use-case scenario identified in version 24.1 required a code fix to the Version Control module in version 24.1 due to release labels not showing. Support ticket #116413
A use-case error identified in version 24.1 required a code fix to the Version Control module in version 24.1 due to an issue with choosing the Level 1 approver when performing a merge. Support ticket #116417, #116692
A use-case error was identified in version 24.1 that required a code fix to the nCino module due to the RBC filters not working on commits. Support ticket #116291
A use-case scenario identified in version 24.1 via an internal ticket required a code fix to the nCino module to correct an error in which the Data Loader clone process is not identifying the new CSV file.
A use-case error identified in version 24.1 required a code fix to the Version Control module to correct an error in which user is unable to create an EZ-Merge. Support ticket #116700
A code fix was applied to the Deployment and Version Control modules to correct a use-case error identified in version 24.1 in which the org comparison is not showing diff results. Support ticket #116039
A use-case scenario required a code fix to the version 24.1 Admin module to correct an error that caused the branching baseline to keep running for 24 hours. Support ticket #114734
A code fix was applied to the Version Control module to correct a use-case error identified in version 24.1 that caused commits to be failing with an 'no credentials mapped' error. Support ticket #116704
A use-case error identified in version 23.1 required a code fix to the Deployment module, applied in versions 23.1 and 24.1, to correct the metadata retrieval in the repository from failing. Support ticket #115818
A code fix identified in version 23.1 by an 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.

26 June 2024

ARM 24.1.2

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
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
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
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
A use-case error in version 24.1 with the Version Control module in which commits were remaining in progress was resolved through a code fix. Support ticket #115691
A use-case error in version 24.1 with the Version Control module with commit CI Job deployment errors was resolved in 24.1 through a code fix. Support ticket #115817
A use-case error reported in version 24.1 required an update to the Admin module to properly reflect X rather than Twitter along with revised copyright information, which was resolved through a code fix. Support ticket #115756

23 June 2024

ARM 24.1.1

A code fix was applied to the Version Control module for a use-case error related to an EZ-Commit re-login issue identified. Support ticket #115664
A code fix was applied to the Version Control and Admin modules for a use-case error related to an issue in which Azure ADO connection and password were returning errors. Support tickets #115489, 115558
A code fix was applied to the Version Control module for a use-case error related to a validation org being requested when attempting to merge changes. Support ticket #115787
A code fix was applied to the Version Control module for a use-case error related to the create artifact button not being visible when attempting to create a release label.
A code fix was applied to the Reports module for a use-case error related to an alignment issue in the weekly reports filter for no deployments.
A code fix was applied to the Admin module for a use-case error in which the user is unable to create a search and substitute rule.
A code fix was applied to the Admin module for a use-case error related to being unable to register a branch.

nCino Improvements

See the recent updates to notes as well.

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

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

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

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

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

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

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

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

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
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
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
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
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
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.
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
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
A code fix was performed due to a use-case error related to the Reports module that required us to fix recursive errors.
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
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
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
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

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.
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.
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
A code fix was applied to the Version Control module related to a use-case error occurring when processing merge conflicts. Support ticket #113606
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
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
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

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
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
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
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
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.
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.
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."
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."
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.
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)

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
A code fix was applied to the Version Control module due to a use-case error in which reverting a commit failed. #112094
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
A code fix was applied to the Deployment module due to a data error in which the org sync was not completing. #111545
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
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)

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
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
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
Code fix applied to Deployments module related to email templates of type Visualforce not being added to the package.xml when deploying. #110762
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.
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)

Module

Summary

Status

Fix Version

Resolution

Cause

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)

Module

Summary

Status

Fix Version

Resolution

Cause

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

CI Jobs

Run test based on changes, noticed issues

Requires Customer Coordination

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)

Module

Summary

Resolution

Cause

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)

Module

Summary

Status

Version

Resolution

Cause

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)

Module

Summary

Resolution

Cause

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)

Module

Summary

Status

Version Reported

Fix Version(s)

Resolution

Cause

Deployments

Org Sync question on Moderation Rule difference

QA Passed

23.1

Code Fix

Use Case

Version Control

Unable to create EZ-Commit for the new user

QA Passed

23.1

Code Fix

Use Case

Reports

Problem with scheduled code coverage reports

QA Passed

23.1

Code Fix

Use Case

Deployments

Profile Comparer - Taking too long to deploy

QA Passed

23.1

Code Fix

Use Case

Version Control

Issue in Merging

QA Passed

23.1

Code Fix

Use Case

Version Control

Incorrect merge status issue

QA Passed

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

Code Fix

Use Case

Version Control

Vlocity DataPacks not being baselined

QA Passed

23.1

Code Fix

Use Case

Admin

Getting stuck in loading when trying to Expand ALM mappings

QA Passed

23.1

Code Fix

Use Case

CI Jobs

CI Deploy job link throwing pop-up error message

QA Passed

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

No Code Fix

Loggers Added

nCino

Data Loader Pro jobs failing for Lead

QA Passed

23.1

Code Fix

Use Case

nCino

nCino Deployment History - search filter criteria is not working

QA Passed

23.1

Code Fix

Use Case

Version Control

Unnecessary select all checkbox is showing in added and modified tab

QA Passed

23.1

Code Fix

Use Case

Version Control

Unable to view created credentials

QA Passed

23.1

Code Fix

Use Case

CI Jobs

Returns all CI Jobs History to EBR Data irrespective of active

Done

23.1

Code Fix

Internal change request in EBR Data Visibility

nCino

Feature Deployment Issue with Salesforce Org Version Control

QA Passed

23.1

Code Fix

Use Case

Data Loader Pro

Issue with Audit Fields

QA Passed

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

Code Fix

Use Case

CI Jobs

Error Message: Cannot invoke "String.startsWith(String)" because the return value of "com.autorabit.entity.admin.UserProject.getProjectType()" is null. Support ticket # 109042

QA Passed

23.1

Code Fix

Use Case

20 March 2024

(ARM v. 23.1.23)

Module

Summary

Status

Fix Version

Resolution

Cause

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)

Module

Summary

Fix Version

Resolution

Cause

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)

Module

Summary

Version

Resolution

Cause

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)

Module

Summary

Resolution

Cause

Feature Flag

Admin

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)

Module

Summary

Resolution

Cause

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

FC, Deployments

Flow Center API: Create a metadata bundle from an org

Code Fix

Use Case

Deployments

"Experience container" metadata type component deployment is failed for org-to-org deployment

Code Fix

Use Case

Version Control

Unable to view the revision number when clicking on prevalidation merge details.

Code Fix

Use Case

Version Control

Unable to fetch date from Auto-Draft when selecting DX branch in sub-user with no mappings.

Code Fix

Use Case

Deployments

Deployment failed with error: ‘Cannot invoke "java.util.Map.clear()" because "this.relatedLayoutRecordTypeIdsMap" is null’

Code Fix

Use Case

nCino

CI Jobs: date filter not selectable or enter date value.

Code Fix

Use Case

12 February 2024

(ARM v. 23.1.18)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Feature enabled by default

Feature Flag Name

Deployments

Upgrade to 23.1.16 + Ubuntu OS Upgrade

QA Passed

23.1

Code Fix

Use Case

Dashboards

ARM dashboard

QA Passed

23.1

Code Fix

Use Case

Deployments

Org sync - Scheduler not working

QA Passed

23.1

Code Fix

Use Case

Version Control

Commit failing without any logs

QA Passed

23.1

Code Fix

Use Case

Version Control

Single-revision merge taking a long time

Customer Coordination [Added Loggers]

No Code Fix - Added Loggers

Data

Version Control

Package.xml fetching the Excluded components during Commit

QA Passed

23.1

Code Fix

Use Case

Deployments

Smart checkbox redeployment

QA Passed

23.1

Code Fix

Change Request

Version Control

PG and ARM instances not working as expected

QA Passed

23.1

Code Fix

Use Case

FILE_SYNC_WITH_OPTIMISTIC_LOCK

Version Control

Commit not getting detected

QA Passed

23.1

Code Fix

Use Case

Version Control

Error while trying to select the revision from branch

QA Passed

23.1

Code Fix

Use Case

7 February 2024

(ARM v. 23.1.17)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Administration

Jira On-prem SSO Cooperation

QA Passed

23.1

Code Fix

Use Case

Version Control

Random Error Message

QA Passed

23.1

Code Fix

Use Case

Deployment

Need a feature to save metadata selection before deployment

QA Passed

23.1

Code Fix

Use Case

Deployment

Page unresponsive in new deployment using Previous Deployment as a source type

QA Passed

23.1

Code Fix

Use Case

Administration, CI Jobs

Upgrade v59 (Beta) to v59

QA Passed

23.1

Code Fix

Use Case

Administration

CI Job and Code Coverage Not Running at Correct Times

Customer Coordination

Dataloader

Configuration job failure

QA Passed

23.1

Code Fix

Use Case

Version Control

In the MergeRequest, CI Job View Screen under Build title, the Merge Request comment alignment is not displaying properly; it is not getting trimmed and appears larger than expected.

QA Passed

23.1

Code Fix

Use Case

Administration

Unable to view ‘Should pass validation criteria for Static Code Analysis’ checkbox under commit validation settings when Salesforce API version is not mapped

QA Passed

23.1

Code Fix

Use Case

Administration

Release Label artifact execution is not working.

QA Passed

23.1

Code Fix

Use Case

nCino

Partial error on CI Job - nCino-Fee Template

QA Passed

23.1

Code Fix

Use Case

28 January 2024

(ARM v. 23.1.16)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Version Control

Email communication error in EZ-Commit * Requires documentation.

QA Passed

23.1

Code Fix

Change Request

Version Control

Finding WaveDataflow components for commit

QA Passed

23.1

Code Fix

Use Case

Deployment

‘Not a well-formed XML.' error when attempting org-to-org deployments in UAT

QA Passed

23.1

Code Fix

Use Case

CI Jobs

Package CI Job Issue

QA Passed

23.1

Code Fix

Use Case

Deployment

Vlocity Deployment issue

QA Passed

22.3, 23.1

Code Fix

Use Case

Version Control

Vlocity Release label issue

QA Passed

23.1

Code Fix

Use Case

Version Control

EZ-Commit not creating a branch

QA Passed

23.1

Code Fix

Use Case

Version Control

ARM failed to auto-reject EZ-Merge request that has Apex class with less than 90% code coverage. Merge setting enforcing 90% code coverage in mock deployment.

QA Passed

23.1

Code Fix

Use Case

Version Control

CodeScan – Delta scan

QA Passed

23.1

Code Fix [Added Loggers for customer understanding,]

CI Jobs

Ignore warnings option in CI jobs is not working properly

QA Passed

23.1

Code Fix

Use Case

Version Control

Commit failing without any logs

QA Passed

23.1

Code Fix

Use Case

Environment Provisioning

Apex Anonymous Template not downloadable

QA Passed

23.1

Code Fix

Use Case

Version Control

‘File can't be loaded’ error

QA Passed

23.1

Code Fix

Use Case

Deployment

During Profile Manger Deployment, "NULL MSG: NULL" is displaying in the log

QA Passed

23.1

Code Fix

Use Case

Deployment

Using Package XML: Document XML files are not being listed in the Org compare screen

QA Passed

23.1

Code Fix

Use Case

CI Jobs

CI Job build is failing without printing reason in logs for BY SELECTING LAST TILE: install unlock package/managed tile.

QA Passed

23.1

Code Fix

Use Case

Dataloader Pro

Multiple issues during data masking

Customer Coordination – Added Loggers

23.1

No Code Fix – Added Loggers

Data

21 January 2024

(ARM v. 23.1.15)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Version Control

EZ-Merge 'Reviewer Comments' section not displaying comments entered by reviewer.

QA Passed

23.1

Code Fix

Use Case

Deployments

Profiles Sync Issue-CustomSettings issue

QA Passed

23.1

Code Fix

Use Case

Version Control

Package.xml generated from release label is other components that are not in the commits

QA Passed

23.1

Code Fix

Use Case

Version Control

Finding WaveDataflow components for commit

QA Passed

23.1

Code Fix

Use Case

Admin

Error: Access token as failed while doing a branching baseline

QA Passed

23.1

Code Fix

Use Case

CI Jobs

Provar version upgrade

QA Passed

23.1

No Code Fix – Only Configuration change for specific customer

Customer-specific

Version Control

Initial commit failing

Customer Coordination

No Code Fix – Added Loggers

Data

Admin

Users’ permissions are being reset.

Customer Coordination

No Code Fix – Added Loggers

Data

CI Jobs, Version Control, Admin, Deployments

Adding authentication check on web hook APIs

QA Passed

23.1

Code Fix

Change Request

Dataloader Pro

Issue while deploying promotions from QAT to PRD the rule set criteria is compressing the value while deploying it to RD

QA Passed

22.3 23.1

Code Fix

Use Case

Dataloader Pro

Issue on Feature Deployments

QA Passed

22.3 23.1

Code Fix

Use Case

14 January 2024

(ARM v. 23.1.14)

MODULE

SUMMARY

FIX VERSION

RESOLUTION

CAUSE

Version Control

Internal - Default SCA branch not reflected while merging

23.1

Code Fix

Use Case

Version Control

EZ-Merge request with apex class metadata files failed to identify related test classes and auto-rejected with validation failure

23.1

Code Fix

Use Case

Version Control

Missing Component in Package: PROD

23.1

Code Fix

Use Case

Deployments

Release Label not appearing in Deployment tab

23.1

Code Fix

Use Case

CI Jobs

API broken for job history

23.1

Code Fix

Use Case

CI Jobs

Deploying Flow - Property 'customErrors' not valid in version 58.0

23.1

Code Fix

Use Case

Deployments

Deployment status failed when deploying Vlocity components

22.3, 23.1

Code Fix

Use Case

Version Control

On Prevalidation Commit, the SonarQube SCA process is auto-rejected, even for unsupported metadata types.

23.1

Code Fix

Use Case

Deployments

Brazil Prod to UAT deployment issue

23.1

Code Fix

Use Case

nCino

Metadata update is failing

23.1

Code Fix

Use Case

Version Control

Commit not progressing

23.1

No Code Fix - Loggers Added

Data

7 January 2024

(ARM v. 23.1.13)

Module

Summary

Fix Version

Resolution

Cause

Admin

Client unable to create New Branching Baseline showing loading icon

23.1

Code fix

Use Case

CI jobs

Request to increase the build label size to 150-200 characters

23.1

Code fix

Use Case

CI jobs

Provar CI Job run takes a very long time and stops at status "Timed-Out"

23.1

Code fix

Use Case

Deployments

ARM API to perform a deployment (or a validation, or a quick deploy)

23.1

Code fix

Use Case

nCino

Issue with Regex on Feature Deployments

23.1

Code fix

Use Case

CI jobs

Team/Slack in CI job post activity notification, users should not have email dependency in email notification. Suggestion.

23.1

Code fix

Use Case

CI jobs

Package creation CI job

23.1

Code fix

Use Case

CI jobs

On both CI Results and CI Lists, user getting the “Invalid FilterExpression: Expression size has exceeded the maximum allowed size;(Service: DynamoDb“error) when selecting the “Ungrouped” value under “group by “ filter dropdown

23.1

Code fix

Use Case

Version Control

CodeScan – EZ-Commit Auto Rejected

23.1

Code fix

Use Case

Admin

Client login error

23.1

Code fix

Use Case

Admin

Unable to edit and save changes for Exclude Baseline Managed Package Changes

23.1

Code fix

Use Case

nCino

Deployment getting failed for queued jobs

23.1

Code fix

Use Case

17 December 2023

(ARM v. 23.1.12)

Module

Summary

Fix Version

Resolution

Cause

Deployment

Profile/Permission Set Manager Report not loading

23.1

Code Fix

Use Case

Version Control

ARM and CodeScan integration EZ- Commit validation issue. Feature Flag: USE_MASTER_ANALYSIS_PACKAGE_DIRECTORY

23.1

Code Fix

Change Request

Version Control

A non admin user cannot access the repository under the VC module.

23.1

Code Fix

Use Case

Deployment

Help investigating deployment errors

23.1

Code Fix

Use Case

CI Jobs

Not receiving post activity notifications

23.1

Code Fix

Use Case

Admin

Feedback option change to message. Will require updated documentation.

23.1

Code Fix

Change Request

Admin

[On-premises – Signup for Demo] The registration screen opens when clicking on 'Signup for Demo,' even if the account is already registered.

23.1

Code Fix

Use Case

Admin

[On-premises] Service registration tab, alignment tab not visible properly and, when clicking on the tab, redirects to the logout page.

23.1

Code Fix

Use Case

Admin

Unable to view ‘Credential already exists’ popup under ‘My profile.’

23.1

Code Fix

Use Case

Reports

Previously deleted log showing on other label if created Static Code Analysis label previously deleted SCA label name.

23.1

Code Fix

Use Case

SFDX

When creating the package on a new module for the first time through modularization, Package creation failed with the error ["SaiJun19thprofile: An object 'SaiJun19thprofile' of type Profile was named in package.xml.'] Will require updated documentation.

23.1

Code Fix

Use Case

Version Control

Unable to view committed files in direct EZ revert commit using DX repository.

23.1

Code Fix

Use Case

Deployment

[On-Premises] Getting 'Malformed Id: Null' error displaying for a few seconds when performing a rollback operation for Org-to-Org deployment.

23.1

Code Fix

Use Case

Deployment

[Org Synchronization] ‘SourceOrg,’ ‘Created date,’ and ‘Created by’ filters are not working properly.

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

Code Fix

Use Case

Deployments

ARM API to perform a deployment (or validation or quick deploy)

23.1

Code Fix

Use Case

Version Control

[ARM-SIT] Unable to view branches in SCM history screen

23.1

Code Fix

Use Case

10 December 2023

(ARM v. 23.1.11)

Module

Summary

Version(s)

Resolution

Cause

All Modules

SF CLI Version upgrade to 2.19.8

23.1

No Code Fix

Configuration Change request

Deployment

Experience bundle not properly generated when deploying using release label

23.1

Code fix

Use Case

SFDX

Error creating unlocked package

23.1

Code fix

Use Case

Version Control

CI Job report for Master-to-BackMerge Org Sync_13-Deployment Failed

23.1

Code fix

Use Case

Version Control

Merge shows no modification, but a CI job is triggered

23.1

Code fix

Use Case

nCino

* User is unable to do nCino Feature Deployments * Requires documentation

23.1, 22.3

Code Fix

Use Case

Dataloader

Getting error when clicking on Dataloader configured filter

23.1

Code Fix

Use Case

CI Jobs and Deployments

ARM API to perform a deployment (or validation or quick deploy)

23.1

Code Fix

Enchancement

Version Control

Unable to perform merge for sub-user, getting error to re-login

23.1

Code Fix

Use Case

Admin

On-premise: ‘Proxy Configuration settings,’ ‘Audit logs’ section, and ‘Pool Mgnt" screen tab are missing.

23.1

Code Fix

Use Case

Admin

On-premise: When trying to save the ‘Audit Logs’ section in ‘My Account’ screen, the error “Uncaught TypeError: Cannot read properties of undefined (reading 'showMessage')” is encountered in the console.

23.1

Code Fix

Use Case

CI Jobs

For the 'Create and Install Package' job, when selecting 'Deploy Using Create a Scratch Org and Install Package,' after successfully completing the build, an error is displayed in the log: “this.salesForceOrgDAO” is null.

23.1

Code Fix

Use Case

Admin

Getting ‘null parameters’ error when clicking on save in the user’s section.

23.1, 22.3

Code Fix

Use Case

Version Control

Unable to perform merge request for sub-user getting error to re-login.

23.1

Code Fix

Use Case

Version

Control

Unable to perform branching baseline on sub-user, getting error to re-login

23.1

Code Fix

Use Case

3 December 2023

(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

No Code Fix - Added Loggers

Data

Deployments

Org sync not completing

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

26 November 2023

(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

22 November 2023

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

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

19 November 2023

(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

15 November 2023

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

12 November 2023

(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

5 November 2023

(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

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.

ARM Release Notes 22.3

We would like to inform you about the End of Life (EOL) for ARM version 22.3. Per our support agreement, this version is now more than 365 days old and is no longer supported. As part of our ongoing commitment to providing the best possible experience for our users and maintaining the highest standards of security and performance, we have made the decision to discontinue support for ARM 22.3.

End of Life Date: April 1, 2024

What Does This Mean?

End of Support: As of April 1, 2024, we will no longer provide maintenance updates, bug fixes, or technical support for ARM 22.3. This includes both security and non-security updates.
Security Risks: Continuing to use ARM 22.3 after the end of support date may expose your system to potential security vulnerabilities, as we will no longer release security patches.
Upgrade Recommendations: We strongly recommend migrating to a supported version of ARM to ensure continued reliability, security, and performance. Our team is available to assist you with this transition process and provide guidance on your upgrade.
Accessing Resources: While official support for ARM 22.3 will no longer be available, you can still access existing resources such as documentation, knowledge base articles, and the Knowledge Hub for reference purposes.

Action Required:

To mitigate any potential risks associated with the EOL of 22.3, we urge you to take proactive steps towards upgrade immediately. Our customer success and support team are here to assist you every step of the way. Please reach out to your CSM to plan this work.

We understand that this transition may present challenges, and we sincerely apologize for any inconvenience it may cause. However, we believe that focusing our efforts on our latest offerings will ultimately benefit you with enhanced features, improved performance, and better security.

Thank you for your understanding and continued support.

December 2022 - Version 22.3 - New Features, Enhancements, Improvements and Changelogs

Date of release: 18 December 2022 Article last updated: 31 July 2023

New Features

1. Retention Policy

You can now define a data Retention Policy and choose how much data should be stored for how long. ARM will now be considerably quicker by eliminating outdated data. Clearing out old and useless data from the database and moving it to the archives keeps the application from underperforming and improves speed across all modules.

A weekly clean-up will ensure that the application runs smoothly. The default data retention period is set as 12 months which will be implemented with the release of ARM version 22.3. Admins can specify the duration of data retention in the history tables from the My Account section and change the retention period from 12 months to 6 months or 3 months.

2. Search, Group, and Filter CI Job List

Finding a CI Job has never been easier. Instead of scrolling through endless pages, you can search for a job or a group by simply typing the name in the new dropdown lists. You can further narrow the search results by combining these two options to look for a particular job within a group.

Additionally, the filter feature provides further options to narrow the search results by source type, date range, and more.

3. Ability to Abort a Vlocity Deployment

We just included new functionality to the ARM 22.3 version that allows users to terminate an ongoing Vlocity deployment process or abort it if get stuck. The Deployment History screen contains the Abort option, which allows you to terminate the deployment process.

Enhancements

1. Release Label Revamp

The revamp of the Release Label page is the feature of version 22.3 that stands out the most. This enhancement is actually a collection of multiple smaller enhancements, each of which is briefly discussed in this section.

While creating a release label, you can choose the specific period for which you want to retrieve the commit history instead of loading the entire commit history, which could take a really long time.
You can also create a release label while simultaneously creating a package simply by selecting a conveniently located checkbox on the same screen.
The selected revisions are also displayed on the same screen and updated dynamically as you select/unselect revisions.
Release labels are color-coded on the Release Label Summary screen for easier identification, and the search now provides leaner results.

2. Additional Metadata Support in Search and Substitute

Additional metadata types are now compatible with the Search and Substitute rule, allowing the application to use them for Deployments and Commits.

Until now, the Search and Substitute functionality only had the ability to select a metadata type and then perform the search for substrings across all members in that type. But now, you can select specific metadata members in a type and substitute values for that member(s).

This enhancement is also helpful when users want to add object permissions only to the production and not to the lower sandboxes.

It is also beneficial to have this feature so that the rules can be created and used in CI Jobs to do the replacements automatically, depending on the deployment settings in the CI Job.

3. Additional details in the Users Export List

Export List is a comprehensive list of all registered users with an organization. This list can be downloaded from the Users module. It includes details like the users' name, email, and title; and information about user accounts created, modified, deactivated, and deleted.

With the recent release, the Export List will include a few additional details related to the last login to ensure security and compliance. Details like the location, login type, IP address, coordinates, and the browser used.

The access level of users is not mentioned in the export list for security reasons, i.e., if any users are Admin or Super Admin, this will not be specified. The company can share this list, if required, with people both inside and outside their organization without jeopardizing the confidentiality of the access granted to the users.

4. Dataloader Clone process

In addition to providing a new name, Dataloader users can now specify a different Salesforce org as a source or destination for the operation while cloning an existing job. This helps the users to reuse the same job configuration with a different Salesforce org without going through the entire process again.

For the Extract operation, users have the option to edit the query corresponding to the new org selected. For Insert/Update/Upsert/Delete operations, users have the option to upload a different .CSV file instead of the original one. Validation is done to verify whether the object is available in the new org and also if the user edits the query for the cloned process.

Improvements

The /syncbranchcommits service is no longer supported. The users will no longer require Auto-sync functionality to create a release label. This simplifies the function's use and gets rid of unnecessary steps.
For improved user experience, the metadata.zip file upload option has been added to the New Deployment page itself. When uploading large files, this is extremely useful.
The password policy is reduced from 13 previously used passwords not being allowed to 5 previously used passwords. This gives users more options while resetting their passwords after the three months period or if they forget their password.
Improvements have been made to VC Repo flow as well as to Salesforce Org flow. You can now run scans on a repo or an org to be tagged to the same project and run comparisons so that you have traceability across the scans. The comparison feature allows for every delta scanned to be compared with the baseline. Scans are run on the source, and the results are available in the Reports module. Users can trace the jobs run using the unique identifier. Click to see a few points to note about these improvements.
Super Admin and the user currently logged in are disabled for ALL actions. They cannot be added, deleted, suspended, activated, deactivated, edited, or their roles delegated to other users. Super Admin is displayed at the top of the users' list for easy identification.
The Users module now displays the last login date and time of the users instead of the phone number, and the first and last names appear under the single Name column for better monitoring and tracking.
Super Admin can now enter the desired thread pool count while registering an ARM agent.
Customers can now request for Pendo and Full Story to be enabled or disabled for their instance. Simple toggle buttons to do this are added under the Product Analytics section on the Super User Accounts page. Only Super Admin will have access to this section.
In DataLoader,
- The number of records that are going to be impacted by the specific operation (Extract, Insert, Update, Upsert, or Delete) is displayed as a message before the operation begins and also on the Summary screen as Records.
- Filters have been added to differentiate between the mapped and unmapped fields when auto-map is selected.
- Success and error count of records is displayed while the job is still in progress. Click to read more about these improvements for each of the operations.

Changelogs

28 February 2024

(ARM v. 22.3.55)

Module

Summary

Fix Version

Resolution

Cause

Version Control

Merges are not being fetched when trying to create a release label for Vlocity components.

22.3

Code Fix

Use Case

Version Control

Unable to Commit the Action Overrides in Service Appointment Object

22.3

Code Fix

Use Case

28 January 2024

(ARM v. 22.3.54)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Deployment

Vlocity Deployment issue

QA Passed

22.3, 23.1

Code Fix

Use Case

Version Control

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

QA Passed

22.3

Code Fix

Use Case

21 January 2024

(ARM v. 22.3.53)

Module

Summary

Status

Fix Version(s)

Resolution

Cause

Dataloader Pro

Issue while deploying promotions from QAT to PRD the rule set criteria is compressing the value while deploying it to RD

QA Passed

22.3 23.1

Code Fix

Use Case

Dataloader Pro

Issue on Feature Deployments

QA Passed

22.3 23.1

Code Fix

Use Case

14 January 2024

(ARM v. 22.3.52)

MODULE

SUMMARY

FIXVERSION

RESOLUTION

CAUSE

Admin

After baselining the branch, it did not pull all metadata for development.

22.3

Code Fix

Use Case

Deployments

Deployment status failed when deploying Vlocity components

22.3 23.1

Code Fix

Use Case

10 December 2023

(ARM 22.3.51)

Module

Summary

Version(s)

Resolution

Cause

nCino

User is unable to do nCino Feature Deployments * Requires documentation

23.1, 22.3

Code Fix

Use Case

Admin

Getting ‘null parameters’ error when clicking on save in the user’s section.

23.1, 22.3

Code Fix

Use Case

3 December 2023

(ARM v. 22.3.50)

Module

Summary

Fix Version(s)

Resolution

Cause

Admin

Issue adding user mapping

22.3, 23.1

Code Fix

Use Case

Admin

nCino View Object Failing

No Code Fix - Added Loggers

Data

Deployments

Org sync not completing

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

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

26 November 2023

(ARM v. 22.3.49)

Module

Summary

Fix Version(s)

Resolution

Cause

CI Jobs

Post activities, particular job status showing as FAILED in ARM even job execution completed with succeed

22.3

Code Fix

Use Case

Admin

Getting empty Configuration under "Configure Default SCA Baseline Branches"

22.3

Code Fix

Use Case

Admin

Able to view empty role under permissions

22.3

Code Fix

Use Case

19 November 2023

(ARM v. 22.3.48)

Module

Summary

Fix Version

Resolution

Cause

Deployments

In sub-user, unable to get the branch in Salesforce Org Mappings section in SF Org Management screen if Admin user given only admin module permission.

22.3

Code Fix

Use Case

Deployments

Deployment tab - Redeploy/Promote issue

22.3, 23.1

Added Loggers

Data

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

15 November 2023

Module

Summary

Fix Version

Resolution

Cause

Deployments

Page unresponsive in new deployment for "previous deployment" as source type

22.3

Code Fix

Use Case

12 November 2023

(ARM v. 22.3.47)

Module

Summary

Fix Version(s)

Resolution

Cause

nCino

User is unable to create Feature Migration Template on Debt Schedule object.

22.3, 23.1

Code Fix

Use Case

5 November 2023

(ARM v. 22.3.46)

Module

Summary

Fix Version(s)

Resolution

Cause

All Modules

New User Creation

22.3

Code Fix

Change Request

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 set: 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

27 October 2023

(ARM v. 22.3.45)

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 Environment Provisioning module in version 22.3 to enable users to view Environment Provisioning templates.
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 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 a maintenance release. The following items were enhanced, fixed, or added by code fixes resulting from use-case scenarios:

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.

22 October 2023

(ARM v. 22.3.44)

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

Implemented an enhancement to version 22.3 identified as part of a use-case issue affecting the Deployments and Org Synchronization modules requiring changing deploy text for validations.
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.
Added loggers to version 22.3 affecting the Version Control module due to a use-case error with user roles missing.
Added loggers to version 22.3 affecting the CI Jobs module resulting from a use-case with automated package generation CI job AR server exception error.
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 v22.3.43)

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

8 October 2023

(ARM v22.3.42)

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 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 v22.3.41)

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 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 to versions 22.3 and 23.1 due to a data error affecting the reports module, in which a user was getting an error message when executing a static code analysis (CodeScan) report.
A code fix was applied to version 22.3 in the version control module pertaining to a use-case error with changes not getting fetched via autodraft after reverting a commit.
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.
A code fix was integrated to the version control module in version 22.3 after a data error caused by a feature template migration issue. The feature flag is MERGE_SKIP_AUTORESOLVE_CONFIGURATION_FILES.
A code fix to version 22.3 was implemented affecting all modules from a data error when setting up SFDX deployment.
A code fix was applied to the version control module in version 22.3 resulting from a use-case error with an ARM commit comment label error.
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 v22.3.40) This is a maintenance release. The following items were enhanced, fixed, or added:

A code fix was implemented due to a use-case error to the Version Control module regarding an issue with merging destructive changes.
A code fix was applied to the Deployment module due to a data error concerning an Org difference pulling changes from the managed packages.
A code fix was applied due to a use-case error relating to the Deployments module with a user unable to deploy components via Org Sync.
A code fix was applied pertaining to the CI Jobs module relating to a use-case error in which the CI Job has two different package directories and changes fall under one package when an analysis is completed on CodeScan
Performed a code fix relating to a use-case error in on the Deployments module in which a deployment bug with multi packags and static resource was bugged.

17 September 2023

(ARM v22.3.39) This is a maintenance release. The following items were enhanced, fixed, or added.

A code fix was implemented to the Deployment module related to a use-case error encountered when deploying Vlocity components from a Git branch.
A code fix was implemented related to the CI Jobs module to institute best practices following a user session.
A code fix was implemented to the Version Control module related to a use-case error pertaining to [integration_EZ-commit]. User was getting a "no package .xml found to retrieve the members" through package manifest when selecting 'all users or the respective SF org user.'

10 September 2023

(ARM v22.3.38)

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

As part of this fix deployment, one of the feature flags, 'RUN_PACKAGE_JOB_ENTIRE_BRANCH_78757,' has been provided. Enabling this feature flag only applies to one specific customer.
Implemented a code fix associated with the version control module for a use-case error in which ALM working items were not loading.
Implemented a code fix for a use-case error pertaining to the version control module for an approval email notification error.
As a result of a use-case error relating to a feature template migration issue, a new feature flag has been provided, 'MERGE_CONFLICTS_AUTORESOLVE_CONFIGFILES_USINGSOURCE,' which must be enabled for one specific customer only: More details are provided in the ticket itself.
Implemented a code fix related to a use-case error where the AutoRABIT deployment initiated using Org Synchronization fails. This error pertains to the Version Control module.
Implemented a code fix related to the CI Jobs module related to setting up SFDX deployment, with the Feature Flag:
RUN_PACKAGE_JOB_ENTIRE_BRANCH_78757
Regarding one ticket, 'Setting up SFDX Deployment': Only for the 'Create and Install an Unlocked/Managed Package Version from a Version Control Branch' CI, type in the CI Job configuration. When selecting the 'Trigger build on commit' option, we have hidden the 'Process commit revision received via hook only' sub-option. This change will be incorporated into our documentation. Further details are available in the ticket itself.
Implemented a code fix related to the nCino module error:
LLC_BI__Schedule_Section__c migration issue#1
Implemented a code fix related to an internal ticket in ARM, in which the user was not able to migrate related data using the Dataloader test environment setup module.
Implemented a code fix related to the Deployment module for an EBR Manual Asyncid XML Copy Automation error.

3 September 2023

(ARM v22.3.37)

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

Implemented a code fix associated with the version control module related to a use-case scenario in which a review artifact was not working.
Implemented a code fix to the nCino module resulting from a user product suggestion to the deployment history filter.
Implemented a code fix to the nCino module related to an instance in which the org name was not displayed for the destination org value field.

27 August 2023

(ARM v22.3.36)

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

Error: "Merging from Devint branch to Developer branch (Back merge) is getting Auto Rejected": Code fix to Version Control module on user merging from Devint branch to Developer branch (Back merge) getting Auto Rejected.
Implemented a UI change to include the “Ignore Warnings” option in both the prevalidation commit and merge flows. This requires a documentation change. See ticket for more details.
Error: “[Client] getting frequent page unresponsive errors in ARM": Introduced a UI change to support Salesforce orgs and the previous label deployment type in the deployment module.
Performed a code fix affecting the Deployments module related to a use-case error with the client getting frequent page unresponsive errors in ARM. This also requires an update in our documentation. Further information is in the ticket.
Error: “Branching baseline is not picking all components from production": Based on the customer-confirmed downtime window, it was necessary to enable the "METADATA_API_TO_DX_CONVERSION" feature flag for this fix deployment.
Performed a code fix concerning the Admin module due to an error with a branching baseline not picking all components from production with feature flag error: ‘METADATA_API_TO_DX_CONVERSION’.
Error in CodeScan Plugin pop-up window where the user was unable to type text in Org key drop-down selection field, which required a code fix to the Admin module. (Internal ticket)
Performed a code fix related to a use-case error during Vlocity deployments showing "NoOrgFoung" after activation of LWC components. Fix applied to the CI Jobs and Deployment modules.
Code fix applied to SFDX module for the user receiving an error message showing login failed. Also related to CI Jobs, scratch org creation was being struck in progress and not able to be deleted.
Applied a code fix for the Version Control module related to a user being unable to select the ALM side, getting a JAVA error.
Initiated a code fix to the Deployments module related to an error during an EZ deployment from a single revision with profiles and comp-specific changes pulling all comps.
Executed a code fix to the Deployments module on a use-case error affecting an AR deployment initiated using Org Synchronization failing.
Applied a code fix related to the following use-case error: [Cijobs-DXModulePckagecreation] facing the "["An unexpected error occurred while preparing endpoint: null. Please contact Salesforce Support and provide the following error code: 795089467-5806 (-1215335089)"].
Initiated a code fix to the nCino module for a client use-case error concerning spread template issues.
Performed a code fix for a customer use-case scenario regarding an error related to an nCino CI job deployment issue.

20 August 2023

(ARM v22.3.35) This is a maintenance release. The following items were fixed and/or added:

Performed a code fix impacting the Deployments and CI Jobs modules related to use cases in which selected test classes for production were not running and users were having code coverage issues.
Performed a code fix for the Admin module related to a specific user having difficulty with PWD policy.
Performed a code fix to the CI Jobs and Deployment modules relating to users unable to deploy changes to production orgs due to a CI Jobs coding issue.
Performed a code fix to the CI Jobs module related to an error message as login failed.
Performed a code fix on the CI Jobs module pertaining to Vlocity SFI components not compiling LWC on destination orgs when deploying via CI Jobs.
Performed a code fix related to the CI Jobs module for CI Job not starting according to schedule.
Performed a code fix related to the CI Jobs module to resolve an error related to setting up SFDX deployment and CI Job configuration.
Performed a code fix to the nCino module for an error in which the screen template failed with a malformed query exception.

13 August 2023

(ARM v22.3.34)

This is a maintenance release. The following items were fixed and/or added:

Performed a code fix pertaining to all modules relating to an SFDX to SF CLI Hotfix.
Performed a code fix relating to version control, CI jobs, and deployment modules initiated via change request due to ALM working items not loading, resolved by enabling the customer domain name.
Performed a code fix for a data error with feature flag name, ‘Disable_Merge_Rename_Detection’ after a merge was failing and took hours to complete.
Performed a code fix for the version control, CI jobs, and deployment modules pertaining to a data error, validation failing for the LWC component despite no error message being displayed in the logs.
Performed a code fix related to a use-case error in the version control module pertaining to a commit showing a “no modification” error.
Performed a code fix related to a use-case error affecting the version control, CI jobs, and deployment modules caused by an error merging a commit from the dev environment to the INT environment.
Performed a code fix to the version control module resulting from a use-case error where the commit was incorrectly showing “no modification”.
Performed a code fix related to a data error pertaining to the version control module, when Jira integration stories redeploy post sandbox refresh.
Performed a code fix for a use-case error in the deployment module related to filter-based retrievals not working when applying the ‘created by,’ ‘modified by,’ ‘created date,’ and ‘modified date’ filters.
Performed a code fix related to a performance issue in the nCino module pertaining to Spread Template issues.
Fixed an error in the deployment module when ‘Run Specified Tests’ is selected from the Apex Test Level dropdown.
Rather than a code fix, a customer-specific utility was provided to address SSO login issues in the admin module. This particular utility only works in versions 22.3.9 or lower for one individual customer.

06 August 2023

(ARM v22.3.33) This is a maintenance release. The following items were fixed and/or added:

Fixed an error under reports where code coverage emails were missing information.
Fixed an error related to a second deployment starting in the middle of a deployment.
Fixed an error in version control module related to not being able to commit or Repush changes in the Training Branch.
Fixed an error in version control module related to a feature flag: USE_PATCH_LOGIC_IN_EZCOMMIT for Code overwritten (feature not enabled by default).
Fixed an error for CI Job module where ALM-enabled failed due to Unparsable date error.
Fixed an error concerning multiple CI Jobs failing due to data error.
Fixed an error related to the Deployment, CI Jobs, and Version Control modules occurring when merging a commit from dev environment to INT environment.
Fixed an error related to deployments getting frequent page unresponsive errors in ARM.
Fixed an error under the Admin module relating to being unable to select the revision number while creating the Tag.
Fixed an error for Create and Install Package CI job deployment failing if having multiple package directories on the branch.
Fixed an error under the Admin module, My Account >> Merge Settings: Not visible Border for "Notify All Criteria Overwrites To" field.
Fixed an error under the Admin module, which enabled Domain names to be visible in the inspect mode.
Fixed an error in the nCino module related to [ARM-QAN] attachments’ deployment Failed with Bulk API.
Fixed an error in the nCino module related to a Pricebook entry.
Fixed an error related to the nCino module with scheduled Job not showing up in UI after completion due to Deploy Status Not Updated.
Fixed an error related to the nCino module with a CI Job Edit not populating with scheduled time details.

30 July 2023

(ARM v22.3.32) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with duplicate not working on EZ-merge requests related to version control.
Fixed EZ deployments from a single revision with profiles comp-specific changes pulling all comps during deployments.
Fixed an error related to CI Jobs not running the pipeline.
Fixed situations with both version control prevalidation commit and merge where static code analysis processes are stuck in an In-progress state when VNC is not started.
Helped generate the reports for CI/CD pipelines for nCino reports.
Performed Jira integration story’s redeploy post-sandbox refresh in version control.
Fixed a specified metadata type is unsupported: [processflowmigration] error in CI Jobs.
Set up the SFDX Deployment in CI Jobs.
Fixed an error with a CI Job not identifying changes.
Fixed an error related to BHG with CI Job webhooks failing to trigger.
Performed nCino AR template updates.

23 July 2023

(ARM v22.3.31) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with a merge use case of handling deleted files in both source and target branches by using git rm command.
Fixed an issue where screen redirects to login page on clicking on User activation email.
Fixed an issue where Commit stuck in InProgress.
Fixed an issue where we receive “JAXB marshall/unmarshall exception” while getting directed to CI results screen.
Fixed an issue where Release labels are taking 30 minutes or more to be available for repository in Version control.
Fixed an issue where Merges are taking a long time to complete in version control.
Fixed an issue where components selected on review component pages were being repeated in the next category in Version Control.
Fixed an issue where same name should be reflected instead of Commit showing a different name in Bitbucket in Version Control.
Fixed an issue where JIRA ALM Filter mappings not working in My profile & Version Control.
Fixed an issue where the Login rate exceeded error on the Salesforce Integration user.
Fixed an issue where Backup to Version Control is not backing up Matching Rules in Salesforce in CI jobs.
Fixed an issue where the shared server with common DB creates another customer weekly report in another server.
Fixed an issue where Custom field property didn’t deploy in CI Jobs and Deployment.
Fixed an issue where Diff report is not generated in New Deployment Module.
Fixed an issue where Unsupported metadata template execution is failing in Sandbox Refresh in Environment Provisioning module.
Enhanced DataLoader uber jar upgrade to 58.0.3.
Fixed an issue where we are facing Record Configuration Time Out in nCino.
Enhanced UI in Post Deployment activities result page in CI Job – nCino.
Enhanced the View details page not being visible unless post-deployment activities are completed – nCino.

18 June 2023

(ARM v22.3.26) This is a maintenance release. The following items were fixed and/or added:

Enhanced ARM by allowing PAT Authentication for Jira.
Fixed an issue where user ran an Org Synchronization history job and tried to access the Diff report to see the metadata difference, but the page kept loading indefinitely without the required diff.
Upgraded Provar to version 2.10.1.
Fixed an issue where the Approval option wasn't functional for L1 Approvers, and the Org Admin couldn't bypass the approval gate on EZ-Merge.
Fixed an issue with nCino where user created a Feature deployment task, but the jobs were stuck the queue.
Introduced a new feature in DataLoader called Hard Delete which can be used to delete the data completely and permanently instead of sending it to the Recycle Bin of the org.
Fixed an issue where CI Job build history was not displaying the results and throwing a blank page instead.
Fixed a UI bug where Abort option for CI job was displaying even after the build was successful.
Fixed an issue where duplicate ALM Commit entries were Displaying while performing ALM Commit with Vlocity repository.
Fixed an issue where the CI edit configuration screen was taking longer to load than expected before throwing Page Unresponsive alert.
Fixed an issue with DataLoader Pro where user created a new job and applied filter, but the source and destination orgs are taken from history page.
Fixed an issue with DataLoader where Insert operation bulk API selection was resulting in console error message serializeToString.
Fixed an issue where Vlocity metadata components were getting expanded on the Finish page.

11 June 2023

(ARM v22.3.25) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where deployment failed with the error message File cannot be loaded.
Fixed an issue where the SharingCriteriaRule component was not deployed to Production even though the user had selected it ().
Fixed an issue where the SharingReasons component was ignored when the deployment/validation was done using Commit Label as source, but the same component was processed using Single Revision deployment or CI Job deployment ().
Fixed an issue where user was trying to create an connect an Active Directory but it kept failing ().
Fixed an issue where user was migrating a field value with Rich Text Area Field type but it was not reflecting in the target org as expected. Hyperlinks, font size, etc., were not migrated as present in the source Salesforce org ( and ).
Fixed a UI bug where Deployment Failed line was displayed twice in the logs for failed deployments (internal ticket).
Fixed an issue where admin was unable to release a user from a team (internal ticket).
Fixed an issue where Null Values were displayed on the ALM Labels screen as well as the ALM Details tab on the respective ALM Commit Label Details screen (internal ticket).
Fixed an issue where selected files for DX Commits were not displayed in the File Changes tab, and after the commit it was showing as No Modifications (internal ticket).

04 June 2023

(ARM v22.3.24) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where a CI job failed to pick the external commit revision which was added to an ALM Label as part of Smart Commits sync ().
Fixed an issue where Class Coverage Report generated was empty for one of the Salesforce orgs, and it was intermittent. The same behavior was observed for RunSpecified and RunLocal test levels ().
Fixed an issue where deploying test classes from manual deployment was throwing an out of memory error ().
Fixed an issue where BackUp to Version Control CI Job was failing due to too many retrieval error messages even though the Bulk API option was enabled ().
Fixed an issue where while performing any commit, Pull Request enabled CI Job was triggering as expected; but its Build and Deployment status was not added in the Comments in Bitbucket ().
Fixed an issue where EZ-Commits were stuck with In-progress status for a few hours before failing. But the commit revisions were generated at the repository level and updated in ARM database ().
Fixed an issue where the Git author was overridden by ARM ().
Fixed an issue with DataLoader where user was unable to create an Update job because the functionality prompoted user to select the Required field within the Mapping Fields ().
Fixed an issue with DataLoader where user was getting a script error in the console while editing an existing old job (internal ticket).
Fixed an issue where Destructive commit for DX was not working as expected for Documents, Reports, and Dashboards types (internal ticket).
Fixed an issue where the Layout file was not displayed in the Review Artifact screen after resolving the layout duplicates (internal ticket).
Fixed an issue where 4 CI jobs were running parallelly even though the parallel process limit was 1 on the external agent (internal ticket).

28 May 2023

(ARM v22.3.23) This is a maintenance release. The following items were fixed and/or added:

Fixed a compliance issue with Apache Commons by removing the text dependency ().
Fixed an issue where CI Jobs were failing due to empty JSON file(s) in the remote repository, and throwing the following error: Failed to initiate deployment. Unexpected end of JSON input ().
Improved the UI by removing the Validate Deployment option if Vlocity is selected, and hiding the whole Board Type option if Vlocity is not enabled ().
Fixed an issue where user was performing CI jobs for Validate and Deploy for a successful commit, but only validation was performed but not the deployment ().
Fixed an issue where CI job deployment was failing because the build was picking duplicate Layout values ().
Fixed an issue where unwanted metadata changes were observed in the package.xml file while performing a commit ( and ).
Fixed an issue where Branching Baseline was not picking all the components from production ().
Enhanced DataLoader by adding related objects and the fields of those objects displayed, so you can select the required fields of the related objects in the filter criteria and edit the query through SOQL editor ( and ).
Fixed an issue with nCino where CI jobs that used a Deployment from Version Control were failing when the build was triggered ().
Improved the New Merge screen by adding Layouts text in the Skip Flow /Profile/ Perm.Set Access-Setting Duplicity Check option (internal ticket).
Fixed a UI bug where SF Org Test Connection notification message was displayed on an unrelated module (internal ticket).
Removed the option to sign up for a 30-day Salesforce trial while registering a DevHub as the trial offer is no longer applicable (internal ticket).

21 May 2023

(ARM v22.3.22) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where wrong timezone region was displaying for users ().
Fixed an issue where the EZ-Commits report file displayed the file count but not the components count ().
Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ().
Fixed an issue where CI job build failed to show changes in the org after deployment ( and ).
Fixed an issue where CI job to generate Code Coverage Report was not reflected in the org or in the e-mail notification ().
Fixed an issue where merge status is displayed as completed but no revision is generated, and the merge is not available in the UAT branch ().
Enhanced DataLoader by adding the ability to field mapping through the lookup fields ().
Fixed an issue with DataLoader where while running an Extract job on the PUBLISHER object, the job was failing with the following error Publisher: column id is not supported in ORDER BY clause ().
Enhanced the nCino filter criteria by adding the ability to search and filter labels using the whole or partial name ().
Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).

14 May 2023

(ARM v22.3.21) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was having trouble while deploying LighteningMessageChannel components ().
Fixed an issue where Destructive Changes wasn't working as expected while performing an Entire Branch merge ().
Enhanced the ALM management feature by adding an option to sync Smart Commits ().
Fixed an issue with CI Jobs Destructive Sharing Rule was not deploying to the Salesforce org ().
Fixed an issue where user could not disable the Smart Commits-Sync option for a repository branch in the VC repos section ().
Improved the New Merge screen by removing the Validate Deployment option from the UI if Vlocity is selected ().
Enhanced the Credentials module by adding SSH Cetificate option for Git Authentication ().
Improved Release label creation by requiring at least two revisions to be selected (internal ticket).
Fixed an issue where Classic SF Org URL with a slash at the end of the URL redirects to the 400 error page, and for a Lightning SF Org URL without a slash gives an OAuth Authentication Failed error message (internal ticket).
Fixed an issue with nCino where user was getting a NullPointerException on Saving Permissions using Bulk Assignment (internal ticket).
Fixed an issue with CI Jobs where all the scheduled timings were not displayed in the Preview & Save page (internal ticket).
Fixed an issue with Dataloader where user was able to upload a 900 MB file despite the limit being 100 MB, causing the process to hang (internal ticket).
Fixed an issue with Dataloader where sever crashed after user performed an Extract operation from an SF org which had Account Object with 2 million records (internal ticket).

07 May 2023

(ARM v22.3.20) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was getting a validation deployment error while performing release label deployment ().
Fixed an issue where Branching Baseline was taking longer than expected ().
Fixed an issue where using the AutoDraft functionality in EZ-Commit was resulting in a malformed exception in the UI ().
Fixed an issue where Branching baseline was not picking all components from production ().
Fixed an issue where prevalidation merge failed with empty metadata package even though there were changes in File Diff ().
Fixed an issue where entire ARM application was down temporarily ().
Fixed an issue where Merge was auto-rejected due to an empty package because the metadata folder path not being specified under branch settings ().
Fixed an issue where user was using the Bulk Assignment feature to assign Sandbox permissions on the Permissions page but encountered the following error: Java.lang.NullPointerException ().
Fixed an issue where users weren't receiving SCA reports by email even though the reports were running ().
Fixed an issue where while performing new EZ-Commit, user edited one line using review artifact option but Diff did not capture the same ().
Fixed an issue where if CI Jobs were added in a queue with Scheduled jobs, then not all jobs were displayed in the queue (internal ticket).
Fixed an issue where existing revision file related delta still existed in agent even after uploading to rabitserver (internal ticket).
Fixed an issue where release label creation was failing when user tried to create package manifest and aborted and refreshed the label for DX repo (internal ticket).
Fixed an issue where Super admin user was getting a blank popup screen while trying to click on the Register Agent button from the Pool Mgmt screen (internal ticket).

30 April 2023

(ARM v22.3.19) This is a maintenance release. The following items were fixed and/or added:

Enhanced the Version Control module by adding SSH Certificate for Git authentication while creating user credentials ().
Fixed an issue where CI Job was picking changes one build but not for the other, and the logs weren't capturing this ().
Fixed an issue where Ignore missing visibility settings function was not working as expected and Record type visibility on the profile was not getting deployed using CI Job ().
Fixed an issue where user merged a new component using a single revision merge but the merge missed to perform a CodeScan analysis ().
Fixed an issue where user was unable to commit the destructive Email Template files as part of commit in SFDX format and getting auto failure ().
Fixed a UI issue where OK button to reject an EZ-Merge was not working ().
Fixed an issue where a field was available in the package but still Validation was throwing error that the field was missing ().
Fixed an issue with DataLoader where multiple jobs were not processing parallelly when user loaded a large number of jobs to the queue ().
Fixed an issue with nCino where user created more than 100 jobs with sub-user but was still getting the following error: No jobs exist to load ().
Fixed an issue where Release Label artifact was not displaying metadata types in the Destructive changes tab for DX repos, but was working as expected for non-DX repos (internal ticket).
Fixed an issue where new jobs are getting added to the queue but not getting triggered, and later throwing NullPointer Exception (internal ticket).
Fixed an issue where Rollback button was not enabled for the first job if that job is came from a queued list (internal ticket).
Fixed an issue where ALM CI Job and Release artifact execution was happening at the same time, and the CI Job build was failing (internal ticket).
Fixed an issue where an empty pop-up was displayed when user tried to edit the existing CI jobs label for Sub-User (internal ticket).
Fixed an issue where if Validate only CI job came from the queue, then direct deployment was executing for that job instead of validate deployment (internal ticket).
Fixed an issue where duplicates revisions were being added to the list while creating the release label when user unselected and reselected the same revisions. (internal ticket).
Fixed an issue where Vlocity revisions were not displaying while user was trying to edit a release label (internal ticket).
Enhanced the Release Label creation page by adding options to the Vlocity label type which were only available for Salesforce revisions before (internal ticket).

23 April 2023

(ARM v22.3.18) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the SCA Report failed to run using Codescan plugin with the below Salesforce error: UNKNOWN_EXCEPTION: An unexpected error occurred. ( and ).
Enhanced the VC Repos page by introducing a feature that allows users to sync external smart commits ().
Updated the UI on the External pull request creation page to reflect the Source and Target fields clearly so users can trace which one is the source and destination branches ().
Fixed an issue where duplicate entries were created in different lines during the Merge process and user wasn't able to remove the duplicate field without clearing the layout tag as well ().
Fixed an issue where the baseline branch is not displayed during Static Code Analysis job creation if the branch name contains spaces in the Reports module ().
Enhanced deployment in ARM by providing a new option Rollback on error in merge pre-validation. This checkbox allows users to choose if deployment should proceed with remaining components in case of errors ().
Fixed an issue with nCino where CI job filter changes on templates were not taking effect after saving ().
Fixed an issue where user created a baseline revision job with the Automation Sanity repo and triggered the build but it failed without any error (internal ticket).
Fixed an issue where user could not fetch the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes as an option (internal ticket).
Fixed an issue where error 405 in the build and deployment logs didn't display further details in the UI log (internal ticket).
Fixed a UI bug where dropdown selection in Reports > CodeCoverage Reports was not working after refreshing the page (internal ticket).
Fixed an issue where Release Label artifact was not displaying metadata types in the Destructive changes tab for DX repos, but was working as expected for non-DX repos (internal ticket).
Fixed an issue where user was unable to revert the commit if a previously reverted commit was deleted while in Conflict state (internal ticket).

16 April 2023

(ARM v22.3.17) This is a maintenance release. The following items were fixed and/or added:

Enhanced the SCA report options by removing the 10,000 limit for exporting issues using CodeScan ().
Enhanced Vlocity CI jobs by allowing Local Compilation for Omniscript and Flexcard objects ( and ).
Fixed an issue where user was unable to use the Redeploy/Promote option after ten iterations of an existing Deployment label ().
Fixed an issue where user was trying to commit System Permissions which were enabled in Salesforce org, but while performing EZ-Commit, file Diff is not getting generated and the system permissions are not getting committed ().
Fixed an issue where ALM label merge option was not working in EZ-Merge feature. This happened only when the ALM Label contained / in it ().
Fixed an issue where EZ-Merge was failing with NullPointerException ().
Fixed a recurring issue of ARM overwriting the Salesforce Org - Default Apex Test Class Configuration by adding a checkbox Do you want us to update the test classes? ().
Fixed an issue where Revert commits were failing without any error messages ().
Fixed an issue where user created a Release label with multiple commit revisions, each with dependency components, but the revisions were not displaying in the right order in UI ().
Fixed a UI bug where when user unchecked Validate deployment option in EZ-Merge, the Run destructive changes checkbox was hidden ().
Fixed an issue where when user had files in conflicted state, selecting the ALL checkbox was not working and user had to click on each file to resolve conflicts ().
Fixed an issue where the NPM repository Access Key wasn't saving after clicking Save, causing the Local Compilation to fail (internal ticket).
Fixed an issue where comments lines were not executed in Metadata when there were spaces in the comment line in merge flow (internal ticket).
Fixed an issue where an empty popup screen is displayed while resolving conflicts in case of malformed file (internal ticket).
Fixed an issue where improper validation message is displayed after clicking on Resolve Duplicates without selecting any files to resolve (internal ticket).
Fixed an issue where SSO user's org was not deleted from the Security-Context XML (internal ticket).
Fixed an issue where the API Token status was marked as Never Accessed, despite the API being in use already (internal ticket).

09 April 2023

(ARM v22.3.16) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where validation jobs on Pull Requests weren't getting triggered (, , and ).
Fixed an issue where Salesforce components were showing under the Apex Test Success tab in the Deployment module, which is not expected behavior ().
Enhanced the Branching Baseline feature by allowing admin to define default baseline branches, making it easier for developers to choose the default branch for each project ().
Fixed an issue where user was unable to register a branch even though Test Connection was successful ().
Fixed an issue where ARM wasn't fetching the ApexClass Tests related to ApexTriggers upon selecting Run Tests Based On Changes option ().
Fixed an issue where SCA Report failed to run using Codescan plugin with the following Salesforce error: An unexpected error occurred. Please include this ErrorId if you contact support: 384187622-16951 (-673032061) ( and ).
Fixed an issue where triggered CI jobs were either failing due to an error No Such File or Directory found, or getting aborted automatically after some time and logs weren't printing at the back end (, , , , , and ).
Fixed an issue where triggered CI jobs were taking too long to build, and also slowing down ARM altogether ().
Fixed an issue where if the file name contained spaces, Commit Validation via VS Code plugin was unable to detect the file ().
Fixed an issue where Search & Substitute was not updating the value for a custom label in the SF org ().
Fixed an issue where there was a discrepancy between the changes captured in the ARM Diff and the repos in BitBucket ().
Fixed an issue where the SF org URL is not displaying the updated one under Profile ().
Fixed an issue with nCino where CI job filter changes on templates are not reflecting after saving ().
Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).

02 April 2023

(ARM v22.3.15) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Custom Metadata type access changes were not detected in version control Diff. There was no diff generated even there were changes in metadata access ().
Fixed an issue where user performed a CI job deployment that had 8 destructive change items in the merge PR, but ARM is displaying only 2 destructive changes ().
Fixed an issue where Git backup job was failing due to unsupported metadata ().
Fixed an issue where scheduled CI jobs were getting queued or not getting triggered as per schedule ().
Fixed an issue where Quick action was not picked for destructive changes ().
Fixed an issue where while running the scan from ARM for the version control branches are failing because .java files were present in the current repository ().
Fixed an issue where user using non-SFDX repo with Custom API enabled failed to pick the changes in the CI job ().
Fixed an issue where Release label displayed commit revisions older than 30 days even when the No. of days filter was set as 30 ().
Fixed an issue where a user had trouble creating artifact for a release label ().
Fixed an issue where there are Vlocity components in Merge Validation, and the validation deployment should bypass and process the merge; instead it is Auto-rejecting as criteria were not met ().
Fixed an issue with Dataloader where a job completes with No records status whenever attachment and content version are selected as child objects in the parent cccount object ().
Fixed an issue with nCino where CI job build status is displayed as Completed for a failed job ().
Fixed an issue with nCino where attachements to nFORMS__Form_Template__c failed to get deployed ().
Fixed an issue where user was unable to initiate static code analysis on a Salesforce Org ().
Fixed an issue with New EZ- Commit where while using Custom YAML file the page was taking much longer to load than usual ().
Fixed an issue where Merge was happening on incorrect files ().
Fixed an issue where for DX repo, Custom field destructive Deployment was failing with the error Package generation without a valid package directory cannot be processed (internal ticket).
Fixed an issue from the VS Code where Static Code Analysis report was not getting executed on the selected files and report generated (internal ticket).
Fixed an issue where Release Label creation with SVN Repo was not successful, and throwing the following errors (internal ticket):
- Supplied AttributeValue is empty, must contain exactly one of the supported datatypes (Service: AmazonDynamoDBv2; Status Code: 400; Error Code: ValidationException; Request ID: a59c77cb-67ad-4a58-80b4-364feb5a4d6c; Proxy: null)
- No Version Control Mappings found for Repo: {} and Branch: {}. Please update it in My Profile
Fixed an issue where Merge was not Auto-rejected after UI logs displayed Mock deployment is failed, so auto rejecting the merge (internal ticket).
Fixed an issue where Revision in Vlocity release label was not getting selected after you clicked save (internal ticket).
Fixed an issue with nCino where user was getting an exception while creating a CI job, and user was selecting the same VC Repo/Branch for multiple times (internal ticket).

26 March 2023

(ARM v22.3.14) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Quick action was not picked for destructive changes ().
Fixed an issue where CI job deployment was failing due to the following error: Error: Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field (line 0, column 0) ( and ).
Fixed an issue where WebStoreTemplates object was not available for deployment ().
Fixed an issue where Merge Request XML file was conflicting with an error No conflict data found for this block ().
Fixed an issue where Release label failed while creating the artifact ().
Fixed an issue where Prevalidation EZ-Commit shows that Diff does not exist even when there are changes. If user tries multiple times, then Diff is displayed sometimes ().
Fixed an issue where user was unable to merge the code from one branch to another branch. ().
Fixed an issue where Ignore Missing Visibility settings not working on EZ-Merge validation ().
Fixed an issue where user was loading multiple DataLoader jobs but it was not processing parallelly ().
Fixed a UI bug in nCino where the header in template details section was missing in Feature Deployment (internal ticket).
Fixed an issue with nCino where Deployment Logs were not displayed when the CI Job failed (internal ticket).

19 March 2023

(ARM v22.3.13) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where CI job deployments were failing with the error, Error 405 Only POST allowed ().
Fixed an issue where multiple deployment requests were being generated while performing Org Sync if the user selected all components instead of a few ().
Fixed an issue where Rollback API threw a 200 response but the Rollback immediately failed in the ARM UI ().
Fixed an issue where SCA report Failed to run using the Codescan Plugin with the following Salesforce error 384187622-16951 (-673032061) ().
Fixed an issue where users were having trouble logging in to ARM due to an error Session Invalid (, , and ).
Fixed an issue where after upgrading to ARM version 22.3 user was unable to approve EZ-Commits that were pending approval in the 22.2 ().
Fixed an issue where Auto-draft was taking much longer than expected to retrieve the metadata in EZ-Commit (, , , , , , and ).
Fixed an issue where user was trying to resolve a conflict in EZ-Merge but was getting a message on the UI that there are no conflicts ().
Fixed an issue where Branching Baseline job does not delete files in static resources sub directories even though the user has selected the Delete existing metadata and commit new changes option ().
Fixed an issue where user was unable to retrieve MutingPermissionSet using the SFDX repository ().
Fixed an issue where the Release Label failed while creating the artifact ().
Fixed an issue where Sharing Rule Set metadata type was found in the Deployment module but not in the Version Control module ().
Fixed an issue where the user performed a merge and approved both level 1 and level 2 reviews but was unable to approve the merge ().
Fixed an issue where errors were occuring while performing Delete Org (internal ticket).
Fixed an issue where for Build only job source from VC with DX repo, if Master Details Object Change is included in the build, we're getting No Modifications even if changes exist (internal ticket).

12 March 2023

(ARM v22.3.12) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Static Code Anaysis was failing due to missing property tag in Apex PMD rules file, but the UI log wasn't displaying this error ().
Fixed an issue where when there was no results generated, the report displayed an error that there are zero metrics instead of displaying the results as zero in all the places when there is no change ().
Fixed an issue where user was unable to deploy a CI job with the RelationshipGraphDefinition components ().
Fixed an issue where Validate deployment was displayed as failed in UI and the database, but was successful as per the logs ().
Fixed an issue with Review Artifact where similar custom fields from different objects were not populating correctly and switching to other fields ().
Fixed an issue where multiple fields of the respective custom objects were getting selected parallelly while performing edit or save or exit operations on the Review Artifact screen (internal ticket).
Enhanced ARM by adding an option for multiple ARM instances to share a single database cluster (internal ticket).

05 March 2023

(ARM v22.3.11) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where ARM was displaying incorrect installation settings and package version information in the deployment log while installing the package version from a CI job ().
Fixed an issue where user chose Exclude Metadata Type for a particular metadata type during a CI Job, but it was still deployed ().
Fixed an issue where user was unable to perform Destructive Commit with PermissionSetGroups metadata type ().
Fixed an issue where users weren't receiving emails after setting up Mail Settings ().
Fixed an issue where there was a discrepancy between EZ-Commit and Commit templates while retrieving Email Template metadata members ().
Fixed an issue where Merge Labels were taking much longer than expected ().
Fixed an issue where user tried to commit the changes without validation and UI displayed an error Another commit is in progress ().
Fixed an issue where user was creating credentials for JIRA in ARM using JIRA Token and but application wasn't allowing more than 150 characters while JIRA Token should allow up to 192 characters ( and ).
Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the Commits History page ().
Fixed an issue where Merge was not auto-rejected when validation criteria was not met ().
Enhanced nCino by adding an option to specify Baseline Revision in Continuous Integration for Version Control to perform feature deployments ( and ).
Enhanced nCino by allowing users to deploy nCino CI build to multiple target sandboxes ().
Fixed a UI bug where incorrect notification was displayed in certain components pages when template was created using one org and was used by another org (internal ticket).
Fixed an issue where Baseline Managed Package Changes option was not displayed on the UI when navigating from Package xml to select manually (internal ticket).
Fixed an issue where there was a discrepancy between the Attachments Records Success/Failure Count and the Retrieved Count when BULK API was enabled for Deployment (internal ticket).

26 February 2023

(ARM v22.3.10) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug in Profile Manager where User Permissions differences are shown in the report but not in the UI ().
Enhanced the Release Label creation by increasing the range of retrievable commit history ().
Fixed an issue where user was unable to use Release Labels to perform Deployment, and it failed while trying to Create Artifact ().
Fixed an issue where users with non-admin access were unable to register branches in EZ-Commit since upgrading to version 22.3 (, , , and ).
Fixed an issue where Release Artifact execution was failing when rabit home did not exist with an external agent (internal ticket).
Fixed a UI bug on the Profile screen where the expand option for the My Projects and My Roles sections was not working (internal ticket).
Fixed an issue where triggering Data Retention for Audit Tables was throwing the following error: Unable to execute HTTP request: Read timed out (internal ticket).
Fixed an issue where extra characters are seen in the Fetch Commit History results while creating a Release Label with Vlocity label type (internal ticket).
Fixed an issue where user was unable to delete Apex test class on the SF Org Management page (internal ticket).
Enhanced nCino by introducing New Spreads Schedule tile in the Feature Creation screen (internal ticket).
Fixed an issue where if the fields did not load for Applied Mappings during deployment, no error was thrown by the application (internal ticket).

19 February 2023

(ARM v22.3.9) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was deploying single revision deployment with only report folder but sub-reports were also getting fetched, and the deployment was failing due to field dependency error ().
Fixed an issue where after deployment with single revision merge, user permission appears to be removed in target org but in the Salesforce target org the user permission is not removed, and an incorrect layout is displayed in UI ().
Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs ().
Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in EZ-Commit ().
Fixed an issue where user was customer trying to register a Salesforce Org with Custom URL but it was failing with an error ().
Fixed an issue where user was unable to remove Revisions/Commit Labels from a Release label ( and ).
Fixed an issue where user was creating credentials for JIRA in ARM using JIRA Token and but application wasn't allowing more than 150 characters while JIRA Token should allow up to 192 characters ( and ).
Fixed an issue where user user uploaded a YAML file to retrieve the Vlocity components but ALL metadata types were retrieved and displayed ().
Fixed an issue where the same merge could be approved and rejected by different users simultaneously ().
Fixed an issue where branch creation was faileing for sub-users in the EZ-Commit screen for Non-DX Repo (internal ticket).
Fixed an issue where Null Pointer was seen in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where all credentials were listed twice in the Credentials dropdown in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where branch creation was failing for sub-users in VC repos when the credential scope was private while Admin credentials were fetched (internal ticket).
Fixed an issue where user was unable to delete the Apex Test class under the SF org Apex default config (internal ticket).
Fixed an issue where the Add manually checkbox under Apex class config was selected by default (internal ticket).
Fixed an issue with nCino where user created a feature Deployment for Credit memo template with attachments, but Attachments Objects Data was not fetched, and the deployment failed with the following error: Data file not fetched for object: Attachment (internal ticket).
Fixed an issue with nCino where Standard Features were not loaded in the Feature Management page (internal ticket).

12 February 2023

(ARM v22.3.8) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was unable to download success/failure reports in Single Dataloader ().
Fixed an issue where when multiple CI Jobs are triggered, jobs are moved into the queue as expected, but new jobs are not starting automatically getting processed once the existing jobs is cleared from the CI Job results page ().
Fixed an issue where Dependency order defined in json file was being changed on every commit but it was not supposed to ().
Fixed an issue where Create Artifact was not working as expected while using Release Label ().
Fixed an issue where user was performing an EZ-Commit with Review Artifact option and download the .zip file to make some changes, but was unable to upload it afterwards ().
Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes ().
Fixed an issue where File Diff was empty in case of modified Uploaded via Review Artifact in PV Commit Flow (internal ticket).
Fixed an issue where Review Artifact Tree was not responding after uploading the modified file in Commit Flow (internal ticket).
Fixed an issue where User Permissions and Ip Ranges are completly removed from the branch after commiting the Permission Sets and Profiles (internal ticket).
Fixed an issue where Super Admin was getting an error while trying to activate newly signed up users (internal ticket).

05 February 2023

(ARM v22.3.7) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where SFDX module creation log shows that deployment is successful but the module creation had failed ().
Fixed an issue with Backup from Org CI Jobs where PermissionSet User Permissions were being deleted ().
Fixed an issue where Org to Org Deployment for Profiles including Deploy Profile Access Settings for selected components only was not working as expected ().
Fixed an issue where Post Destruct fields were also added to Pre Destruct despite the user setting it to post ().
Fixed an issue where user set the Max depth value as '0' under Vlocity Configuration Settings but it was retrieving all level dependancy components ().
Fixed an issue with DataLoader where the Credit Memo Template migration was not deploying after user upgraded their instance ().
Fixed an issue where user selected Custom Metadata members (records), but EZ-Commit was failing to generate File Diff with Null error ().
Fixed an issue where Merge was taking longer than usual, and then failing with Null Exception ().
Fixed an issue where EZ-Commits and EZ-Merges were taking much longer than usual ().

29 January 2023

(ARM v22.3.6) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the deployment was failing with the following error when user was deploying Permissionset with a user-permission Manage Public Documents: Permission Manage Public Documents depends on permission(s): Create Document, Delete Document, Edit Document, Read Document ().
Fixed an issue where CI jobs were failing intermittently with the following error: Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request ().
Fixed an issue where Reports deployment validation failed in EZ-Merge but was successful in EZ-Commit and Deployment modules ().
Fixed an issue where user performed a merge and sent it for approval, but it was not available under the Commit history tab ().
Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error null at Diff ().
Fixed an issue where Validate Deploy failed in QuickMerge and displayed the following message: This folder unique name already exists for this folder type or has been previously used. Please choose a different name (internal ticket).
Fixed an issue where CI job wasn't considering the metadata changes, so the destructive changes were not being prepared or displayed on the build. (internal ticket).

22 January 2022

(ARM v22.3.5) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user changed the permissions to list view from visible to all users to visible only for me while using the previous commit label, it is added under the Deleted tab ().
Fixed an issue where commit was running for longer and remained in-progress and validation check log is also in progress ().
Fixed an issue where commits with SFDX metadata structure are failing in metadata retrieval stage ().
Fixed an issue where user couldn't create a managed package with the selected ancestor ().
Fixed an issue where CI Job was occasionally failing with the error BUILD FAILED ().
Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user ().
Salesforce API version 57 (Beta support) is upgraded. The label is modified throughout ARM application including DataLoader and nCino (internal ticket).
Fixed an issue where nCino CI job was stuck in Build Success status for more than a week ().
Fixed an issue where user was trying to deploy RBC (nCino Screens) and the deployment was failing for some of the objects, but there were no error messages shown on the UI ().
Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error: Invalid Private Key ().
Fixed an issue where user has created a Commit label but it was not available while trying to perform an EZ-Merge ().
Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff ().
Fixed an issue where user was getting an error while trying to create a new branch in GitHub (). For more information, click .
Fixed an issue where user could not create an xml package for deployment because artifact creation and package manifest preparation were failing with an invalid credentials error ().
Fixed an issue where user was trying to perform single revision merge but validation deployment was failing with the following error Metadata package is empty ().
Fixed an issue where when there are special characters in Layout metadata then the user was not able to add it manually in Skip Members section ().
Fixed an issue where user wanted to choose commit revision in a release label based on its comment but if the comment was not in text, it was not completely visible in the UI ().
Fixed a UI bug where an incorrect validation message was seen while adding Skip Members manually (internal ticket).
Fixed an issue where the selected tab checkbox in the metadata components page in the EZ-Commit was not functioning as expected (internal ticket).
Fixed an issue where the EZ-Commit validation screen was displaying incorrect notification when name of the template was empty (internal ticket).

15 January 2022

(ARM v22.3.4) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Merge validation failed to process when there was a Flow metadata ().
Fixed an issue with user received 6 notifications for a failed CI Job instead of 1 ().
Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error: Lower Region ().
Fixed a recurring issue where Commits and Merges were slowing down at a particular step, and EZ-Merge was failing with an error at commit phase ().
Fixed an issue where while performing destructive changes in EZ-Commit, it was creating package.xml in root path folder in SFDX structure ().
Fixed a UI bug on CI List and CI Results pages where when pagination was changed, the first 25 records were repeated (internal ticket).
Fixed an UI bug where the LastUsedDate column was not displayed in the Branch Table (internal ticket).

8 January 2022

(ARM v22.3.3) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Admin was able to see the Teams field under ALM Integration but the same field was unavailable for sub-users ().
Fixed an issue where Environment provisioning processes were failing to update when user was trying to change the email deliverability access level from No access to All email ().
Fixed a build bug where CI Job Build was failing during package preparation step 5 failing while commiting DecisionMatrixDefinition and throwing an error ().
Fixed an issue with Branching Baseline where the developers were migrating the changes from dev branch to INT, but Diff was showing 100% addition which is incorrect ().
Fixed an issue where generating Diff for a Commit Label was taking much longer than expected ().
Fixed an issue where Code coverage job was running 4 hours earlier than scheduled every time services were restarted ().
Fixed an issue where SFDX scratch org was failing during data deployment but without any errors on UI, and the logs did not capture the failure either ().
Fixed an issue where Merge validation failed to process when there was a Flow metadata (, , and ).
Fixed an issue where CheckMarx is executed successfully, but when trying to open the file user is the following error popup: Result file not exists (internal ticket).
Fixed an issue where ActionCall and Decision Nodes were not shown in the Duplicate Resolving screen (internal ticket).

1 January 2022

(ARM v22.3.2) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was unable to create Environment Provisioning templates for multiple component types ().
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error: JSONObject["Assets"] is not a string ().
Fixed an issue where AutoRABIT SSH credentials were failing with an error Auth failed while trying to connect with AWS CodeCommit ().
Fixed an issue where EZ-Commit Diff was taking approximately 4 hours while Refactoring CustomField, which is much longer than expected ().
Fixed an issue where ExternalCredential metadata type was not getting excluded even when user added it in the excluded lists in CI Configuration (internal ticket).
Fixed an issue where after triggering Branching baseline, standard value set metadata type was getting displayed under the deleted components through Autodraft for Non-DX repo (internal ticket).
Fixed an issue where Destructive Components are not seen in case of PV-DX-Destructive Merge for Report metadata type. Instead, it displaying a message: Package is empty (internal ticket).
Fixed an issue where Deployment was failing with certain Permission set metadatatypes that were not selected (internal ticket).

25 December 2022

(ARM v22.3.1) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ().
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected ().
Fixed an issue where user was performing a single Merge with only two approval process, but while selecting SCA, process is auto rejected ().
Fixed an issue where SFI components were not getting fetched in Commit and Deployment module ().
Fixed an issue where non-admin users were unable to select Branch Type while trying to create a new branch from New EZ-Commit Branch ().
Fixed an issue where CI jobs are failing intermittently with the following error: Getting access token failed from refresh tokenHTTP/1.1 400 Bad Request ().
Fixed an issue where user was trying to deploy only the Documents from the branch to Org, but deployment failed and Asynch ID is not generating ().
Fixed an issue where user was trying to deploy login hours. First they merged it to target branch, then once CI job triggers login hours are not getting deployed to target org ().
Fixed multiple issues where user was having trouble creating new package version from previous ancestor version ().
Fixed an issue where Merge is failing with the following error: failed to push some refs to 'https://github.com/salesforce-align/SFDX.git' ().
Fixed an issue where the Standard Field Account.name is displayed in the deleted components list ().
Fixed an issue where the prevalidation commit failed at delta stage ().
Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).

18 December 2022

(ARM v22.3.0) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with DataLoader Pro where jobs executed in the last 6 months were not showing in the database process table and in the Reports module ().
Fixed an issue with Deploy SFDX Source With ALM Mapping where CI job with ALM Mapping was not working as expected for Team which is not default ().
Fixed an issue where Profile Diff is working as expected for Selective Deployment, but not while using the same profile in the profile manager ().
Fixed an issue where Environment provisioning processes were failing to update when user was trying to change the email deliverability access level from No access to All email (, ).
Fixed an issue where Provar jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ().
Fixed an issue where user triggered a CI Job but it deployed with many more components than expected ().
Fixed an issue where user was creating an EZ-Commit, mapping the ALM Project (VersionOne) but received the following error: JSONObject["Assets"] is not a string ().

ARM Release Notes 22.2

Date of release: 9 October 2022 Article last updated: 15 May 2023

New Features

1. Teams/Slack Notifications

Mail Settings module in the Admin section is relabeled as Notifications. Through this module, you can choose to send notifications about specific events triggered in ARM to specific groups or channels within your organization through Teams or Slack. For whichever messaging app you use, you can configure a webhook connection for each of the groups or channels, and then integrate them with ARM. You can customize and select which group(s) to notify when events like build failure, build success, deployment failure, merge reports, etc. are triggered.

2. Salesforce Scanner plugin

In addition to the existing static code analysis tools, ARM now provides the ability to choose the Salesforce Scanner CLI plugin.

Most static code analysis tools specialize in one language or a set of languages. Many applications (including typical Salesforce packages), however, contain an assortment of components created using different languages. A single static analyzer is insufficient to address all aspects of such applications, and managing multiple static analyzer tools could prove unfeasible.

This is where the Salesforce CLI Scanner plugin shines. This plugin aggregates the results of static analyzers that are most relevant to Salesforce developers while providing a unified experience.

With the Salesforce CLI Scanner plugin, you can look forward to a:

Single installation process
A single set of commands to interact with multiple rule engines
A unified set of rules that are checked by their respective rule engines
Unified rule violation report that includes all issues identified by the engines.

3. AutoRABIT for nCino

We’ve added the ability to view and review datasets corresponding to each version of the nCino feature template before using it for deployment. Prior to this release, the capability was available only for the latest version of the template.

Enhancements

1. ApexPMD Upgrade to 6.49 version

With this release, PMD has been upgraded to version 6.49. If you have not uploaded a rules file, ARM will use the default Apex PMD rules file. However, you can add new rules to the default ruleset.

Click to view the list of currently deprecated rules available on GitHub.

2. Auto-approve on validation success

We have moved one step closer to automating the flow by adding an option to choose if an EZ-Commit or an EZ-Merge should be approved automatically if the SCA validation is successful. Combined with the existing option to auto-commit on approval, this leads to a true CI/CD experience.

3. HashiCorp Vault Integration

While adding HashiCorp credentials to ARM, you can now choose the AWS Authentication method so that the Vault Token will be generated automatically whenever the existing token expires. Now the user will not have to update the token manually from the application when it expires.

4. SFDX CLI Upgrade

The SFDX CLI has been upgraded to the latest stable 7.169 version.

Key characteristics to look for:

Support for the quick deploy functionality for SFDX jobs.
Use CLI commands to generate the package manifest and rollbacks.

5. Salesforce Winter (API 56.0) Support

To keep our product up to date with the most recent Salesforce updates, AutoRABIT supports the most recent API 56.0 version in this release. The most recent API version is intended for customizing the metadata model and developing tools to manage it.

6. Merge to multiple branches

With this release, you can choose to merge from one source branch to multiple destination branches upon successful deployment.

7. OAuth for Jira

In addition to the Standard access type, users can now set up SSO as authentication for Jira using the OAuth access type while registering an ALM. You can also switch between Standard and OAuth access types for already registered ALMs.

Improvements

Users with Admin access can now turn off the Jira comments and notifications created by AR. This ensures a cleaner workspace. These comments and notifications are very development centric, so the end users who use Jira cannot make sense of our technical comments from AR, and this may create confusion for them.

Changelogs

28 May 2023

(ARM v22.2.28) This is a maintenance release. The following items were fixed and/or added:

Fixed a compliance issue with Apache Commons by removing the text dependency ().
Fixed an issue where CI Jobs were failing due to empty JSON file(s) in the remote repository, and throwing the following error: Failed to initiate deployment. Unexpected end of JSON input ().
Improved the UI by removing the Validate Deployment option if Vlocity is selected, and hiding the whole Board Type option if Vlocity is not enabled ().
Fixed an issue where user was performing CI jobs for Validate and Deploy for a successful commit, but only validation was performed but not the deployment ().
Fixed an issue where CI job deployment was failing because the build was picking duplicate Layout values ().
Fixed an issue where unwanted metadata changes were observed in the package.xml file while performing a commit ( and ).
Improved the New Merge screen by adding Layouts text in the Skip Flow /Profile/ Perm.Set Access-Setting Duplicity Check option (internal ticket).
Fixed a UI bug where SF Org Test Connection notification message was displayed on an unrelated module (internal ticket).
Removed the option to sign up for a 30-day Salesforce trial while registering a DevHub as the trial offer is no longer applicable (internal ticket).

21 May 2023

(ARM v22.2.27) This is a maintenance release. The following items were fixed and/or added:

Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).

14 May 2023

(ARM v22.2.26) This is a maintenance release. The following items were fixed and/or added:

Improved Release label creation by requiring at least two revisions to be selected (internal ticket).
Fixed an issue where Classic SF Org URL with a slash at the end of the URL redirects to the 400 error page, and for a Lightning SF Org URL without a slash gives an OAuth Authentication Failed error message (internal ticket).
Fixed an issue with nCino where user was getting a NullPointerException on Saving Permissions using Bulk Assignment (internal ticket).
Fixed an issue with CI Jobs where all the scheduled timings were not displayed in the Preview & Save page (internal ticket).
Fixed an issue with Dataloader where user was able to upload a 900 MB file despite the limit being 100 MB, causing the process to hang (internal ticket).
Fixed an issue with Dataloader where sever crashed after user performed an Extract operation from an SF org which had Account Object with 2 million records (internal ticket).

07 May 2023

(ARM v22.2.25) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where if CI Jobs were added in a queue with Scheduled jobs, then not all jobs were displayed in the queue (internal ticket).
Fixed an issue where existing revision file related delta still existed in agent even after uploading to rabitserver (internal ticket).
Fixed an issue where release label creation was failing when user tried to create package manifest and aborted and refreshed the label for DX repo (internal ticket).
Fixed an issue where Super admin user was getting a blank popup screen while trying to click on the Register Agent button from the Pool Mgmt screen (internal ticket).

09 April 2023

(ARM v22.2.23) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).

19 March 2023

(ARM v22.2.22) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where errors were occuring while performing Delete Org (internal ticket).
Fixed an issue where for Build only job source from VC with DX repo, if Master Details Object Change is included in the build, we're getting No Modifications even if changes exist (internal ticket).

12 March 2023

(ARM v22.2.21) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where multiple fields of the respective custom objects were getting selected parallelly while performing edit or save or exit operations on the Review Artifact screen (internal ticket).
Enhanced ARM by adding an option for multiple ARM instances to share a single database cluster (internal ticket).

05 March 2023

(ARM v22.2.20) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug where incorrect notification was displayed in certain components pages when template was created using one org and was used by another org (internal ticket).
Fixed an issue where Baseline Managed Package Changes option was not displayed on the UI when navigating from Package xml to select manually (internal ticket).
Fixed an issue where there was a discrepancy between the Attachments Records Success/Failure Count and the Retrieved Count when BULK API was enabled for Deployment (internal ticket).

26 February 2023

(ARM v22.2.19) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Release Artifact execution was failing when rabit home did not exist with an external agent (internal ticket).
Fixed a UI bug on the Profile screen where the expand option for the My Projects and My Roles sections was not working (internal ticket).
Fixed an issue where triggering Data Retention for Audit Tables was throwing the following error: Unable to execute HTTP request: Read timed out (internal ticket).
Fixed an issue where extra characters are seen in the Fetch Commit History results while creating a Release Label with Vlocity label type (internal ticket).
Fixed an issue where user was unable to delete Apex test class on the SF Org Management page (internal ticket).
Enhanced nCino by introducing New Spreads Schedule tile in the Feature Creation screen (internal ticket).
Fixed an issue where if the fields did not load for Applied Mappings during deployment, no error was thrown by the application (internal ticket).

19 February 2023

(ARM v22.2.18) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where branch creation was faileing for sub-users in the EZ-Commit screen for Non-DX Repo (internal ticket).
Fixed an issue where Null Pointer was seen in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where all credentials were listed twice in the Credentials dropdown in Create Branch in EZ-Commit flow (internal ticket).
Fixed an issue where branch creation was failing for sub-users in VC repos when the credential scope was private while Admin credentials were fetched (internal ticket).
Fixed an issue where user was unable to delete the Apex Test class under the SF org Apex default config (internal ticket).
Fixed an issue where the Add manually checkbox under Apex class config was selected by default (internal ticket).
Fixed an issue with nCino where user created a feature Deployment for Credit memo template with attachments, but Attachments Objects Data was not fetched, and the deployment failed with the following error: Data file not fetched for object: Attachment (internal ticket).
Fixed an issue with nCino where Standard Features were not loaded in the Feature Management page (internal ticket).

12 February 2023

(ARM v22.2.17) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where File Diff was empty in case of modified Uploaded via Review Artifact in PV Commit Flow (internal ticket).
Fixed an issue where Review Artifact Tree was not responding after uploading the modified file in Commit Flow (internal ticket).
Fixed an issue where User Permissions and Ip Ranges are completly removed from the branch after commiting the Permission Sets and Profiles (internal ticket).
Fixed an issue where Super Admin was getting an error while trying to activate newly signed up users (internal ticket).

05 February 2023

(ARM v22.2.16) This is a maintenance release. The following items were fixed and/or added:

29 January 2023

(ARM v22.2.15) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Validate Deploy failed in QuickMerge and displayed the following message: This folder unique name already exists for this folder type or has been previously used. Please choose a different name (internal ticket).
Fixed an issue where CI job wasn't considering the metadata changes, so the destructive changes were not being prepared or displayed on the build. (internal ticket).

22 January 2022

(ARM v22.2.14) This is a maintenance release. The following items were fixed and/or added:

Salesforce API version 57 (Beta support) is upgraded. The label is modified throughout ARM application including DataLoader and nCino (internal ticket).
Fixed a UI bug where an incorrect validation message was seen while adding Skip Members manually (internal ticket).
Fixed an issue where the selected tab checkbox in the metadata components page in the EZ-Commit was not functioning as expected (internal ticket).
Fixed an issue where the EZ-Commit validation screen was displaying incorrect notification when name of the template was empty (internal ticket).

15 January 2022

(ARM v22.2.13) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug on CI List and CI Results pages where when pagination was changed, the first 25 records were repeated (internal ticket).
Fixed an UI bug where the LastUsedDate column was not displayed in the Branch Table (internal ticket).

8 January 2022

(ARM v22.2.12) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug where scrollbar and pagination were not visible on the Org Sync History page (internal ticket).

01 January 2022

(ARM v22.2.11) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Deployment was failing with no changes in the package (internal ticket).
Fixed an issue where ExternalCredential metadata type was not getting excluded even when user added it in the excluded lists in CI Configuration (internal ticket).
Fixed an issue where after triggering Branching baseline, standard value set metadata type was getting displayed under the deleted components through Autodraft for Non-DX repo (internal ticket).
Fixed an issue where Destructive Components are not seen in case of PV-DX-Destructive Merge for Report metadata type. Instead, it displaying a message: Package is empty (internal ticket).

25 December 2022

(ARM v22.2.10) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).

18 December 2022

(ARM v22.2.9) This is a maintenance release. The following items were fixed and/or added:

11 December 2022

(ARM v22.2.8) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Enhanced nCino to:
- Modify notification messages for null checks on request parameters (internal ticket).
- Display only nCino revisions for Version Control in nCino feature deployment (internal ticket).

04 December 2022

(ARM v22.2.7) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).

27 November 2022

(ARM v22.2.6) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).

20 November 2022

(ARM v22.2.5) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with nCino where Record Classification and Classification Objects were missing in the template (internal ticket).
Fixed an issue with nCino where user was creating a CI Job and observed that Use UTF-8 file encoding for the file read and write operations flag was displayed at the bottom below the Commit Details section (internal ticket).
Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).

13 November 2022

(ARM v22.2.4) This is a maintenance release. The following items were fixed and/or added:

06 November 2022

(ARM v22.2.3) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with DX CI Job where user selected Do Not Include Skip Members but the respective mapper reports were not skipped (internal ticket).
Fixed the following issues in CI and Reports modules (internal ticket):
- Build With NULL ERROR (issue exists both with Proxy and without Proxy)
- SF Org Code coverage Execution is failing (issue exists both with Proxy and without Proxy)
- Jenkins Build is updated with FAILED status even after it is successfully completed (issue exists only without Proxy)
- Checkmarx text is not displaying the Proxy Configuration note (Only With Proxy)
Fixed an issue with QA Environments where user was unable to create and delete the SFDX module because of the Apache config CACHE settings (internal ticket).
Fixed an issue where user was trying to perform a Quick Merge but was getting an Undefined error for all labels (internal ticket).

30 October 2022

(ARM v22.2.2) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug on the CI Jobs page for Install an Unlocked or Managed Package from a Version Control Branch type where old Dev Hubdropdown list was displayed in the Deploy section (internal ticket).
Fixed an issue where Page Size value on the Edit Release Label screen is defaulting to the previous value instead of the set value (internal ticket).
Fixed a UI bug where OK Button in Automation is not visible in the Create Release Label pop-up when opened in 100% zoom (internal ticket).

23 October 2022

(ARM v22.2.1) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was adding URLs to the Proxy Configuration Settings but the URL List was not reflecting the same (internal ticket).
Fixed an issue where the Created By value was not visible in Dataloader, Dataloader Pro DL Config, and the TestEnv History page (internal ticket).

16 October 2022

(ARM v22.2.0) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where a new database file is created and overwritten with an existing database file whenever the server was restarted (internal ticket).
Fixed an issue where user was trying to resolve conflicts on Merge Request Labels created more than 7 days ago, but application was throwing an error: undefined (internal ticket).

ARM Release Notes 22.1

Date of release: 20 March 2022 Article last updated: 23 October 2022

New features

1. Squash and merge

We have added the Squash and Merge feature in this release. Sometimes, when merging a long list of changes from a development branch into the master, it's helpful to squash those commits into one change for ease of review and declutter the repo's commit history. AutoRABIT offers an option to squash all commits in a merge request into one commit after the merge is approved and completed.

2. SFDX- Import packages

Packages

The users could previously build a new package (unlocked or managed) and update the package's version in Salesforce DX. With this release, you may now import packages and update the version of packages created outside of AutoRABIT.

Dev Hub management

With this update, users will see all of the packages in their dev hub in the record view. You may expand each package to show the package's versions in order and package data such as version name, version number, ancestor version, ancestor dependencies, etc.

3. Step-based rollback

The option to list the API-supported and unsupported API components is added to the CI job/deployment rollback. If such components may be deployed to the target environment but do not have API support to delete them, ARM will display them individually as unsupported API types. Take, for example, RecordType.

The RecordType component may be deployed to the target environment, but it cannot be removed; instead, we need to connect to the target Salesforce environment to deactivate the component.

Enhancements

1. Checkmarx upgrade to v9.4.1

Checkmarx has been updated to version 9.4.1. Earlier, Checkmarx used a username/password-based authentication method. Now, the user will be able to use token-based authentication with the Checkmarx upgrade.

2. Export all users

The Export All Users feature allows the org admins to export a CSV file of all the users currently in their account. We now have added the following fields to the existing CSV file:

CreatedDate
CreatedByName
DeativatedDate
LastLoginDate
DeactivatedByName
LastModifiedDate
LastModifiedByName.

3. Pull request support for Azure cloud repositories

We have extended the support of having the pull request support in the CI Job for the Azure repository. This feature was previously available for Github cloud/Enterprise and Bitbucket cloud/Enterprise; however, we've added support for Azure cloud repositories (DX and non-DX repositories) with this release.

4. Merge/commit approval eligibility

If you want to make sure one or more people approve every commit or merge, you can enforce this workflow by using merge/commit approvals. These approvals allow you to set the number of necessary approvals to approve every commit/ merge in a project.

The org admins' eligibility level has been enhanced with the ARM 22.1 version. If you're an administrator, you will have the privilege to approve self-merge even if the criteria to self-approve a merge is set to FALSE. This permission will be denied to all members of your team except the org admin. To put it another way, no criteria can restrict an org administrator from approving any EZ-commit/ EZ-Merge.

5. CodeScan additional metadata support

We have enhanced the scope for analysis of what CodeScan does by adding support for additional metadata and rules. For our ARM users who want to incorporate the SCA tool into their subscriptions, CodeScan would be their first choice as it now supports more robust integrations.

Below is the list of CodeScan supported metadata types:

Apex Triggers

Apex Classes

Aura Definition Bundles

Lightning Component Bundles (LWC)

Visualforce Pages

Custom Object

Settings

Flows

Workflows

Profiles

Sharing Rules

Sharing Criteria Rules

Sharing Owner Rules

Sharing Territory Rules

Permission Sets

6. SFDX CLI update

The SFDX CLI has been upgraded to the latest stable 7.134 version.

Key characteristics to look for:

Single deployment request for constructive and destructive changes
Quick deploy and rollbacks work for both constructive and destructive changes
Package preparation has been improved.

Improvements

The jquery-UI version has been upgraded to v1.13.0 to fix security issues. Upgrading to the most recent version of jquery makes our application more secure and potentially faster in script execution and loading.
Minor performance, bug fixes, and security improvements can also be observed in the ARM portal.

Changelogs

21 May 2023

(ARM v22.1.48) This is a maintenance release. The following items were fixed and/or added:

Enhanced ARM by using known vulnerable components through the DataTables 1.10.12 plugin for advanced data table functionalities such as sorting, filtering, pagination, and more. This allows users to easily display and manipulate large sets of data on their web pages in a user-friendly manner (internal ticket).
Fixed an issue with Prevalidation Merge where users were unable to deploy the ApexClass Tests related to ApexClasses and Apex Triggers (internal ticket).
Fixed a UI bug where the date column in the EZ-Commit Weekly report was displaying incorrect values (internal ticket).

09 April 2023

(ARM v22.1.46) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with Dataloader Pro where user tried to migrate Account Object Data with Attachments Object, but the logs verify that there is a Null Pointer Exception. (internal ticket).
Improved nCino by adding additional loggers for Branching baseline for user to view the status in the UI (internal ticket).
Fixed an issue where user was unable to filter while trying to select a job which had spaces in the job name (internal ticket).

25 December 2022

(ARM v22.1.38) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was unable to create commit label for the same repository second time, and branches were not displayed (internal ticket).

11 December 2022

(ARM v22.1.37) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).
Enhanced nCino to:
- Modify notification messages for null checks on request parameters (internal ticket).
- Display only nCino revisions for Version Control in nCino feature deployment (internal ticket).

04 December 2022

(ARM v22.1.36) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Commits added from non-nCino Repositories were not cleared from the Workspace causing the Commit to either not be visible in the UI or it is added to the queue but not deployed to the Destination Org (internal ticket).

27 November 2022

(ARM v22.1.35) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).

20 November 2022

(ARM v22.1.34) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with nCino where Record Classification and Classification Objects were missing in the template (internal ticket).
Fixed an issue with nCino where user was creating a CI Job and observed that Use UTF-8 file encoding for the file read and write operations flag was displayed at the bottom below the Commit Details section (internal ticket).
Fixed an issue with nCino where the UTF-8 Encoding Flag was not displayed in the pop-up during Re-Deployments (internal ticket).

13 November 2022

(ARM v22.1.33) This is a maintenance release. The following items were fixed and/or added:

06 November 2022

(ARM v22.1.32) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue with DX CI Job where user selected Do Not Include Skip Members but the respective mapper reports were not skipped (internal ticket).
Fixed the following issues in CI and Reports modules (internal ticket):
- Build With NULL ERROR (issue exists both with Proxy and without Proxy)
- SF Org Code coverage Execution is failing (issue exists both with Proxy and without Proxy)
- Jenkins Build is updated with FAILED status even after it is successfully completed (issue exists only without Proxy)
- Checkmarx text is not displaying the Proxy Configuration note (Only With Proxy)
Fixed an issue with QA Environments where user was unable to create and delete the SFDX module because of the Apache config CACHE settings (internal ticket).
Fixed an issue where user was trying to perform a Quick Merge but was getting an Undefined error for all labels (internal ticket).

30 October 2022

(ARM v22.1.31) This is a maintenance release. The following items were fixed and/or added:

Fixed a UI bug on the CI Jobs page for Install an Unlocked or Managed Package from a Version Control Branch type where old Dev Hubdropdown list was displayed in the Deploy section (internal ticket).
Fixed an issue where Page Size value on the Edit Release Label screen is defaulting to the previous value instead of the set value (internal ticket).
Fixed a UI bug where OK Button in Automation is not visible in the Create Release Label pop-up when opened in 100% zoom (internal ticket).

23 October 2022

(ARM v22.1.30) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where user was adding URLs to the Proxy Configuration Settings but the URL List was not reflecting the same (internal ticket).
Fixed an issue where the Created By value was not visible in Dataloader, Dataloader Pro DL Config, and the TestEnv History page (internal ticket).

16 October 2022

(ARM v22.1.29) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where a new database file is created and overwritten with an existing database file whenever the server was restarted (internal ticket).
Fixed an issue where user was trying to resolve conflicts on Merge Request Labels created more than 7 days ago, but application was throwing an error: undefined (internal ticket).

09 October 2022

(ARM v22.1.28) This is a maintenance release. The following items were fixed and/or added:

02 October 2022

(ARM v22.1.27) This is a maintenance release. The following items were fixed and/or added:

26 September 2022

(ARM v22.1.26) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where scheduled auto-sync of external commits was not working (internal ticket).
Fixed an issue with the New EZ-Commit screen where ALM Types are changing to old ALM type names after resaving details on the ALM Management screen (internal ticket).
Fixed an issue with Pre-validation merge where the Object file content was empty in the CodeScan Analysis SCA report (internal ticket).

19 September 2022

(ARM v22.1.25) This is a maintenance release. The following items were fixed and/or added:

Fixed multiple issues with CodeScan<>ARM Integration (internal ticket).
Fixed an issue where CI Jobs and Deployments were both failing for Reports and Dashboards because the folder could not be found (internal ticket).
Fixed an issue with New Commit screen where the Select All checkbox was getting unselected when navigating from the DELETED tab to the ADDED/MODIFIED METADATA COMPONENTS tab and back to the DELETED tab (internal ticket).
Fixed an issue with Version Control Prevalidation Commit where for the selected Custom Metadata and Permission Set, Diff was being generated as expected but the Deployment was failing (internal ticket).
Fixed an issue with Version Control Prevalidation Merge where SCA report was empty, and throwing the following error in the console: Uncaught TypeError: Cannot read properties of undefined (reading 'length') (internal ticket).
Enhanced Vlocity loggers for Branching Baseline by displaying to the user Status Count of Remaining, Success, Error and Ignored (internal ticket).

11 September 2022

(ARM v22.1.24) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue in Version Control Commit Labels history where Created By and Created Date values were exchanged (internal ticket).

04 September 2022

(ARM v22.1.23) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where creating multiple deployment jobs from the same source org to the same destination org for different templates, the jobs were failing with Null Pointer Exception error (internal ticket).
Fixed an issue with DX Pre-validation merge where Destructive Deployment for custom labels failed without any errors (internal ticket).

28 August 2022

(ARM v22.1.22) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where Unpackaged Packages Directory folder was being created in the Deployment Promotion zip package when deploying Static Resource Metadata type using Single revision DX Deployment (internal ticket).
Fixed an issue where choosing the Select Manually option while doing a commit was resulting in a blank screen for the Deleted tab (internal ticket).
Fixed an issue where while doing Prevalidation commit in AR, Commit Only Permissionsets For The Selected Metadata functionality was not working properly for both DX and Non-DX cases (internal ticket).
Fixed an issue in Dataloader where an Undefined Error was displayed when user was trying to create and save the Screens Template (internal ticket).
Fixed an issue where the search functionality was not working in Dataloader Configuration as well as Dataloader Test Environment Setup (internal ticket).
Fixed an issue in CI Jobs deployments where Bulk API option for Attachments was throwing an error (internal ticket).

21 August 2022

(ARM v22.1.21) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where DX CI Job build failed if document metaxml change commit revision includes in the build [Including Email templates and Static Resources types] (internal ticket).
Enhanced the Dataloader history screen (internal ticket):
- Column mover added to table column alignment for text view.
- Moved Last Run details to the Date/Time column.
Fixed an issue for the nCino CI Jobs were failing due to default selection of AutorabitExtId__c in Mappings (internal ticket).
Fixed an issue for the nCino Deployments where even if LookupKey is available, by default Name is selected in External ID Mapping (internal ticket).
Fixed an issue for the nCino CI Jobs where Attachments were failing due to External Mappings not being set to the NAME field (internal ticket).
Added the feature to dynamically handle the respective nCino Prefix rather than depending on the JSON file to identify the External Id field

14 August 2022

(ARM v22.1.20) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where for both CI Jobs and Deloyments (Non-DX and DX), the deployment was getting failed with the below error although the Ignore missing visibility settings is checked: permissionset error--- Error in field: customPermission not found (internal ticket).
Fixed an UI bug where while performing test connection for any successful Salesforce org registered, the messasge is displayed as "Success" instead of "Testconnection was successful" (internal ticket).

07 August 2022

(ARM v22.1.19) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the package URL was not visible for the SFDX modules successfully configured in ARM (internal ticket).
Fixed an issue where our internal team members got the undefined error while creating a new scratch org and selecting the module (internal ticket).
Fixed the below deployment-related issues:
Fixed an issue where the status log .csv files are inconsistent for deployment via CI jobs (internal ticket).

31 July 2022

(ARM v22.1.18) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were unable to login to ARM via SSO (internal ticket).
Duplicate classes from the ARM repo has been removed (internal ticket).
Fixed an issue where for both CI Jobs and Deloyments (Non-DX and DX), the deployment was getting failed with the below error although the Ignore missing visibility settings is checked: permissionset error--- Error in field: customPermission not found (internal ticket).
Fixed an UI bug where while performing test connection for any successful Salesforce org registered, the messasge is displayed as "Success" instead of "Testconnection was successful" (internal ticket).

24 July 2022

(ARM v22.1.17) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the Rollback settings were not getting saved in the My Account page (internal ticket).
Fixed an UI bug where the ARM application displays unwanted scrollbar when "Exclude Installed (Managed) components" is selected in the My Account page (internal ticket).
Enhanced the ARM workspace feature to automatically unlock the workspace after sufficient time to run the workspace operations.
Added the feature to set Limit 0 option for the Dataloader Pro jobs. This limit will allow users to skip migrating child or Ancestors objects.

17 July 2022

(ARM v22.1.16) This is a maintenance release. The following items were fixed and/or added:

Fixed a bug where our internal team were able to use the perform the prevalidation commit and direct commit without giving the prevalidation commit label name and without commit comment, which are mandatory fields (internal ticket).
Fixed an issue where the ALM workitems are not retrieved in CI job through merge (internal ticket).
Fixed a bug where our internal team were able to save the Install an Unlocked or Managed Package from a Version Control Branch CI job even though Installation key were not uploaded which is a mandatory field (internal ticket).
[Enhancement] Added the Salesforce versions information in the logs for all Dataloader related jobs activities.
[Enhancement] Added the ability to delete a commit before it is pushed to your remote repository so that you have a choice to redo incorrect commits/ merges.
Fixed an issue where the Delete Commit button was not seen after approving an EZ-Commit label (internal ticket).
Fixed an issue where the toggle button for the dashboard metadata type in the commit label screen is not working as expected (internal ticket).
Fixed an issue for the nCino Feature Deployments where the users were getting audit field issue when trying to deploy with Insert/Update with Null Values option (internal ticket).
Fixed an issue for the nCino CI jobs using Spreads Templates where the users were getting NullPointerException error when trying to deploy with Insert/Update with Null Values option (internal ticket).

10 July 2022

(ARM v22.1.15) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the constructive changes are picked in the CI build, although no constructive changes are in-between From and To revisions (internal ticket).
Fixed an issue with the SFDX job, where for the Report metadata type, the rollback feature was working weirdly (internal ticket).
Fixed a bug where editing the Dataloader job shows "Job Group" as null or empty (internal ticket).
Vlocity has been upgraded to v1.15.5.
Fixed an issue with the CI job where the version control using Salesforce with attachments was not picking the attachments during CI build (internal ticket).
Fixed an issue where our internal team members could not create a new role from the Admin section (internal ticket).
Fixed a bug where the Invalid Schema error is seen for non-SFDX prevalidation merge (internal ticket).

03 July 2022

(ARM v22.1.14) This is a maintenance release. The following items were fixed and/or added:

Fixed a bug where our internal team members were not able to view the Salesforce Org URLs in the My Profile section (internal ticket).
Fixed an issue where the metaXML file were not retrieved for the ContentAsset metadata type for the SFDX "Entire Branch" merge case (internal ticket).
Fixed an issue where the deployment validation were failing for the prevaildation merge with the error: No source backed components present in the package (internal ticket).

26 June 2022

(ARM v22.1.13) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the user was getting "field integrity exception: unknown (CreatedByID(0051X00000BbMIR) is not in org" for the records that were available in the destination org.
Fixed an issue where the Git tags were being added to the queue but not being processed (internal ticket).
Fixed an isse where the delta was getting failed in the EZ-Commit flow (internal ticket).
Fixed a bug where the users were not able to view the log reports after registering Tags via ARM (internal ticket).
Fixed an issue where the tags creation got failed when the tag name contains 'error' with custom API flow (internal ticket).

19 June 2022

(ARM v22.1.12) This is a maintenance release. The following items were fixed and/or added:

Fixed a minor bug where the child members checkboxes remained checked even when the parent metadata type was unchecked (internal ticket).
Fixed an issue where the users while accessing the commits older than 30 days, ARM throws Request parameters are empty/null error (internal ticket).
Fixed an issue where the users when accessing the Commit History page throws Invalid FilterExpression error (internal ticket).
Fixed an issue where the TAF execution were getting failed (internal ticket).
Fixed an issue where the From Revision was not visible when user access their CI job from CI Job History page (internal ticket).
Fixed an issue that caused Chrome to crash anytime a user attempted to view the functional test results for the task of running a Selenium Maven test. The functional test results screen enters a continuous cycle of requests, which crashes the browser (internal ticket).
Fixed an issue where the skip members feature of ARM was not working as expected (internal ticket).

12 June 2022

(ARM v22.1.11) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the Jenkins builds were failing during the CI/CD process (internal ticket).

05 June 2022

(ARM v22.1.10) This is a maintenance release. The following items were fixed and/or added:

29 May 2022

(ARM v22.1.9) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the Jenkins builds were failing during the CI/CD process (internal ticket).

22 May 2022

(ARM v22.1.8) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.

15 May 2022

(ARM v22.1.7) This is a maintenance release. The following items were fixed and/or added:

08 May 2022

(ARM v22.1.6) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.

01 May 2022

(ARM v22.1.5) This is a maintenance release. The following items were fixed and/or added:

24 April 2022

(ARM v22.1.4) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the "invalid session" error occurs when the user tries to delete and resave the cloned CI job.

17 April 2022

(ARM v22.1.3) This is a maintenance release. The following items were fixed and/or added:

Enabled feature flag settings to select between classic ARM and Salesforce CLI process to generate package manifest.
Fixed the below nCino issues:
- Non-template records were being picked up during nCino deployment.
- Non-template records are fetched in the dataset.
- Spread Statement Record failing with the error “Missing Statement Types.” This is now fixed.

10 April 2022

(ARM v22.1.2) This is a maintenance release. The following items were fixed and/or added:

Fixed the issue where the SFDX deployment is getting failed even though the user uploaded the correct file.
Fixed a bug where the static code analysis (SCA) status shows as in progress for a failed execution.
Fixed a bug where the New EZ-Commit > Deleted Component tab throws a null error on expanding the metadata types.
Addressed out of memory (OOM) and other performance issues in this weekly release.

03 April 2022

(ARM v22.1.1) This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were receiving layout permissions errors when using Prevalidation Commit.
Fixed an issue where the users were unable to update any changes in the permission section.

27 March 2022

(ARM v22.1.0) This is a maintenance release. The following items were fixed and/or added:

ARM Release Notes 21.6

Date of Release: 21 November 2021

On this page:

New Features

Pull Request Support for Azure DevOps

During Ez-Commit and new Pull Requests, you can now create a Pull Request in Azure with the assignee.
You should be able to choose the repository, the base branch, and another branch to compare during the creation of a pull request.
A link to the Azure DevOps application will be included in each pull request created in AutoRABIT. The pull request can also be approved directly from the AutoRABIT application.

Enhancements

Audit Log Report

AutoRABIT had an audit report feature that gave you a comprehensive view of your business operations by fostering a collaborative operational audit environment. In this release, we've made some enhancements and added a button called "Audit Log Report" on the CI job page, which allows you to generate a report in PDF format for a specific period.

We've improved the CI Job Result screen by giving users the option to generate an Audit log report for internal auditing purposes. This is a report of CI jobs deployments and the commits associated with each deployment, including commit details such as Author, Commit Time Stamp, and so on.
We changed the timestamp in the Audit log report from 12-Hour format to 24-hour UTC format by default to comply with ISO 8601 notation, which is a commonly recommended format for representing date and time.
Added support for custom “keynames”, “Salesforce Org type“ and “AR SF Org type” in the Audit trail report wherever Salesforce org name details are applicable.

Salesforce CLI Upgrade

Salesforce CLI is a command-line interface for working with your Salesforce org that makes development and build automation easier. It can be used to create and manage organizations, synchronize sources to and from organizations, create and install packages, and more. In this version of ARM, Salesforce-DX CLI is upgraded to the latest 7.129 version.

Salesforce Winter (API 53) Support

In order to keep our product up to date with the most recent Salesforce updates. AutoRABIT now supports the most recent API version 53 in this release. Now our Salesforce developers will begin using API 53 on their Sandboxes for development. The most recent API version is intended for customizing the metadata model and developing tools to manage it.

Improvements

Platform Improvements

We've been working hard over the last few weeks to improve our platform's stability, performance, query optimizations, code smells, security vulnerabilities, and reliability. With this release, you will notice significant improvements in our application, such as faster page load times, improved performance, and faster search functionality, among other things.
JQuery Upgrade: JQuery was updated from version 1.8.3 to version 3.6. Upgrading to the most recent version of jQuery makes our application more secure, as well as potentially faster in terms of script execution and loading.

UI Improvement

Across the CI Job module, "Load More" buttons have been replaced with "Previous" and "Next" buttons. This new feature will allow our users to display 25, 50, 75, or 100 records on a single page and navigate between pages using the Previous and Next buttons. This feature was previously limited to the Version Control module, but it has recently been expanded to include the CI Job module as well.

Changelogs

11 Mar 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed the following SSO errors:
- Unable to log in via SSO in the chrome and the firefox browser.
Fixed a bug where users were getting an undefined error for the standard templates while editing the CI job.
Fixed an issue where the users were unable to replace attachment records in the destination org.

06 Mar 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were receiving layout permissions errors when using Prevalidation Commit.
Fixed an issue where the users were unable to update any changes in the permission section.

27 Feb 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were unable to update the "Validation checks" status from the in-progress state to the completed state.
Fixed an issue where changes from multiple package directories were not being retrieved without selecting a package directory.
Fixed an issue where the users were unable to attach the CSV file while carrying out the CI deployment.
Fixed an issue that caused users to receive an invalid session error when changing their password.

20 Feb 2022

This is a maintenance release. The following items were fixed and/or added:

13 Feb 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed a bug where the sub-users without admin privileges were able to export and download the org users' data from Admin > Users section.
Fixed a minor user-interface bug where the users were unable to find the Resolve Conflict button to resolve the merges conflict. This is now resolved.

Limitations identified in this release:RestrictionRule metadata type is not supported for the SFDX deployment.

06 Feb 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed the below UI issues:
- For the entire deployment, the "To Revision" radio button was disabled, and users were unable to select revisions from the list provided.
- Although the field "Timezone" was mandatory upon signup, the users were able to proceed without picking a timezone.
Fixed a bug where the users were unable to register a dev hub on the SDFX > Hub Management page.

30 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were receiving an error message saying "Please select the date" even though the date was selected when registering the SVN Branch.
Fixed an issue where when users expanded the metadata types on the Profile Manager screen, they were able to spot duplicate child components.
Fixed a bug that displays the nCino-related CI Jobs on the ARM CI Jobs Results page.

29 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision.
Fixed an issue where the metadata types "NavigationMenu" and "IframeWhiteListUrlSettings" were included in the build view changes for both DX and non-DX CI Jobs, despite being excluded.

23 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were facing the "Null Pointer Exception" error during the merge prevalidation process.
Fixed an issue where If the users picked all the conflicted files during a merge request, they would receive an error message saying "Please click on any conflicted file."
Fixed an issue where the users were unable to find the log report for the newly created branch in AutoRABIT.
Fixed an issue where the users were unable to find out the work item statuses during the deployment process for the unlocked packages.
ALM Enhancements:
- Added a new section called "ALM Management" to the Admin module for merge requests
- Detailed information on all of your ALM's active and inactive sprints.
- Smart commits to reading the comment in a revision associated with your ALM story.
- We have introduced the ALM Details section that lists the work items linked with the commits along with the existing and post-merge status.
- Ability to keep the work item status without a change or update it during EZ-Commit.
- You may now configure the job to pick up revisions based on your work item status while deploying from version control to a Salesforce org, allowing you to adjust the status even after a successful rollback.

16 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision.
Fixed an issue where the metadata types "NavigationMenu" and "IframeWhiteListUrlSettings" were included in the build view changes for both DX and non-DX CI Jobs, despite being excluded.

09 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were receiving an error message saying "Please select the date" even though the date was selected when registering the SVN Branch.
Fixed an issue where when users expanded the metadata types on the Profile Manager screen, they were able to spot duplicate child components.
Fixed a bug that displays the nCino-related CI Jobs on the ARM CI Jobs Results page.

02 Jan 2022

This is a maintenance release. The following items were fixed and/or added:

Fixed a bug that restricted users from entering the credential name on the "Create Credential" screen because the field was disabled.
Fixed a bug where the super administrator was getting an empty popup screen when navigating to the Process Summary page.

26 Dec 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the users were receiving an error message saying "Please select the date" even though the date was selected when registering the SVN Branch.
Fixed an issue where when users expanded the metadata types on the Profile Manager screen, they were able to spot duplicate child components.
Fixed a bug that displays the nCino-related CI Jobs on the ARM CI Jobs Results page.

19 Dec 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision.
Fixed an issue where the metadata types "NavigationMenu" and "IframeWhiteListUrlSettings" were included in the build view changes for both DX and non-DX CI Jobs, despite being excluded.

12 Dec 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the deployment report is getting failed while doing prevalidation merge with the report folder.
Fixed an issue where the code coverage percent is not available in the case of SFDX merge operation.
Fixed an issue where the code coverage percentage shows as 0 in the UI logs even after deployment validation is passed.
Fixed a bug where the changes are being committed even after a failed validation.
Fixed an issue where the package directory filter in the release labels is not working as expected.

05 Dec 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the alm mapping details for the scratch org with alm configuration could not be found.
While executing scratch org alm commit with skip mapping set to false, the current ALM work item status was reporting "empty" results. This is now fixed.
Fixed a bug that allowed users to save multiple criteria rows with the same priorities for ApexPMD.
Fixed an issue where the repository filter on the Commit History screen was reset to default after resolving a conflict.
Fixed a bug where the failed component count position is wrong when the window is scrolled.

28 Nov 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the "include delete records" checkbox is de-selected automatically during editing the data loader extract job.
Fixed an issue where the scratch org permissions are not visible on "hub level permissions" and "scratch org permissions" screens.
Fixed Ez-commit issue where a sub user with only one repository registered with AutoRABIT, is not able to find/select his repository in the EZ-Commit screen.
Fixed an issue where the repository filter is reset to default during the conflict resolve flow.
Fixed registering the branch issue when the branch registration crossed 100 limits in AutoRABIT.
Fixed a bug where the parent checkbox in the download zip for CI Job is not working as expected.
Fixed wave-dependent missing files from the package during the prevalidation merge operation.
Fixed an issue where the non-SFDX CI job for WaveTemplates is showing no modifications when triggered.
Fixed single data loader and data loader pro filter issues while carrying out the edit functionality.

21 Nov 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the user was not able to retrieve the metadata to deploy the changes using AutoRABIT's deployment feature.

ARM Release Notes 21.5

Date of Release: 29 August 2021

On this page:

In keeping with our dedication to continual improvement, the August-21 (AR 21.5) release delivers a plethora of exciting upgrades and improvements to our AutoRABIT application.

Enhancements

UI/UX Improvements: Focused on application performance and user experience. Try it out for yourself and let us know how to feel:
- Page Navigation: When working with several records, breaking data into multiple pages is always a good idea. You can now view 25, 50, 75, or 100 records on a single page, and use the Previous and Next buttons to switch to the previous or next page. This feature is now only available in the Version Control module, but it will be expanded to other modules in future releases.
- Never miss a required field: You will be prompted to fill in all the required fields before you proceed. Follow the UI highlights to minimize rework.
Customize CI jobs for desired Salesforce API versions: To support different Salesforce API versions for distinct Salesforce orgs instead of a global setup, we've added a new checkbox named Salesforce API version across the CI Job module. This will offer a granular facility in a CI job to select the required Salesforce API version.
Improved Audit Trail Report: Additional data was added to the reports to support improved report analysis.
Performance Improvement: Waiting is always boring- we have reduced that wait for you.
Salesforce CLI Upgrade- Salesforce CLI upgraded to the latest stable 7.112 version.

Changelogs

14 November 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed deployment issues
Fixed SFDX parent and child job triggered the issue.
Fixed an issue where the review artifact with AutoDraft functionality was not working properly in the EZ-commit screen.

07 November 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed an issue where the wave template related dependent files were missing from the package [CI, Deployment, VC].
Fixed an issue where all existing credentials for version control mappings that were created using the Profile screen were reset.

31 October 2021

This is a maintenance release. The following items were fixed and/or added:

Fixed a bug that caused metadata retrieval to fail with a Null error during revision range deployment.
[Profile Manager] Fixed an issue where the org compare feature would not work when three orgs were configured, resulting in a "Empty screen" error.
[Profile manager] Fixed an issue where after comparison, duplicate metadata entries and empty popups were displayed.
[nCino CI Jobs] Fixed an issue where the unwanted objects are displayed on editing the cloned CI Job.

PreviousRelease Notes NextCodeScan Release Notes

Last updated 2 days ago

Was this helpful?