ARM Release Notes

ARM Release Notes 26.3.11
Release Date: 13 Sep 2026
Apache Tomcat 11.0.24 Upgrade – Enhancement
ARM now runs on Apache Tomcat 11.0.24 on Shared, Dedicated, and On-Premise instances. This replaces 11.0.22 and includes Tomcat security and stability updates. Application startup and existing ARM workflows are unchanged.
Salesforce Org Delete After Clone Fix
Fixed an issue where a cloned Salesforce org could not be deleted if the org name contained a leading or trailing space. ARM showed Salesforce org does not exist even though the org was visible in the UI.
With this fix, org names are trimmed when registering or cloning. Cloned orgs can be deleted in both the Classic UI and the New UI. Re-authentication no longer clears the cloned flag or the original registration date.
EZ-Merge Validating Salesforce XML Log Fix
Fixed an issue where EZ-Merge showed No log data available during the Validating Salesforce XML stage when Skip Flow/Layout/Profile/Perm.Set Access-Setting Duplicity Check was enabled.
With this fix, that stage writes execution details to the process log in both the Classic UI and the New UI, for DX and Non-DX repositories.
EZ-Commit Folder Metadata Duplicate Member Fix
Fixed an issue where removing a folder-based metadata type and adding it again listed the same members twice. This affected folder types such as ReportFolder, DashboardFolder, DocumentFolder, and EmailFolder.
With this fix, removing the folder clears its members. Adding the same folder again lists each member only once in both the Classic UI and the New UI, for DX and Non-DX repositories.
CI Job Abort Cleanup Fix
Fixed an issue where aborting a CI Job from the UI could leave an unhandled interruption error in the agent log during job cleanup.
With this fix, abort completes for Version Control to Org and Org to Org CI Jobs without that agent error.
Scratch Org Create Button Fix – New UI
Fixed an issue in the New UI where Create Scratch Org stayed disabled on the last step of the Scratch Org flow when only the main user was present.
With this fix, the button is enabled for a single main user and for orgs with multiple permitted users.
SCA Job Name Validation Fix
Fixed an issue where an SCA job name that included \ or ; could be saved, then failed on Run or Delete. A semicolon in the name could also end the user session.
With this fix, new SCA job names reject those characters. Existing jobs can still be run, scheduled, deleted, and viewed in logs and history.
Branching Baseline Revision Details Fix – New UI
Fixed an issue in the New UI where Branching Baseline Revision Details could fail to render the revision value.
With this fix, Revision Details open from a completed baseline row and show author, date, message, file count, and revision without an error.
ARM Release Notes 26.3.10
Release Date: 6 Sep 2026
API 67 Metadata Types – Enhancement
ARM now supports the following Salesforce API 67 metadata types across commit, constructive changes, and deployment:
AdminSuccessSettings
AgentforceAccountManagementSettings
AgenticCtxtDecorDefinition
DataMaskPolicy
DataMaskSettings
These types can be retrieved, compared, committed, and deployed when the org is on API 67.0 or later. Settings types can be updated but cannot be deleted, which matches Salesforce Metadata Coverage. Existing metadata types are unchanged.
Run Tests Based on Changes Deployment Log – Enhancement
When Run Tests Based on Changes is used, the deployment log previously showed only the final consolidated list of Apex test classes. It was not clear which classes came from the deployed Apex, dependency mapping, or default org test classes.
With this enhancement, the deployment log lists:
Test classes identified from the Apex classes in the package
Default Apex test classes configured on the Salesforce org
The final consolidated list passed to Salesforce
This applies to Version Control to Org and Org to Org deployments in both the Classic UI and the New UI.
Data Retention Audit Cleanup Fix
Fixed issues where the daily Data Retention job did not delete eligible Workspace Audit and Mailer Audit records. The job could report success while old audit rows were left in place.
With this fix, ARM normalizes legacy audit values and completes Workspace Audit and Mailer Audit cleanup according to the configured retention period.
Release Label and High-Volume Page Load Fix
Fixed an issue where Release Labels and other high-volume pages could stop responding with a DynamoDB throughput error. Opening a label with a large number of revisions could leave the page stuck.
With this fix, ARM retries and handles temporary DynamoDB capacity limits so Release Labels, CI Jobs, Deployments, EZ-Commit, EZ-Merge, Feature Migration, Data Loader, and Administration pages can load and complete.
EZ-Commit Prompt Metadata File Diff Fix
Fixed an issue where EZ-Commit file diff failed for Prompt metadata destructive changes with no matching SFDX folder type. After the diff, Prompt could also show No Modifications because the file extension was incorrect.
With this fix, Prompt metadata is recognized in DX and Non-DX repositories. File diff and constructive and destructive commits complete, and Prompt files use the .prompt-meta.xml extension.
EZ-Commit Picklist Record Type Scope Fix
Fixed an issue where committing picklist changes on one object could show extra file changes on Record Types for other objects. Deactivating or activating picklist values on the selected object updated unrelated objects that shared similar picklist labels.
With this fix, EZ-Commit applies picklist and Record Type updates only to the selected object in both DX and Non-DX repositories.
Unused API Token Endpoint Removal
Removed an unused API endpoint that returned API token values in the HTTP response body.
Token creation and use in the application and the VS Code plugin are unchanged.
DataLoader + DataLoader Pro Release Notes 26.3.10
Release Date: 6 Sep 2026
Correct Empty Relationship Fields in Data Loader Exports
Resolved an issue where empty User Role or Manager fields could incorrectly display the user’s name in exported CSV files. Data Loader now leaves these relationship fields blank when no value is available. The correction applies to normal and aggregate queries in both the existing and new interfaces.
ARM Release Notes 26.3.9.1
Release Date: 2 Sep 2026
Salesforce Winter ’27 (API 68.0) Deploy Result Parsing Fix
Fixed an issue that caused EZ-Merge, deployments, and CI Jobs to fail after Salesforce upgraded sandboxes to Winter ’27 (API 68.0). When an Apex test level was selected, ARM could not parse the updated Metadata API deploy result and failed with "Cannot invoke "com.sforce.soap.metadata.DeployDetails.getComponentFailures()" because "deployDetails" is null". Validations that ran without a test level completed successfully, and the same deployment could succeed directly in Salesforce. ARM Salesforce libraries are now updated to API 68.0 so deploy results and test coverage responses parse correctly across all Apex test levels.
Impacted Areas:
EZ-Merge
Deployments
CI Jobs
Pre-Validated Commit
Pre-Validated Merge
Salesforce Code Coverage Reports
ARM Release Notes 26.3.9
Release Date: 30 Aug 2026
Support Custom Package XML Filenames in Deployment – Enhancement
Custom Deployment previously required the uploaded Salesforce package manifest to be named exactly package.xml. Customers maintaining multiple manifests, such as qa.xml, uat.xml, or production.xml, had to rename the file before each deployment.
Custom Deployment now accepts any .xml filename that contains a valid Salesforce Package manifest, consistent with EZ-Commit. ARM validates the XML contents rather than the filename, processes accepted files internally as package.xml, and rejects non-package metadata files such as Profile or CustomObject XML. Existing deployments that use package.xml continue to work without change.
Extend Deployment Approval Auto-Reject Timeout to 7 Days – Enhancement
Pending L1 and L2 deployment approvals were automatically rejected after 3 days (72 hours), which did not always give approvers enough time to complete review.
Pending L1 and L2 approvals now remain active for 7 days (168 hours) before auto-rejection. A notification email is sent 24 hours before auto-rejection to the primary and secondary approvers and the deployment creator. The notification includes the deployment identifier, pending approval level, auto-rejection date and time, and the action required to avoid rejection. Approvals or rejections completed before the warning window do not trigger the reminder. Existing approval statuses, including Auto Rejected, are unchanged.
Display Actual Static Code Analysis Pass/Fail Result – Enhancement
ARM previously displayed a green tick when Static Code Analysis execution completed, even when the CodeScan or SonarQube Quality Gate had failed. This made it appear as though analysis had passed.
ARM now keeps the existing completion indicator and displays the actual Quality Gate result next to Static Code Analysis as Analysis: PASS or Analysis: FAIL. PASS and FAIL use the corresponding success and failure treatments. The result is shown only after the final outcome is received from CodeScan or SonarQube and applies to Commit, Merge, and Quick Merge in both the Classic UI and the New UI. This display applies to CodeScan and SonarQube only.
ECA Concurrent Session Lockout Fix
Fixed an issue where an ECA-enabled Salesforce org could be locked out with an INVALID_SESSION_ID error when a CI Job using Deploy from Salesforce Org and an EZ-Commit ran at the same time against the same source org. After the conflict, Re-Authorize did not reliably restore the org.
With this fix, ARM coordinates refresh-token rotation for the same org so concurrent CI Job and EZ-Commit operations can complete without invalidating each other’s session. Re-authorization restores org connectivity when needed, and single-operation workflows are unchanged.
OAuth and OAuth-with-ECA Registration and Re-Authorization Fix
Fixed issues where Salesforce org registration and re-authorization failed in several OAuth flows. OAuth to OAuth-with-ECA re-authorization did not complete, new OAuth registrations and re-authorization below API version 64 failed, and OAuth to OAuth-with-ECA re-authorization failed when PKCE was disabled.
With this fix, PKCE is supported for the standard OAuth flow as well as OAuth via ECA. Registration, re-authorization, token refresh, and test connection succeed with PKCE enabled or disabled, including when converting an existing org from OAuth to OAuth via ECA.
EZ-Merge Git Push Status Fix
Fixed an issue where EZ-Merge could be marked Successful when the remote Git push was rejected, for example by branch protection rules. The locally created commit revision was still shown as successful, and users had to inspect logs to discover that the push had failed.
With this fix, ARM validates the remote Git push result before marking the merge complete. If the push is rejected, the merge is marked Failed, the local commit revision is not shown as a successful revision, and the Git rejection error is displayed to the user. Merges that push successfully continue to be marked Successful.
Revision Number Display Fix in Commits, Merges, and CI Jobs
Fixed an issue where the full Git commit hash was displayed after merge conflict resolution, in merge notifications, in the EZ-Commit label section, and in CI Jobs.
With this fix, revision numbers are displayed as a short SHA across Commit, Merge, and CI Job views in both the Classic UI and the New UI.
Profile Compare Deploy View Fix
Fixed an issue in Profile Compare where Deploy and Update and Deploy applied permission changes to the target org, but the comparison grid did not refresh to show the post-deployment state. The grid could display stale or inverted source and target values.
With this fix, comparison data is refreshed after Deploy and Update and Deploy so the grid reflects the actual org state. Permissions continue to be applied only to the target org.
Vlocity Release Label Merge Board Type Fix
Fixed an issue where the Board Type field was not auto-populated during Release Label Merge for Vlocity release labels. The field remained blank and required manual input, unlike non-Vlocity release label merges.
With this fix, Board Type is automatically populated from the selected Vlocity release label and repository configuration for both release label and commit label merge workflows.
CI Job DynamoDB Throughput Error Fix
Fixed an issue where CI Jobs could fail during build processing with a DynamoDB throttling error indicating that throughput exceeded the current table or index capacity.
With this fix, CI Job processing handles this condition correctly so scheduled, webhook, pull request, and parallel CI Job executions can complete without this failure.
Quick Deploy After Validate Only Fix
Fixed an issue where Quick Deploy was unavailable after a successful Validate Only deployment to a Production org when the test level was set to Salesforce Defaults. In the Classic UI, the label name was disabled. In the New UI, a valid Asynchronous ID was not available for selection.
With this fix, Quick Deploy is available after a successful Validate Only deployment to Production when using Salesforce Defaults. The label name is populated and ARM-generated Asynchronous IDs are available. Quick Deploy remains unavailable after Validate Only on non-production orgs when Salesforce Defaults are used, which is expected.
Branching Baseline Commit Log Fix
Fixed an issue where initiating a Branch Baseline could fail with a UI exception while loading commit logs, including the message Error parsing SCM commit log file. Concurrent access to the commit log file could corrupt the file and block the baseline.
With this fix, ARM locks the commit log file during read and write operations and releases the lock when the operation completes. Branch Baseline can retrieve commit logs and proceed even when push protection is enabled or configuration files such as .gitignore and package.xml are missing from the branch.
DataLoader + DataLoader Pro Release Notes 26.3.9
Release Date: 30 Aug 2026
Data Loader Pro Job Configuration Settings Not Retained
Resolved an issue where selected Data Loader Pro job settings were not retained during execution.
Options such as disabling workflows and validation rules and processing null values are now saved and applied correctly.
ARM Release Notes 26.3.8
Release Date: 23 Aug 2026
Create Pull Request for Merged Changes in ez-Merge – New Enhancement (New UI)
Introduced the Create Pull Request On Merged Changes option in ez-Merge. When enabled, ARM applies the merged changes to a temporary branch, validates them, and creates a pull request targeting the selected destination branch instead of committing the changes directly.
The option is available only when Pre-validation Merge is configured and supports all pull-request-enabled repositories. Pull request details and the URL are available in the new Pull Request Creation process log.
Duplicate Picklist Member Selection Fix in EZ-Commit – New UI
Fixed an issue where a Custom Object already added as a Picklist member remained available in the dropdown and could be selected again without any feedback.
With this fix, previously added Custom Objects are no longer displayed in the dropdown, preventing duplicate selection and improving the metadata selection experience.
Branching Baseline Gitignore Handling Fix
Fixed an issue where the Branching Baseline process replaced the repository’s existing .gitignore file with a default version. This caused ignored files, such as manifest/package.xml, to be included and could trigger repository push-protection violations.
With this fix, ARM retains and applies the existing .gitignore file during the Branching Baseline process. The default .gitignore file is used only when one is not already available in the repository.
EZ-Commit File Diff Failure Fix – Old UI
Fixed an issue where Picklist metadata was incorrectly treated as a Custom Field when reusing a previously validated EZ-Commit label. This caused false deleted components and resulted in a file-diff failure.
With this fix, Picklist values are correctly processed as Picklist metadata, preventing false destructive entries and file-diff failures.
SonarQube SCA Execution with S3 Fix
Fixed an issue where SonarQube SCA executions failed when using S3 and incorrectly displayed the Updating CodeScan Project message.
With this fix, the S3-specific analysis path is restricted to CodeScan, ensuring SonarQube SCA executions are processed correctly.
Ignore Missing Visibility Setting Display Fix
Fixed an issue where the Ignore Missing Visibility setting was not displayed in the commit history details.
With this fix, the setting and its configured value are now visible under More on the Commit History Details page.
Standard Field Changes Detection Fix in EZ-Commit – New UI
Fixed an issue where changes to standard field permissions were not detected or displayed during comparison in EZ-Commit.
With this fix, standard field permission changes are correctly retrieved and displayed in the New UI.
Skipped Components Exclusion Fix
Fixed an issue where components configured as skipped were still included during repository-to-org deployments, even when Do Not Include Skip Members During Deployment was enabled.
With this fix, skipped components are correctly excluded from CI Job and Manual Deployment workflows for both DX and non-DX repositories.
Password Reset Screen Responsiveness Fix
Fixed an issue where the password reset screen became unresponsive when a Pendo survey appeared during login, preventing users from entering a new password.
With this fix, users can complete the password reset process without interference from Pendo notifications.
Support Contact Information on Password Reset – Enhancement
Added the AutoRABIT Support email address to the password reset message. Users who do not receive the reset email or continue experiencing login issues can now contact support@autorabit.com directly for assistance.
CheckmarxOne Analysis Report Category Display Fix – New UI
Fixed an issue where the Critical category was missing from CheckmarxOne SCA analysis reports and appeared as an unlabeled column.
With this fix, all severity categories—Critical, High, Medium, Low, and Information—are displayed correctly.
AI Bundle Metadata Processing Fix
Fixed issues where AiAuthoringBundle and GenAiPlannerBundle metadata could be incorrectly included or processed during commit, CI Job, and deployment workflows.
With this fix, bundle metadata is handled correctly based on user selection, exclusion lists, and skipped members for both DX and non-DX repositories, preventing unintended deployment failures.
DataLoader + DataLoader Pro Release Notes 26.3.8
Release Date: 23 Aug 2026
Data Loader Pro Org Re-Registration Consistency
Corrected inconsistent behavior between manual and scheduled executions after a Salesforce source org was re-registered with different name casing. The system now correctly identifies the source and destination orgs regardless of case sensitivity in the registration name.
ARM Release Notes 26.3.7
Release Date: 16 Aug 2026
Vlocity CI Job Deployment Report Fix - New UI
Fixed an issue in the New UI where Deployment Reports for Vlocity CI Jobs displayed a "Reports not available"message even when the deployment completed successfully. The CI Job deployment flow has been updated to capture and store Vlocity deployment results correctly, allowing users to view component-level deployment details directly from the CI Job History.
Vlocity Deployment Validation Flow Fix
Fixed an issue where Vlocity deployments and Quick Merge workflows could fail or remain stuck due to unsupported validation and Static Code Analysis (SCA) options being processed for Vlocity components.
The deployment configuration flow has been updated to correctly handle Vlocity deployments by hiding SCA, deployment validation, and their related configuration fields when they are not applicable. This ensures Vlocity deployment and Quick Merge workflows can be configured and processed without unintended validation failures.
Auto Populate Apex Test Classes Progress Status Fix
Fixed an issue where the Auto Populate progress status for default Apex test classes was incorrectly carried over when switching between Salesforce orgs. The loading and progress state is now handled independently for each selected org, allowing users to initiate Auto Populate for different Salesforce orgs without requiring a page refresh or waiting for another org's process to complete.
EZ-Commit Version Control Credential Handling Fix
Fixed an issue where EZ-Commit used the repository credentials configured under Admin settings instead of the logged-in user's profile-mapped Version Control credentials when Salesforce Org Author was set to All and Skip Mappings was disabled.
EZ-Commit now consistently uses the credentials mapped to the user performing the commit, ensuring repository permissions and branch protection rules are correctly enforced for both Direct and Pre-Validated commits.
Rollback Button State Fix - New UI
Fixed an issue in the New UI where the Rollback button remained enabled even after a rollback completed successfully. The Deployment History screen now disables the Rollback button while rollback is in progress and hides it once the rollback has completed successfully.
Weekly Reports Data Consistency Fix
Fixed an issue where data generated from the Weekly Reports module did not match the corresponding build information displayed in CI Job History. The filtering logic in both the UI and back end has been corrected to ensure reports display accurate and consistent CI Job build data across both the Classic and New UI.
CI Job Apex PMD SCA Criteria Status Fix
Fixed an issue where CI Jobs configured with Apex PMD SCA criteria could be incorrectly marked as unstable during execution. The SCA criteria processing and logging have been corrected to ensure the build status accurately reflects the Apex PMD analysis results.
EZ-Commit ALM Mapping Fix - Classic UI
Fixed an issue in the Classic UI where ALM Work Item details were not correctly populated and configured during EZ-Commit when using a Scratch Org with Skip Mappings disabled. The EZ-Commit selection flow now ensures ALM work items are fully loaded before resolving their statuses, allowing the mapped work item, current status, and available status options to be populated and function correctly. This provides consistent ALM mapping behavior across the Classic and New UI.
DataLoader + DataLoader Pro Release Notes 26.3.7
Release Date: 16 Aug 2026
Summary Side Panel Alignment Fix
The Summary side pop-up in Dataloader Pro and DL Config now displays content with proper left alignment. This reduces unused blank space, improves readability, and helps prevent long values from appearing clipped at the right edge.
ARM Release Notes 26.3.6
Release Date: 9 Aug 2026
Azure DevOps SSO Enhancement New UI
Enhanced Azure DevOps Single Sign-On (SSO) to support authentication using Microsoft Entra Tenant ID and Object ID, providing greater flexibility in user identity mapping. Administrators can now configure these identifiers for users, enabling successful SSO authentication even when the Identity Provider (IDP) username differs from the ARM username. If the Tenant ID and Object ID are not configured or do not match, ARM automatically falls back to the existing username-based validation, ensuring backward compatibility with current SSO configurations.
Org-to-Org CI Job Incremental Build Fix
Fixed an issue in Org-to-Org CI Jobs where destructive change tracking did not behave correctly for unpackaged deployments. The destructive change processing has been improved to correctly maintain the destructive baseline, ensuring deleted components are tracked consistently across deployment cycles while preserving the expected behavior for incremental builds.
External Credential File Diff Fix
Fixed an issue where deleting External Credential metadata in DX repositories caused file diff generation to fail during EZ-Commit with a "No enum constant" error. ARM now correctly recognizes External Credential metadata during deletion workflows, enabling successful file diff generation for both direct and pre-validation commit operations.
Scratch Org Azure Boards Mapping Fix - New UI
Fixed an issue in the New UI where the Team Name field was not displayed during Scratch Org creation when configuring Azure Boards ALM mappings. The ALM mapping workflow has been updated to correctly display the required Team Name field, allowing users to complete Scratch Org creation without additional manual configuration.
Deployment Destructive Changes Pagination Fix
Fixed an issue where the Destructive Changes selection list did not display all available components during deployments, making it difficult to select destructive changes. The pagination logic has been improved to dynamically track the total number of filtered records, ensuring all matching components are displayed correctly during browsing and search.
Profile Rollback Permission Restoration Fix
Enhanced the rollback process for Profile metadata to correctly restore Object and Field permissions to their original state. ARM now preserves the pre-deployment permission state, including cases where no permissions previously existed, ensuring newly added permissions are properly removed during rollback for both Deployments and CI Jobs.
Search & Substitute XPath Handling Fix
Fixed an issue where Search & Substitute rules failed to replace values containing special characters, such as single quotes, in Custom Metadata fields. The XPath parsing logic has been corrected to properly handle these values, ensuring substitutions are applied successfully during deployment instead of being silently skipped.
Custom Field Translation Deletion Fix
Fixed an issue where deleting a Custom Field through EZ-Commit did not remove its associated Field Translation metadata from the repository. ARM now automatically deletes the related field translations when a destructive commit is performed for Custom Fields, ensuring translation metadata remains synchronized with the deleted field in both DX and non-DX repositories.
Ignore Missing Visibility Settings Fix
Fixed an issue in CI Jobs where enabling Ignore Missing Visibility Settings, If Package Contains Profiles or Permission Sets incorrectly removed valid Permission Set tab visibility entries during deployment. The backend logic has been updated to remove only references to metadata that are unavailable in the target org, preserving existing valid visibility settings and preventing unintended changes to Permission Sets.
EZ-Commit Object Selection Fix - New UI
Fixed an issue in the New UI where duplicate object names could appear in the EZ-Commit object selection picklist, preventing users from accessing the required fields. The object filtering logic has been updated to correctly handle object prefixes, ensuring object names are displayed uniquely and the appropriate fields are available for selection.
Deployment Timeout Status Fix
Fixed an issue where long-running Quick Deploy operations with a large number of components could be incorrectly marked as Timed Out in ARM, even though the deployment completed successfully in Salesforce. The deployment status handling has been improved to prevent active deployments from being incorrectly classified as timed out while background processing is still in progress, ensuring the deployment status accurately reflects the final outcome.
Automatic Cleanup of Deactivated Picklist Value References
Introduced an enhancement that automatically removes references to deactivated picklist values from affected Record Types during metadata processing. When a picklist value is deactivated, ARM identifies all Record Types belonging to the same object, removes only the invalid picklist value references, and automatically includes the updated Record Types in the generated deployment or commit package. This ensures metadata consistency across branches and deployments while preserving all other Record Type configurations and unrelated metadata.
DataLoader + DataLoader Pro Release Notes 26.3.6
Release Date: 09 Aug 2026
External ID Mapping Persistence
Addressed a DataLoader issue reported through Support Case, where saved custom External ID field mappings reverted after a browser refresh. The mapping now persists as expected, helping users retain intended source-to-destination field relationships across sessions.
ARM Release Notes 26.3.5
Release Date: 2 Aug 2026
Profile Rollback Restoration Improvement
Enhanced the rollback process for Profile metadata to ensure profile permissions are restored correctly after a rollback operation. ARM now creates a more complete Profile backup by including the required dependent metadata, enabling Salesforce to accurately restore Profile permissions during rollback for both CI Jobs and Deployments.
GitLab Cloud Pull Request Support
Added support for creating GitLab Cloud Pull Requests directly from ARM, allowing users to create Pull Requests without leaving the application. ARM validates the selected repository and branches before creating the Pull Request and displays the Pull Request number and URL upon successful creation, providing a streamlined and integrated GitLab Cloud workflow. Refer to the documentation on External Pull Requests here.
Dependent CI Job Execution Fix
Fixed an issue where a Child CI Job triggered automatically after a successful Parent CI Job deployment could fail during the build phase without displaying an error. The post-deployment execution flow has been improved to handle deployment status correctly, ensuring dependent Child CI Jobs execute reliably when triggered from Parent CI Jobs.
Salesforce Org Registration API
Added a new API that enables Salesforce organizations to be registered in ARM using standard Username, Password, and Security Token authentication. The API supports secure, token-based access, allowing Salesforce Org registration to be automated and integrated with external provisioning and onboarding workflows without relying on the ARM user interface. Refer to the full list of API references here.
CI Job Clone API
Added a new API that enables users to clone an existing CI Job in ARM, allowing CI Job configurations to be duplicated programmatically without using the ARM user interface. This simplifies the automation of CI/CD setup and integration with external systems. Refer to the full list of API references here.
CI Job Baseline Revision Pagination Fix
Fixed an issue where the Baseline Revision selection dialog retained the previously selected page after clicking Get Latest Head or Get All Revisions. The revision list now refreshes from the first page, ensuring users can immediately view the latest revisions and browse the complete revision list as expected.
DataLoader + DataLoader Pro Release Notes 26.3.5
Release Date: 02 Aug 2026
DataLoader Pro Job Visibility for Subusers (DevHub Orgs)
Fixed an issue where Dataloader Pro jobs created by a subuser were not visible to the same subuser who created them. Jobs now correctly appear for both the creator (subuser) and admin users, ensuring consistent ownership-based visibility.
ARM Release Notes 26.3.4
Release Date: 26 July 2026
Provar CI Job Execution Fix (New UI)
Fixed an issue where CI Jobs configured by selecting the Provar Plugin before entering Version Control details failed to execute due to missing credential and test file information. The configuration flow has been corrected so Provar jobs execute successfully regardless of the order in which the Provar and Version Control options are selected.
GitHub Enterprise Pull Request Webhook Fix
Fixed an issue where CI Jobs configured to trigger on Pull Request events in GitHub Enterprise were not starting automatically, even though the webhook payload was successfully received. The webhook processing logic has been updated to correctly identify the configured repository and process Pull Request events, ensuring CI Jobs are triggered as expected.
Deployment History Search Fix New UI
Fixed an issue where searching by Deployment Label in the Deployment History page did not return matching deployment records, even though the deployments were present in the history. The search logic has been updated to use the correct deployment label field, ensuring accurate results when searching by full or partial deployment label names.
Scratch Org ALM Mapping Validation Fix
Fixed an issue where creating a Scratch Org failed with the error "Please fill in all required ALM mapping fields" even when all required mappings were configured. The validation logic has been updated to correctly recognize ServiceNow ALM mappings, allowing users to proceed with Scratch Org creation successfully.
Org Synchronization Deployment Navigation Fix (New UI)
Fixed an issue where initiating an Org Synchronization deployment did not automatically redirect users to the Deployment History page. The navigation flow has been updated to redirect users after deployment initiation, and automatic log polling has been added so deployment progress and status are displayed without requiring manual page refreshes.
Automatic OAuth Token Refresh and PKCE Support for External Connected Apps – Enhancement
Enhanced Salesforce External Connected App authentication with automatic OAuth token refresh and support for Proof Key for Code Exchange (PKCE) for newly registered Salesforce organizations.
When an access token expires, ARM uses the stored refresh token to obtain a new access token and automatically retries the original Salesforce API request, eliminating the need for manual reauthorization. PKCE support further strengthens the security of the OAuth authorization flow.
AiAuthoringBundle Merge Validation Fix
Fixed an issue where EZ-Merge validation for AiAuthoringBundle metadata failed because the required .bundle-meta.xml file was not included in the deployment package during merge validation. ARM now automatically includes the corresponding bundle metadata file, ensuring successful validation and consistent behavior across subsequent versions of the same agent.
ARM Release Notes 26.3.3
Release Date: 19 July 2026
Release Label Artifact Update Fix
Fixed an issue where updating an existing Release Label with a new revision did not regenerate the associated artifact correctly, resulting in missing delta files. ARM now regenerates the package manifest using the latest revision data whenever a Release Label is updated, ensuring the generated artifact accurately reflects all changes included in the updated Release Label.
Ignore Installed Components Information Update
Updated the Ignore Installed Components option across ARM to provide clearer guidance on its behavior. An informational message is now displayed wherever this option is available, helping users understand when installed components will be skipped during deployment and CI Job execution. This enhancement improves usability by setting the correct expectations before the operation is initiated.
Additional Vlocity DataPack Metadata Support
Added support for the following Vlocity DataPack metadata types in ARM:
OfferMigrationPlan
CpqConfigurationSetup
IntegrationRetryPolicy
String
These metadata types can now be retrieved through Vlocity commit workflows, committed to version control, and deployed between Salesforce orgs while preserving the required matching keys, parent-child relationships, and Global Key handling.
Financial Cloud Standard Value Set Support
Added support for additional Salesforce Financial Cloud Standard Value Sets to ensure standard picklist values are correctly retrieved during metadata operations. This enhancement improves compatibility with Salesforce Financial Cloud by enabling standard value sets to be included in EZ-Commit, Review Artifact creation, and selective deployment workflows.
Deployment History Visibility Fix
Fixed an issue where newly initiated deployments could temporarily disappear from the Deployment History page after clicking Deploy, requiring multiple page refreshes before becoming visible. The deployment processing flow has been updated to ensure deployment jobs are displayed immediately after they are initiated, providing a more consistent and reliable user experience.
Sharing Rule Destructive Change Detection Fix
Fixed an issue where deleted Sharing Rule metadata was not automatically detected as a destructive change during Version Control deployments. ARM now correctly identifies deleted Sharing Rule components and automatically includes them in the Destructive Items list, ensuring consistent destructive change handling across DX, Non-DX, and Release Label deployment workflows.
ARM Release Notes 26.3.2
Release Date: 12 July 2026
Salesforce CLI Upgrade
Upgraded the bundled Salesforce CLI (SF CLI) from v2.130.9 to v2.140.6 to incorporate the latest Salesforce CLI enhancements, stability improvements, and bug fixes. This update improves compatibility with the latest Salesforce platform capabilities and ensures continued support for ARM operations that rely on the Salesforce CLI.
EZ-Merge Multi-Level Approval Fix - New UI
Fixed an issue in the New UI where EZ-Merge requests requiring multiple approval levels could complete after the first approval instead of progressing through the configured approval workflow. The approval flow has been corrected to properly process all configured approvers, ensuring merge requests follow the expected approval sequence before completion.
Subscription Management for All Customers
Enhanced Subscription Management to be available for all ARM customers, regardless of the number of purchased licenses. Customers with fewer than 20 licenses can now access subscription details, release allocated licenses, and manage license usage without requiring manual intervention for license downgrades. Team management remains unchanged for customers with 20 or more licenses, while the Create Team option is unavailable for customers with fewer than 20 licenses.
This enhancement simplifies license management and enables a smoother license downgrade process.
Vlocity Build Tool CLI Upgrade
Upgraded the bundled Vlocity Build Tool (VBT) CLI from v1.17.20 to v1.17.24 to include the latest fixes, stability improvements, and compatibility updates for Vlocity-related operations in ARM.
Compare Process Notification Improvement
Updated the Compare Changes workflow to display a clear warning message instead of an error when a compare or commit operation is already in progress in another browser tab or session. This provides a more accurate user experience and better communicates the operation status during concurrent Compare Changes activities.
External Client Application File Diff Fix
Fixed an issue where deleting an External Client Application (ECA) through EZ-Commit did not generate the expected file diff, causing the commit process to fail. Support for ECA metadata has been added to ensure file differences are generated correctly during both direct commits and pre-validation commit workflows involving metadata deletions.
EZ-Merge File Difference Consistency Fix
Fixed an issue where the file changes displayed during EZ-Merge did not match the changes shown during the corresponding EZ-Commit. The merge file comparison logic has been corrected to ensure the merge preview accurately reflects the committed changes, providing consistent and reliable file difference information during conflict resolution.
Provar Configuration Display Fix - New UI
Fixed an issue in the New UI where Provar configuration fields were not displayed after selecting Provar in the CI Job Tests screen. The configuration options now load correctly, allowing users to configure the required Provar settings, including Repository, Branch, Test Cases Root Path, and Test Cases Execution Path.
SonarQube Baseline Branch Support - New UI
Fixed multiple issues in the New UI where the Baseline Branch dropdown was not displayed for SonarQube Static Code Analysis. The Baseline Branch selection is now available and retained correctly across EZ-Merge, CI Job Edit, and SCA Label workflows, ensuring a consistent configuration experience with CodeScan.
Credential Creation Save Button Fix - Old UI
Fixed an issue in the Old UI where the Save button did not respond when creating a new credential due to a client-side loading error. The credential creation dialog now loads correctly, allowing users to save new credentials successfully.
Release Labels Loading Fix - New UI
Fixed an issue in the New UI where navigating directly to the Release Labels page from the left-side menu caused the page to remain in an infinite loading state. The navigation flow has been corrected to ensure the Release Labels page loads successfully when accessed directly.
Package.xml Upload Fix (Old UI)
Fixed an issue in the Classic (Old) UI where clicking Select Package.xml while creating a Custom Deployment from Package.xml did not respond or open the local file browser. The upload component has been corrected to initialize properly, allowing users to successfully select and upload Package.xml and ZIP deployment files during deployment creation. This issue was limited to the Classic UI and did not affect the New UI.
DataLoader + DataLoader Pro Release Notes 26.3.2
Release Date: 12 July 2026
Knowledge KAV language filter not auto-populating in New UI
Fixed an issue in the New UI where the Language filter on the Knowledge KAV object did not prefill with the existing language value. The filter behavior now matches the Old UI.
ARM Release Notes 26.3.1.1
Release Date: 6 July 2026
SSO Login Redirection Fix
Fixed an issue that prevented users from logging in through Single Sign-On (SSO) due to an overly restrictive Content Security Policy (CSP). The SSO redirection flow has been updated to allow successful authentication and seamless redirection to the configured identity provider.
Impacted Areas:
SSO Authentication
ARM Release Notes 26.3.1
Release Date: 5 July 2026
Backup-Enabled Validation Metadata Retrieval Fix
Fixed an issue where Validate Only deployments with Backup enabled could fail due to additional metadata retrieval during the backup flow. The backup metadata retrieval process has been improved to correctly handle validation scenarios and avoid unnecessary failures when deployment components are limited to selected metadata.
Impacted Areas:
Deployment Module
Branch Unregistration Improvements
Improved the branch unregistration process to ensure branch-related records are cleaned up correctly during synchronization. The update enhances multi-branch unregistration handling, removes stale branch mapping data, and improves logging to provide more accurate status reporting and consistent behavior across branch synchronization workflows.
Impacted Areas:
Version Control Repository Settings
Sync Branches
Apache Tomcat 11.0.22 Upgrade
Upgraded Apache Tomcat from 11.0.21 to 11.0.22 across Shared, Dedicated, and On-Prem environments to incorporate the latest security fixes and stability improvements. This update enhances platform security while maintaining compatibility and consistent performance across all deployment models.
Impacted Areas:
Shared Instances
Dedicated Instances
On-Prem Deployments
Permission Set Compare Changes Consistency Fix
Fixed an issue where the Compare Changes view did not match the actual changes committed to GitHub when using Create/Append Revision to Existing Label in EZ-Commit. Permission Set commit options are now applied consistently throughout the commit workflow, ensuring the Compare Changes view accurately reflects the final commit content.
Impacted Areas:
EZ-Commit
CI Job File Changes Retention Fix
Fixed an issue where the File Changes tab in CI Job history could appear empty after historical CI Job data was cleaned up. The retention process has been updated to preserve the required file difference information, ensuring deployed file changes remain available for supported CI Job history records.
Impacted Areas:
CI Jobs
Microsoft Teams Workflows Webhook Support
Added support for Microsoft Teams Workflows webhook URLs, enabling ARM notifications to continue working as Microsoft phases out traditional Incoming Webhooks. ARM can now deliver deployment and system notifications using the new Teams Workflows integration, helping customers transition seamlessly to Microsoft's supported notification model.
Impacted Areas:
Notification Integrations
DataLoader & DataLoader Pro Release Notes 26.3.1
Release Date: 05 June 2026
Query Editor Workflow for Dynamic and Custom Queries – DL & DL PRO
The Query Editor in DataLoader Basic and DataLoader Pro now supports two modes: Query Builder Mode (build queries using field selections, filters, and order-by options) and Manual Query Edit Mode (edit queries directly in the text editor). Users can seamlessly switch between modes with clear confirmation prompts, and the system correctly manages state transitions to prevent conflicts between manual edits and dynamic query generation.
ARM Release Notes 26.2.13
Release Date: 28 June 2026
Environment Provisioning History Performance Improvement
Improved the Environment Provisioning History screen performance by implementing backend pagination. This ensures history records load based on the selected page size, reducing load time during initial access and page refresh.
Impacted Area:
Environment Provisioning History
CodeScan Project-Level Exclusions Support
Improved CodeScan integration to correctly honor project-level file exclusions configured in the CodeScan UI when no exclusions are defined in the ARM CodeScan plugin. ARM-defined exclusions continue to take precedence when explicitly configured, ensuring consistent and expected scan behavior across analysis workflows.
Impacted Areas:
CodeScan Integration
Profile IP Ranges Handling Enhancement
Enhanced Profile IP Range handling to support consistent Append, Replace All, and Remove IP Ranges behavior across commit and deployment workflows. The Replace All option now ensures Profile IP ranges are fully synchronized from the source or branch metadata, aligning target org values with the selected deployment source while keeping other Profile metadata behavior unchanged.
Impacted Areas:
Commit Workflows
Deployments
GitHub Enterprise OAuth Validation
Improved repository registration by validating GitHub repository URLs before allowing OAuth authentication. OAuth registration is now restricted to GitHub Cloud repositories, and users attempting to register GitHub Enterprise repositories are prompted to use Username/PAT authentication instead, preventing unsupported configurations and subsequent branch operation failures.
Impacted Area:
Repository Registration (New UI)
GitHub OAuth Authentication
CI Job Repository Cloning Performance Improvement
Improved CI Job execution performance by resolving an issue that caused unnecessary repository cloning during Repo-to-Org workflows. Repository configuration handling has been enhanced to reuse existing repository data where applicable, reducing clone operations and improving overall CI Job execution time.
Impacted Areas:
CI Jobs – Repo-to-Org (DX & Non-DX)
Repository Cloning Performance
GitHub OAuth Branch Creation UI Improvement
Improved the EZ-Commit branch creation experience for GitHub OAuth repositories by hiding the Credentials selection when OAuth authentication is in use. This ensures the branch creation dialog displays only relevant options, providing a cleaner and more intuitive user experience.
Impacted Area:
EZ-Commit Branch Creation
GitHub OAuth Repository Integration (New UI)
Pre-Validation Commit SCA Date Filter Fix - New UI
Fixed an issue in the New UI where Pre-Validation Commit SCA did not correctly apply the selected date range due to a date format parsing error. The date selection handling has been updated so SCA analyzes only the components within the chosen date range.
Impacted Area:
EZ-Commit → Pre-Validation Commit
ARM Release Notes 26.2.12
Release Date: 21 June 2026
Merge Conflict Resolution Progress Indicator
Enhanced the merge conflict resolution workflow to provide better visibility and prevent duplicate actions during commit processing. A progress indicator is now displayed when conflict resolution commits and related background downloads are initiated, and user actions are properly synchronized to prevent multiple commit requests and UI exceptions.
Impacted Area:
Version Control → Commit History → Conflict Resolution Workflow
AccelQ Error Details Display Fix
Fixed an issue where error details for failed AccelQ test cases were not displayed in the Old UI. Users can now view failure information, including error messages and test execution details, directly from the test report, providing consistent behavior across both Old and New UI experiences.
Impacted Areas:
CI Jobs – Test Results
Deployment Module – Test Results
AccelQ Integration (Old UI)
Deployment Comparison Handling for Destructive Changes
Fixed an issue in the New UI where deployment comparisons could become unresponsive when only destructive changes were selected. Comparison handling has been improved to correctly process destructive metadata selections and prevent comparison workflows from getting stuck during metadata retrieval.
Impacted Areas:
Org-to-Org Deployments
Deployment Comparison (New UI)
Destructive Change Processing
Register Branch Usability Improvements
Enhanced the Register Branch experience by enabling branch searches to be executed using the Enter key in the Branch Name Search field, providing a faster and more intuitive workflow. Additionally, the informational Note message has been updated for improved clarity.
Updated Note Message:
Previous: Support to "src" as default folder is no more exists.
Updated: Support to "src" as default folder if no other folders exist.
Impacted Areas:
Register Branch (Classic UI)
User Interface Messaging
Deployment Compare Screen Validation Message Fix - New UI
Fixed an issue in the New UI where an incorrect destructive-change confirmation dialog was displayed on the Compare screen when no constructive members were selected. Users now receive an appropriate validation message prompting them to select at least one member before proceeding, ensuring a clearer and more consistent deployment experience.
Impacted Areas:
Deployment Compare Screen (New UI)
Dataloader Post-Activity Status Handling Fix
Fixed an issue in CI Jobs where Dataloader post-activity processing could continue logging repeated status checks even after the Dataloader job had completed. Status handling has been improved to correctly recognize completion states and stop further polling, ensuring post-activity logs accurately reflect the final execution status.
Impacted Area:
CI Jobs – Post Activities
CodeScan Report Synchronization Fix
Fixed an issue where ARM displayed incorrect CodeScan analysis results by retrieving report data from an unrelated scan instead of the executed analysis. Report retrieval logic has been updated to ensure ARM displays the correct violations and file counts, keeping SCA results synchronized with the corresponding CodeScan execution.
Impacted Areas:
Static Code Analysis (SCA) Reports
ARM Release Notes 26.2.11
Release Date: 14 June 2026
Parallel Processor Execution Fix
Fixed an issue in CI Jobs where Parallel Processor executions could fail to trigger external automation workflows due to backend request handling inconsistencies. The execution logic has been updated to ensure parallel processor requests are processed correctly, improving the reliability of post-deployment automation integrations.
Impacted Areas:
CI Jobs
Parallel Processor Integration
Post-Deployment Automation Workflows
Branching Baseline Deletion Control Improvement
Improved Branching Baseline handling by restricting deletion actions when an abort operation is already in progress. This prevents users from performing conflicting actions on baseline iterations and helps maintain consistent baseline processing behavior.
Impacted Area:
Settings → Branching Baseline Module
Connected App Search & Substitute Support
Enhanced Search & Substitute to support ConnectedApp metadata, allowing users to dynamically replace Connected App configuration values during Commit, CI Job, and Deployment execution.
This enhancement helps manage environment-specific Connected App configurations without manual XML updates.
Impacted Areas:
Search & Substitute
Permission Set Agent Access Support
Added support for the <agentAccesses> node in Salesforce Permission Sets to ensure agent access configurations are correctly retained during metadata operations. Previously, these entries were retrieved successfully but were excluded during commit processing. With this enhancement, agent access configurations are now preserved across version control and deployment workflows.
Impacted Areas:
Version Control
Deployments
Package.xml Custom Object Retrieval Fix
Fixed an issue in EZ-Commit where certain metadata components, including Custom Objects, could be skipped when retrieving components using an uploaded package.xml. The package.xml retrieval logic has been improved to ensure valid metadata components are retained and displayed correctly in the Added/Modified Metadata Components tab.
Impacted Area:
EZ-Commit using
package.xml
Merge Approval Link Fix - New UI
Fixed an issue in the New UI where approvers saw an “Unknown Error” after clicking the approval link from an EZ-Merge email notification. The approval link now redirects correctly to the Merge Label approval pop-up, allowing users to review and approve merge requests as expected.
Impacted Area:
EZ-Merge Approval Workflow (New UI)
Branch Permission Inheritance for Commit Visibility
Fixed an issue where commit labels created by sub-users were not visible to Custom Admins when branches were created through the EZ-Commit workflow. Branch permissions are now automatically inherited and synchronized during branch creation, ensuring authorized users can view and approve commits without requiring manual branch access assignment.
Impacted Areas:
EZ-Commit Branch Creation
Commit Label Visibility
Commit Label Visibility for Custom Admins
Fixed an issue where Custom Admins could not view or approve commit labels created by sub-users when branches were created through the EZ-Commit workflow. Branch permissions are now automatically inherited from the parent branch and synchronized during branch creation, ensuring commit labels remain visible and accessible to authorized approvers.
Impacted Areas:
EZ-Commit Branch Creation
Commit Label Visibility
DataLoader Pro Release Notes 26.2.11
Release Date: 14 June 2026
DL Data Retention Policy Fix
Fixed missing components in the data retention policy for "DL & DL PRO". Single DataLoader bulk file deletion was not being executed, and "DL & DL PRO" S3 backup deletions were targeting the wrong bucket. ARM data retention settings now apply to "DL & DL PRO" by default without requiring a separate checkbox.
DataLoader Pro Query Failure on Knowledge__kav Object
Fixed an issue where DataLoader Pro jobs failed when a custom query was applied to the Knowledge__kav object. The error occurred because the system incorrectly appended a WHERE clause to queries that already contained filtering conditions (e.g., LIMIT), resulting in a syntax error. Query construction logic has been corrected to handle Knowledge objects properly.
ARM Release Notes 26.2.10
Release Date: 7 June 2026
Support for Salesforce Run Relevant Tests in Deployments (New Enhancement)
AutoRABIT now supports Salesforce’s Run Relevant Tests test level for deployment validations and deployments. This option executes only the Apex tests identified by Salesforce as impacted by the changes being deployed, helping reduce deployment time and improve CI/CD efficiency while maintaining required test coverage. Support is available across validation, deployment, and Quick Deploy workflows.
Salesforce Summer ’26 (API Version 67) Support (New)
AutoRABIT now supports Salesforce API Version 67, enabling compatibility with the latest Salesforce Summer ’26 release. This update includes support for newly introduced metadata types such as FlowValueMap, EmailAuthorizationSettings, InsPlcyLimitConsumptionRule, and OrchestrationPlanCtxMapping, along with support for Salesforce metadata enhancements in Queue, DataSrcDataModelFieldMap, Network, InvocableActionExtension, and Flow.
EZ-Commit Performance Improvements for Large Salesforce Schemas
Enhanced EZ-Commit performance for Salesforce orgs containing large volumes of custom fields and metadata components. Optimizations to schema processing and change detection improve component loading, retrieval responsiveness, and overall user experience across EZ-Commit, AutoDraft, and Package Manifest workflows.
My Profile – VC Mappings Performance Improvements
Improved performance of the My Profile → VC Mappings page for environments with a large number of branches. Backend pagination and loading optimizations reduce page load times and improve responsiveness when viewing and managing version control mappings.
EZ-Commit User Experience Improvements
Enhanced the EZ-Commit save experience by improving validation feedback for required fields. Mandatory fields are now clearly highlighted when left unselected, helping users identify missing information more quickly and reducing submission errors.
ARM Release Notes 26.2.9
Release Date: 31 May 2026
Bitbucket Token Authentication & Email Support Update
Effective Date: 9 June 2026
To align with Bitbucket's deprecation of App Passwords, ARM now supports Token-based authentication for Bitbucket integrations and introduces an optional Email Address field for Bitbucket credentials. The email address is used for Bitbucket API operations such as Pull Request creation, while Git operations (Clone, Fetch, Push) continue to work using Token or SSH authentication.
Existing App Password credentials will continue to function until Bitbucket's deprecation date. Customers are encouraged to migrate to Token-based authentication and update their Bitbucket credentials with an email address to ensure uninterrupted API functionality.
Action Required: Review and update your Bitbucket credentials to use Token authentication and provide an email address for API-based operations.
For complete details, configuration steps, and migration guidance, please refer to the documentation link below:
Documentation:
Pin/Favorite CI Jobs for Quick Access - New UI
Introduced the ability to pin or favorite CI Jobs in the New UI, allowing users to quickly access frequently used jobs without searching through the full job list. Pinned jobs are displayed in a dedicated section at the top of the CI Job List and are maintained individually for each user.
Impacted Area:
CI Jobs List (New UI)
SiteDotCom Metadata Retrieval Fix
Fixed an issue where SiteDotComSite metadata changes were not included in Single Revision Deployments and Release Labels when only the .site file was modified. Metadata processing has been improved to correctly retain and retrieve associated SiteDotCom components, ensuring changes are accurately captured across deployment workflows.
Impacted Areas:
Single Revision Deployment
Revision Range Deployment
Release Labels
Org-to-Org Deployments
CI Jobs (DX & Non-DX)
SiteDotCom Metadata Processing
SonarQube Analysis Result Synchronization Fix
Fixed an issue where SonarQube violations were not displayed in the ARM Analysis Dashboard despite being available in SonarQube. The result retrieval process has been updated to correctly fetch and synchronize SonarQube scan results, ensuring accurate visibility of violations within ARM.
Impacted Areas:
EZ-Commit
EZ-Merge
Static Code Analysis (SCA)
CI Jobs using SonarQube Integration
ARM Release Notes 26.2.8.1
Release Date: 27 May 2026
Conflict File Truncation Fix
Fixed an issue in EZ-Merge where conflicted files could become truncated during conflict resolution, causing merge failures for certain profile files. The file copy handling has been improved to ensure complete file content is preserved during conflict processing.
Impacted Areas:
EZ-Merge
Multiple Branch Mapping Retention Fix
Fixed an issue in My Version Control Mappings where selecting and saving a new branch caused previously mapped branches to become unselected. The credential update logic has been improved to retain mappings for existing branches while updating credentials only for the selected branch.
Impacted Areas:
My Version Control Mappings
Branch Creation
Branch Registration
Credential Mapping Workflows
ARM Release Notes 26.2.8
Release Date: 24 May 2026
Improvements to Log Viewer Experience - New UI
We’ve enhanced the log viewing experience across multiple ARM modules to improve usability and performance.
What’s Improved
Removed unwanted auto-scroll behavior for completed jobs and logs
Users can now freely interact with the page without UI locking
Added quick navigation buttons to:
Scroll to Top
Scroll to Bottom
Added Full-Screen mode for easier log analysis
Improved live log streaming and polling for running jobs
Enhanced handling of large logs for smoother scrolling and improved responsiveness
Impacted Areas
CI Jobs, Deployment, Dataloader, Reports, SFDX, Admin Settings, and Version Control.
Improvements to EZ-Commit Destructive Changes Handling
Enhanced the handling and display of deleted metadata changes in EZ-Commit for improved consistency and accuracy.
What’s Improved
Added support for displaying
Action = Dfor deleted metadata changes in the Old UIImproved consistency between the Old UI and New UI for destructive changes handling
Updated deleted changes behavior during the
package.xmlupload flow:Modified ByandModified Datefields will now remain empty for destructive changes to avoid misleading information
Impacted Areas
EZ-Commit – Deleted Metadata Changes Handling (Destructive Changes)
ARM Release Notes 26.2.7
Release Date: 17 May 2026
Report Folder Selection Handling
Improved metadata filtering in VC-EZ-Commit to correctly recognize nested Report folders from package.xml uploads, even when a corresponding metadata file is not present. This ensures complete folder hierarchies are properly detected and displayed during metadata selection.
Impacted Area: VC-EZ-Commit
Azure Logic App Audit Log API Compatibility
Enhanced the Audit Logs service to improve compatibility with Azure Logic Apps by removing mandatory header validation for GET requests. This resolves issues where audit log API calls were failing due to automatically stripped Content-Type headers in Azure Logic App integrations.
Impacted Area: Audit Logs Service
Branch Credential Mapping Improvement
Improved branch credential mapping in ARM Version Control to ensure branches created through the EZ-Commit workflow are correctly associated with the user-selected credentials. This resolves issues where feature branches created by sub-users were not searchable during PR creation workflows.
Impacted Areas:
EZ-Commit
Pull Request Workflow
Branch Registration & Credential Mapping
Version Control Repository Integration
Enhanced Pagination Support - New UI
Improved pagination options across deployment reporting screens by adding support for viewing up to 100 records per page. This enhancement helps users review large datasets more efficiently within Deployment History, Release Labels, and related deployment report views.
Impacted Areas:
Deployment History
Release Labels
Active CI Job Filtering in Permissions - New UI
Updated the New UI permissions workflow to display only active CI jobs during user permission assignment, aligning the behavior with the Old UI experience. This prevents inactive jobs from appearing in CI job selection lists across permission management screens.
Impacted Areas:
Users & Permissions
AiAuthoringBundle Metadata Support
Added support for the AiAuthoringBundle metadata type across ARM metadata operations, enabling proper handling during deployments, exclusions, skip-member configurations, and CI job processing. This resolves issues where deployments involving AiAuthoringBundle components were failing or not being recognized correctly.
Impacted Areas:
CI Jobs
Deployment Module
Version Control
DataLoader Pro Release Notes 26.2.7
Release Date: 17 May 2026
ZIP File Attachments Not Migrating via Data Loader Pro
Resolved an issue where ZIP file attachments associated with HTML Report object records were not being migrated from Production to sandbox environments using Data Loader Pro. PDF and other attachment types migrated correctly, but ZIP files were silently skipped. All attachment types now migrate as expected.
ARM Release Notes 26.2.6.1
Release Date: 13 May 2026
Deployment and Validation Status Reporting Failure for Salesforce Summer ’26 Sandboxes
Resolved an issue where Merge/Commit validations and deployments were incorrectly reported as failed in ARM for Salesforce Sandbox/Production environments upgraded to Salesforce Summer ’26 (API version 67).
Customers experienced the following error in ARM UI popup messages and logs when using any Test Level option:
Run Local Tests
Run All Tests
Run Specified Tests
Use Salesforce Default
com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...
Resolution
Upgraded Salesforce Metadata API libraries to version 67 to support Salesforce Summer ’26 API response changes and ensure accurate deployment and validation status reporting.
ARM Release Notes 26.2.6
Release Date: 10 May 2026
Testim Integration with ARM CI Jobs – New UI
Testim is now integrated with ARM CI Jobs to enable automated testing, rollback handling, and improved deployment visibility.
Enabled execution of Testim tests (Suite, Label, Plan) within CI Jobs
Added automatic test execution during CI runs
Introduced rollback on failure based on test results
Added email notifications with test results, job details, and rollback status
Provided execution logs and results in CI Job history
More Information: https://knowledgebase.autorabit.com/product-guides/arm-1/integration-and-plugins/testim
Date Filter UX Improvements – New UI
Enhancements to the date filter improve usability and accuracy in the New UI.
Calendar now opens only for Custom Range selection
Predefined ranges apply instantly without requiring Apply
Fixed incorrect month display and removed future month visibility
SCM Authentication Improvements for Branch Registration
Improvements to repository credential handling ensure consistent authentication during branch registration.
Save button enabled only when changes are made
Validates last modified user’s credentials during branch registration
Automatically falls back to repository-level credentials if validation fails
CI Job History – Job Name Visibility Enhancements – New UI
Enhancements improve visibility and readability of CI job names.
Job Name column is now resizable in CI List and Job History pages
Improved handling of long job names to reduce truncation
EZ Commit Label Validation Fix – New UI
Resolved inconsistency in label validation between New UI and Old UI.
Updated validation logic to support special characters
Fixed regex for allowed and invalid characters
Labels with characters like -, ., +, [ ] are now accepted
Run Specified Tests – Multiple Test Input Fix – New UI
Resolved issue with handling multiple test class inputs during deployments.
Restored support for comma-separated test classes
Supports input via comma, Enter key, and pasted values
Each test class is correctly parsed as an individual entry
Commit Fetching Fix for SFDX Repositories
Resolved issue where commits were not fetched for SFDX repositories.
Updated SSH-based logic to fetch revisions based on selected package directory
Ensures commits are retrieved correctly when a package folder is selected
ARM Release Notes 26.2.5.1
Release Date: 13 May 2026
Deployment and Validation Status Reporting Failure for Salesforce Summer ’26 Sandboxes
Resolved an issue where Merge/Commit validations and deployments were incorrectly reported as failed in ARM for Salesforce Sandbox/Production environments upgraded to Salesforce Summer ’26 (API version 67).
Customers experienced the following error in ARM UI popup messages and logs when using any Test Level option:
Run Local Tests
Run All Tests
Run Specified Tests
Use Salesforce Default
com.sforce.ws.ConnectionException: unable to find end tag at: START_TAG seen ...
Resolution
Upgraded Salesforce Metadata API libraries to version 67 to support Salesforce Summer ’26 API response changes and ensure accurate deployment and validation status reporting.
ARM Release Notes 26.2.5
Release Date: 3 May 2026
Configurable Deployment Behavior for Profile IP Ranges (Limited)
Introduced a new configuration to control how Profile IP Ranges are handled during deployments. This feature is enabled via a Feature Flag, and the Deployment Mode options are visible only when the flag is turned ON.
Deployment Mode Options:
Append (Default): Adds new IP ranges without removing existing ones in the target
Replace All: Ensures the target matches the source/package by deploying only the IP ranges included and removing any others from the target
Important Notes:
The Replace All option is fully supported for Org-to-Org deployments, where it aligns the target exactly with the source.
For other deployment types (such as CI Jobs, Single Revision, Commit Label, and Revision Range), behavior depends on package preparation. Only the IP ranges included in the deployment package are applied, and any others will be removed from the target.
Since these deployments follow a delta-based mechanism, users should carefully prepare packages when using Replace All to avoid unintended removal of IP ranges.
BotOne V Metadata Upload – Full Path Exposure Fix (Support Case #213285)
Fixed an issue where full file path details were exposed during metadata ZIP upload for the BotOne V type, posing a potential security concern.
This issue occurred due to missing bot metadata during Release Label package generation. The fix ensures that the required bot metadata is included, preventing path exposure and ensuring correct upload behavior.
Impacted Areas: Release Labels, DX Deployments, DX ZIP Deployment, CI Jobs (DX with Bot metadata)
Independent Visibility for Permission Set Commit Options (Enhancement)
Improved the EZ Commit experience by making Permission Set commit options visible independently in the Submit Validation panel. Previously, the Remove user permissions option was only shown when Commit access settings for selected metadata was enabled, causing confusion.
With this enhancement:
Both options are now displayed by default when a Permission Set is selected.
Users can choose either option independently or use both together, without any dependency between them.
Impacted Areas: Version Control – EZ Commit
SonarQube New Code Identification Fix for PR Analysis (Support Case #204387)
Fixed an issue where SonarQube analysis from ARM did not correctly identify new code for commits made to non-main branches without an associated Pull Request. Previously, such analyses were treated as standalone branches, leading to incorrect reporting.
With this fix, the selected baseline branch is now correctly used during Pull Request analysis. This ensures that changes are properly compared and reflected under New Code in SonarQube, improving accuracy and consistency in reporting.
Impacted Areas: EZ Commit, EZ Merge, SCA Reports, Deployments with SCA (SonarQube Integration)
Stale Scheduled Job Execution Fix for ACCELQ Jobs (Support Case #222962)
Fixed an issue where scheduled jobs were triggering even when they were not present, deleted, or not properly saved in the UI. This caused inconsistencies between the UI and scheduler, leading to repeated and unnecessary job executions.
With this fix, cleanup logic has been implemented to remove stale and orphaned scheduler (cron) entries for ACCELQ jobs. Jobs that are deleted or not properly configured are no longer triggered, ensuring alignment between the UI and scheduler state.
Impacted Areas: CI Jobs, Scheduler (ACCELQ Jobs), Deployment Execution
Pattern-Based Substitution Support for Named Credentials (Enhancement)
Enhanced the Search & Substitute feature to support pattern/wildcard-based substitution for Named Credential parameter values. Previously, only exact-match substitutions were supported, requiring multiple rules for similar URL patterns.
With this enhancement, a new subelement, namedCredential.parameterValueMatchExpression, allows users to define a single rule to handle multiple URL variations dynamically. This reduces duplication and simplifies maintenance by replacing only the matched portion while preserving the remaining value.
Existing exact-match behavior using namedCredential.parameterValue remains unchanged.
Impacted Areas: Admin – Search & Substitute, CI Jobs, Deployment Configuration
DataLoader Pro Release Notes 26.2.5
Release Date: 03 May 2026
DataLoader Pro Job Result Inaccessible Resolved an issue where result files from completed DataLoader Pro jobs were not accessible. Users can now successfully view and download job results as expected.
ARM Release Notes 26.2.4
Release Date: 26 April 2026
Accurate Error Message Display for Deployment Failures (Support Case #207169)
Fixed an issue where incorrect or misleading error messages were displayed in the Deployment UI logs. In certain cases, users saw generic authentication-related errors, even when the actual failure was due to invalid deployment configurations (e.g., selecting “No Test Run” for Production deployments).
With this fix, the UI now reflects the correct backend error messages, providing clear and accurate insights into deployment failures. This helps users quickly identify and resolve issues.
Impacted Areas: Deployment, CI Jobs
Template Sharing for Subusers – Environment Provisioning (Both UIs) - New Enhancement
Introduced an enhancement to allow Subusers to share environment provisioning templates they have created. Previously, only Admin users could share templates.
With this update:
Subusers can now share their own templates.
Sharing remains restricted for templates created by other users.
Admin users continue to have full sharing access across all templates.
This improvement reduces dependency on Admins and enables better collaboration.
Impacted Areas: Environment Provisioning (Template Management) – Old UI & New UI
Multiple Diff View Support in EZ-Commit – New UI (Support Case #215475)
Enhanced the EZ-Commit experience in the New UI to allow users to view multiple file diffs simultaneously. Previously, opening a diff would automatically close any previously opened diff, limiting comparison across components.
With this update, users can expand multiple diff sections at the same time, enabling easier side-by-side review and improved validation before committing.
Impacted Areas: EZ-Commit, CI Jobs, Deployments, Version Control, Merge Requests
Baseline Revision Selection Display Fix – Classic UI (Support Case #211183)
Fixed an issue in the Classic UI where the selected Baseline Revision was not visually reflected in the CI Job edit screen, even though it was correctly saved. This caused confusion and unnecessary validation errors.
With this fix, the selected revision is now properly highlighted, and users are automatically navigated to the relevant page. If no revision is selected, the default view is shown without disruption.
Impacted Areas: CI Jobs, Deployments, Merge Requests (Revision Selection Popup)
Merge Conflict Email Notification Accuracy Fix (Support Case #210042)
Fixed an issue where non-conflicting files were incorrectly listed under the “Conflicted Files” section in merge conflict email notifications.
With this fix, only the actual conflicting files are displayed in the “Conflicted Files” section, while successfully merged files are shown correctly under “Merged Files,” improving clarity and accuracy of notifications.
Impacted Areas: Version Control – EZ-Merge
Apache Tomcat Upgrade for On-Prem Instances
Upgraded Apache Tomcat from version 11.0.13 to 11.0.21 for all On-Prem deployments. This update ensures improved performance, enhanced security, and better stability of the ARM application environment.
Impacted Areas: On-Prem Installations
Login Redirection Issue Fix – New UI (Support Case #214960,#222145,#218645)
Fixed an issue where users were unable to log in correctly after enabling the New UI and were repeatedly redirected despite switching back to the Old UI.
This fix ensures stable login behavior by restoring failed script handling and improving error visibility, allowing users to successfully access the application across browsers.
Impacted Areas: Login, UI Navigation (Old UI & New UI)
Faster Branch Creation Using GitHub API (Both UIs) - New Enhancement
Introduced an enhancement to improve branch creation performance by creating branches instantly using the GitHub API. Previously, branch creation was delayed due to synchronous workspace copy and setup processes.
With this update:
Branches are created immediately upon user action.
Workspace checkout and related processes run asynchronously in the background.
Users can access and start working on the branch without delay.
The system falls back to the existing process if GitHub pull request support is not enabled.
This enhancement improves responsiveness and overall user experience.
Impacted Areas: Version Control, EZ-Commit (Old UI & New UI)
CI Jobs List Auto-Refresh Fix After Activate/Deactivate (Support Case #217089 – New UI)
Fixed an issue in the New UI where the CI Jobs list did not automatically refresh after activating or deactivating a job. Previously, although the change was successfully applied in the backend, the UI did not reflect the updated Last Date Modified or reorder the job in the list until a manual refresh was performed.
With this fix, the CI Jobs list now refreshes automatically upon successful activation or deactivation. The Last Date Modified timestamp is updated instantly, and the modified job is moved to the top of the list, ensuring consistency with the default sorting behavior.
Impacted Areas: CI Jobs – List Page (New UI)
Users/Permissions Access Issue for Non-Admin Users (Support Case #216643 – New UI)
Fixed an issue where non-admin users were unable to directly access the Users/Permissions section in the New UI despite having the required permissions. Access was only possible after navigating via the Old UI, leading to inconsistent behavior.
With this fix, routing logic now correctly validates user permissions, allowing direct access from the New UI and ensuring consistent behavior across both interfaces.
Impacted Areas: User Management – Navigation (Old UI & New UI)
Apache Tomcat Upgrade to Version 11.0.21 (Shared & Dedicated Environments)
Upgraded Apache Tomcat from version 11.0.13 to 11.0.21 across both Shared (SaaS) and Dedicated environments to address known security vulnerabilities and improve overall platform stability.
This upgrade ensures a secure and reliable runtime environment, with validation confirming compatibility across multi-tenant and customer-specific setups. Core functionalities, performance, and environment-specific configurations continue to operate as expected post-upgrade.
Impacted Areas: Platform Infrastructure – Shared (SaaS) & Dedicated Environments
Salesforce CLI Upgrade to v2.130.9 (Support Case #219699)
Upgraded the Salesforce CLI from version 2.125.2 to 2.130.9 across development and CI/CD environments to ensure compatibility with the latest Salesforce features, bug fixes, and security updates.
Post-upgrade validation confirmed that existing workflows—including deployments, org authentication, and package operations—continue to function as expected, with no impact on automation or pipelines.
Impacted Areas: Development Environments, CI/CD Pipelines, Deployment Workflows
DataLoader Release Notes 26.2.4
Release Date: 26 April 2026
Data Retention Policy for nCino & DataLoader — Admins can now enable automatic cleanup of unused jobs (DataLoader processes, Feature Deployments, CI Job histories, etc.) via a configurable retention policy under My Account.
DataLoader Release Notes 26.2.3
Release Date: 26 April 2026
Dataloader Extract Job not returning all field columns
When using a DataLoader Extract job with a WHERE IN clause, the downloaded file did not include all field columns from the query. Removing the WHERE IN clause returned all columns correctly. Fixed to ensure all queried fields are present in the extracted output, regardless of clause type.
ARM Release Notes 26.2.2
Release Date: 12 April 2026
1. ARM Deployment: Improved Error Message Rendering (Support Case #206745 – New UI)
Fixed an issue in the New UI where ARM did not correctly parse or escape < > characters in error messages returned from Salesforce during deployments. This caused error details to display incorrectly in the Failed Components section of the deployment report.
With this fix, error messages are now properly rendered, ensuring accurate and readable visibility into deployment failures.
Impacted Areas: Deployment Report (Failed Components Section)
2. Permission Set XML Consistency for Data Cloud (Support Case #211123)
Resolved an issue where Data Cloud-enabled Permission Sets showed inconsistencies between ARM IDE and Compare Files, due to the <dataspaceScopes> node missing in comparison results. This prevented users from committing changes successfully.
Support for the dataspaceScopes field has now been added, ensuring accurate metadata mapping when present in the Salesforce org. This enables seamless comparison, commit, and deployment of Permission Sets.
Impacted Areas: EZ Commit, Merge, Deployment, CI Jobs (DX and Non-DX)
3. EZ Commit: Duplicate Component Selection Prevention (Support Case #212351 – New UI)
Fixed an issue in the New UI where components selected under the Added/Modified Components tab in EZ-Commit (with Autodraft enabled) were not reflected in the All Metadata Components tab, allowing duplicate selections during commit.
With this fix, component selections are now synchronized across tabs, preventing duplicates and ensuring accurate commit lists.
Impacted Areas: EZ-Commit Flow
4. CI & Selective Deployment: Consistent Component Evaluation (Support Case #210095)
Addressed inconsistent behavior between CI Jobs and Selective Deployment when using the Ignore Installed Components option.
In CI Jobs, component evaluation was correctly performed at the parent level, resulting in the expected “No local changes to deploy” message.
In Selective Deployment, evaluation was limited to the child level, leading to incorrect deployment eligibility.
This fix aligns Selective Deployment logic with CI behavior, ensuring consistent and accurate component evaluation across deployment flows.
Impacted Areas: Org-to-Org Deployment, VC-to-Org Deployment (Workflow Metadata)
5. Salesforce Org Registration via OAuth with ECA Fails with “Undefined Error” (Support Case #217635)
Fixed an issue where users encountered an “undefined error” while registering a Salesforce Org in AR using OAuth via ECA. This issue was specific to version 26.2.1 and did not occur in earlier releases.
With this fix, the missing SfOrg ID is now properly added during new org registration, allowing Salesforce orgs to be registered successfully through OAuth with ECA.
Impacted Areas: Salesforce Org Registration, ECA OAuth Flow
6. ALM Integration Enhancements (Salesforce)
Note: These enhancements are available only in the New UI.
Overview
This release enhances AutoRABIT’s ALM integration by extending automatic Work Item status updates beyond commit operations. Updates are now supported across multiple modules, enabling consistent lifecycle tracking within Salesforce ALM.
What’s New
Work Item Status Updates Across Modules Work Item status updates are now supported in:
EZ-Commit (existing support)
Merge Requests (new UI)
EZ-Merge (new UI)
CI Jobs (new UI)
These enhancements enable automatic synchronization of Work Item statuses during key development activities such as commits, merges, and CI pipeline executions, improving traceability and process consistency.
ARM Release Notes 26.2.1
Release Date: 05 April 2026
Custom Setting Migration Template – Save Confirmation Pop-up Fix (New UI) [SupportCase#205885] Fixed an issue where newly provisioned data values were not displayed in the Save confirmation pop-up while creating or editing a Custom Setting migration template in the New UI. This prevented users from verifying configuration details before saving. This issue was limited to the New UI and did not impact the Old UI. Impacted Areas: Environment Provisioning, Custom Setting Migration Template (Save & Edit – New UI)
Quick Deploy Not Enabled for UseSalesforceDefaults – [Support Case #203174] Fixed an issue where the Quick Deploy option was not available in CI jobs when using the UseSalesforceDefaults test level, even though it was supported and enabled in the Salesforce Production org. This update ensures ARM behavior aligns with Salesforce by correctly enabling Quick Deploy based on the selected test level. Impacted Areas: CI Jobs (Org-to-Org, VC-to-Org Deployments)
CI Job Stuck in In-Progress State Blocking PR Validation Trigger – [Support Case #201347] Fixed an issue where CI jobs remained in an In-progress state in the Job History UI even after successful validation. This prevented subsequent CI builds, including PR validation jobs, from triggering automatically. The issue also caused abort actions from the UI to fail. With this fix, CI job statuses are now correctly updated upon completion, ensuring normal job execution flow. Impacted Areas: CI Jobs
AI Metadata Components Not Processed in Org-to-Org Deployments – [Support Case #201393] Fixed an issue where AI metadata components (GenAiFunction) were not properly processed during Org-to-Org deployments, causing compare operations to hang indefinitely and direct deployments to fail with a “No changes found” message. This update ensures AI metadata components are correctly considered during deployment and comparison workflows, enabling successful execution. Impacted Areas: Deployments (Org-to-Org)
Release Label Not Fetching Latest HEAD Revisions – [Support Case #201799] Fixed an issue where merged revisions from pull requests were not being fetched during Release Label creation, even though they were present in the remote repository. This led to discrepancies where revisions were visible in EZ-Merge but missing in Release Label selection. This update improves the revision-fetching logic to include all relevant folder-based and merged revisions, ensuring consistency across features. Impacted Areas: Release Labels, EZ-Merge, CI Job Configuration, Deployments (Single Revision & Range), nCino Flows
Commit History Date Format Inconsistency – [Support Case #209987] Fixed an issue where the commit history date format in the New UI differed from the Old UI. Previously, the New UI displayed dates in DD/MM/YY format, while the Old UI followed MM/DD/YY, leading to inconsistency. This update standardizes the date format in the New UI to match the Old UI for a consistent user experience. Impacted Areas: Commit History, Version Control
Save Button Triggering Re-authentication in Salesforce Org Details – [Support Case #213381] Fixed an issue where clicking the Save button in the Salesforce Org Detail page incorrectly triggered the re-authentication flow, redirecting users to the Salesforce login page. This update ensures that the Save action only updates org details within the application, while the Re-authenticate action correctly handles the login flow, maintaining clear separation of functionality. Impacted Areas: Settings → Salesforce Org
EZ Commit Pagination Infinite Loop in New UI – [Support Case #213239] Fixed an issue in the EZ Commit flow where the paginated component list entered an infinite loop when users rapidly navigated between pages after setting a higher pagination limit. This update improves pagination handling to ensure smooth and stable navigation across component lists. Impacted Areas: Version Control (EZ Commit), Metadata Selection Pagination (New UI)
Unable to Add Users in New UI Due to Missing Mail Extension – [Support Case #214523] Fixed an issue where admins were unable to add new users in the New UI because the mail extension dropdown appeared empty, preventing user creation. This update ensures the default domain is correctly handled and displayed, allowing admins to successfully add users. Impacted Areas: Admin → User Management (New UI)
DataLoader Pro Release Notes 26.2.1
Release Date: 05 April 2026
New UI: DataLoader Pro CSV validation incorrect
Fixed DataLoader Pro in the new UI so invalid CSV input is correctly validated and flagged.
DataLoader Release Notes 26.2.1
Release Date: 05 April 2026
DataLoader Basic job stuck / Salesforce error during extract
Fixed an issue where DataLoader Basic extract jobs showed a stuck status and unexpected Salesforce errors during execution.
Fields and query not loading when editing extract job
Fixed DataLoader extract job editing so fields and the saved query now load correctly.
ARM Release Notes 26.1.13
Release Date: 29 March 2026
Automatic Dependency Fetch for Data Cloud Data Kits (DX only) - New UI
ARM now automatically retrieves all dependent metadata for a selected Salesforce Data Cloud Data Kit using connected org credentials. This eliminates the need to manually download and upload the package manifest (package.xml) during commit or deployment workflows.
This enhancement streamlines the process, reduces manual effort, and minimizes errors.
Impacted Areas: Data Cloud Deployments, Commit Workflow.
Environment Provisioning – Post Deployment Behavior Fix - #201758
Fixed issues with the Post Deployment step to ensure templates are included only when explicitly selected.
This update improves usability and ensures more reliable execution of provisioning steps.
Impacted Areas: Environment Provisioning, Migration Templates
CodeScan Baseline Not Applied in EZ Commit – Fix - (#199417,#204388,#204387)
Resolved an issue where the configured CodeScan baseline was not applied during EZ Commit or EZ Merge operations for mapped Salesforce orgs.
The system now correctly uses the defined baseline for analysis.
Impacted Areas: EZ Commit, EZ Merge, SCA Module
OmniStudio Components Missing in CI Deployments – Fix - #206010
Fixed an issue where OmniStudio components (such as OmniScript and OmniDataTransform) were excluded from CI deployments when listed under excluded metadata types.
Improved visibility helps identify such configurations and ensures accurate deployments.
Impacted Areas: CI Jobs, OmniStudio Deployments
CI Jobs History – “More Info” Text Selection Fix - #209352
Fixed a regression in the New UI where users were unable to select or copy text from the More Info popup in CI Jobs History.
Text selection and copying now work as expected.
Impacted Areas: CI Jobs History, More Info Popup (New UI)
Missing Bot & GenAI Metadata in Deployments – Fix - #209232
Fixed an issue where GenAI and GenAI Planner Bundle metadata were not included during deployments using Release Labels, even when selected.
Deployments now correctly include all selected metadata components.
Impacted Areas: Commits, Deployments
Assessment Metadata Missing in Release Label Deployments – Fix - #204091
Resolved an issue where AssessmentQuestionSet and AssessmentQuestion metadata were not included during Release Label deployments.

