# Welcome to the Knowledge Base Your Source of Truth for All Things AutoRABIT **The Knowledge Base** is a centralized, always-evolving source for technical documentation, product guidance, release notes, FAQs, and operational support across the AutoRABIT ecosystem. Whether you’re leading enterprise-scale transformation or optimizing daily flows, this is where insight meets action. #### Built for Precision at Scale AutoRABIT is not just a toolset, it’s a system. Our enterprise-grade DevSecOps platform is purpose-built for Salesforce, enabling controlled speed, secure scalability, and intelligent automation across development, compliance, and data management workflows. **Our ecosystem includes:** * **AutoRABIT** [**ARM**](/product-guides/arm)**:** Structured CI/CD pipelines for Salesforce. Aligns governance with acceleration. * **AutoRABIT** [**CodeScan**](/product-guides/codescan)**:** Industry leading static analysis to enforce quality and secure code before it ships. * **AutoRABIT** [**Vault**](/product-guides/vault)**:** Resilient, compliant backup and recovery tailored for complex Salesforce data models. * **AutoRABIT** [**Guard**](/product-guides/guard)**:** Real-time permission intelligence and compliance automation. Prevents access risk before it becomes exposure. * [**Integral Zone**](/product-guides/integral-zone)**:** MuleSoft-focused API quality, security, governance, and delivery automation. Together, these products form the industry’s most complete DevSecOps solution for Salesforce, trusted by the most security-conscious and performance-driven teams in the world. #### What You’ll Find Here * [**AI-Powered Search**](https://knowledgebase.autorabit.com/?q=)\ Precision answers, fast. Use our embedded AI assistant to extract exact steps, explanations, and insights from our full documentation library. * [**Release Notes**](/release-notes/release-notes)\ Stay informed. Track feature updates, patch releases, and roadmap-aligned improvements - built for enterprise-readiness. * [**Step-by-Step Product Guides**](/product-guides/arm)\ From initial configuration to advanced workflows, our user guides provide structured clarity for every role and function. * [**Troubleshooting & FAQs**](/fundamentals/faq)\ Self-serve solutions to unblock your team and reduce downtime. * **How-To Tutorials**\ Get practical. Resolve common challenges, optimize configurations, and apply best practices confidently. {% @mailchimp/mailchimpSubscribe cta="Release Notes Mailing List:" %} *** #### Can’t Find What You’re Looking For? [***Suggest an Update via GitHub***](https://github.com/AutoRabitOrg/knowledgebase) ***(Recommended)*** Have a clarification, correction, or improvement in mind? Every page in this Knowledge Base includes an **“Edit on GitHub”** button in the right-hand sidebar. This opens a GitHub Pull Request pre-linked to the exact page, so you can propose updates directly—whether it’s adding missing context, flagging outdated content, or refining explanations. Your suggestions help us evolve the documentation in real time—driven by the people who use it most. If there’s a concept, use case, or integration we haven’t covered yet, let us know. Our documentation team partners closely with product and support to continuously expand coverage based on real-world needs. [\[Contact the Documentation Team via Support →\]](https://support.autorabit.com/portal/en/newticket?departmentId=241415000000006907\&layoutId=241415000000074011) *** #### Quick Access * [**AutoRABIT Solutions Overview**](https://www.autorabit.com/) * [**LearningHub: Onboarding & Certifications**](https://learninghub.autorabit.com/) * [**Product Release Notes**](/release-notes/release-notes) # AutoRABIT Solutions At AutoRABIT, we're at the forefront of Salesforce DevOps solutions. Our advanced platform streamlines your development, testing, and release cycles, promoting continuous integration and delivery. AutoRABIT delivers comprehensive **Salesforce DevSecOps solutions** tailored for regulated industries, ensuring **security, quality, and productivity** in Salesforce development. Since Salesforce was built as a Customer Resource Module (CRM) rather than a development platform, AutoRABIT simplifies complex processes through automation—enabling teams to achieve more with fewer resources. ## **Who We Are** Founded in 2015, AutoRABIT is a global company dedicated to helping organizations **regain control of their Salesforce development** and implement **continuous delivery** of value to customers and employees. ## **What We Offer** AutoRABIT provides an integrated suite of DevSecOps tools to **automate, secure, and optimize** Salesforce development: * **Automated Release Management (ARM):** Reducing the complexity of Salesforce development, deployment, and management enables teams to meet quality, security, and compliance standards with strategic automation. * **CodeScan:** Performing static code analysis and applying policy management tools gives you total visibility into the health of your Salesforce environment, reduces costs, finds vulnerabilities, and decreases time to market. * **AutoRABIT Vault:** Implementing automated backup and recovery of Salesforce data, sophisticated data comparison tools, easy sandbox seeding, archiving, and comprehensive data management features ensures IT security, risk, and compliance needs are met. * **AutoRABIT Guard:** Automated security and compliance solution for Salesforce, designed to help enterprises protect their critical operations by continuously monitoring, enforcing policies, and remediating security risks. It eliminates the manual oversight typically required to manage Salesforce’s complexity, addressing security gaps, misconfigurations, and compliance risks in real time. ## Why It Matters * **Version Control**: We provide seamless integration with popular version control systems, enabling efficient tracking and management of changes to your codebase. * **Automated Metadata Deployment**: Our platform automates the deployment process, ensuring quick, reliable, and error-free releases. * **Data Deployment and Backup**: AutoRABIT ensures the integrity and security of your data through automated data deployment, backup, and recovery solutions. * **Test Automation**: We enable teams to automate their testing processes, ensuring high-quality output and faster release cycles. * **CodeScan Integration**: We integrate with CodeScan for enhanced static code analysis. This allows us to conduct thorough code quality checks, detect vulnerabilities early, and ensure your code adheres to the highest standards of performance and security. * **Governance and Compliance**: Our platform facilitates adherence to regulatory standards and corporate policies, ensuring smooth audits and compliance checks. Our mission is to simplify Salesforce DevOps and enhance productivity, letting businesses focus on what they do best: deliver value to their customers. By taking the complexities out of the DevOps process, AutoRABIT helps teams accelerate their development cycles, improve quality, and drive business growth. # Getting Set Up ## What do I need to get started? ### Salesforce Salesforce is a web-based CRM, which is an essential cloud application that ARM works with to build a successful **CI/CD pipeline**. Therefore, whether you are in support, engineering, enterprise services, product, or customer success, it is essential to have a Salesforce environment to replicate bugs, train, or verify bug fixes. Salesforce provides a full copy of the **Lightning Platform** for free. This means you can get your own Developer Edition to integrate with ARM for free by signing up at: ; ### Version Control System In addition to Salesforce, it is critical to have a **Version Control System** to ensure that the version control is the source of truth. There are several Version Control Systems out there, including **GitHub**, **Bitbucket**, and **Azure DevOps Server** (formerly known as TFS \[Team Foundation Server]). Each client may utilize a different Version Control System, but ARM allows you to connect to the three most popular Version Control Systems: **GIT**, **SVN**, and **TFS**. ### Microsoft Visual Studio Code In addition to Developer Edition orgs and a Version Control System, having **Microsoft Visual Studio** **Code** is beneficial. Microsoft VS Code is a powerful source code editor on your desktop. You can download Visual Studio Code, which integrates GIT for Windows, macOS, and Linux. Follow this link to download for your appropriate platform: . ### Git Bash In addition to the tools mentioned above, it is recommended to install **Git Bash**. The URL to download Git Bash for Mac OS X, Windows, Linux/Unix can be found here: . Git Bash is a command line through which users can use Git features, including standard Unix commands. One of the common Unix commands available through Git Bash is to add a file to your existing Git repository: ```actionscript # create new file $ touch README ``` # FAQs # General User Definitions {% hint style="info" %} **ARM-Specific User Definitions**: The information below is generalized across the entire AutoRABIT suite of products. For information specific to ARM, please refer to the ARM User Definitions page [here](https://knowledgebase.autorabit.com/~/revisions/r1tfuUId2G5l58MjsNr3/product-guides/arm/arm-administration/user-management/arm-user-definitions). {% endhint %} **Standard User** A Standard User is an individual authorized by the Customer to log in to and fully utilize AutoRABIT’s subscribed products. Standard Users have access to all product functionalities, including the Web UI, IDE plugins, APIs, and other interfaces. Platform Owners/Admins are included in the Standard User class, ensuring administrative rights without affecting licensing terms. **Platform Integration User** A Platform Integration User is an individual authorized by the Customer to perform actions that trigger the execution of AutoRABIT products (directly or indirectly). This includes, but is not limited to: * Analyzing reports or data from AutoRABIT to identify and resolve code quality, security, compliance, or system performance issues. * Agents, bots, or systems executing actions via AutoRABIT to automate testing, deployments, or compliance checks. * Using AutoRABIT IDE plugins * Triggering AutoRABIT APIs * Directly changing Salesforce org configurations * Committing changes to a source code repository **Key Points:** * Automation (e.g., bots, agents) utilizing AutoRABIT for testing, deployment, or monitoring must be licensed appropriately. * Any person who commits code to a Source Code Management (SCM) system, where the commit directly or indirectly triggers a job in AutoRABIT, requires a Platform Integration License. * If a service account is used to trigger automation or integrate with AutoRABIT, the person or team responsible for the actual code commit must still hold a Platform Integration License. This ensures that each individual whose actions contribute to triggering AutoRABIT processes is appropriately licensed. * Any code commits triggering AutoRABIT jobs, directly or indirectly, manual or automated**,** count toward Platform Integration Licenses. Example: In Git, multiple commits pushed simultaneously are counted individually toward user licensing. Platform Integration Users are included in licensing with view-only permissions. **Additional Notes:** * The number of licensed users represents the total unique users of the products throughout the Subscription Term. # Salesforce External Connected App (ECA) Configuration for AutoRABIT How AutoRABIT products (CodeScan, Guard, and Vault) connect to a customer Salesforce org using a Salesforce External Client App (ECA). Follow the product-specific guides to create or reuse an ECA, capture the Client ID and Client Secret, and complete the connection setup and user authorization required for that product. {% hint style="info" %} **Important:** This setup is **Salesforce org-specific**. You must repeat this process **for each customer Salesforce org** you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials. {% endhint %} {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} # ARM: Salesforce ECA (Local) Connection Setup Steps This is a step by step on how to implement the Local ECA solution to establish a new connection with ARM. {% stepper %} {% step %} ### Pre-req: get your Callback URL (redirect URI) For AutoRABIT’s ARM ECA setup, you need **the callback URL** Callback URL is depending on the instance: ``` {$instancename}/oauth/_callback ``` Example: ``` https://arm-qan5.autorabit.com/oauth/_callback ``` {% endstep %} {% step %} ### Create the External Client App (ECA) in your Salesforce Org 1. Login into Salesforce
2. In **Salesforce**, go to **Setup**. 3. In **Quick Find**, search **External Client Apps**. 4. Open **External Client App Manager** (or the External Client Apps area).
5. Click **New External Client App**. 6. Fill in the basics: * **Name / Label ( e.g. AR\_Local)** * **API Name** (auto-filled) * **Contact Email** * **Distribution State**: * **Local** (only for this org)
{% endstep %} {% step %} {% hint style="info" %} **Important Note**: After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error error=invalid\_client\_id\&error\_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, then try again to allow the Salesforce configuration to sync completely {% endhint %} {% endstep %} {% step %} ### Enable OAuth + set callback URL + scopes 1. Click **Enable OAuth** (or expand **API (Enable OAuth Settings)** and check **Enable OAuth**). 2. Set \**Callback URL* The URL you collected in step 1. 3. Choose **OAuth Scopes**: * Access the identity URL service (id, profile, email, address, phone) * Manage user data via APIs (api) * Full access (full) * Access Connect REST API resources (chatter\_api) * Perform requests at any time (refresh\_token, offline\_access) * Access custom permissions (custom\_permissions)
{% endstep %} {% step %} ### Flow Enablement 1. In **Flow Enablement**, select **Enable Authorization Code and Credentials Flow**. 2. **user credentials are required in the POST body** (Salesforce shows this option when you choose that flow) should be disabled.
{% endstep %} {% step %} ### Security toggles (common defaults) In the **Security** section the next options should be enabled: * **Require secret for Web Server Flow** * **Require secret for Refresh Token Flow** {% endstep %} {% step %} ### Create the app and capture Client ID / Secret 1. Click **Create**. 2. Open the app’s **Settings** tab and locate **Consumer Key and Secret**: * **Consumer Key** = **Client ID** * **Consumer Secret** = **Client Secret**
When you click the button for Consumer Key and Secret a code will be sent to the registered email for the user creating the configuration
After getting the code and verify in Salesforce the Consumer Key (CliendID) and Consumer Secret (Client Secret) will be displayed. **IMPORTANT: STORE THIS VALUE IN A SAFE PLACE WHERE IT CAN BE EASILY USED FOR FUTURE REFERENCE.**
{% endstep %} {% step %} ### Configure Policies (very important) After creating the ECA, open the **Policies** tab and adjust as needed (exact options vary by org/security posture), commonly: * **Permitted Users**: often set to **Admin approved users are pre-authorized** for controlled rollouts. * Add the required **profiles/permission sets** (or approved users) for who is allowed to authorize. {% endstep %} {% step %} ### What you’ll use in AutoRABIT Once created, the set of values you’ll reference in your ARM configuration are: * **Client ID** * **Client Secret** Also, the internal direction is to be clear that **one ECA per customer org** can be used across products (rather than creating one per AR product). *** After the configuration in Salesforce is complete, and you have obtained the ClientID and Client Secret, we can go to ARM to create the connection In the menu Click in Salesforce org and click in register Salesforce org
Create the connections filling the required information obtained from Salesforce.
Important Note: After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error error=invalid\_client\_id\&error\_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, and try again to allow the Salesforce configuration to sync completely. Once the Validate and save button is clicked, a Salesforce login is shown to log in with the user we intend to use for the Connection.
A message from Salesforce will show to require granted permissions for the user to use the scopes defined in the ECA, Click Allow
Then, you will be returned to ARM and the connection will be saved.
{% endstep %} {% endstepper %} {% hint style="info" %} **Important:** This setup is **Salesforce org-specific**. You must repeat this process **for each customer Salesforce org** you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials. {% endhint %} # CodeScan: Salesforce ECA (Local) Connection Setup Steps This is a step by step on how to implement the Local ECA solution to establish a new connection with CodeScan. {% stepper %} {% step %} ### Pre-req: get your Callback URL (redirect URI) For AutoRABIT’s CodeScan ECA setup, you need **the callback URL** Callback URL is depending on the instance: ``` {$instancename}/_codescan/oauth2/authorize ``` Example: ``` https://perf.codescan.io/_codescan/oauth2/authorize ``` {% endstep %} {% step %} ### Create the External Client App (ECA) in your Salesforce Org 1. Login into Salesforce
2. In **Salesforce**, go to **Setup**. 3. In **Quick Find**, search **External Client Apps**. 4. Open **External Client App Manager** (or the External Client Apps area).
5. Click **New External Client App**. 6. Fill in the basics: * **Name / Label ( e.g. AR\_Local)** * **API Name** (auto-filled) * **Contact Email** * **Distribution State**: * **Local** (only for this org)
{% endstep %} {% step %} ### Enable OAuth + set callback URL + scopes 1. Click **Enable OAuth** (or expand **API (Enable OAuth Settings)** and check **Enable OAuth**). 2. Set \**Callback URL* The URL you collected in step 1. 3. Choose **OAuth Scopes**: * Access the identity URL service (id, profile, email, address, phone) * Manage user data via APIs (api) * Manage user data via Web browsers (web) * Perform requests at any time (refresh\_token, offline\_access)
{% endstep %} {% step %} ### Turnment 1. In **Flow Enablement**, select **Enable Authorization Code and Credentials Flow**. 2. **user credentials are required in the POST body** (Salesforce shows this option when you choose that flow) should be disabled.
{% endstep %} {% step %} ### Security toggles (common defaults) In the **Security** section the next options should be enabled: * **Require secret for Web Server Flow** * **Require secret for Refresh Token Flow** {% endstep %} {% step %} ### Create the app and capture Client ID / Secret 1. Click **Create**. 2. Open the app’s **Settings** tab and locate **Consumer Key and Secret**: * **Consumer Key** = **Client ID** * **Consumer Secret** = **Client Secret** {% hint style="info" %} **Important Note**: After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error: error=invalid\_client\_id\&error\_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, then try again to allow the Salesforce configuration to sync completely. {% endhint %}
When you click the button for Consumer Key and Secret a code will be sent to the registered email for the user creating the configuration
After getting the code and verify in Salesforce the Consumer Key (CliendID) and Consumer Secret (Client Secret) will be displayed. **IMPORTANT: STORE THIS VALUE IN A SAFE PLACE WHERE IT CAN BE EASILY USED FOR FUTURE REFERENCE.**
{% endstep %} {% step %} ### Configure Policies (very important) After creating the ECA, open the **Policies** tab and adjust as needed (exact options vary by org/security posture), commonly: * **Permitted Users**: often set to **Admin approved users are pre-authorized** for controlled rollouts. * Add the required **profiles/permission sets** (or approved users) for who is allowed to authorize. {% endstep %} {% step %} ### What you’ll use in AutoRABIT Once created, the set of values you’ll reference in your CodeScan configuration are: * **Client ID** * **Client Secret** Also, the internal direction is to be clear that **one ECA per customer org** can be used across products (rather than creating one per AR product). *** After the configuration in salesforce is complete, and you have obtained the ClientID and Client Secret, we can go to CodeScan to create the connection In Project analysis click on Add Analysis Project
If no previous connections are found or the required org is not present in the Connection list, a message to go into the Salesforce Connections page is displayed.
If that is the case, go in the Salesforce Connections page, click on the existing connection or click on the Create connection button
Create the connections filling the required information obtained from Salesforce.
Once the connection is created, go back into adding a new Analysis page and click again in Add Analysis Project and select the desired connection.
Once the Confirm button is clicked a salesforce login is shown to login with the user we intend to use for the analysis.
A message from Salesforce will show to require granted permissions for the user to use the scopes defined in the ECA, Click Allow
Then, you will be returned to configure the new Analysis, fill up the form.
Then the analysis with the connection will be added to the list.
{% hint style="info" %} **Important:** This setup is **Salesforce org-specific**. You must repeat this process **for each customer Salesforce org** you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials. {% endhint %} {% endstep %} {% endstepper %} # Guard: Salesforce ECA (Local) Connection Setup Steps This is a step by step on how to implement the Local ECA solution to establish a new connection with Guard. {% stepper %} {% step %} ### Pre-req: get your Callback URL (redirect URI) For AutoRABIT’s Guard ECA setup, you need **the callback URL** Callback URL is depending on the instance: ``` {$instancename}/oauth/_callback ``` Example: ``` https://yourguard.autorabit.com/oauth/_callback ``` {% endstep %} {% step %} ### Create the External Client App (ECA) in your Salesforce Org 1. Login into Salesforce
2. In **Salesforce**, go to **Setup**. 3. In **Quick Find**, search **External Client Apps**. 4. Open **External Client App Manager** (or the External Client Apps area).
5. Click **New External Client App**. 6. Fill in the basics: * **Name / Label ( e.g. AR\_Local)** * **API Name** (auto-filled) * **Contact Email** * **Distribution State**: * **Local** (only for this org)
{% endstep %} {% step %} ### Enable OAuth + set callback URL + scopes 1. Click **Enable OAuth** (or expand **API (Enable OAuth Settings)** and check **Enable OAuth**). 2. Set \**Callback URL* The URL you collected in step 1. 3. Choose **OAuth Scopes**: 1. Access the Identity URL service (id, profile, email, address, phone) 2. Manage user data via APIs 3. Manage user data via web browsers (web) 4. Full access (full) 5. Perform requests at any time (refresh\_token, offline\_access.
{% endstep %} {% step %} ### Turnment 1. In **Flow Enablement**, select **Enable Authorization Code and Credentials Flow**. 2. **user credentials are required in the POST body** (Salesforce shows this option when you choose that flow) should be disabled.
{% endstep %} {% step %} ### Security toggles (common defaults) In the **Security** section the next options should be enabled: * **Require secret for Web Server Flow** * **Require secret for Refresh Token Flow** {% endstep %} {% step %} ### Create the app and capture Client ID / Secret 1. Click **Create**. 2. Open the app’s **Settings** tab and locate **Consumer Key and Secret**: * **Consumer Key** = **Client ID** * **Consumer Secret** = **Client Secret** {% hint style="info" %} **Important Note**: After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error error=invalid\_client\_id\&error\_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, and try again to allow the Salesforce configuration to sync completely. {% endhint %}
When you click the button for Consumer Key and Secret a code will be sent to the registered email for the user creating the configuration
After getting the code and verify in Salesforce the Consumer Key (CliendID) and Consumer Secret (Client Secret) will be displayed. **IMPORTANT: STORE THIS VALUE IN A SAFE PLACE WHERE IT CAN BE EASILY USED FOR FUTURE REFERENCE.**
{% endstep %} {% step %} ### Configure Policies (very important) After creating the ECA, open the **Policies** tab and adjust as needed (exact options vary by org/security posture), commonly: * **Permitted Users**: often set to **Admin approved users are pre-authorized** for controlled rollouts. * Add the required **profiles/permission sets** (or approved users) for who is allowed to authorize. {% endstep %} {% step %} ### What you’ll use in AutoRABIT Once created, the set of values you’ll reference in your Guard configuration are: * **Client ID** * **Client Secret** Also, the internal direction is to be clear that **one ECA per customer org** can be used across products (rather than creating one per AR product). *** After the configuration in salesforce is complete, and you have obtained the ClientID and Client Secret, we can go to Guard to create the connection Click in Salesforce Orgs
Click in the button Add a new Org
If the org that wants to be connected already has the Guard Connected App installed and active, the connected app option should be selected if not, select External Client App as the connection type and enter all the required details in the corresponding fields.
Once the form is completed, click on the button Login to Salesforce, and a salesforce login page is shown to login with the user we intend to use for the connection.
A message from Salesforce will show to require granted permissions for the user to use the scopes defined in the ECA, Click Allow
Then, the org will be added successfully. {% hint style="info" %} **Important:** This setup is **Salesforce org-specific**. You must repeat this process **for each customer Salesforce org** you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials. {% endhint %} {% endstep %} {% endstepper %} # AutoRABIT Vault: Salesforce ECA (Local) Connection Setup Steps This is a step by step on how to implement the Local ECA solution to establish a new connection with AutoRABIT Vault. ### Pre-req: get your Callback URL (redirect URI) For AutoRABIT’s Vault ECA setup, you need **the callback URL** Callback URL is depending on the instance: ``` {$isntancename}/dashboard/setup/addSfOrg ``` Example: ``` https://vault-qa.autorabit.com/dashboard/setup/addSfOrg ``` {% stepper %} {% step %} ### Create the External Client App (ECA) in your Salesforce Org 1. Login into Salesforce
2. In **Salesforce**, go to **Setup**. 3. In **Quick Find**, search **External Client Apps**. 4. Open **External Client App Manager** (or the External Client Apps area).
5. Click **New External Client App**. 6. Fill in the basics: * **Name / Label ( e.g. AR\_Local)** * **API Name** (auto-filled) * **Contact Email** * **Distribution State**: * **Local** (only for this org)
{% endstep %} {% step %} {% hint style="info" %} ### **Important Note:** After creating the ECA in Salesforce, there may be a replication delay on the Salesforce side. If you encounter the error error=invalid\_client\_id\&error\_description=client%20identifier%20invalid while attempting to connect or register the org, please wait 30 minutes, then try again to allow the Salesforce configuration to sync completely. {% endhint %} {% endstep %} {% step %} ### Enable OAuth + set callback URL + scopes 1. Click **Enable OAuth** (or expand **API (Enable OAuth Settings)** and check **Enable OAuth**). 2. Set \**Callback URL* The URL you collected in step 1. 3. Choose **OAuth Scopes**: 1. Access the Identity URL service (id, profile, email, address, phone) 2. Manage user data via APIs 3. Manage user data via web browsers (web) 4. Full access (full) 5. Perform requests at any time (refresh\_token, offline\_access.
{% endstep %} {% step %} ### Turnment 1. In **Flow Enablement**, select **Enable Authorization Code and Credentials Flow**. 2. **user credentials are required in the POST body** (Salesforce shows this option when you choose that flow) should be disabled.
{% endstep %} {% step %} ### Security toggles (common defaults) In the **Security** section the next options should be enabled: * **Require secret for Web Server Flow** * **Require secret for Refresh Token Flow** {% endstep %} {% step %} ### Create the app and capture Client ID / Secret 1. Click **Create**. 2. Open the app’s **Settings** tab and locate **Consumer Key and Secret**: * **Consumer Key** = **Client ID** * **Consumer Secret** = **Client Secret**
When you click the button for Consumer Key and Secret a code will be sent to the registered email for the user creating the configuration
After getting the code and verify in Salesforce the Consumer Key (CliendID) and Consumer Secret (Client Secret) will be displayed. **IMPORTANT: STORE THIS VALUE IN A SAFE PLACE WHERE IT CAN BE EASILY USED FOR FUTURE REFERENCE.**
{% endstep %} {% step %} ### Configure Policies (very important) After creating the ECA, open the **Policies** tab and adjust as needed (exact options vary by org/security posture), commonly: * **Permitted Users**: often set to **Admin approved users are pre-authorized** for controlled rollouts. * Add the required **profiles/permission sets** (or approved users) for whom is allowed to authorize. {% endstep %} {% step %} ### What you’ll use in AutoRABIT Once created, the set of values you’ll reference in your AutoRABIT Vault configuration are: * **Client ID** * **Client Secret** Also, the internal direction is to be clear that **one ECA per customer org** can be used across products (rather than creating one per AR product). *** After the configuration in Salesforce is complete, and you have obtained the ClientID and Client Secret, we can go to Vault to create the connection In the menu Click Salesforce Org Integration
Create the connections, filling in the required information.
Enter the Client ID and Client Secret that you received from Salesforce.
Once the continue button is clicked, a Salesforce login is shown for the user we intend to use with the connection.
A message from Salesforce will show to require granted permissions for the user to use the scopes defined in the ECA, Click Allow.
Then you will be returned, and the connection will be saved.
Click finish, and the success message will appear.
{% hint style="info" %} **Important:** This setup is **Salesforce org-specific**. You must repeat this process **for each customer Salesforce org** you want to connect, since the External Client App is created inside (and scoped to) that org and produces org-specific credentials. {% endhint %} {% endstep %} {% endstepper %} # ARM FAQs Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information [here](https://knowledgebase.autorabit.com/~/revisions/cT0ZuVgeUzTQt27sMR9n/product-guides/arm/troubleshoot/arm-faqs) for FAQs on AutoRABIT ARM. # CodeScan FAQs Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information [here](https://knowledgebase.autorabit.com/~/revisions/Sxgg9jAjbkdELNi4g1n4/product-guides/codescan/codescan-faqs) for FAQs on CodeScan. # AutoRABIT Vault FAQs Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information [here](https://knowledgebase.autorabit.com/~/revisions/4D085eRCQQOD5ETlONn0/product-guides/vault/vault-faqs) for FAQs on AutoRABIT Vault. # Automatic Cleanup of Deactivated Picklist Values #### What is changing in ARM? ARM now automatically removes references to deactivated picklist values from all impacted Record Types associated with the same Salesforce object. #### Why is this needed? When a picklist value is deactivated at the field level, Salesforce removes its availability from associated Record Types. However, Record Type metadata already stored in Git may continue to reference the deactivated value if those Record Types are not included in the commit. This can result in stale metadata and potential deployment validation issues. #### How did ARM handle this previously? Previously, ARM removed the deactivated picklist value only from the Record Types explicitly selected as part of the commit. Other Record Types under the same object could continue to reference the deactivated value in Git. #### How does ARM handle this now? When a picklist value is deactivated, ARM will: 1. Identify the parent object. 2. Scan all Record Types under that object. 3. Identify Record Types referencing the deactivated value. 4. Remove the invalid reference. 5. Automatically include the impacted Record Types in the commit. #### Do I need to select all impacted Record Types? No. ARM automatically scans all Record Types under the parent object, regardless of which Record Types you selected for the commit. #### Will ARM modify unrelated Record Types or metadata? No. Only Record Types containing references to the deactivated picklist value are updated. Active picklist values and unrelated metadata remain unchanged. #### What is the benefit? This enhancement keeps field and Record Type metadata synchronized in Git, reduces stale metadata references and deployment issues, and eliminates the need to manually identify and commit every affected Record Type. # Announcements Stay informed — this page is your go-to destination for all organization-wide announcements. # Status of AutoRABIT in the Middle East #### **Update: 5 March 2026** AWS has indicated that services in this region continue to experience disruption, which is impacting certain AutoRABIT services. Our teams continue to actively monitor the situation and remain engaged with AWS as they work toward full service restoration.\ \ As AWS services have begun to recover, we have successfully restored one impacted AutoRABIT Vault instance (ME106). We have validated that the instance is functioning normally, and we are now coordinating directly with affected customers to confirm operational status.\ \ At this time, service restoration for other impacted environments remains dependent on AWS recovery efforts. We will continue to monitor developments closely and will share additional updates as more information becomes available. *** #### Status of AutoRABIT in the Middle East - 3 March 2026 We are currently experiencing a regional infrastructure disruption impacting AWS facilities in the Middle East region. AWS has indicated that certain production data centers in the region are affected. We are actively coordinating with AWS and closely monitoring their restoration efforts. Based on the latest information provided by AWS, there is currently no indication of data loss, but service restoration may take additional time and could extend up to or beyond 24–48 hours. We will continue to share updates as confirmed information becomes available. Our deployment is regionally redundant within the Middle East. Given the current impact to AWS infrastructure in the region, cross-region failover is not operationally feasible at this time. If the disruption continues and you would like to explore temporary deployment in another AWS region (e.g., U.S., Europe, or Asia Pacific), please reach out to your CSM, account representative, or Support. Any such change would require review of applicable contractual and data residency considerations and would be handled on a case-by-case basis. Restoring service safely and completely remains our highest priority. We will continue monitoring and will notify you promptly if that status changes. # Upgrading the Node Runtime for Azure DevOps {% hint style="info" %} **This change applies to all CodeScan customers running scans through the Azure DevOps extension.** If you use Microsoft-hosted (default) agents, no action is required. If you run your pipelines on custom (self-hosted) agents, please review the *Custom (Self-Hosted) Agents* section below. {% endhint %} #### **Overview** As part of our ongoing commitment to platform security and maintenance, CodeScan is upgrading the Node runtime used by our Azure DevOps extension to **Node 24** on **October 11, 2026**. To support a smooth transition, **Node 20 will remain available as a fallback** alongside Node 24, ensuring uninterrupted operation while customers validate compatibility with the new runtime. Your scan functionality remains the same — this is a runtime update only. #### Actions Required **If you use Microsoft-hosted (default) agents**, no action is required. Microsoft-hosted agents are already compatible with both Node 20 and Node 24, and your pipelines will continue to run without changes. **If you use custom (self-hosted) agents**, please ensure your agents are compatible with at least Node 20 ahead of the upgrade date. Agents that meet this requirement will continue to operate without interruption when the upgrade takes effect. #### Custom (Self-Hosted) Agents To confirm your self-hosted agents are ready for the upgrade: 1. Verify that each agent machine has a supported Node runtime installed (Node 20 or later). 2. Confirm operating system and architecture compatibility with your installed Node version. 3. Where possible, we recommend upgrading agents to Node 24 to align with the new default runtime and benefit from the latest security and performance updates. #### Need Help? 1. Refer to Microsoft's [Azure Pipelines agents documentation](https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/agents) for guidance on managing self-hosted agents. 2. Contact AutoRABIT Support (). #### Additional Resources For more information on Node.js release schedules and supported versions, refer to the [Node.js release documentation](https://nodejs.org/en/about/previous-releases). # Deprecation of Node 20 on GitHub Actions Runners {% hint style="info" %} **This change applies only to GitHub projects scanned using GitHub Actions** (a `codescan.yml` workflow that calls the CodeScan scanner action). If you use the native CodeScan–GitHub integration, where scans are triggered from within CodeScan with no YAML workflow file, this change does not affect you, and no action is required. {% endhint %} #### **Overview** As part of GitHub's ongoing platform maintenance, the Node 20 runtime on GitHub Actions runners is being retired and replaced by Node 24. To ensure your scans continue running without interruption, CodeScan will release an updated scanner action (`@3.0`) on **October 11, 2026**. We recommend updating your workflow ahead of GitHub's Node 20 removal, which is currently estimated for Fall 2026 (see more [here](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/)). Your scan functionality remains the same—this is a runtime update only. #### Actions Required Update the following action versions in your `codescan.yml` workflow: 1. `codescan-io/codescan-scanner-action` : `@2.0` → `@3.0` 2. `actions/checkout` : `@v4` → `@v6` 3. `actions/cache` : `@v4` → `@v5` 4. `github/codeql-action/upload-sarif` : `@v3` → `@v4` 5. `actions/upload-artifact` : `@v3`/`@v4` → `@v6` #### Custom (Self-Hosted) Runners If you run your GitHub Actions workflows on custom (self-hosted) runners rather than GitHub-hosted ones, an additional step is required beyond updating your action versions: 1. **Update your action versions** in `codescan.yml` (as listed in *Actions Required* above). 2. **Upgrade your runner** to a version that supports Node 24 (**v2.328.0 or later**), and confirm operating system and architecture compatibility: * Node 24 is **not compatible with macOS 13.4 or earlier** — please upgrade the operating system on affected runners. * **ARM32 is no longer supported** — these runners will stop working once Node 20 is removed. #### Runtime Configuration Option GitHub provides an environmental variable to help you manage the transition on your own timeline. This is optional — updating your Action versions as described above is the recommended path. **To temporarily continue on Node 20:** Once Node 24 becomes the default, you can temporarily opt out by setting `ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true` {% hint style="info" %} Please note that this is a temporary measure until Node 20 full removal. {% endhint %} #### Need Help? 1. Please refer to the [GitHub Changelog](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/) for additional details. 2. Contact AutoRABIT Support (). # Preparing for Salesforce Connected App Usage Restrictions {% hint style="info" %} **The information on this page has been deprecated as of 25 February 2026.** Please see the following page for additional information on the [**Salesforce Oath External Client App (ECA) Transition**](https://knowledgebase.autorabit.com/fundamentals/announcements/salesforce-oauth-external-client-app-eca-transition). {% endhint %} ### **Overview** Salesforce has announced changes to how uninstalled connected apps function in customer orgs, effective September 2025. These changes impact AutoRABIT products that connect to your Salesforce environments using the OAuth 2.0 Client Credentials Flow. ### What’s Changing in Salesforce 1. Uninstalled connected apps restricted — New authorizations will be blocked unless specific permissions are granted. > **Note:** The existing connections between AutoRABIT and Salesforce are not going to be impacted by this change 2. OAuth 2.0 Device Flow blocked — Not used by AutoRABIT. 3. New permissions introduced: 1. Approve Uninstalled Connected Apps 2. Use Any API Client ### Impact on AutoRABIT Products 1. AutoRABIT Vault, ARM, and CodeScan Cloud connect to Salesforce via Client Credentials Flow, which creates an uninstalled connected app. 2. Existing connections (before September 2025): Will continue to work. 3. New connections (after September 2025): May fail unless permissions are updated by your Salesforce admin. ### Actions Required *For existing customers with an already connected Org/s to AutoRABIT*\ No action is required. Recommended configuration:\ *For existing customers, adding net new Salesforce Sandbox Orgs* **Install Connected App** 1. In your Salesforce Org, Navigate to Setup → type Connected Apps OAuth Usage in the Quick Find box. 2. Find the AutoRABIT connected app in the list. If it’s not installed, there will be an Install button next to it. 3. Click Install, then confirm on the subsequent page. **Optional Configuration:**\ *Applies to initial authentications with AutoRABIT made after the connected apps security change made by Salesforce, or net new production orgs (this will be updated, as more information becomes available from Salesforce)* Actions Required 1. Identify AutoRABIT Connected Apps: 1. Go to Setup → Connected Apps OAuth Usage in Salesforce. 2. Locate entries linked to AutoRABIT. 2. Update User Permissions: 1. If API Access Control is enabled: Assign “Use Any API Client.” 2. If API Access Control is not enabled: Assign either “Approve Uninstalled Connected Apps” or “Use Any API Client.” Grant these permissions only to trusted integration users. ### Best Practices 1. Use a dedicated integration user for AutoRABIT. 2. Grant only minimum required permissions. 3. Review unused connected apps regularly and remove them. ### Need Help? 1. Contact AutoRABIT Support (). 2. Refer to Salesforce’s announcement: Prepare for Connected App Usage Restrictions Change. ### Additional Resources Refer to the [Salesforce documentation](https://help.salesforce.com/s/articleView?id=005132365\&type=1) below for additional details. ### FAQ **Will my existing AutoRABIT connections stop working?** No. If you connected AutoRABIT products (AutoRABIT Vault, ARM, CodeScan Cloud) to Salesforce before the enforcement date in September 2025, your existing integrations will continue to work. **What happens if I try to create a new connection after September 2025?** New connections may fail unless your Salesforce administrator assigns the new permissions introduced by Salesforce (Approve Uninstalled Connected Apps or Use Any API Client). **Which Salesforce permission should be used?** If API Access Control is enabled in your org, assign 'Use Any API Client'. If it is not enabled, you may assign either 'Approve Uninstalled Connected Apps' or 'Use Any API Client'. These should be granted only to trusted integration users. **Does AutoRABIT use the OAuth Device Flow?** No. AutoRABIT uses the OAuth 2.0 Client Credentials Flow, which creates an uninstalled connected app in your Salesforce org. The blocked device flow is not used by AutoRABIT. **Is there a long-term solution beyond permissions?** Yes. AutoRABIT is actively working on enhancements to move towards installed connected apps for greater security and compliance. Updates will be shared in future product releases. **Do I need to reinstall AutoRABIT in my Salesforce org?** No reinstallation is required. You only need to ensure the correct Salesforce permissions are assigned to your integration user for new connections after September 2025. **Where can I read Salesforce’s official announcement?** You can view Salesforce’s official article at . **Who should I contact if I face issues?** Please contact AutoRABIT Support () for assistance with setup, permissions, or troubleshooting. # Salesforce’s February 5, 2026 DigiCert G2 certificate change – No Impact to AutoRABIT Services Salesforce is making an update to its security certificates beginning **February 5, 2026**. These updates are part of Salesforce’s ongoing efforts to keep its platform secure and reliable.\ We’re pleased to confirm that **AutoRABIT customers will not be affected by this change**. **What This Means for You** You do **not** need to take any action. AutoRABIT has already completed all the necessary preparations to ensure full compatibility with Salesforce’s update. All AutoRABIT services—including backups, deployments, and integrations—will continue to operate normally. **Why You’re Seeing This Notice** Some customers may receive communications directly from Salesforce about upcoming certificate updates. These messages are informational and apply to many different systems that integrate with Salesforce. AutoRABIT has reviewed the change and proactively ensured full alignment so your service remains uninterrupted. **Do I Need to Update Anything?** No. Everything has already been handled by the AutoRABIT team. **Can I Continue Using AutoRABIT Normally?** Yes—there will be no disruption to your backups, CI/CD processes, or any other features. # Salesforce OAuth External Client App (ECA) Transition ### Overview Salesforce is transitioning from the legacy Connected App model to External Client Apps (ECA) for new OAuth integrations. This change affects how new integrations are registered within Salesforce orgs and is tied to the Salesforce Spring ’26 release. For more details from Salesforce, see their official announcement: . AutoRABIT is actively updating its products to support this new Salesforce framework. This article addresses common questions and clarifies what this means for your existing and future Salesforce integrations. ### Does this impact my existing Salesforce integration? No. Existing Salesforce connections in AutoRABIT’s products will continue to work as they do today. If your Salesforce org is already connected to AutoRABIT’s products using a Connected App, no action is required. There is no expected downtime and no disruption to current integrations. This change only affects new Salesforce org registrations. ### What exactly is changing in Salesforce? Salesforce is replacing Connected Apps with External Client Apps for new OAuth-based integrations. In upcoming Salesforce releases, customers will no longer be able to create new Connected Apps and must instead use the External Client App framework. This is a Salesforce platform change intended to modernize the integration and authentication model. For more information, refer to Salesforce’s documentation: . ### Who is affected by this change? You may be impacted if you are using connected app and registering a new Salesforce org/sandbox in AutoRABIT’s products.If your Salesforce org is already connected to AutoRABIT’s products, you are not impacted. ### What happens if I try to register a new org today? Salesforce has indicated the following regarding continued use of connected apps as part of the Spring ’26 release: > What happens to existing connected apps? There is no change to existing connected apps. Connected app editing, installing (packaging, OAuth install), and deleting will not be affected by this change. > What is the longer-term plan for connected apps? Connected apps will be replaced with external client apps. We are giving customers time to work on transitioning their connected apps to ECAs by gradually moving to End of Support. AutoRABIT is actively working on full compatibility with External Client Apps and will notify customers as soon as support is available. ### Will I need to reconnect my existing Salesforce orgs? No. Existing integrations will continue functioning normally. Reconnection would only be required if: * The existing OAuth connection is manually revoked. * The Connected App is deleted in Salesforce. * Credentials are invalidated for another administrative reason. Otherwise, no migration or reconfiguration is required at this time. ### Why is Salesforce making this change? Salesforce is modernizing its integration model to improve security, modularize authentication plugins, and provide clearer lifecycle management for external integrations. This change applies across the Salesforce ecosystem and is not specific to AutoRABIT. Additional details are available in Salesforce’s release documentation: . ### What about Salesforce sandboxes? Salesforce sandboxes require separate app registrations. If you create or refresh a sandbox, you may need to register it again once AutoRABIT’s ECA support is released. Existing connected sandboxes will continue to function as expected. ### Is there any security impact? There is no negative security impact. Existing AutoRABIT integrations remain secure. AutoRABIT continues to use OAuth 2.0 best practices and encrypted token storage. The Salesforce platform change does not weaken or expose existing integrations. ### What is AutoRABIT doing? AutoRABIT is updating its products to support Salesforce External Client Apps using OAuth 2.0 Web Server Flow. The update will include: * A guided Salesforce registration workflow * Clear setup instructions * Live validation during connection * Improved error handling * Enhanced visibility into integration health We will announce availability as soon as the update is released. ### When will support be available? Support for Salesforce External Client Apps is planned to be available by the end of February 2026. Customers will be notified through in-app messaging and updated documentation when the feature is released. ### Additional Questions If you have further questions about how this change affects your organization, please reach out to AutoRABIT Support. Our team is available to assist and provide clarity on your specific environment. # Salesforce Summer ’27 Update: Retirement of SOAP API login() Authentication ### Overview Salesforce has announced the retirement of the **SOAP API `login()` authentication method** by **Summer ’27**. This method allows integrations to authenticate using **Username + Password + Security Token**. AutoRABIT currently provides a legacy authentication option that uses this mechanism to connect to Salesforce organizations. Since Salesforce is deprecating this method, it may impact integrations that rely on this authentication approach. ### Impact If your AutoRABIT connection to Salesforce uses the following authentication method: * Username * Password * Security Token then it relies on the **SOAP API `login()` method**. Once Salesforce retires this functionality, this authentication method will no longer be supported by Salesforce, and integrations using it may fail to authenticate. ### Where to Find the Setting You can locate this setting in **Salesforce Setup**. **Navigation:**\ `Setup → Quick Find → User Interface → Enable SOAP API login()` If this option is enabled, external systems can authenticate using the **SOAP API `login()` call**. ### Important Note Salesforce has announced that **SOAP API `login()` will be retired in Summer ’27**. For new Salesforce orgs, this option is **disabled by default**. Even if you see a message about the retirement when hovering over the setting, it simply indicates the future deprecation notice and does **not affect the current configuration**. ### Recommendation Salesforce is moving toward a modern integration model using **External Client Apps**. External Client Apps are designed for **secure API-based integrations** and provide stronger authentication and governance controls for external systems. AutoRABIT recommends using authentication based on **OAuth authentication via External Client Apps**. This approach aligns with Salesforce’s long-term **security and integration strategy**. ### References **Salesforce Documentation – SOAP API `login()`**\ **Salesforce Knowledge Article**\ {% hint style="info" %} **Note:** Customers are encouraged to review their current authentication configurations and update them before the **Summer ’27 Salesforce release** to avoid potential service disruptions. {% endhint %} # Bitbucket App Password Deprecation – Action Required Before June 9, 2026 ### Overview Atlassian is deprecating **Bitbucket Cloud App Passwords** effective **June 9, 2026**. After this date, App Passwords will no longer be supported for authentication and any integrations, automation, or API operations that rely on App Passwords may fail. To avoid service disruptions, all users currently using Bitbucket App Passwords must migrate to **Bitbucket API Tokens** before the deadline. *** ### Who Is Impacted? You are impacted if you use Bitbucket App Passwords for: * API integrations * CI/CD pipelines * Automation scripts * Third-party integrations * Repository operations performed over HTTPS authentication #### Not Impacted Users who authenticate using **SSH keys** for Git operations are **not affected** by this change and do not need to take any action. *** ### Required Actions #### 1. Replace App Passwords with API Tokens If your integrations, scripts, or tools currently use Bitbucket App Passwords, update them to use **Bitbucket API Tokens**. Review all automation, integrations, and configuration settings to identify and replace any stored App Password credentials. #### 2. Update API Authentication Credentials As part of this change, Bitbucket now requires the **email address associated with the Bitbucket account** for API authentication. **Previous Behavior** * Git Operations: Username * API Operations: Username **New Behavior** * Git Operations: Username * API Operations: Email Address (mandatory) Any API integrations that currently use only the Bitbucket username must be updated to use the account's registered email address along with the API Token. **User Guide(ARM)** {% embed url="" %} {% embed url="" %} # CodeScan Rules Deactivation Five CodeScan rules are being fully deactivated as of the 21st of September. Review your Quality Profiles and switch to the replacement rules listed below. ## Upcoming Rule Deactivations: 5 Rules Retiring on the 21st of September 2026 {% hint style="warning" %} **Five CodeScan rules will be fully deactivated as of 21st September 2026.** Each rule below has already been marked **Deprecated** and superseded by an improved rule with better or more accurate coverage. {% endhint %} ### How to check if you're affected {% hint style="info" %} Rules subject to deactivation are highlighted in **red** next to the overall rule count within your Quality Profiles. {% endhint %} 1. Navigate to **Quality Profiles** in CodeScan. 2. Look for rules highlighted in red next to the overall rule count within each profile. 3. Open any flagged rule to see its specific deactivation reason and recommended replacement. ### Rules being deactivated #### 1. Custom fields must have a description field Key: `sfmeta:RequireDescriptionField` Language: `Salesforce Metadata` Type: `Code Smell` **Why it's flagged**\ Custom fields should have a description of their function to avoid confusion. This rule requires `.object` or `.field-meta.xml` metadata files to be downloaded. **Reason for deactivation**\ All functionality has been folded into `sfmeta:RequireDescriptionComponent`. {% hint style="success" %} **Action:** Remove this rule from your custom Quality Profile and add `sfmeta:RequireDescriptionComponent` instead. {% endhint %} #### 2. Unnecessary Parentheses Key: `sf:UnnecessaryParentheses` Language: `Apex` Type: `Code Smell` **Why it's flagged**\ Expressions are sometimes wrapped in unnecessary parentheses, making them look like function calls. **Reason for deactivation**\ Superseded by an improved rule covering the same code style concern. {% hint style="success" %} **Action:** Remove this rule from your custom Quality Profile and add `sf:UselessParentheses` instead. {% endhint %} #### 3. Use System.Assert instead of System.assertEquals Key: `sf:UseAssertInsteadOfAssertEquals` Language: `Apex` Type: `Code Smell` **Why it's flagged**\ When asserting that a value equals a boolean literal, `System.assert` should be used instead of `System.assertEquals`. **Reason for deactivation**\ Salesforce now recommends using the `Assert` class for unit tests. {% hint style="success" %} **Action:** Remove this rule from your custom Quality Profile and add `sf:UseIsTrueInsteadOfAreEqual` instead. {% endhint %} #### 4. Use System.assertEquals instead of System.assert (equality via `==`) Key: `sf:UseAssertEqualsInsteadOfAssertEquality` Language: `Apex` Type: `Code Smell` **Why it's flagged**\ This rule detects unit test assertions on object reference equality. Instead of using `System.assert` combined with `==` as the equality operator, assertions should use a more specific method like `assertEquals`. **Reason for deactivation**\ Salesforce now recommends using the `Assert` class for unit tests. {% hint style="success" %} **Action:** Remove this rule from your custom Quality Profile and add `sf:UseAreEqualInsteadOfAssertBoolean` instead. {% endhint %} #### 5. Use System.assertEquals instead of System.assert (equality via `.equals()`) Key: `sf:UseAssertEqualsInsteadOfAssert` Language: `Apex` Type: `Code Smell` **Why it's flagged**\ This rule detects unit test assertions on object reference equality. Instead of using `System.assert` combined with `.equals()` as an equality check, assertions should use a more specific method like `assertEquals`. **Reason for deactivation**\ Salesforce now recommends using the `Assert` class for unit tests. {% hint style="success" %} **Action:** Remove this rule from your custom Quality Profile and add `sf:UseAreEqualInsteadOfIsTrue` instead. {% endhint %} ### Quick reference table | Deprecated Rule | Rule ID | Replacement Rule | | -------------------------------------------------------------- | ------------------------------------------- | -------------------------------------- | | Custom fields must have a description field | `sfmeta:RequireDescriptionField` | `sfmeta:RequireDescriptionComponent` | | Unnecessary Parentheses | `sf:UnnecessaryParentheses` | `sf:UselessParentheses` | | Use System.Assert instead of System.assertEquals | `sf:UseAssertInsteadOfAssertEquals` | `sf:UseIsTrueInsteadOfAreEqual` | | Use System.assertEquals instead of System.assert (`==`) | `sf:UseAssertEqualsInsteadOfAssertEquality` | `sf:UseAreEqualInsteadOfAssertBoolean` | | Use System.assertEquals instead of System.assert (`.equals()`) | `sf:UseAssertEqualsInsteadOfAssert` | `sf:UseAreEqualInsteadOfIsTrue` | ### What you need to do 1. Check your Quality Profiles for any of the five rules listed above. 2. If found, remove the deprecated rule and add its corresponding replacement rule. 3. Re-run your analysis to confirm the new rule is active and behaving as expected. {% hint style="info" %} **Questions?** Contact us at . {% endhint %} # New CodeScan Rules for LWC Server-Side Rendering (SSR) Support ### Overview CodeScan is expanding its JavaScript/LWC rule coverage with 6 new rules that help identify code incompatible with Lightning Web Components Server-Side Rendering (SSR). These rules are part of our ongoing sync with the latest `@lwc/eslint-plugin-lwc` release. ### What's New | Rule | Severity | Type | | ------------------------------------------------------- | -------- | ------------- | | `ssr-no-disallowed-lwc-imports` | Critical | Vulnerability | | `ssr-no-host-mutation-in-connected-callback` | Critical | Bug | | `ssr-no-restricted-browser-globals` | Critical | Bug | | `ssr-no-unsupported-node-api` | Critical | Bug | | `ssr-no-form-factor` | Major | Bug | | `ssr-no-static-imports-of-user-specific-scoped-modules` | Major | Code Smell | All 6 rules apply to JavaScript/LWC code and carry the `lightning` and `salesforce` tags. ### Activating the New Rules These rules are **not active by default**. To include them in your scans: 1. Go to your custom Quality Profile. 2. Search for the `lightning` or `salesforce` tag to locate the new rules. 3. Activate the rules you want included. Existing scan results will not change until you complete this step. ### Prerequisite: Node.js Version Supporting these rules requires the scanning engine to run on ESLint 9, which in turn requires **Node.js 18.20.0 or later**. | Environment | Action Needed | | ----------------------------------------- | -------------------------------------------------------------------- | | CodeScan cloud-hosted service | None — we manage the runtime for you. | | Custom (self-hosted) CI/CD agents/runners | Confirm Node.js 18.20.0+ is installed before enabling the new rules. | | On-premises CodeScan installation | Confirm Node.js 18.20.0+ is installed before enabling the new rules. | If your environment doesn't meet this minimum, activating the new rules may cause scan failures until Node.js is upgraded. ### Need Help? Contact AutoRABIT Support at . # Release Notes {% @mailchimp/mailchimpSubscribe cta="Sign up to receive AutoRABIT updates!" listId="a085e26e7e" %} **Welcome to the AutoRABIT Release Notes page! This is your go-to resource for the latest updates and changes to all of our key products, including ARM, CodeScan, AutoRABIT Vault, Guard, and nCino integrations.** Here, you'll find detailed release notes that provide insights into new features, enhancements, and bug fixes for each product update. Our goal is to keep you informed and equipped with the knowledge to make the most of our products. {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} {% embed url="" %} By staying tuned to this page, you'll gain a deeper understanding of how our products are evolving to meet your needs and the changing landscape of software development. From small adjustments to major overhauls, every update is documented here to ensure you have all the information you need at your fingertips. Whether you're a new user learning the ropes or an experienced customer seeking to optimize your use of our products, our Release Notes page is an invaluable tool for staying up-to-date with AutoRABIT's dynamic suite of solutions. # ARM Release Notes
## 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. {% embed url="" %} #### 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**](mailto: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. {% embed url="" %} #### 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. {% embed url="" %} *** ## 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](https://knowledgebase.autorabit.com/product-guides/arm-1/arm-features/version-control/external-pull-request). #### 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](https://knowledgebase.autorabit.com/product-guides/arm-1/introduction-to-arm-developer-apis/api-references). #### 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](https://knowledgebase.autorabit.com/product-guides/arm-1/introduction-to-arm-developer-apis/api-references). #### 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 {% embed url="" %} *** ## 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 {% embed url="" %} {% embed url="" %} #### 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 `` 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:** {% embed url="" %} {% embed url="" %} #### 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 = D` for deleted metadata changes in the Old UI * Improved consistency between the Old UI and New UI for destructive changes handling * Updated deleted changes behavior during the `package.xml` upload flow: * `Modified By` and `Modified Date` fields 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: *** #### 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 `` 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** 1. **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)
2. **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)
3. **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
4. **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)
5. **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
6. **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
7. **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
8. **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)
9. **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. These components are now properly processed and deployed. **Impacted Areas:**\ Deployments, CI Jobs #### **LightningTypeBundle Metadata Not Detected in EZ Commit – Fix -** #210860 Fixed an issue where **LightningTypeBundle** metadata was not retrieved or displayed in **Review Artifacts** during EZ Commit, resulting in missing diffs. The system now correctly detects and processes this metadata across workflows. **Impacted Areas:**\ EZ Commit, EZ Merge, CI Jobs, Deployments *** ## DataLoader Pro Release Notes 26.1.13 **Release Date:** **29 March 2026** **DataLoader Pro - Pagination Issue in DataLoader Pro (New UI)** Resolved an issue where pagination did not function correctly after fetching objects in DataLoader Pro job configuration. Pagination now works as expected when navigating through master objects. *** ## DataLoader Release Notes 26.1.13 **Release Date:** **29 March 2026** **DataLoader Basic** - **Concurrent Job Validation in Data Loader Basic (New UI)** Fixed an issue where multiple jobs could be triggered for the same org without proper validation. The system now correctly prevents concurrent job execution and displays an appropriate error message when a job is already in progress. *** ## ARM Release Notes 26.1.12 **Release Date:** **22 March 2026** #### **Code Coverage & Test Class Report Structure Enhancement (New Enhancement)** Improved the structure of the **Code Coverage Report CSV** and **Test Class report** so that the test class name is now repeated on every row for each test method. This makes sorting, filtering, and analysis by class and method more reliable, especially for larger orgs. **Impacted Areas**\ Code Coverage Report CSV\ Test Class Report *** #### **Parallel Processor Support in CI Jobs – New UI** The **Parallel Processor** configuration is now available in the **New UI** for CI Jobs. This feature allows users to configure **GET or POST requests** to be executed before or after a Salesforce deployment as part of the CI job execution. This capability was previously available in the **Old UI** and has now been integrated into the **New UI** with the same functionality and behavior, ensuring feature parity across both interfaces. **Impacted Areas**\ CI Jobs – New UI Configuration *** #### **Scratch Org Deployment – Access Token Retrieval Fix** Fixed an issue where **CI Job deployments from a Salesforce Org to a Scratch Org** could fail with a **400 Bad Request error** while attempting to fetch an access token using the stored refresh token. This occurred when the **destination org was registered using Standard authentication and had a different login URL than the source org** (for example, Production/Developer source org and Sandbox destination org). The token retrieval logic has been updated to correctly handle such scenarios, preventing CI job failures during Scratch Org deployments. **Impacted Areas**\ CI Jobs – Deploy from Salesforce Org to Scratch Org *** #### **Dev Hub Selection Retention Fix – Create Unlocked Package Version and Install It to Salesforce (New UI)** Fixed an issue in the **New UI** where the selected **Dev Hub** was not retained in the CI Job type **“Create Unlocked Package Version and Install It to Salesforce.”** After saving the job configuration and completing deployment, returning to the **Edit Deployment** screen showed the **Dev Hub** field as empty, even though a value had been previously selected. The initialization logic has been corrected to ensure the saved **Dev Hub selection is retained and displayed properly** when reopening the job configuration. **Impacted Areas**\ CI Job → Create Unlocked Package Version and Install It to Salesforce → Deployment Settings → Dev Hub Selection (New UI) *** #### **ContentAsset Handling Fix – Release Label Artifacts** Fixed an issue where **including a ContentAsset modification revision in a Release Label artifact** caused package generation to fail with an error indicating missing source files for the **ContentAsset** type. The packaging logic has been updated to ensure that when a **ContentAsset** `.meta.xml` **file** is detected, the corresponding **binary asset file** is also included in the generated package if it exists in the repository. This prevents manifest generation failures and ensures ContentAssets are packaged correctly. **Impacted Areas**\ Release Labels in Version Control (DX and Non-DX)\ Release Label Deployment and Merge (ContentAsset changes) *** #### **CI Job Backup Failure Fix – Unsupported Metadata Type Handling** Fixed an issue where **CI Jobs configured for Backup to Version Control** could fail with the error **“Missing metadata type definition in registry for id 'CustomObjectBinding'.”** This occurred because Salesforce exposes the **CustomObjectBinding** metadata type during discovery, even though it is not currently supported for retrieval. The system previously attempted to include this metadata in retrieval batches, causing the job to fail. The metadata type has now been **added to the exclusion map**, preventing retrieval attempts and allowing CI backup jobs to complete successfully. **Impacted Areas**\ CI Jobs – Backup to Version Control *** #### **1-Month Data Retention Policy Option** ARM now supports a **1-Month retention policy** to provide greater flexibility in managing system data. Previously, retention policies were limited to **3 months, 6 months, and 12 months**. With this enhancement, administrators can configure a **30-day retention period**, enabling automatic removal of data older than one month. This helps organizations better manage storage usage, improve system performance, and align with internal compliance or governance requirements. Existing configurations using **3-month, 6-month, or 12-month** retention policies remain unchanged. **Impacted Areas**\ Administration → Retention Policy Settings *** #### **Multiple Approver Support for EZ-Merge – New UI** Added support for selecting **multiple approvers in EZ-Merge** within the **New UI**. Previously, users were limited to selecting only a **single approver** when creating a merge request, unlike the Old UI which allowed multiple approvers. This enhancement restores the ability to **select multiple approvers for merge approvals**, aligning the New UI behavior with the functionality available in the Old UI. **Impacted Areas**\ EZ-Merge – New UI *** #### **CI Job Configuration Save Fix – Install Package Job (New UI)** Fixed an issue in the **New UI** where configuration changes were not saved correctly for the CI Job type **“Install an Unlocked or Managed Package from a Version Control Branch.”** In some cases, fields such as **Run Apex Compile, Security Type, and Upgrade Type** reverted to different values when switching between the New UI and Old UI. The issue was caused by values not being properly retained in **disabled fields** during the save operation. This has been corrected to ensure the selected configuration values are saved and displayed accurately. **Impacted Areas**\ CI Job → Edit Job → Deploy Page (New UI) *** #### **Salesforce Spring ’26 (API 66) Metadata Support** ARM now supports additional metadata types introduced with **Salesforce Spring ’26 (API 66)**. The following metadata types are now supported: * AffinityScoreDefinition * CleanDataService * DuplicateRule * ExtlClntAppCanvasSettings * Flow sub-types (FlowSchedule, FlowScreenStyleSetting) * GiftEntryGridTemplate **Impacted Areas**\ Version Control\ Deployments\ CI Jobs *** ## Data Loader Pro Release Notes 26.1.12 **Release Date: 22 March 2026** **Flexible Result File Downloads**\ Users can now download Dataloader Pro job results in their preferred file format, making it easier to consume and share output data. This enhancement allows teams to align exports with their reporting standards or downstream tools without needing manual conversions after download. **Default Columns in Dataloader UI**\ Default column configurations have been introduced and corrected across Dataloader Basic and Pro screens. Previously, no default view options were applied, forcing users to manually adjust columns each time they accessed a screen. With this fix, users now see a sensible default column set, improving usability and reducing setup time for common workflows. **Correct Status for Aborted DL Pro Jobs**\ Aborted DL Pro jobs from the old UI now show an accurate status instead of incorrectly appearing as “Failed” in both the old and new interfaces. This fix improves the reliability of job status reporting, enabling teams to distinguish between genuine failures and intentional aborts, and to analyze actual failure trends more accurately. *** ## DataLoader Release Notes 26.1.12 **Release Date: 22 March 2026** **Accurate Count(id) in DL Basic Extract**\ The Count(id) column now correctly displays record counts in the new UI for DL Basic Extract jobs. Earlier, the column appeared empty in the new UI while still showing values in the old UI, leading to confusion and forcing users to cross-check between interfaces. The fix aligns both UIs so users can confidently rely on the new interface for record counts. **Accurate Count(id) in DL Basic Extract**\ The Count(id) column now correctly displays record counts in the new UI for DL Basic Extract jobs. Earlier, the column appeared empty in the new UI while still showing values in the old UI, leading to confusion and forcing users to cross-check between interfaces. The fix aligns both UIs so users can confidently rely on the new interface for record counts. *** ## ARM Release Notes 26.1.11 **Release Date:** **15 March 2026** #### Backup to Version Control – Credential Refresh Fix Fixed an issue in **CI → Jobs → Backup to Version Control** where changing the selected repository or branch did not refresh the associated credentials. The system previously continued using credentials from the initial selection, which could lead to authentication failures or incorrect commit identities. The credential refresh logic has been corrected to ensure the appropriate credentials are loaded whenever the repository or branch selection changes. **Impacted Areas**\ CI → Jobs → Backup to Version Control *** #### EZ-Commit – Retrieval Logs Button Fix Fixed an issue in **Version Control → EZ-Commit (Review Artifact screen)** where the **Retrieval Logs** button became unresponsive after the first click. Users can now open the logs panel multiple times without interruption, ensuring smooth review of retrieval logs during the commit process. **Impacted Areas**\ EZ-Commit (Version Control) → Retrieval Logs Button *** #### Mail Extension Placeholder & Validation Fix – New UI Fixed an issue in the **New UI → My Account → Mail Extensions** where the placeholder text in the **Extension Name field** suggested using an “@” symbol even though the system does not allow it. The placeholder and validation message have been updated to display valid examples and ensure consistency with the accepted input format. **Impacted Areas**\ New UI → My Account → Mail Extensions *** #### Env Provisioning – Unsupported Metadata Template Execution Fix Fixed an issue in **Env Provisioning** where executing the **“DisableTeams” template (Environment Provisioning Unsupported Metadata)** returned a **Succeeded** status, but the changes were not reflected in the target Salesforce Org. The template creation logic has been updated to ensure the configuration is properly processed so that all expected settings are applied after execution. **Impacted Areas**\ Env Provisioning *** #### Environment Provisioning History – Pagination Fix Fixed an issue in the **Environment Provisioning History** page where the grid displayed only **10 records** even when a higher page size was selected. Pagination has been corrected to ensure the grid displays the number of records based on the selected page size. **Impacted Areas**\ Environment Provisioning History Page *** #### Environment Provisioning – Duplicate Template Name Validation Fixed an issue in **New UI → Environment Provisioning → Templates** where the system allowed creation of templates with duplicate names without any validation. A validation check has been added to prevent duplicate template names and ensure users receive an appropriate error message when attempting to create one. **Impacted Areas**\ Create New Environment Provisioning Template *** #### #200317 – CI Jobs: Email Notification After Quick Deploy Enhanced **CI Job notifications** to support sending report emails after **Quick Deploy** execution. Previously, email notifications were sent only after the **Validate** stage. With this update, users will also receive CI Job report emails once the **Quick Deploy** process is completed. **Impacted Areas**\ CI Jobs with notification enabled and Quick Deploy applicable *** #### #201002 – Revision Range Deployment Commit Selection Fix Fixed an issue in **Deployment → Revision Range Deployments** where users were unable to select commits from the **first page of the “To” revision list** during a revision-range deployment. The UI logic has been corrected to allow proper selection of commits from the displayed list. **Impacted Areas**\ Deployment → Revision Range Deployments *** #### #198567 – Quick Merge Continue Button Fix (New UI) Fixed an issue in **New UI → Version Control → Commit History** where the **Continue** button in **Quick Merge** was disabled immediately after performing a new **EZ-Commit**. Users can now proceed with Quick Merge without needing to exit and reopen the page. **Impacted Areas**\ Version Control → Commit History → Quick Merge *** #### #202013 – CheckmarxOne Project Creation During EZ-Merge Resolved an issue where **AutoRABIT EZ-Merge operations with CheckmarxOne SCA validation** created a **new project in CheckmarxOne for every execution**. With the fix, scans executed during EZ-Merge will use a **single common project** instead of creating multiple projects. To apply this behavior, enable the feature flag **ENABLE\_CHECKMARK\_COMMON\_PROJECT\_EZMERGE**, which ensures all EZ-Merge scans are executed under the project **“AR-Merge.”** **Impacted Areas**\ EZ-Merge with CheckmarxOne SCA Validation *** #### #203270 – CI Job Validate Only Execution Fix Fixed an issue in **CI Jobs** where a queued job triggered with the **Validate Only** option executed as a **regular deployment**instead of validation. The issue occurred when multiple jobs were triggered and one entered the queue. The logic has been corrected to ensure queued jobs retain the **Validate Only** configuration and execute accordingly. **Impacted Areas**\ CI Jobs with Deployment (Validate Only and Real Deployment) option *** #### **GitHub OAuth Authentication Support for Repository Integration (New UI)** Introduced OAuth-based authentication support for GitHub repository integration in ARM, alongside the existing Personal Access Token (PAT) method. Users can now select OAuth during repository registration, authorize access via GitHub, and securely connect repositories without manually managing tokens. > **Note:** This feature is currently available only in the New UI. For step-by-step guidance, refer to the documentation:
**Impacted Areas:**\ Version Control → Repository Registration (GitHub OAuth) *** ## DataLoader Pro Release Notes 26.1.11 **Release Date: 15 March 2026** **DL Pro – Corrected Record Count Display for Objects with Similar Names** An issue was resolved where the **success count and error count** were displayed incorrectly in the **DL Pro results table** when multiple objects had the same name but different prefixes. The system now correctly distinguishes between such objects, ensuring that **success, error, and extracted record counts** are displayed accurately in the DataLoader parent and child relations result table. *** ## DataLoader Release Notes 26.1.11 **Release Date: 15 March 2026** **Deployment from Deployment History Fix** An issue was resolved where deploying a dataset directly from the **Deployment History** screen resulted in the error *“Unable to fetch feature deployment iteration objects.”* This has been fixed, and datasets can now be deployed successfully from the **Deployment History** view as expected. **Relational Compare Fix in Deploy using Template** An issue was resolved where performing a **relational compare** during **Deploy using Template** failed with the error *“Cannot retrieve data from Salesforce with the unique identifier.”* This occurred when parent records were not fetched during the relational compare process. The issue has been fixed, and relational compare now retrieves data correctly and proceeds without errors. **Aggregate Query Handling Improvement** An issue was addressed in **DataLoader** where running aggregate SOQL queries resulted in the error *“Field must be grouped or aggregated.”* Query validation and extract operations have been improved to correctly support relational field extraction when using **GROUP BY** and **ORDER BY** clauses, ensuring aggregate queries execute successfully. *** ## ARM Release Notes 26.1.10 **Release Date: 08 March 2026** #### RecordType Picklist Values Detection Fix #190557 Resolved an issue where newly added `` in **RecordType metadata** were not detected during **CI Job runs** or **Single Revision deployments** when the file contained a `` node. The delta generation logic has been updated to ensure picklist value changes are correctly identified and included in deployment packages. **Impacted Areas**\ Deployments, CI Jobs *** ## DataLoader Pro Release Notes 26.1.10 **Release Date: 08 March 2026** #### Processing Rule Migration – Parent-Child Relationship Fix Resolved an issue where **Processing Rule child records were not created during sandbox migration**, causing all rules to be imported as parent records. The migration logic has been updated to correctly handle **self-referential parent-child relationships**, ensuring that both parent and associated child rules are migrated as expected. *** ## ARM Release Notes 26.1.9 **Release Date: 01 March 2026** This release includes usability improvements, UI consistency enhancements, deployment fixes, and expanded authentication support. #### Merge Request – Delete Feature Branch Behavior Improvement We’ve improved the behavior of the **“Delete Feature Branch”** option in Merge Requests to ensure a smoother and more predictable user experience. #### What’s Improved * The **Delete Feature Branch** button is automatically hidden after commit when *“Delete source branch”* is selected. * The button remains visible if the option is not selected. * The button is temporarily disabled while deletion is in progress to prevent duplicate actions. This enhancement prevents accidental multiple deletions and improves workflow clarity. #### Clear AutorabitExtId – Status & Log Visibility Fix Resolved icon visibility issues during the **Clear AutorabitExtId** operation in both Old UI and New UI. ### Improvements * Status and Log icons no longer disappear during or after execution. * Status now correctly updates to **Success** or **Failed** upon completion. * Log access remains available after execution. * In the New UI, the **Live Status Log** icon is visible during execution. This ensures better execution tracking and improved transparency. #### Static Resource Deletion Fix – CI Deployment Addressed a CI deployment issue related to incomplete Static Resource deletions. ### Enhancement * Static Resources are now fully removed during deletion. * Prevents deployment errors caused by residual metadata. * Ensures accurate manifest generation in CI jobs. This improves deployment reliability and consistency. #### Search Functionality Enhancement – Metadata Filters Search functionality has been improved and aligned across Old UI and New UI. #### Search Now Supports Filtering By: * Metadata Member Name * Modified By * Modified Date This resolves previous inconsistencies and ensures consistent filtering behavior across interfaces. #### JIRA OAuth Redirection – 413 Error Fix Resolved a **413 – Request Entity Too Large** error occurring during JIRA OAuth registration in the New UI. OAuth registration now works seamlessly in both Old UI and New UI. #### Salesforce Org Registration via OAuth – External Client App (ECA) ARM now supports OAuth via External Client App (ECA) as a modern Salesforce authentication method. #### What’s New * New authentication option: OAuth via External Client App * Secure OAuth authorization * Encrypted token storage * Token lifecycle management * Re-authentication support with editable **Consumer ID** and **Consumer Key** * Please use the link below for Step-by-Step guidance * #### Migration Support Existing Salesforce orgs using Standard or Connected App OAuth can migrate to ECA without: * Creating a new org entry * Losing pipelines, jobs, or configurations * Affecting existing mappings The authentication type and connection status update automatically upon successful migration. This enhancement strengthens security and aligns with modern Salesforce authentication standards. #### Salesforce Org Visibility After Permission Update (New UI) Fixed an issue where updating User Permissions in the New UI caused the associated Salesforce Org to disappear from **My Profile → My Salesforce Orgs**. The save logic has been corrected to ensure the Org association remains intact after permission updates. *** ## DataLoader Pro Release Notes 26.1.9 **Release Date: 01 March 2026** #### Hierarchical Object Handling – Parent Resolution Consistency Enhanced object hierarchy handling to ensure consistent behavior between job configuration and execution. Previously, in cases where an object (e.g., **Loan**) functioned both as a child (in the UI) and as a parent (in the hierarchy), additional parent objects were fetched during execution even if they were not selected during job creation. With this fix, only the objects selected during configuration will be processed during execution, unless mandatory parent dependencies are explicitly required. *** ## ARM Release Notes 26.1.8 **Release Date: 22 February 2026** #### Test Mapping Management – Bulk Import/Export (New UI) Enhanced Test Mapping management is now available in the new UI to simplify maintenance and reduce unnecessary test executions. Users can now download existing test mappings, edit them offline, and re-upload via CSV for bulk updates. The uploaded file fully replaces the existing mapping set after confirmation. System validations ensure correct file format and structure before processing. A backup of the previous file is automatically maintained (one version at a time) and can be downloaded if needed. The UI also displays last updated date and updated by details, with changes tracked in back-end tables. **Note:** Only three columns are supported in import: Sno, Apex Test Class, and Apex Class/Trigger. **Impacted Areas (DEV)**\ CI Jobs – Test Mapping Configuration (New UI) **Functional Impact Areas (QA)**\ CI/CD – Run Tests Based on Changes\ Test Mapping Management (New UI Only)\*\* #### Rollback Log – Org Name Display Fix Fixed an issue where the **Org Name** was displayed as `null` on the Rollback Log page after executing a CI Job with rollback enabled. The internal Org Name value was not populated during rollback execution, resulting in unclear log entries. Logging logic has been corrected to prevent null internal values from being displayed. Additionally, unnecessary fields (`constructiveChanges`, `destructiveChangesPre`, `destructiveChangesPost`, `destructiveChanges`) were removed from rollback logging to avoid misleading entries. **Impacted Areas (DEV)**\ Rollback Log Page **Functional Impact Areas (QA)**\ CI Rollback #### CI Job History – Pagination Missing for Sub-users Fixed an issue where **Sub-users** could not see pagination controls on the **CI Job History** page. As a result, only the first **25** job records were shown and users could not navigate to additional history entries. Sub-users can now view pagination (Next/Previous/page numbers) and access all available CI Job History records. #### Sync Branch – Unregister Button Visibility Fix Fixed a UI issue in the **Sync Branch** pop-up where the **Unregister** button was not visible when a large number of branches (100+) were listed. The modal did not provide scrolling, preventing users from accessing the action button. A scrollable container has now been added to the branch list to ensure proper responsiveness. The Unregister button remains accessible regardless of the number of branches displayed or screen resolution. **Impacted Areas (DEV)**\ Sync Branches Popup **Functional Impact Areas (QA)**\ Sync Branches Popup #### Report Deployment – Package Structure Fix- #193182 Fixed an issue where Report deployments were failing with the error:\ *“An object '\' of type Report was named in package.xml, but was not found in zipped directory.”* The failure occurred due to additional child folder entries being incorrectly added to the generated `package.xml` during deployment. Package-generation logic has been corrected to include only the required Report folders and Report components, preventing mismatches between the package.xml and the zipped directory. **Impacted Areas (DEV)**\ Deployments, CI Jobs (Org to Org, SCM Repo to Org), Commits including Reports **Functional Impact Areas (QA)**\ Org to Org Deployment\ CI – Salesforce to Salesforce Deployment\ Repo to Org Deployment #### ALM Integration (New UI) – Work Items Not Displaying - #198093 Fixed an issue where work items were not displayed in the **ALM Integration (New UI)** for certain projects and sprint selections. The issue occurred due to the request payload using the project/sprint key instead of the required ID, resulting in empty responses. The request handling has been updated to use the correct ID parameter, ensuring work items load properly for the selected project and sprint. **Impacted Areas (DEV)**\ EZ-Merge – ALM Integration **Functional Impact Areas (QA)**\ EZ-Merge – ALM Work Items (New UI)\*\* #### Pagination Count & Record Display Fix Fixed an issue where changing the pagination dropdown (e.g., 10 to 20 or 50 records) did not update the displayed results on the **CI Job History and Details** pages. The back-end logic has been corrected to properly apply the selected page size. Also resolved pagination count mismatches observed in the following modules: * Credential Page * Commit History * Branching Baseline * CI Job Details Pagination now correctly reflects the selected page size and displays accurate record counts across affected screens. **Impacted Areas (DEV)**\ CI Job Details Page **Functional Impact Areas (QA)**\ CI Job History and Related Modules #### Default Apex Test Cases – Success Message Added Fixed an issue where no confirmation message was shown after successfully downloading the **Default Apex Test Cases** file. A success toast notification is now displayed once the export action completes, providing clear confirmation to the user. **Impacted Areas (DEV)**\ Salesforce Org – Export (Default Apex Test Cases) **Functional Impact Areas (QA)**\ UI/UX Validation – Toast Notifications & Front-End Response Handling *** ## ARM Release Notes 26.1.7 **Release Date: 15 February 2026** #### Internal Cases #### Smart Commit Pattern & Webhook Selection Not Persisting Fixed an issue where the selected Smart Commit pattern and enabled Webhook settings under ALM Management were getting cleared after saving the Integration configuration. The issue was caused by null values overwriting existing records in the database during update operations. The update logic has been modified to prevent null fields from overriding saved configurations, ensuring selections are retained correctly. **Impacted Areas:** ALM Configuration Updation #### Default Branch Not Updated After Deletion via Sync Branches Fixed an issue where ARM did not automatically assign a new default branch after the existing default branch was deleted using the **Sync Branches** operation. When the default branch was removed, the system failed to promote the last-used branch as the new default. The logic has been enhanced to detect deletion of the default branch and automatically update the last-used branch as the new default. The implementation introduces a streamlined default-branch update flow (without unnecessary workspace creation) and consolidates common logic to avoid duplication. **Impacted Areas:**\ Branch Management (Sync Branches), Branch Creation, Registration, Deletion, and Updation #### Default Branch Not Reflected in UI After Sync (New UI) Fixed an issue in the New UI where, after deleting the current default branch via the **Sync Branches** operation, the updated default branch was not immediately reflected in the UI. The system required a full page refresh for the new default branch to appear correctly. The backend correctly promoted the next available branch as the default; however, the UI state was not refreshed automatically. The flow has been updated to call the repository details API after sync, ensuring the updated default branch is reflected instantly without requiring a manual refresh. **Impacted Areas:**\ Sync Branches in VC Repositories #### Time Zone Discrepancy in Default Date Range (New UI) Fixed an issue in the New UI where the default calendar date range was calculated using the system time zone instead of the time zone configured in the user’s profile. This resulted in incorrect date ranges and missing recent entries across history-related screens. The logic has been updated to apply the user-specific time zone when determining the default date range, aligning the New UI behavior with the Old UI. **Impacted Areas:**\ Default date range handling in CI Jobs, Deployments, Dashboards, and Analytics #### Repository Search Not Updating Branch Details Panel (New UI) Fixed an issue where searching for a repository on the **Repositories** screen filtered the list correctly but did not update the right-hand **Branches** detail panel. The previously selected repository’s branch data remained visible, and the newly searched repository could not be selected to load its details. The behavior has been corrected to reset the detail view after search and default to the first tab selection, ensuring that users can select a searched repository and immediately view the corresponding Branches data. **Impacted Areas:**\ Search functionality in VC Repositories #### Support Cases: **Support Case: #186557** #### Sandbox Mapping Failure in My Salesforce Orgs Fixed an issue where mapping a specific sandbox under **Profile → My Salesforce Orgs** resulted in an error, even after re-registering the sandbox. The issue was caused by a SOQL query length limit being exceeded (100,000 character limit) while retrieving Salesforce users for sandboxes with large user datasets. The logic in `getSfUsers` has been enhanced to partition large SOQL queries into manageable chunks, ensuring successful user retrieval and sandbox mapping without errors. **Impacted Areas:**\ Profile → My Salesforce Orgs (Sandbox User Mapping)\ Salesforce Integration – User Retrieval **Support Case: #174294** #### Reports with Subfolders Not Recognized in EZ Commit Fixed an issue where Reports containing subfolders were not retrieved in **EZ Commit** when uploading a `package.xml`, although the same worked correctly in the Deployment module. Enhanced metadata handling to correctly process members with subfolder paths ("/"), ensuring proper retrieval and commit of Report, Document, and EmailTemplate metadata in both DX and non-DX modes. **Impacted Areas:** EZ Commit (Report, Document, EmailTemplate metadata – DX & Non-DX) **Support Case: #186894** #### Workflow Deletion – Destructive Merge Validation Failure Fixed an issue where **Merge Validation** failed for revisions containing only destructive metadata (e.g., deleted Workflow components) when **Run Destructive = Enabled** and **Type = Post**. Previously, the system generated the destructive XML only if at least one non-destructive component was present. As a result, revisions with only destructive members produced an empty `package.xml`, causing validation failure. The logic has been updated to always process destructive components and generate the destructive XML package correctly, even when no non-destructive components are included. **Impacted Areas:** EZ-Merge (Pre-Validation) **Support Case: #189316** #### Incorrect Storage Display in Super Admin Workspace Management Fixed a UI issue where increasing workspace storage from the **Super Admin** account did not correctly update the displayed used and remaining storage values. The discrepancy was visible only in the Super Admin view, while registered user accounts displayed accurate values. The calculation logic for available storage has been corrected in the Super Admin → Workspace Management UI to ensure accurate storage metrics are shown. **Impacted Areas :** Super Admin → Workspace Management **Support Case: #177966** **CI Jobs – Parallel Processor Endpoint Handling** Enhanced Parallel Processor configuration to support scenarios where the target API does not accept the default `/version/parallelexec` suffix appended at runtime. A new internal flag (`AR_37880_PARALLEL_EXEC_ENDPOINT_IGNORE_LAST_SEGMENT`) allows trimming of the auto-appended version and `parallelexec` segments, enabling compatibility with custom API endpoint structures. **Impacted Areas:** CI Jobs – Parallel Processor *** ## ARM Release Notes 26.1.6 **Release Date: 08 February 2026** \ **Support Ticket: #186267** **Reports – Code Coverage** Fixed an issue where recent Salesforce Tooling API changes could result in inconsistent code coverage data, leading to failures during Code Coverage report generation. The SOQL query used to retrieve coverage data has been updated, and additional validations have been added before processing the queried data to prevent unexpected errors and ensure reports run reliably. **Impacted Areas:** Reports – Code Coverage **Support Ticket: #187473** **CI Job History** Fixed an issue where changing the page size after applying a group filter could display CI jobs unrelated to the selected group. The filtering logic has been improved to ensure group and other applied filters are retained correctly when the page size is changed, providing consistent and accurate CI job history results. **Impacted Areas:** CI Job Results, CI Job History Page *** ## DataLoader Pro Release Notes 26.1.6 **Release Date:** **08 February 2026** #### Improved Filtered Data Migration Resolved an issue where data migrations could fail when filters were applied to master objects. The system now ensures that all required related records are included automatically, preventing migration failures due to missing references. #### Selective Deployment – Improved Log Visibility Fixed an issue where data retrieval logs were not visible during selective deployments. Logs are now displayed correctly and only when applicable, providing clearer visibility into deployment progress. *** ## ARM Release Notes 26.1.5 **Release Date: 01 February 2026** **Refreshed UI** \ \ The refreshed ARM UI is now available to all customers on shared instances. Customers on shared instances can access the refreshed UI immediately and switch between the existing UI and the refreshed UI at any time using the in-app toggle. Switching does not impact configuration, data, or any in-progress work. For customers on dedicated instances, the refreshed UI can be enabled on request. Please contact AutoRABIT Support or your Customer Success Manager to schedule the upgrade.\ \ **Support Case: #182599** **CI Job Not Updating Branch After Multiple Builds** Fixed an issue where CI jobs continued to run successfully but stopped updating the target branch after multiple builds. The backend logic has been updated to correctly detect metadata changes and commit them to the branch, ensuring the repository stays in sync with the latest successful CI job execution. This fix applies to CI jobs regardless of whether **“Check-out with user credentials and commit changes with the actual modified user credentials”** is enabled or disabled. **Impacted Area:** Version Control → CI Jobs **Support Case: #184383** **Admin Visibility of DevHub-Enabled Salesforce Orgs** Fixed an issue where Salesforce orgs registered with **DevHub enabled** were visible in **Admin → Salesforce Org Management** but not shown under **My Profile → My Salesforce Orgs** for other Admin users. Backend logic has been corrected to ensure that any org present in Salesforce Org Management is also visible in My Salesforce Orgs for **all Admin users**, regardless of DevHub configuration. **Impacted Area:**\ Admin → Salesforce Org Management\ Profile → My Salesforce Orgs *** ## ARM Release Notes 26.1.4 **Release Date: 25 January 2026**\ \ **Refreshed UI – Phase 2 – Europe / Canada / Middle East Region**\ The refreshed ARM UI is now available to customers in the APAC region as part of a phased, region-based rollout. This update refreshes the UI layout only, with no changes to functionality or core workflows. Some UI elements have been repositioned to improve usability and consistency. Customers can switch between the existing UI and the refreshed UI at any time using the provided toggle. No configuration, data, or in-progress work is lost when switching between experiences. Availability will expand to additional regions in upcoming releases.\ \ **Support Case: 160127 :** Pagination added for Single Revision deployments\ The Single Revision deployment page could become unresponsive when handling a large number of revisions on a branch. Pagination has been introduced in the UI to efficiently manage large revision lists and prevent page freezes during deployments across CI Jobs and Deployments modules.\ \ **Support Case: 177903:** EZ-Merge reverse sync conflict resolution loop\ When performing a reverse sync using Entire Branch EZ-Merge with the conflict resolution strategy set to Source changes, AutoRABIT continued to prompt for manual conflict resolution and surfaced new conflicts repeatedly. This issue has been fixed to ensure conflicts are automatically resolved using source branch changes as expected, allowing the operation to complete successfully.\ \ **Support Case: 180026:** CI Job deployment fails with “no local changes to deploy”\ CI Jobs were unable to correctly determine whether a Matching Rule was installed or org-created because the NamespacePrefix was not being evaluated. The CI Jobs module has been updated to check NamespacePrefix and apply the same installed versus unmanaged filtering logic used in the Deployments module.\ \ **Support Case: 173748:** Branching Baseline status mismatch between UI and backend\ In Branching Baseline, the UI logs showed the process as completed while the backend status was failed, leading to confusing and unclear logs. This has been fixed to correctly surface backend failures in the UI and display clear error information. *** ## DataLoader Pro Release Notes 26.1.4 **Release Date:** **25 January 2026** #### DataLoader Pro – FeedItem & ContentDocumentLink Status Handling Improved DataLoader Pro job execution for Account migrations by correctly handling field mappings for objects processed via **Bulk API v1**, ensuring accurate status reporting for related objects such as **FeedItem** and **ContentDocumentLink**. #### DataLoader Pro – Parent Record Handling with Filters Enhanced DataLoader Pro data retrieval logic to ensure that when filters are applied, **all related parent records (including self-referenced and multi-level parents)** are automatically identified and migrated up to the top level, preventing partial data migration when filters are used. #### DataLoader Pro – Batch Size Handling for Screen Section Objects Fixed an issue where DataLoader Pro jobs completed with a “No Records” status when a batch size was specified for Screen Section objects by improving handling of recursive processing scenarios. *** ## DataLoader Release Notes 26.1.4 **Release Date:** **25 January 2026** #### DataLoader Extract – Limit Not Applied Fixed an issue where the **Limit** specified in the Extract Job configuration pop-up was not being honored during execution, causing all records to be extracted instead of the defined subset. #### DataLoader – Insert Operation Stability Fixed an issue where DataLoader insert jobs failed without producing success or error records by handling duplicate column generation during CSV preparation for lookup-mapped fields. *** ## ARM Release Notes 26.1.3 **Release Date: 18 January 2026** **Refreshed UI – APAC only**\ The refreshed ARM UI is now available to customers in the APAC region as part of a phased, region-based rollout. This update refreshes the UI layout only, with no changes to functionality or core workflows. Some UI elements have been repositioned to improve usability and consistency. Customers can switch between the existing UI and the refreshed UI at any time using the provided toggle. No configuration, data, or in-progress work is lost when switching between experiences. Availability will expand to additional regions in upcoming releases.\ \ \ **Support Case #178052 – Unable to View Compare Changes**\ Fixed an issue in **EZ-Commit** where users could not view **Compare Changes** on the review page during diff generation, resulting in an error. A new backend API now clears any stuck *live status* key from in-memory storage, preventing failures in the compare/diff flow. **Impacted Area:** Version Control → EZ-Commit (Review → Compare Changes / Diff Generation) **Support Case #175864 – Skip Org Mappings Missing During Role Creation**\ Fixed an issue where the **Skip Org Mappings** option was not visible during role creation or editing, even when it was expected to be configurable. The visibility condition has been corrected to ensure the option is displayed appropriately based on configuration and not incorrectly hidden at the org level. **Impacted Area:** Admin → Roles (Create / Edit Roles) **Internal Case – Workspace Limit Error During Pre-validation Commit**\ Fixed an issue where **Pre-validation commits** in the ARM–SIT integration branch failed during the **Delta** step due to a workspace limit error. Backend logic has been updated to avoid unnecessary workspace creation, allowing the pre-validation commit to complete successfully. **Impacted Areas:** * Version Control → EZ-Commits * Version Control → Merges *** ## DataLoader Pro Release Notes 26.1.3 **Release Date**: **18 January 2026** #### **DataLoader - Validation and Workflow Rules Visibility Fix** Resolved an issue where **Validation Rules and Workflow Rules** were not displayed in the Data Loader job pop-up when disabled during Insert, Update, or Upsert operations. #### **DataLoader - Test Environment Dropdown Fix** Fixed an issue where the **“All Groups”** dropdown remained disabled after creating a Data Loader job in the Test environment and required a manual page refresh. The dropdown is now enabled immediately, improving usability. #### **DataLoader Pro - Custom Mapping Fix** Resolved an issue where **Data Loader Pro jobs** failed when custom object mappings were selected. The issue has been fixed to ensure successful job execution with custom mappings. #### DataLoader Pro - **Group Job Clone Filter Restoration Fix** Resolved an issue where **object filters were not restored when cloning group jobs** in Data Loader Pro. Filters are now correctly retained and displayed after cloning. #### **DataLoader Pro - Upsert Fix for Knowledge Objects** Resolved an issue where **Data Loader Pro upsert jobs** processed zero records despite valid source data being present. The issue was fixed by correctly handling **external ID fields for Knowledge (KAV) objects**. #### **DataLoader Pro - Skip Object Selection UI Fix** Resolved an issue where the **Skip** checkbox was not reflected in the UI after an ancestor object was skipped. The selection state is now correctly saved and displayed. *** ## ARM Release Notes 26.1.2 **Release Date: 11 January 2026** **Internal Case**\ An issue where adding a user to a team completed user creation but returned an API 404 error has been resolved. The user creation process now completes successfully without errors. *Impacted Area:*\ Admin → Subscriptions → Team User Management **Support Case: #173910** Single Revision Merge now validates that the selected revision belongs to the chosen source branch. If a revision from a different branch is entered, the merge is blocked with a clear validation message. *Impacted Area:*\ Version Control → EZ-Merge (Single Revision) *** ## ARM Release Notes 26.1.1 **Release Date: 4 January 2026** **Support Case: #160652** **Improved handling of Record Type picklist values in CI delta jobs:** CI jobs now more accurately process Record Type changes when delta is enabled. If picklist values are added or removed, only the actual differences are included in the build as expected. If a Record Type change does not involve picklist values (for example, updating only the description), the generated build file excludes picklist value tags. This prevents unintended dependency issues and ensures existing picklist values in the target org are not accidentally overwritten during deployment. Impacted Areas: Commits, CI job and Deployments. **Support Case: #173939** **Improved commit stability during concurrent approvals:** Commits no longer fail when reviewers approve multiple commits at the same time. The commit processing logic has been updated to correctly handle queued commits, preventing unnecessary failures and eliminating the need for developers to recommit their changes when approvals occur concurrently. Impacted Areas: Commits **Support Case: #174471** **Fixed deployment failures when using “Ignore missing visibility settings”:** Deployments using the *Ignore missing visibility settings* option now work correctly for single-revision delta deployments. An issue where Profile metadata was not fully packaged—resulting in truncated files and deployment failures—has been resolved by improving the file copying mechanism used during deployment processing. This ensures Profile metadata is included correctly and deployments behave consistently with CI jobs. Impacted Areas: Deployments *** ## ARM Release Notes 25.4.13 **Release Date: 28 December 2025** **Support Case: #150240** Resolved an issue where the Delta step was incorrectly marked as failed during commits despite successful completion. The fix improves delta handling for new repositories across Custom API and Non-Custom API (JGit) flows, impacting EZ-Commit, Merge, Release Label, Deployment, and CI Jobs. **Support Case: #165779** Fixed an issue where the validation deployment report was not visible for a failed CI job build due to a missing deployment Async ID. The backend logic has been updated to handle such exceptions gracefully, ensuring deployment reports are displayed correctly in CI Job deployment reports **Support Case: #161304** Resolved an issue where CI jobs did not detect picklist value name changes even when *Include Picklist Modifications* was enabled. Backend logic has been updated to correctly track picklist value changes based on manageable states, ensuring CI jobs now pick up these updates reliabl**y.**\ \ **Support Case: #161295** Fixed an issue where scheduled CI jobs for rebasing hotfix and pre-prod branches consistently failed due to a null pointer exception. The update improves CI job stability by correctly handling backup-to-VC flows with auto-switch to bulk retrieve service when metadata governor limits are hit, including support for Custom Objects and Custom Fields. *** ## ARM Release Notes 25.4.12 **Release Date: 21 December 2025** **User Story: Commit Retrieval Issue** We’ve introduced a new **feature flag** that allows customers to continue using the **legacy “Select Manually” behavior** in EZ Commit. When this feature is enabled, selecting **“Select Manually”** will retrieve **all detected changes across all authors**, regardless of the author selected in the user interface. This helps support existing workflows that depend on the earlier behavior for managing metadata dependencies. If the feature is not enabled, EZ Commit will continue to behave as it does today, retrieving changes only for the selected author. **Support Case: #172610** Subject: EZ Commit – Package Manifest Selection Fix We fixed an issue where component selections made using **“Select All”** in the Package Manifest flow were reset when navigating between pages. Selections now persist correctly across all pages, improving bulk commits for larger packages in both **Autodraft** and **Package Manifest** workflows. **Support Case: #169831** Subject: Deployment Logs Display Restored After Quick Deploy We fixed an issue introduced after the instance upgrade where **deployment logs were not visible in the UI** following a **Quick Deploy**. Customers can now view both **validation and deployment logs** as expected, restoring full visibility into deployment activity. **Support Case: #169858** Vlocity Component Selection Warning Fixed We fixed an issue where a misleading warning message, **“Please select at least one metadata type or member,”** was shown during Vlocity component deployments after users selected all members of a metadata type and then deselected a few. The selection logic has been improved to correctly reflect user choices and prevent this unnecessary warning. *** ## ARM Release Notes 25.4.11 **Release Date: 14 December 2025** **Internal Ticket:** **Fix for Duplicate Deployment Logs in Org Sync History:**\ Resolved an issue where performing actions like *Add to Destination Org* or *Delete from Destination Org* followed by *Synchronize Orgs* with **Validate Deploy** enabled resulted in duplicate deployment logs for the same label. The system now correctly generates a single log per deployment. **Internal Ticket:** **Fix for Team Name Validation and Warning Message:**\ Addressed an issue where an empty warning message appeared and the feature did not work in both the old and new UI. Validation has been enhanced to ensure team names cannot contain spaces, and the warning message now displays correctly. **Internal Ticket:** **Fix for Merge Criteria Validation in Merge Settings**\ Resolved an issue where merge settings could be saved even when no merge criteria options were selected. The system now correctly prevents saving unless at least one option is chosen when merge criteria are enabled, ensuring proper validation. \ **Support Ticket: #161454** **Fix for Field Persistence Issues When Editing CI Jobs:**\ Resolved an issue where editing a CI Job with a configured Parallel Processor caused certain fields to clear unexpectedly and triggered validation errors. Additionally, updating the Baseline Revision previously cleared the Package Directory. The **Client ID**, **Client Secret**, and **Access Token URL** fields now persist correctly, and the editing workflow functions as expected. \ **Support Ticket: #158630** **Fix for Incorrect File Count and Missing Metadata in EZ Commit Code Scan**\ Addressed an issue where EZ Commit using **“Only Newly Added Supported Metadata Types”** produced inaccurate scan results. Some metadata types—such as Custom Fields and Permission Sets—were not included in the static code analysis, and the SCA logs always reported **“Total number of files identified for static analysis: 1”** regardless of the actual count. The logic has been updated to correctly include Custom Fields and Permission Sets during analysis and to display an accurate file count in the logs. *** ## ARM Release Notes 25.4.10 **Release Date: 7 December 2025** * Resolved an issue where the **IgnoreWarnings** flag from the UI was not passed correctly, causing prevalidation to fail on warnings even when the checkbox was selected. Updated the UI request mapping so the correct value is stored and processed by the backend.\ Support Case: #160228 * The issue preventing users from selecting the **Release Label** and other options in the **Change Label** module under VC has been resolved by updating the routing mechanism to `router.go`, restoring proper navigation from both the left menu and top bar.\ Support Case: #172715 *** ## ARM Release Notes 25.4.9 **Release Date: 30 November 2025**
* Fixed an issue where scheduled jobs could not be deleted through Environment Provisioning. The system now correctly validates permissions and job eligibility, enabling successful scheduled job removals from target environments.\ Support Case: #159287 * A performance optimization was implemented to improve how UserVersionControl details are retrieved. Instead of fetching data individually for each user, the system now retrieves the required information in a single bulk operation and processes it efficiently. This significantly reduces load time and restores a responsive user experience in EZ-Merge.\ Support Case: #158633 *** ## ARM Release Notes 25.4.8 **Release Date: 23 November 2025**
* EZ-Merge report timestamps now adjust accurately to each user’s time-zone settings, ensuring Merge Submission, L1 Review, and L2 Review dates display consistently across regions.\ Support Case: #156046 * CI Job validation behavior has been streamlined so that the Build Now option becomes available in the UI whenever the job’s deploy and overall status reach a completed state, providing a more consistent experience.\ Support Case: #158357 * Backup-to-VC jobs now present the appropriate Git message during push scenarios, such as permission or hook restrictions, while clearly indicating “No modifications” only when no updates are present—offering more accurate visibility into job outcomes.\ Support Case: #159296 * Delta commit results now reflect completion accurately, ensuring that the commit status aligns with the actual execution of the delta operation.\ Support Case: #150240 *** ## ARM Release Notes 25.4.7 **Release Date: 16 November 2025**\ \ **Highlights**: Improved downstream CI chaining, expanded Agentforce support, optimized EZ-Commit performance, and key platform upgrades. \ **Downstream CI job chaining enhancement**\ AutoRABIT now allows downstream CI jobs to trigger even when a parent job completes without identifying artifacts during the delta build process. This removes unnecessary pipeline breaks, eliminates manual intervention, and ensures uninterrupted job chaining, especially for Vlocity and other metadata patterns where no-change builds are common. (This would be available basis only on feature flag).\ \ **Expanded Agentforce metadata support**\ ARM now supports a wider set of Agentforce metadata types across CI, Deployments, and Version Control flows. | **Agentforce Metadata Type** | **Supported** | | ---------------------------------------------------- | ------------- | | GenAiPromptTemplate | Yes | | GenAiPromptTemplateActv | Yes | | GenAiPlugin | Yes | | GenAiFunction | Yes | | GenAiPlanner (API 60 to 63) | Yes | | ​GenAiPlannerBundle (API 64 and Above) | Yes | | Bot | Yes | | BotVersion | Yes | | Custom Apex invoked by agents (ApexClass) | Yes | | Flows used by agents (Flow) | Yes | | Permission Sets assigned to the Agent User | Yes | | CustomSite | Yes | | Network | Yes | | DigitalExperienceBundle | Yes | | EmbeddedServiceConfig | Yes | | MessagingChannel | Yes | | Flow (specifically the Omnichannel flow for routing) | Yes | | Queue | Yes | | QueueRoutingConfig | Yes | \ **Rollback failure fix for DX CI Jobs involving consecutive RecordTypes and StandardValueSets**\ A rollback issue caused DX CI Jobs to fail when only RecordTypes and StandardValueSets were selected but CustomLabels were excluded, resulting in a “not found in package.xml” error. The rollback logic has been updated to respect user-selected members, ensuring successful rollback operations even when other components are omitted. Destructive rollback continues to exclude RecordTypes due to Salesforce API limitations.\ (Support Case: 155931) **EZ-Commit in-flight fetch optimization**\ Introduced an in-flight check to prevent repeated fetch calls during EZ-Commit table data loading. The update adds a fetch-state tracker, improves the loading indicator, stabilizes table rendering to occur only after a successful fetch, and resets state cleanly on errors resulting in faster UI responsiveness and reduced redundant API calls.\ (Support Case: 155994) **Tomcat upgrade to version 11.0.13**\ ARM’s application runtime has been upgraded to Tomcat 11.0.13, delivering improved security, better performance, and alignment with the latest Java ecosystem standards.\ (Support Case: 158573) *** ## ARM Release notes 25.4.6 **Release Date: 9 November 2025**\ \ **Highlights** Salesforce is deprecating the **username + password + security token** method for SOAP API integrations. To ensure compatibility with **API version 65**, ARM now supports **OAuth (JWT) authentication**. This release also includes: * Support for **Salesforce Metadata API v65** * A new **CodeScan Configuration Wizard** for simplified setup * Enhanced audit visibility with **CEF login logs** * Fix for **CaseTeamRole** handling of multi-word names in environment templates **Limitation:** OAuth (JWT) is currently supported only for **Salesforce Dev Hub**. Regular Salesforce orgs continue to use **OAuth 2.0 Web Server Flow**. Other authentication methods are not supported in this release.\ \ **Salesforce SOAP Login Deprecation Notice**\ Salesforce has deprecated the “username + password + security token” authentication method for integrations using the SOAP API starting with version 65. This legacy method will be completely disabled by Summer ’27 for API versions 31–64. Customers using this method in AutoRABIT connections (e.g., {{ConnectionName}}) must migrate to OAuth authentication to ensure uninterrupted connectivity. \ **Salesforce Metadata API Version 65 Support**\ ARM now supports Salesforce Metadata API version 65, ensuring full compatibility with the latest metadata structures introduced by Salesforce. As part of this release, ARM has validated several metadata types across both DX and Non-DX environments, enabling consistent retrieval, validation, deployment, and CI/CD operations. | Metadata Type | Supported | Verified | | ------------------------ | --------- | -------- | | LightningOutApp | Yes | Yes | | InvocableActionExtension | Yes | Yes | | PresenceDeclineReason | Yes | Yes | | PresenceUserConfig | Yes | Yes | | QueueRoutingConfig | Yes | Yes | | DuplicateRule | Yes | Yes | | AnalyticsVisualization | Yes | No | | SrvcMgmtObjCollabAppCnfg | Yes | No | | DgtAssetMgmtProvider | Yes | No | | DgtAssetMgmtPrvdLghtCpnt | Yes | No | **CodeScan Configuration Wizard for Repository and Org Mapping**\ Introduced a guided configuration wizard for CodeScan integration to simplify project and branch mappings across ARM repositories and Salesforce orgs. The system now intelligently pre-matches existing CodeScan projects and branches, allows users to persist mappings, and ensures consistent baseline comparisons across Commit, Merge, CI Jobs, Custom Deployment, and SCA modules. This minimizes redundant project creation and improves scan relevance.\ \ **CEF Logger Added for Login Events**\ ARM now logs both successful and failed user login attempts through the Common Event Format (CEF) logger, improving traceability and compliance visibility for system administrators.\ (Support Case: 156220) **Environment Provisioning Template – Multi-Word Case Team Role Names**\ ARM now handles the creation and execution of environment provisioning templates containing multi-word CaseTeamRole names (e.g., “VMI Specialist”, “Supply Chain Finance”). The template execution correctly supports full role names and ensures accurate reflection in the target Salesforce org.\ (Support Case: 154640, 152188) *** ## ARM Release Notes 25.4.5 **Release Date: 2 November 2025**\ \ **Highlights:** Improved validation visibility, enhanced deployment reliability, and Data Cloud DevOps support introduced. ### Enhancements **Data Cloud DevOps Support**\ Introduced full support for Salesforce Data Cloud metadata deployment using DevOps Data Kits. Users can now commit, validate, and deploy Data Cloud components such as Data Streams, Data Model Objects, Calculated Insights, and Data Packages through EZ-Commit, Deployments, and CI Jobs. Key highlights include: * Deployment support for **DataPackageKitDefinition**, **DataSourceBundleDefinition**, **DataStreamTemplate**, and **DataKitObjectDependency**. * Strict separation between Data Cloud and standard Salesforce metadata for packaging. * Prerequisite checks for permissions and Data Cloud-specific access. * Recommended DX repository usage and manifest-based commit flow for Package.xml-dependent metadata. * Support for both constructive and destructive changes across DX and non-DX repositories. * Validated Merge, Release Label, and Branching Baseline flows for all Data Cloud metadata types.\ \ *Learn more* [*https://knowledgebase.autorabit.com/product-guides/arm/salesforce-extensions/arm-for-salesforce-data-cloud*](https://knowledgebase.autorabit.com/product-guides/arm/salesforce-extensions/arm-for-salesforce-data-cloud) ### Bugs **Partial FlexiPage Commit Handling**\ Fixed an issue where FlexiPage metadata was partially committed during Prevalidation Commits, resulting in missing content during CI Job deployment. Added schema validation checks to ensure full FlexiPage integrity and introduced detailed logging for file uploads on the Review Artifact screen.\ (Support Case: 155665) **App Deployment Failure in Profile Manager**\ Addressed a “Malformed request detected” error encountered during “Apps” deployment using the Profile Manager process. Deployments now complete successfully, and changes are accurately reflected in the target Salesforce org.\ (Internal) **Validation Circle Color Accuracy During Code Coverage Failure**\ Resolved an issue in EZ-Commit where both validation circles appeared green even when Salesforce validation failed due to insufficient code coverage. The circles now correctly turn red when code coverage fails, ensuring accurate validation feedback.\ (Support Case: 154962)\ \ **Caching Issue in EZ-Commit AutoDraft Flow**\ In version 25.4.4, a cache-related issue caused errors when expanding metadata components in the AutoDraft step of the EZ-Commit flow. Users encountered the message “Cannot invoke 'java.lang.Comparable.compareTo(Object)' because 'k1' is null.”This issue has been resolved in the current release. Metadata components now expand and display their contents correctly without any errors. *** ## ARM **Release Notes 25.4.4** **Release Date: 26 October 2025**\ \ **Highlights**: Improvements in EZ-Commit author handling, EZ-Merge responsiveness, and CI Job error reporting. * **EZ-Commit Author-Specific Retrieval**\ Resolved an issue where EZ-Commit was not correctly filtering metadata changes by the selected Salesforce Org Author. The process now accurately fetches only Author-related changes when a specific Author is chosen in both “Select Manually” and “Re-Use Previously Validated Commit Labels” modes.\ (Support Case: 151097) * **EZ-Merge Screen Freeze After Target Branch Selection**\ Fixed a delay where the EZ-Merge screen froze for 14–17 seconds after selecting the target branch (“To” branch). The merge approver validation API (`/mergerevieweremail`) has been optimized with asynchronous handling to improve responsiveness during branch selection.\ (Support Case: 155279) * **CI Job Failure with No Error Displayed**\ Addressed an issue where CI Jobs failed silently when component names contained dots and were misclassified under different component types (e.g., Profiles) in DX environments. The fix ensures accurate component handling and consistent error reporting for both DX and Non-DX CI Jobs initiated from Version Control to Deploy Org.\ (Support Case: 155649) *** ## ARM **Release Notes 25.4.3** **Release Date**: **19 October 2025**\ \ **Highlights**: Enhancements to metadata handling for destructive commits, standard value set retrieval, CI Job status accuracy, and Quick Deploy validation behavior. * **UserAccessPolicy Deletion in Destructive Commits**\ Destructive commits containing the 'useraccesspolicy' metadata type failed during execution. The metadata type has now been added to the SfdxMetadataFolder to ensure it is recognized for deletion.\ (Support Case: 153113) * **ContactPointUsageType Standard Value Set Retrieval**\ ARM was unable to retrieve the "ContactPointUsageType" standard value set, which is associated with the "Contact Point Email" object. Since standard value sets cannot be fetched using describe calls, the metadata was added to the internal static list to ensure successful retrieval.\ (Support Case: 154150) * **Quick Deploy Criteria Validation for PR-Triggered CI Jobs**\ Quick Deploy was unavailable after a successful Pull Request–triggered validation due to incorrect variable binding of the "preventDeploy" setting. The logic has been corrected, ensuring Quick Deploy remains unavailable when "Prevent Deployment" is selected under "Validate Deployment," matching expected behavior.\ (Support Case: 153792) * **ManagedContentType Destructive Commit Failure**\ Destructive commits for MANAGEDCONTENTTYPE metadata were failing due to unrecognized metadata classification. This metadata type has now been added to the SfdxMetadataFolder, ensuring it is properly recognized and deletable.\ (Support Case: 154888) * **CI Job Status Stuck in Progress After Completion**\ Some CI Jobs continued showing as “In Progress” even after build and validation completion, blocking new runs on the same target org. A blocking wait mechanism was implemented to continuously check CIJobInfo until the deploy status updates to “Completed.”\ (Support Case: 154818) *** ## ARM Release Notes 25.4.2 **Release Date**: **15 October 2025**\ \ **Highlights**: Stability improvements across CI Jobs, Commit handling, and Scratch Org creation. * **CI Job Email Notifications – Missing Error Details**\ Fixed an issue where CI job email reports did not display deployment failure details for Apex Classes. The notification logic now correctly includes all error and failed test details in the email report.\ (Support Case: 154005) * **Backup CI Jobs – Git Push Pre-Receive Hook Error**\ Addressed a problem causing Backup CI Jobs to fail with the error “GIT Push remote update Result: pre-receive hook declined.” The exception is now taken care and the UI displays a simplified message: “No modifications exist.”\ (Support Case: 154837) * **EZ-Commit Validation – File Copy Failure**\ Resolved a FileNotFoundException that occurred during EZ-Commit validation when a metadata file was missing from the source folder. The updated logic now skips missing files and continues copying remaining files, allowing the commit process to complete successfully.\ (Support Case: 154753) * **Scratch Org Creation – Salesforce Org Validation**\ Resolved an issue where users received a “Salesforce Org Doesn’t Exist” error while attempting to retrieve data for Scratch Org creation. The system now correctly validates the selected Salesforce org and proceeds with successful data retrieval. *** ## ARM Release Notes 25.4.1 **Release Date**: **5 October 2025**\ \ **Highlights:** Fixes for Quick Deploy iteration visibility, CI post-deploy log accuracy with DataLoader Pro, and complete Jira sprint retrieval across ALM flows. * **Quick Deploy iteration visibility**\ A validated deployment could be quick-deployed from a later iteration while the Quick Deploy button remained visible and usable on earlier iterations, which diverged from Salesforce behavior; this affected deployment iteration handling in the Deployments UI. Quick Deploy is now correctly disabled for the current iteration and all previous iterations once an actual deployment is performed, matching Salesforce semantics and preventing accidental re-deploys of validated iterations.\ (Support Case: 150463) * **CI job post-deploy logs and DataLoader Pro status accuracy**\ CI jobs that triggered a post-deploy DataLoader Pro process sometimes showed a null error or incorrect "not yet run" status in post-activity logs even though the DataLoader Pro job executed and made changes in the org. We handled the null pointer and corrected status mapping between the DL module and CI logs; CI jobs now complete without the null error and post-activity logs reflect accurate in-progress and final statuses. The system also ensures the DataLoader Pro job is triggered and its final status is shown correctly.\ (Support Case: 153953) * **Jira sprint pagination and ALM updates**\ Fetching sprints in new EZ-Commit, EZ-Merge, and CI Job flows was stopping after the first page because Jira API maxResults was 50, so not all sprints were returned. We now page through all results and surface every sprint across the UI, restoring full sprint visibility. Additionally, Jira ALM integration updates for status and comments have been improved so status updates and comments propagate correctly from ARM flows.\ (Support Case: 154690) *** ## ARM Release Notes 25.3.12 **Release Date**: **28 September 2025** * **Wavedashboard deployment failure due to xmd conversion**\ When customers uploaded a package.xml containing wavedashboard type and members, ARM converted them to wavexmd and the deployment failed because the wavexmd files were missing from the zip. Implemented backend logic to prune xmd metadata entries when corresponding xmd files are not retrieved from the source org, preventing missing-file deployment errors.\ (Support Case: 151073) * **Email approvals bypassing branch access**\ Users who had branch access removed could still approve merge requests via the merge validation email notification. Added an enforcement check for email-based approvals that validates destination branch permissions against the merge approval role; users without permission on the destination branch will no longer be shown as eligible approvers or be able to approve via email.\ (Support Case: 153126) * **Jira Work Items Not Retrieved from Sprints**\ Fixed an issue where customers were unable to select Jira work items during ALM flows in EZ-Commit and Merge, with the error “No work items found in this sprint.” Jira had deprecated the API (v2) used by ARM to fetch work items, causing sprint data retrieval failures.\ ARM now uses Jira API v3 for work item retrieval, restoring functionality across EZ-Commit, EZ-Merge, Merge Requests, and CI Jobs.\ *(Support Case: #150934 & #151385)* *** ## ARM Release Notes 25.3.11.1 **Release Date**: **24 September 2025** * **Jira Work Items Not Retrieved from Sprints**\ Fixed an issue where customers were unable to select Jira work items during ALM flows in EZ-Commit and Merge, with the error “No work items found in this sprint.” * Jira had deprecated the API (v2) used by ARM to fetch work items, causing sprint data retrieval failures. * ARM now uses Jira API v3 for work item retrieval, restoring functionality across EZ-Commit, EZ-Merge, Merge Requests, and CI Jobs.\ *(Support Case: #150934 & #151385)* *** ## ARM Release Notes 25.3.11 **Release Date**: **21 September 2025** **Highlights**: Fixes for EZ-Commit folder retrieval, branch registration, SCA validation, and webhook API token updates.
* **EZ-Commit – Report and Dashboard Folder Retrieval**\ Fixed an issue where report and dashboard folders were not being retrieved when using a package.xml. Now, folders and their members are correctly retrieved during EZ-Commit, covering scenarios for both DX and non-DX repos, with and without Autodraft.\ *(Support Case: 150181)* * **Branch Registration – Default Branch Change**\ Resolved an issue where the main default branch was unintentionally updated when registering a new branch for the first time. The default branch is now updated only if the current default branch does not exist in the remote repository.\ *(Support Case: 149845)* * **SCA Validation with Special Characters**\ Fixed an error where SCA analysis failed when branch names or paths contained "/" or special characters. The fix covers EZ-Commit, EZ-Merge (including Pre-validation and Release Label merges), CI Jobs (Package from Version Control), Deployment (Version Control & Release Label), and Report Module.\ *(Support Case: 152825)* * **Webhook API Token Status**\ Corrected an issue where the webhook API token’s last status always showed as "Never Accessed," even after being used in CI Job triggers. The last access status now updates correctly when tokens are used.\ *(Support Case: 153909)* *** ## ARM Release Notes 25.3.10.1 **Release Date:** **20 September 2025** * **SCA Validation with Special Characters**\ Fixed an error where SCA analysis failed when branch names or paths contained "/" or special characters. The fix covers EZ-Commit, EZ-Merge (including Pre-validation and Release Label merges), CI Jobs (Package from Version Control), Deployment (Version Control & Release Label), and Report Module.\ *(Support Case: 152825)* *** ## ARM Release Notes 25.3.10 **Release Date**: **14 September 2025** **Highlights**: Stability improvements across Custom Deployment, Release Labels, EZ-Commit, CI Jobs, and Salesforce ALM integration. ### Bug Fixes * **Custom Deployment – Full Profile Deployment Failure:** Fixed an issue where Full Profile Deployment using Version Control failed with a size limit error because the `.git` folder was unintentionally included in the build preparation. Now, hidden folders (starting with ".") are excluded from the build process. * **Custom Deployment – Deployment Fails with Ignore Installed Components:** Resolved an issue where deployments failed silently on the UI when the **Ignore Installed Components** option was selected. The deployment now completes as expected. * **Deployment Logs – UI Visibility Issue:** Customers reported deployment logs not consistently showing in the UI. While the root cause is still under review, additional logging has been added to capture scenarios when logs fail to display. * **Release Label – Deployment with Apex Meta Files:** Fixed an issue where Release Label deployments failed when changes existed only in the Apex `-meta.xml` file and not in the corresponding `.cls` file. Such changes are now correctly included in the manifest.\ *Communication*: For existing Release Labels, customers must re-run artifact preparation to apply this fix. New Release Labels will work as expected. * **EZ Commit – Pre-Validation Error:** Addressed a parsing error ("XML document structures must start and end within the same entity") that caused pre-validation EZ-Commits to fail. A new file copy library has been implemented to resolve this in **EZ-Commit (Validate Deploy)**, **CI Jobs**, and **Deployments**. * **Salesforce ALM Integration – Status Updates:** Fixed an issue where ALM work items failed to update if the **status field’s API name** differed from the picklist label. Updates now correctly use the API name for mapping. * **CI Jobs – Missing Debug Information in Failed Builds:** Fixed an issue where failed builds did not display detailed error logs. The UI now shows schema validation errors with file and line details, helping users quickly identify and resolve issues. * **File Upload Error in EZ-Merge Conflict Resolution**: Customers reported being unable to re-upload modified files after downloading the conflict resolution zip in EZ-Merge. The issue was caused by restrictive file size limits. \ Fix: Increased the maximum supported file upload size to 100MB, ensuring smoother conflict resolution workflows. *** ## ARM Release Notes 25.3.9 **Release Date**: **7 September 2025** ### Bug Fixes * **Revision Retrieval Error During Deployment:** Fixed an error where retrieving revisions with a single revision or while creating a release label caused runtime exceptions from Git. Updated logic now ensures stable fetch during revision retrieval. * **Intermittent Workspace Not Found Error in EZ-Merge:** Resolved an issue where merges intermittently failed with “Workspace not found with id….” Logic was updated to handle the scenario reliably. * **Sub-User Branch Visibility in Admin VC Repos:** Addressed a problem where sub-users couldn’t see newly created branches unless permissions were manually updated. Sub-user visibility is now automatically enabled when a new branch is created. * **CI Job Stuck Issue in Abort Functionality:** Fixed a corner case where a CI job could get stuck, preventing new builds from being triggered. The abort functionality has been refined to avoid such blocking scenarios. * **Deployment Trigger Date Accuracy:** The deployment date recorded in the Reports module and Audit Tab now reflects the exact trigger time instead of relying on package creation time. This ensures more accurate tracking for all new deployments. ### **Enhancements** * **Webhook Security Update**\ As part of our ongoing security improvements, webhook security has been strengthened in this release. * Support for old webhook URLs was retired earlier in ARM v23.1.15. * With this release, it is now **mandatory to use an API token** with all webhook endpoints. * This change ensures stronger protection and prevents unauthorized access to your integrations.\ . *** ## ARM Release Notes 25.3.8 **Release Date**: **31 August 2025** **Highlights**: Fixes and improvements across permission sets, profile comparison, reports accuracy, and SSO configuration. ### Bug Fixes * **Permission Set – Deleted Tags Displayed:** Resolved an issue where deleted tags appeared under Permission Sets when committing with ServicePresenceStatus. Support for ServicePresenceStatusAccess has been added to Permission Sets, and necessary code changes were made to ensure correct behavior.
* **Profile Compare – Custom Permissions Not Visible:** Fixed an issue where the Profile Compare feature in the Deployment module did not show custom permissions for orgs. Updated UI logic ensures that deltas for custom permissions now display correctly.
* **Reports – Discrepancy in Deployment Counts:** Addressed a mismatch where reports displayed an incorrect deployment count when using custom range filters. Deployment counts are now consistent with actual values.
* **SSO Configuration – Empty Metadata File:** Corrected an issue where downloading the AutoRABIT SSO Metadata XML returned an empty file. The file now downloads with the correct default content. *** ## ARM Release Notes 25.3.7 **Release Date: 24 August 2025** **Highlights:** Fixes to EZ-Commit translations, webhook API token status, and rollback iterations. ### Bug Fixes 1. **EZ Commit – Case Values Removed from CustomObjectTranslation:** Resolved an issue where case values were being removed from the CustomObjectTranslation file when performing multiple EZ-Commits under Japanese language. The problem was caused by unmarshalling and marshalling logic comparing values incorrectly. The comparison logic has been updated to rely on additional fields to properly support translations for different languages. 2. **Webhooks – API Token Last Access Not Updating:** Fixed an issue where webhook API tokens continued to display “Never Accessed” even after recent runs triggered by CI jobs. The back-end logic has been corrected to update and display the last access time accurately. 3. **Rollback – Iteration and Components Not Available After Revert:** Addressed an issue where rolling back a previously deployed iteration caused both the iteration and its components to disappear. A change event has been added to ensure iterations and components are available after a revert rollback. *** ## ARM Release Notes 25.3.6 **Release Date: 17 August 2025** **Highlights**: Stability improvements and fixes for CI Jobs and Admin functionalities. ### Bug Fixes * **CI Jobs – Baseline Revision Update Issue**: Resolved an issue where CI jobs were stuck and queued after a specific build. The problem was traced to a scenario where the baseline revision was not updating. The back end has been updated to address this case and additional logging has been added for better diagnostics.
* **Admin – Adding Released Users to Teams**: Fixed an issue where adding a delegated or released user to a team displayed a success message but did not actually add the user. The root cause was an error in fetching released user details. Logic has been corrected to ensure the released user is properly added to the team.
* **CI Jobs – Rollback Failure for Selective Components**: Addressed a rollback failure during CI job deployments when rolling back selective components, resulting in a “Not in Package.xml” error. Back-end logic has been updated to handle the workflow metadata type correctly. *** ## ARM Release Notes 25.3.5 **Release date: 10 August 2025** ### Bug Fixes * **Branching baseline now supports committing child metadata components for Sharing Rules, Workflow, and Managed Topics**: This enhancement ensures these metadata types are correctly captured and pushed to the remote repository, addressing gaps identified in earlier releases. *** ## ARM Release Notes 25.3.4 **Release Date: 3 August 2025**\ \ **Highlights**: Reliability and accuracy improvements across CI jobs, release labels, and EZ-Commit workflows. ### Bug Fixes * **CI job cleanup for Provar executions**: Unused test-result folders in Provar job paths were not deleted after runs, slowly consuming disk space. A cleanup mechanism now removes temporary directories and report data immediately after each job completes.
* **Destructive change detection in remote branches**: CI jobs missed destructive updates performed directly in GitHub, causing build failures. Backend logic has been corrected so that remote destructive changes are reliably detected and processed.
* **Release label revision count displayed inaccurately**: When modifying an existing release label, the UI showed an incorrect number of selected revisions. Increment logic has been fixed so the description now reflects the true revision count.
* **Static resources misidentified during destructive EZ-Commit**: Deleting one static resource while another with a similar name remained caused the diff view to include both files. Selection logic has been refined so only the intended destructive file is picked up, even when naming conventions overlap. *** ## ARM Release Notes 25.3.3 **Release Date: 27 July 2025** #### Enhancements * **New ALM Support**: ARM now links to the SaaS Tool Kit so EZ-Commit can update Salesforce ALM records automatically. After a simple one-time setup, developers select the User Story or Defect during an EZ-Commit, add notes or effort, and ARM pushes the commit details to Salesforce while advancing the record’s status from Unit Complete → Ready For SIT and SIT Complete → Ready For UAT—no manual edits needed. **Bug Fixes** * **QuickAction metadata deployments fail due to package.xml exclusion**: Fixed the package-preparation logic so QuickAction files are included, allowing validation and deployment to succeed.
* **Environment-provisioning flow errors not displayed**: Corrected run-time array handling so success and failure details are now shown when enabling flows via an environment-provisioning template. *** ## ARM Release Notes **25.3.2** **Release Date**: **20 July 2025**\ \ **Highlights**: UI fixes in conflict resolution, improved destructive change handling in DX/Non-DX, and artifact preparation reliability enhancements. ### Bug Fixes * **Merge Conflict Resolution – UI Handling:** Improved the reliability of conflict resolution in the Merge Conflict screen. Resolved a UI issue where repeated lines were unintentionally removed after resolving conflicts using "Block from Source/Destination", leading to incorrect merges.
* **Destructive Changes in Commit (Non-DX):** Enhanced support for Report, Dashboard, Document, and EmailTemplate components in the Deleted tab under EZ-Commit for Non-DX repositories. These were previously not triggering the proper validation and error messaging during component selection.
* **CI Job Deployment – Classic Manifest Support in DX:** Fixed a bug where CI Jobs using DX repositories and Classic Package Manifest settings only packaged destructive changes, ignoring constructive ones. Validations and deployments now correctly handle all combinations of destructive and constructive changes.
* **Release Label Creation – Git SSH Response Handling:** Addressed an issue where release label creation failed due to invalid credentials. The system now properly handles Git responses when fetching branches via SSH, ensuring artifact preparation continues smoothly. *** ## Release Notes 25.3.1 **Release Date: 13 July 2025** Highlights: Stability and accuracy improvements across EZ Commit, Branching Baseline, and CI Jobs. * **EZ Commit** – Deployment-validation reports older than 30 days were missing in EZ Commit. It's now available.
* **EZ Commit** – Malformed XML errors when committing permission-set files are resolved by refining the copy logic.
* **Branching Baseline** – UNKNOWN\_EXCEPTION errors during batch processing eliminated by removing the parent Workflow entry and explicitly adding the child Workflow metadata types (WorkflowTask, WorkflowFieldUpdate, WorkflowAlert, WorkflowFlowAutomation, WorkflowKnowledgePublish, WorkflowOutboundMessage, WorkflowRule, WorkflowSend) to metadatatypes.json.
* **CI Jobs** – Object-level permissions in permission sets were unintentionally wiped during CI Job deployments. Back-end logic now preserves object permissions while propagating FLS changes. *** ## ARM Release Notes 25.2.12 **Release Date**: **6 July 2025**\ \ **Highlights**: Key enhancements and fixes to CI jobs, VS Code integration, deployment modules, audit reports, and environment provisioning. #### Bug Fixes * **Audit Reports – Deployment Label & Metadata Fixes**\ Added the Deployment Label column in the Audit Reports section. Fixed issues with Invalid Date in the created/modified date columns and removed special characters from downloaded CSV headers.
* **Env Provisioning – Apex Test Level Execution Support**\ Improved the Enable/Disable Apex Trigger Migration Template by reintroducing the Test Level dropdown in the execution window. Now the execution status updates correctly based on test result outcomes.
* **CI Jobs – Sharing Rules Not Deployed**\ Resolved an issue where Sharing Rules were skipped during deployment when linked to custom objects from installed packages.
* **VS Code Plugin – File Diff Undefined Error**\ Fixed an undefined error in EZ Commit via VS Code when accessing file diffs post-commit. The file diff generation model is now available.
* **Destructive Changes – Entitlement Process Commit Fail**\ Addressed commit failures during the Entitlement Process, destructive changes by updating the logic for DX Repositories.
* **Deployment – Missing Permissions in Profile Deployments**\ Corrected permission deployment for profiles with “Ignore Missing Visibility” enabled. This included handling for PushTopic permissions.
* **Audit Reports – Triggered Date Incorrect**\ Fixed the mismatch in deployment-triggered date display under the Audit tab.
* **CI Jobs – Abort Doesn’t Terminate Background Process**\ Improved CI job abort handling to ensure background processes are completely stopped. Now, aborted jobs no longer get stuck, and subsequent jobs queue and execute as expected. *** ## ARM Release Notes 25.2.11 **Release Date: 29 June 2025** **Highlights**: Git Performance Optimization, Accurate CI Deployments, and Enhanced Reporting Visibility #### **Enhancements** * **Faster Git-Based Version Control Validations**\ We’ve improved how ARM validates Git branches and revisions.\ These checks are now performed directly on the **remote Git repository**, eliminating the need for local workspace setup.\ This significantly boosts performance and reduces processing time during operations. #### **Bug Fixes** * **Installed Components Now Properly Excluded in CI Jobs**\ The **“Ignore Installed Components”** option in CI jobs was previously not functioning as expected—installed components were still being deployed.\ This has been corrected. The selected option now effectively excludes these components from deployment.
* **Resolved Validation Error During Permission Set Commit**\ Users encountered commit validation errors when working with permission sets and specific metadata selections.\ We've refined commit logic to ensure permission set files are filtered correctly based on selected options.
* **Permissionset Deployments No Longer Drop Object Permissions**\ Deploying a new permission set with **“Ignore Missing Visibility”** enabled previously removed `DataStreamDefinition` object permissions.\ This issue is now resolved. Both `DataStream` and `DataStreamDefinition` object permissions are preserved regardless of the setting.
* **Deployment Reports Display Accurate Results for All Years**\ Reports for years like 2023 and 2024 were previously showing incorrect data due to a mismatch in attribute formatting.\ We’ve added compatibility for both older and newer report formats, ensuring accurate data display on the dashboard. *** ## ARM Release Notes 25.2.10 **Release date: 22 June 2025** ### **Overview** This release delivers targeted improvements to Vlocity deployments, CI job processing, sandbox provisioning, permission settings, and EZ-Commit behavior. Key internal issues have been resolved to enhance reliability, reduce metadata deployment anomalies, and streamline configuration workflows. #### **Internal – Vlocity Calculation Matrix Fix** **1. Issue: After a commit, comma-separated Calculation Matrix Components were not being correctly committed to the branch. Only the YAML file was pushed, and that too in an incorrect format.** **Fix:** Introduced logic to backup the Calculation Matrix member name, fetch the correct member, and update the YAML file accordingly. Now, the Calculation Matrix Components are committed as expected, supporting direct commits, commit labels, and release labels. * Vlocity Version Control Deployments (including release, commit label, and AutoRABIT build) now retrieve and deploy comma-separated Calculation Matrix Components accurately. * Vlocity Org-to-Org Deployments are verified and working correctly. * CI Jobs now correctly retrieve and deploy comma-separated Calculation Matrix Components from source to target Salesforce org. **Module:** Vlocity Commit, Deployments, and CI Jobs **2. Issue: Managed package components that were intended to be excluded were still being included during deployments.** **Fix:** Implemented proper filtering logic to ignore installed (managed) components during deployments and CI job executions, ensuring expected exclusion behavior. **Module:** CI Jobs and Deployments **3. Issue: During a sandbox refresh, the template failed because the Sandbox Access field was missing for the production. Salesforce updates now require explicit configuration of access levels during the refresh process.** **Fix:** Introduced a new Sandbox Access field to the environment provisioning template. Users can now define the appropriate access level, enabling complete control during sandbox refresh. **Module:** Environment Provisioning
**4. Issue: During an EZ-Commit, the Diff view did not correctly reflect profile permission changes (field/object permissions), despite being configured under My Account > Salesforce Settings.** **Fix:** Applied backend logic to ensure that global profile and permission set rules apply only to the configured profiles/permissions. The Diff screen now accurately displays modifications relevant to the EZ-Commit context. **Module:** EZ-Commit (Profile & Permission Set) **5. Issue: In the "Apply Global Profile / PermissionSets Settings" screen under My Account, unnecessary permission selections were displayed. This contradicted the help text stating that all field/object permissions would be universally set to true (grant) or false (revoke), making the checkbox list appear redundant.** **Fix:** Now, only explicitly granted or revoked object/field permissions are selected or deselected in the UI, making the configuration clearer and more accurate. **Module:** Admin → My Account → Profile / Permission Set Configuration **6. Issue: An internal CI Job history API call was failing. Customers were unable to retrieve data via Postman due to an invalid filter applied to the DB query.** **Fix:** Corrected the filter logic in the DB query that powers the API. The API is now functioning as expected and can return CI job history details without failure. **Module:** CI Job History API (Postman & DB Filter) *** ## ARM Release Notes 25.2.9 **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 Release Notes 25.2.8 **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 *** ## ARM 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 *** ## ARM 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 *** ## ARM 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. *** ## ARM 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 *** ## ARM 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 *** ## ARM 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 [Release Notes](https://knowledgebase.autorabit.com/release-notes/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.3-release-notes) 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 [Release Notes](https://knowledgebase.autorabit.com/overview/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.2-release-notes) 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. I*mpacted 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 [Release Notes](https://knowledgebase.autorabit.com/overview/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.0-release-notes) 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 ``, ``, and ``. 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: 1. **Deployment History Display**: * Vlocity deployments now appear correctly in the deployment history, ensuring users can track and review their deployments without issues. 2. **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. 1. **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." 2. **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: 1. **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. 2. **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. 1. **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 2. **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. 3. **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. 1. **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. 2. **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: 1. **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. 2. **Layout Fix**: The layout issue where five columns were displayed instead of six during profile comparisons has been addressed. 3. **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. 1. **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. 2. **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. 3. **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 1. In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability. 2. SOAP to REST services were upgraded. 3. Third-party libraries were upgraded. *** ## ARM Release Notes 24.1 **Release Date: June 2024** **Version 24.1 – Enhancements and Improvements** ### Enhancements 1. **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.
2. **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.
3. **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.
4. **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.
5. **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.
6. **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. 1. In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability. 2. SF CLI Version upgrade to 2.41.8 3. 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. 4. 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. 5. Upgrade of third-party libraries 6. 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. 7. 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 1. 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 2. 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 3. 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. 4. 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 5. 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** 1. 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 2. 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 3. 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 4. 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 5. 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. 6. 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 revision information were not displaying. 7. 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 8. 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 9. 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 10. 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 11. 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 12. 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 13. 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 14. 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 15. 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 16. 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. 17. 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** 1. 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 2. 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 3. 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. 4. A code fix was applied to the nCino module in version 24.1 related to a use-case error in which DataLoader Pro was not fetching the child object. Support ticket #116928 #### 10 July 2024 **ARM 24.1.4** 1. 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 2. 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 3. 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. 4. 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** 1. 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 2. 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. 3. 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. 4. 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. 5. 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. 6. 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 \[+]). 7. 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. 8. 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. 9. 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 10. 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 11. 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 12. 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. 13. 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 14. 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 15. 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 16. 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 17. 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 18. 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** 1. A data error reported in version 23.1 with the Version Control module that resulted in version control being deleted was resolved in both 23.1 and 24.1 through adding loggers. Support ticket #114503 2. A use-case error reported in version 23.1 with the Version Control module in which the user was unable to use an existing conflicted file, which resulted in reraising merge requests, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115084 3. A use-case error reported in version 23.1, which resulted in an issue with the Data Loader module in which the software was not inserting the correct record type, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #114076 4. A use-case error reported in version 23.1 with the nCino module in which rollbacks were only partially being completed was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115204 5. 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 6. 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 7. 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 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 2. 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 3. 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 4. 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. 5. 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. 6. 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. 7. 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 [nCino release 24.1](/release-notes/release-notes/ncino-release-notes/release-notes-24.1) 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 1. **Salesforce Spring (API 57.0) & Summer (API 58.0) Support**\ AutoRABIT supports the most recent API 57.0 & API 58.0 versions in this release to keep our product updated with Salesforce updates. The most recent API version is intended for customizing and developing tools to manage the metadata model. 2. **Exporting Selected User Details**\ Users with Admin access can now choose the fields they want to include while exporting users' details to a CSV file. While selecting the Export option, the list of available fields is displayed. Admins can select and deselect the required fields by clicking the corresponding checkbox. Some of the fields are selected by default for ease of use. Admins can always deselect these fields if they are not required. Thus, based on the teams with whom they will be shared, Admins can customize the fields in the list. 3. **More Info on CI Jobs and Info**\ Users are now able to view the CI Jobs they created in the CI Job List screen to date inside ARM. The list is displayed in chronological order with the most recent jobs listed at the top. 4. **'Created and Requested by' in Deployment UI**\ Users are now able to view the ‘Created by’ and ‘Triggered by’ fields in the Deployment home screen without scrolling through multiple screens for this info, enabling monitoring of the deployment’s real-time progress. [Read more](/product-guides/arm/arm-features/deployment) 5. **Self-Service Connected App Setup for Jira OAuth in ARM**\ We've introduced a self-service feature allowing users to set up Jira OAuth-connected apps in ARM autonomously. With guidance from our user manual's Connected App guide, users can effortlessly create and register their app credentials, eliminating the need for support team assistance. Users can quickly establish a robust connection by inputting the generated Client ID and Server Key into ARM's settings. 6. **Unified Admin Roles**\ We’re excited to introduce a streamlined and more efficient Admin experience. We’ve consolidated the roles of Super Admin and Registered Admin into a single empowered Admin role. This change means Admins now have a unified set of tools and permissions, streamlining tasks and creating a more user-friendly Admin experience. 7. **CI Jobs List and Results: Filter and Export Option**\ We've enhanced the platform with a user-friendly quick filter and export feature in response to user feedback. This functionality empowers administrators, release managers, and users to efficiently organize and analyze data by alphabet or date, facilitating faster insights and informed decision-making. 8. **Create Artifact: Release label more than 180 days**\ In the Create Artifact section, users can now generate a Release Label and have the flexibility to choose an extended timeframe of over 180 days for retrieving comprehensive commit history data. This enhancement offers users a broader historical perspective, facilitating more in-depth analysis and tracking of commits for their projects. 9. **Enhanced security and user experience. (NEW)**\ The new features focus on enhancing security and user experience. They include a single-user session control to prevent multiple active sessions under the same username, automatic logout for inactivity to bolster security, and support for multiple tabs or pages in the same browser, improving user productivity and maintaining the environment's integrity. ### Improvements This update has implemented significant performance upgrades to enhance the tool's efficiency and responsiveness. These enhancements encompass optimized queries and leverage new technologies, collectively resulting in a smoother, faster user experience. ### Changelogs #### 31 July 2024 **ARM 23.1.40** 1. A code fix was applied to the CI Jobs module of versions 23.1 and 24.1 related to a use-case error causing the CI Jobs History report to not generate. Support ticket #116943 #### 24 July 2024 **ARM 23.1.39** 1. A code fix was applied to the Version Control module in version 23.1 related to a use-case error in which the merge completion was taking too long. Support ticket #113102 2. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which an issue was occurring with the system administrator lite. Support ticket #117297 3. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to see the metadata through the single revision deployment. Support ticket #116919 4. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to deploy the Einstein Prediction builder. Support ticket #116909 5. A code fix was applied to the Admin module of versions 23.1 and 24.1 due to a use-case error with users losing access. Support ticket #111830 6. A code fix was applied to the Version Control module of versions 23.1 and 24.1 due to a use-case error requiring multiple revisions on an ALM work item. Support ticket #117810 7. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error with the new profile compare feature. Support ticket #117309 8. A code fix was applied to the Deployments module of version 23.1 due to a use-case error with 'add additional member' showing duplicates when expanding the toggle. Internal request. 9. A code fix was applied to the Version Control module of version 23.1 due to a use-case error with users getting an error for a commits tab external pull request using Bit bucket repo. Internal request. #### 17 July 2024 **ARM 23.1.38** 1. A code fix was applied to the nCino module in version 23.1 related to a use-case error in which Data Loader Pro was not fetching the child object. Support ticket #115313 #### 10 July 2024 **ARM 23.1.37** 1. A use-case error identified in version 23.1 required a code fix, which was applied in versions 23.1 and 24.1 to the Deployment and Version Control modules, to correct a scenario in an org-to-org full-profile deployment where it was not capturing package visibility and permissions. Support ticket #110760 2. A use-case error identified a code fix needed to the Reports module of version 23.1 to fix a product test class in which the weekly scheduled job failed. Support ticket #115654 3. A code fix was applied to versions 23.1 and 24.1 due to a use-case error identified in version 23.1 where commits were failing with a 'no credentials mapped' error in the Version Control module. Support ticket #116704 4. A code fix was applied to the Admin module in version 23.1 related to a use-case scenario that required additional support to create the ARM instance from scratch. Support ticket #117015 5. A code fix was applied to the Deployment module in version 23.1 due to a use-case error in which the user was unable to get the popup while deploying using package.xml as the source. Support ticket #116967 #### **3 & 7 July 2024** **ARM 23.1.36** 1. A use-case scenario identified an error in version 23.1 with metadata retrieval from the repository failing in the Deployment module, which was resolved in versions 23.1 and 24.1. Support ticket #115818 2. A code fix identified in version 23.1 was applied to correct a use-case error in the Version Control module of version 23.1 related to commit templates. Support tickets #116124, #116138 3. A code fix identified in version 23.1 by internal request ticket was applied to the Admin and CI jobs modules in versions 23.1 and 24.1 to upgrade v61 (Beta) to v61. 4. A use-case error in version 23.1 required a code fix to version 23.1 Deployment and Version Control modules due to an org comparison not showing diff results. Support tickets #112752, #116025 #### 26 June 2024 **ARM 23.1.35** 1. A data error reported in version 23.1 with the Version Control module that resulted in version control being deleted was resolved in both 23.1 and 24.1 through adding loggers. Support ticket #114503 2. A use-case error reported in version 23.1 with the Version Control module in which the user was unable to use an existing conflicted file, which resulted in reraising merge requests, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115084 3. A use-case error reported in version 23.1, which resulted in an issue with the Data Loader module in which the software was not inserting the correct record type, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #114076 4. A use-case error reported in version 23.1 with the nCino module in which rollbacks were only partially being completed was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115204 #### 12 June 2024 **ARM 23.1.34** 1. A code fix was performed due to a use-case error related to the CI Jobs module in which nCino CI Jobs were not triggered by metadata CI Jobs on success. Support ticket #113887 2. A code fix was performed due to a use-case error related to the Version Control module in which the API response from CodeScan returned a page not found (404) error in ARM. Support tickets #108895, #115120, #114434 3. A code fix was performed due to a use-case error related to the Deployment module in which the Deployment button was not enabled in AutoRABIT after validation. Support ticket #107108 4. A code fix was performed due to a use-case error related to the Deployment module in which the user was unable to deploy a Bot from a Branch to a sandbox. Support ticket #11497 5. A code fix was performed due to a use-case error related to the Version Control module in which an ALM work item was not displaying in the merge. Support ticket #113626 6. A code fix was performed due to a use-case error related to the Admin module in which a user was unable to implement ARM and Zoho desk integration with JWT. 7. A code fix was performed due to a use-case error related to the Version Control module in which a user was unable to perform EZ-Commits. Support ticket #114441 8. A code fix was performed due to a use-case error related to the Version Control module in which the previously validated commit label showed to add a date instead of the label dropdown. Support ticket #115249 9. A code fix was performed due to a use-case error related to the Reports module that required us to fix recursive errors. 10. A code fix was performed due to a use-case error related to the Data Loader module in which the master-child relationships were not being applied when loaded through Data Loader Pro. Support ticket #111780 11. A code fix was performed due to a use-case error related to the nCino module in which the CI job was not updating templated objects and object record count when the checkout was not taken from version control. Support ticket #112704 12. A code fix was performed due to a use-case error related to the nCino module wherein CI Jobs for nCino RBC feature migrations were failing. Support ticket #114991 13. A code fix was performed to the Admin module as a result of a change request related to users being unable to log in to AutoRABIT. Support tickets #115392, #113300 #### 5 June 2024 **ARM 23.1.33** 1. A code fix was applied to all modules prompted by an internal change request in preparation for support of the Salesforce Summer '24 release. This will require updates to internal documentation. 2. A code fix was applied to the Deployments module resulting from an internal request to correct a use-case error in which a deployment failure and document discrepancy were encountered, with subsequent deployment attempts unsuccessful. 3. A code fix was applied to the Version Control module initiated by a use-case error in which the team encountered an ALM commit issue related to the label name when testing a user story. Support ticket #113308 4. A code fix was applied to the Version Control module related to a use-case error occurring when processing merge conflicts. Support ticket #113606 5. A code fix was applied to the Admin module related to a data error in which the branching baseline was not updating the LWCs in the branch. Support ticket #113174 6. A code fix was applied to the Data Loader module related to a configuration error causing Data Loader to not work as expected. Support ticket #113575 7. A code fix was applied to the ARM module related to a use-case audit logging API error with start time and end time issues occurring when fetching logs. #113739 #### 29 May 2024 **ARM 23.1.32** 1. A code fix was applied to the Version Control module to resolve a use-case error in which the user cannot approve or reject a Merge Request when the label name contains a "+" symbol. When the merge label contains unsupported characters, the merge label is not submitted as expected and the validation message displays the supported characters. Support ticket #112715 2. A code fix was applied to the Admin module related to a use-case error occurring when modifying the Team Administrator, it created duplicate Teams, consuming existing licenses. Support ticket #109457 3. A code fix was applied to the CI Jobs module due to a use-case error in which a Checkmarx scan was not matching up and breaking the build. Support ticket #105217 4. A code fix was applied to the CI Jobs module due to a use-case error occurring when multiple CI jobs run on GitHub PRs, AutoRABIT reports incorrectly that the jobs were successful. \* Issue requires updated documentation. Support ticket #111955 5. A code fix was applied to the Version Control module related to a use-case error in which Mock Deployment criteria check lines were not logged in the UI during the Prevalidation Deployment refresh, but they do appear after auto-rejection and subsequent refresh. 6. A code fix was applied to the Deployment module to correct a use-case error occurring when selecting and deselecting ApexClass and CustomField metadata types, the Deploy pop-up incorrectly displayed "All components are selected" for ApexClass instead of the list of selected components. 7. A code fix was applied to the Version Control module to correct a use-case error displaying unwanted characters, such as different language letters, like “— in the message: "Please wait†when a compare and commit is in progress." 8. A code fix was applied to the Version Control module due to a use-case PrevalidationMerge error occurring when the user was trying to approve a Merge Label through an API with an auto-rejected label, the status changed from "Auto-reject" to "Commit." 9. A code fix was applied to the Version Control module after a user observed three gaps/issues in Commit Templates: 1) Data Table Change in the Commit Template under the 'All Metadata' tab should also sync across all three places, like Deployments, VC Commit, and Commit Template under the 'All Metadata' tab for data table changes. 2) Folder-Related Members Visibility: Folder-related all members are not visible when selecting the folder. This does not sync with EZ Commit All Metadata, from new commit all members. When selecting the folder, all respective folder-related members are visible but not included in the Commit Template when selecting the same Salesforce org. 3) Input Search Dropdown Missing for selecting Folders. 10. A code fix was applied to the Data Loader module concerning a use-case error in which the user was unable to create a project journey with a BIC\_\_c field using "LookUp via" feature. Support ticket #110111 #### 22 May 2024 **(ARM 23.1.31)** 1. A code fix was applied to the Version Control module due to a use-case error related to EZ-Commits and EZ-Merges not taking the master branch, even when Baseline Branch "master" is selected. #107151 2. A code fix was applied to the Version Control module due to a use-case error in which reverting a commit failed. #112094 3. A code fix was applied to the Version Control module due to a use-case error related to the system failing to select multiple reports. #112381, #112812 4. A code fix was applied to the Deployment module due to a data error in which the org sync was not completing. #111545 5. A code fix was applied to the Deployment module due to a data error in which there was a problem in component selection during deployment. #111892 6. A code fix was applied to the Deployment module due to a data error in which the selected items tab was now showing the selected components, as well as the search filter not always being visible. #112095 #### 15 May 2024 **(ARM 23.1.30)** 1. Code fix applied to Deployments module due to user receiving error message: INVALID\_LOGIN: Invalid username or password or security token or API version or user locked out. #111008 2. Code fix applied to Version Control module due to user not being able to see the merge request label name in BitBucket after merging. This required a feature flag, MERGE\_STRATEGY\_ENABLE\_NON\_FF, which is not enabled by default and must be enabled. #110541 3. Code fix applied to the Deployments module related to user experiencing Redeploy/Promote hanging if previous deployment used specified tests. This requires a feature flag, AR\_33697\_ENABLE\_APEX\_TEST\_GET\_CALL, which is not enabled by default and must be enabled. #110764 4. Code fix applied to Deployments module related to email templates of type Visualforce not being added to the package.xml when deploying. #110762 5. Internal - Code fix applied to Version Control module due to DX Package Directory Selection lists not being visible when configuration changes from Vlocity SF org and Vlocity repo to DX Repo. 6. Code fix applied to Version Control module related to an auto-rejected merge label being pushed to a remote repository. #112244 #### 7 May 2024 **(ARM 23.1.29)**
ModuleSummaryStatusFix VersionResolutionCause

Version Control

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

QA Passed

23.1

Code fix

Configuration

Version Control

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

QA Passed

23.1

Code fix

Use case

Version Control

Commit Issue with Custom Page Web Links Deletions

QA Passed

23.1

Code fix

Use case

Version Control

Configure Gated Check-Ins Report for Deployment Validation

QA Passed

23.1

Code fix

Use case

Version Control

Improve Performance of All Metadata Components Screen

QA Passed

23.1

Code fix

Use case

Administration

EBR User Metrics

Done

23.1

Code fix

EBR Change Request

Data Loader

Data Loader Pro jobs not picking up Records

Customer Coordination

23.1

Added Loggers

Use case

#### 29 April 2024 **(ARM 23.1.28)**
ModuleSummaryStatusFix VersionResolutionCause

Deployments

Getting error on deployments

QA Passed

23.1

Code fix

Use case

CI Jobs

Skip member is not working

QA Passed

23.1

Code fix

Use case

Version Control

EZ-Commits failing

QA Passed

23.1

Code fix

Use case

Version Control

Static resources not identified by ARM SCA

QA Passed

23.1

Code fix

Use case

Version Control

Merge showing as no modifications

QA Passed

23.1

Code fix

Use case

Version Control

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

QA Passed

23.1

Code fix

Use case

Reports

Inquiries regarding report module

QA Passed

23.1

Code fix

Use case

Deployments

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

QA Passed

23.1

Code fix

Use case

CI Jobs

Build did not include second revision

Requires Customer Coordination

 Loggers addedLoggers added

CI Jobs

Run test based on changes, noticed issues

Requires Customer Coordination

Loggers addedLoggers added

nCino

IDs of parents/children and records not resolving

QA Passed

23.1

Code fix

Use case

#### 24 April 2024 **(ARM 23.1.27)**
ModuleSummaryResolutionCause

Version Control

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

Code fix

Use case

Version Control

Release Label: Package is not preparing

Code fix

Use case

Reports

Weekly Reports tab error

Code fix

Use case

Deployments

Backups not being created for user

Code fix

Use case

Version Control

Code Scan Analysis not showing in AR ARM tool - UI

Code fix

Use case

Version Control

setting default repository

Code fix

Use case

Deployments

ExternalCredentialPrincipalAccess (permissionSet) is ignored on a git revision deployment

Code fix

Use case

Version Control

Unknow error while merging site components

Code fix

Use case

CI Jobs

CI Job does not deploy all components

Code fix

Use case

Admin

SSH connectivity issue

Code fix

Use case

Version Control

request_closure_duration_mins mismatch for the merges

Code fix

Use case

Reports

B2C Prod Code Scan report

Code fix

Use case

nCino

AR issues

Added Loggers

Use case

Dataloader

User Object Requiring ALL Fields for Uploads

Added Loggers

Use case

#### 14 April 2024 **(ARM 23.1.26)**
ModuleSummaryStatusVersionResolutionCause
DeploymentsOrg Sync issue with case componentsQA Passed23.1Code fixUse case
DeploymentsB2C Org sync diff mail notification issueQA Passed23.1Code fixUse case
CI Jobs, DeploymentsEinstein Chatbot Deployments FailingQA Passed23.1Code fixUse case
Adminlog files are not presentQA Passed23.1Code fixUse case
DeploymentsDeployments are not workingQA Passed23.1Code fixUse case
CI Jobs, DeploymentsFailed to initiate the deploymentQA Passed23.1Code fixUse case
Version controlProfile commit progress delayQA Passed23.1Code fixUse case
AdminTeam Administrator modifications creating duplicate Teams and consuming existing licensesQA Passed23.1Code fixUse case
Version controlIssue Retrieving Components QA Passed23.1Code fixUse case
Version controlRelease Label Stuck while building ArtifactRequires Customer CoordinationLoggers added
Deploymentsutils.js was not deployed as part of packageRequires Customer CoordinationLoggers added
nCinoVersion control record deployments to Salesforce Environments falling offQA Passed23.1Code FixUse case
nCinoLack of Consistency in Filter Functionality Across Feature Management, Deployment History, Commit History, and CI JobsQA Passed23.1Code FixUse case
Version controlUnable to view the Autodraft date and managed package changes dropdownQA Passed23.1Code FixUse case
AdminSuper Admin EBR Token Security Enhancement Done23.1Code fixInternal change request
#### 3 April 2024 **(ARM 23.1.25)**
ModuleSummaryResolutionCause
Reports, CI Jobs, Deployments, Version ControlARM overwrites any exclusions set up in CodeScan UI * Requires documentation.

Code Fix

Change Request

DeploymentsSingle revision deployment taking longer time to retrieve revision

Code Fix

Use Case

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

Code Fix

Use Case

Version ControlGetting empty revision when performing single revision merge with no modifications

Code Fix

Use Case

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

Code Fix

Use Case

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

Code Fix

Use Case

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

Code Fix

Use Case

nCinoVersion control record deployments to Salesforce environments dropping offCode FixUse Case
#### 27 March 2024 **(ARM 23.1.24)**
ModuleSummaryStatusVersion ReportedFix Version(s)ResolutionCause

Deployments

Org Sync question on Moderation Rule difference

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to create EZ-Commit for the new user

QA Passed

23.1

23.1

Code Fix

Use Case

Reports

Problem with scheduled code coverage reports

QA Passed

23.1

23.1

Code Fix

Use Case

Deployments

Profile Comparer - Taking too long to deploy

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Issue in Merging

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Incorrect merge status issue

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

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

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Vlocity DataPacks not being baselined

QA Passed

23.1

23.1

Code Fix

Use Case

Admin

Getting stuck in loading when trying to Expand ALM mappings

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

CI Deploy job link throwing pop-up error message

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

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

Customer Coordination

23.1

NA

No Code FixLoggers Added

nCino

Data Loader Pro jobs failing for Lead

QA Passed

23.1

23.1

Code Fix

Use Case

nCino

nCino Deployment History - search filter criteria is not working

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unnecessary select all checkbox is showing in added and modified tab

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to view created credentials

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

Returns all CI Jobs History to EBR Data irrespective of active

Done

23.1

23.1

Code Fix

Internal change request in EBR Data Visibility

nCino

Feature Deployment Issue with Salesforce Org Version Control

QA Passed

23.1

23.1

Code Fix

Use Case

Data Loader Pro

Issue with Audit Fields

QA Passed

23.1

23.1

Code Fix

Use Case

Admin, Version ControlUnable to register the same repository twice *

REQUIRES FEATURE FLAG:
SKIP_DUPLICATE_REPOSITORY_REGISTRATION_CHECK		QA Passed23.123.1Code FixUse Case
CI JobsError Message: Cannot invoke "String.startsWith(String)" because the return value of "com.autorabit.entity.admin.UserProject.getProjectType()" is null. Support ticket # 109042QA Passed23.123.1Code FixUse Case
#### 20 March 2024 **(ARM v. 23.1.23)**
ModuleSummaryStatusFix VersionResolutionCause

CI Jobs

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

QA Passed

23.1

Code Fix

Use Case

Version Control

Regarding unable to approve commit request

QA Passed

23.1

Code Fix

Use Case

Version Control

Very slow commits

QA Passed

23.1

Code Fix

Use Case

Version Control

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

QA Passed

23.1

Code Fix

Use Case

Version Control

Issues after Branching Baseline

Requires Customer Coordination

Added Loggers

No Code Fix

Reports

Static Code Analysis fails with timeout error

Requires Customer Coordination

Post fix awaiting customer confirmation.

Code Fix for SF CL timeout configuration.

Admin

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

QA Passed

23.1

Code Fix

Use Case

CI Jobs, Deployments

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

QA Passed

23.1

Code Fix

Use Case

Flow Center

Enable SSL for the Kafka used to communicate with FlowCenter.

QA Passed

23.1

Code Fix

 Use Case

nCino

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

QA Passed

23.1

Code Fix

Use Case

Data Loader Pro

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

QA Passed

23.1

Code Fix

Use Case

#### **13 March 2024** **(ARM v. 23.1.22)**
ModuleSummaryFix VersionResolutionCause
DeploymentsProfile Comparer was taking too long to deploy

23.1

Code Fix

Use Case

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

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

23.1

Code Fix

Use Case

DeploymentspackExport is not failing when selecting data packs

23.1

Code Fix

Use Case

CI JobsStatus Check API working incorrectly on UI

23.1

Code Fix

Use Case

CI JobsIssue when deploying the release to the master branch

23.1

Code Fix

Use Case

Version ControlIssue 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 ControlIntermittent issue with the Merge screen

23.1

Code Fix

Use Case

Version ControlCommit Labels within EZ-Merge no longer sorted by latest Commits

23.1

Code Fix

Use Case

ReportsCodeScan analysis discrepancies in APAC Prod * Requires documentation update

23.1

Code Fix

Use Case

Version ControlTerritory metadata type is not fetched as destructive changes during EZ-Commit.23.1Code FixUse Case
DataloaderDataloader Pro was not copying over Contact fields when migrating data

23.1

Code Fix

Use Case

DataloaderWhen 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 JobsDeployment stuck23.1Code FixUse Case
#### 6 March 2024 **(ARM v. 23.1.21)**
ModuleSummaryVersionResolutionCause

ARM

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

23.1

Code Fix

Use Case

Deployments

Org Sync issue

23.1

Code Fix

Use Case

Admin

Unable to Log in to AutoRABIT via Okta

23.1

Code Fix

Use Case

Version Control

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

23.1

Code Fix

Use Case

Version Control

EZ-Commit Salesforce Org Authors not completed

23.1

Code Fix

Use Case

CI Jobs

Dashboards and reports were overwritten after the deployment to PROD

23.1

Code Fix

Use Case

Admin

Suggestion-SF org UI

23.1

Code Fix

Use Case

Reports

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

23.1

Code Fix

Use Case

Admin

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

23.1

Code Fix

Use Case

Version Control

Added metrics in ARM DB

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

nCino

CI Jobs Build Page - Pagination displayed as "undefined"

23.1

Code Fix

Use Case

nCino

nCino CI jobs - Date Literals Value not being populated

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

Dataloader

Unable to migrate related EmailMessage records of Case

23.1

Code Fix

Use Case

CI JobsUnable to view API 59 version in CI configuration under API version dropdown.23.1Code FixUse Case
#### 28 February 2024 **(ARM v. 23.1.20)** | Module | Summary | Resolution | Cause | Feature Flag | | -------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------- | ------------------------------------- | ----------------------------------------- | |

Admin

| Login Error |

Code Fix

|

Use Case

|

| |

Ci Jobs

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

Code Fix

|

Use Case

|

| |

ARM

| SF CLI version upgrade to 2.28.6 for ARM 23.1 instances |

Code Fix

|

Change Request

|

| |

Version Control

| Able to approve auto-rejected merge from email |

Code Fix

|

Use Case

|

| |

Version Control

| PersonAccount AutoRABIT bug |

Code Fix

|

Use Case

|

| |

CI Jobs

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

Code Fix

|

Use Case

|

| |

SFDX

| Error on create package version and install type of job. |

Code Fix

|

Use Case

| AR\_33235\_SKIP\_UPDATE\_PACKAGE\_COMMAND | |

Dataloader

| CPQ Dataload in Developer Sandbox - Errors |

Code Fix

|

Use Case

|

| |

nCino

| nCino CI Job issue |

Code Fix

|

Use Case

|

| |

Dataloader

| Invalid CSV file. Please check for blank columns. |

Code Fix

|

Use Case

|

| |

Dataloader

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

Code Fix

|

Use Case

|

| |

Version Control

| Getting Undefined Error for target branch in External Pull request |

Code Fix

|

Use Case

|

| |

Version Control

| Unable to resolve conflicts in release label merge. |

Code Fix

|

Use Case

|

| |

Flow Center

| Search & Substitute rules are not applied in the pipelines. |

Code Fix

|

Use Case

|

| #### 21 February 2024 **(ARM v. 23.1.19)** | 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)**
ModuleSummaryStatusFix Version(s)ResolutionCauseFeature enabled by defaultFeature Flag Name

Deployments

Upgrade to 23.1.16 + Ubuntu OS Upgrade

QA Passed

23.1

Code Fix

Use Case

NO

NO

Dashboards

ARM dashboard

QA Passed

23.1

Code Fix

Use Case

NO

NO

Deployments

Org sync - Scheduler not working

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Commit failing without any logs

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Single-revision merge taking a long time

Customer Coordination [Added Loggers]

No Code Fix - Added Loggers

No Code Fix - Added Loggers

Data

NO

NO

Version Control

Package.xml fetching the Excluded components during Commit

QA Passed

23.1

Code Fix

Use Case

NO

NO

Deployments

Smart checkbox redeployment

QA Passed

23.1

Code Fix

Change Request

NO

NO

Version Control

PG and ARM instances not working as expected

QA Passed

23.1

Code Fix

Use Case

NO

FILE_SYNC_WITH_OPTIMISTIC_LOCK

Version Control

Commit not getting detected

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Error while trying to select the revision from branch

QA Passed

23.1

Code Fix

Use Case

NO

NO

#### 7 February 2024 **(ARM v. 23.1.17)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

nCinoPartial error on CI Job - nCino-Fee TemplateQA Passed23.1Code FixUse Case
#### 28 January 2024 **(ARM v. 23.1.16)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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 ProMultiple issues during data maskingCustomer Coordination – Added Loggers23.1No Code Fix – Added LoggersData
#### 21 January 2024 **(ARM v. 23.1.15)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

23.1

Code Fix

Use Case

Version Control

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

23.1

Code Fix

Use Case

Version Control

Finding WaveDataflow components for commitQA Passed

23.1

Code Fix

Use Case

Admin

Error: Access token as failed while doing a branching baselineQA Passed

23.1

Code Fix

Use Case

CI Jobs

Provar version upgradeQA Passed

23.1

No Code Fix – Only Configuration change for specific customerCustomer-specific

Version Control

Initial commit failingCustomer CoordinationNo Code Fix – Added LoggersData

Admin

Users’ permissions are being reset.Customer CoordinationNo Code Fix – Added Loggers

Data

CI Jobs, Version Control, Admin, DeploymentsAdding authentication check on web hook APIsQA 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 DeploymentsQA Passed

22.3
23.1

Code Fix

Use Case
#### 14 January 2024 **(ARM v. 23.1.14)**
ModuleSummaryFix Version(s)ResolutionCause
MODULESUMMARYFIX VERSIONRESOLUTIONCAUSE
Version Control Internal - Default SCA branch not reflected while merging 23.1

Code Fix

Use Case

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

DeploymentsDeployment status failed when deploying Vlocity components 22.3, 23.1

Code Fix

Use Case

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

23.1

Code Fix

Use Case

DeploymentsBrazil Prod to UAT deployment issue

23.1

Code Fix

Use Case

nCino Metadata update is failing

23.1

Code Fix

Use Case

Version ControlCommit not progressing

23.1

No Code Fix - Loggers Added

Data
#### 7 January 2024 **(ARM v. 23.1.13)**
ModuleSummaryFix VersionResolutionCause

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)**
ModuleSummaryFix VersionResolutionCause

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)**
ModuleSummaryVersion(s)ResolutionCause

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

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

23.1, 22.3

Code Fix

Use Case

Version ControlUnable 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 | NA | No Code Fix - Added Loggers | Data | | Deployments | Org sync not completing | NA | No Code Fix - Added Loggers | Data | | Dataloader | Corrected a spelling mistake in ARM steps. | 23.1, 22.3 | Code Fix | Use Case | | Dataloader | Corrected data seeding error preventing upsert | 23.1, 22.3 | Code Fix | Use Case | | Reports | Getting ‘cannot invoke "String.length()" because of "text" is “null”’ error when performing the ‘Get latest reports’ in Weekly reports | 23.1 | Code Fix | Use Case | | Reports | When navigating to Static Code Analysis screen from Reports module, getting the “comparison method violates its general contract!” error. | 23.1 | Code Fix | Data | | Version Control | On DX branch release label artifact execution, on deleted components, the destructive changes artifact preparation is not generated. | 23.1 | Code Fix | Use Case | | nCino | On-premise testing: CI Job with template option failed due to "data and metadata retrieval failed” error | 23.1, 22.3 | Code Fix | Use Case | | CI Jobs | Failed to deploy destructive changes though CI jobs. | 23.1 | Code Fix | Use Case | #### 26 November 2023 **(ARM v 23.1.9)**
ModuleSummaryFix Version(s)ResolutionCause
AdminBranching baseline issue23.1Code FixUse Case
CI JobsThe new feature of merging only revision in the CI job build is not working23.1Code FixUse Case
CI JobsCI job filter not working properly23.1Code FixUse Case
Version ControlCommit not getting detected23.1Code FixUse Case
Version ControlRejecting a commit is merging the changes23.1Code FixUse Case
AdminUnable to save Pull Request Plugin config23.1Code FixUse Case
Version ControlAR commit File Diff process is failing with errors23.1Code FixUse Case
Version ControlMerge auto-rejected but CI job triggered23.1Code FixUse Case
AdminChanging role from Dev to Admin shows orgs and branches in New EZ- Commit without mapping under profile23.1Code FixUse Case
Version Control and DeploymentRelease Label Artifact not including code for a commit23.1Loggers AddedData
DataloaderDataloader Pro jobs causing huge threads pileup23.1EnhancementUse Case
CI JobsData 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.1Code FixUse Case
Version ControlWhile submitting the ALM commit with these “<ALM Issue ID>“, “{ALM Issue ID}” ALM patterns, unable to submit the commit23.1Code FixUse Case
DeploymentsSub-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" error23.1Code FixUse Case
Version ControlWith Release label deployment, the flow-meta.xml retrieval issue both constructive and destructive23.1Code FixUse Case
#### 22 November 2023
ModuleSummaryFix Version(s)ResolutionCauseEnabled by default?Feature Flag Name
Version ControlBranch Protection Policy enforced and behavior of EZ- merge23.1Code FixUse CaseNOGIT_LOGGEDIN_USER_AS_COMMIT_USER
Version ControlIssue while creating feature branches in EZ - Commit screen23.1Code FixUse Case
Version ControlUpload File option not available during EZ- commit with Option package manifest23.1Code FixUse Case
#### 19 November 2023 **(ARM v. 23.1.8)**
ModuleSummaryFix VersionResolutionCause
DeploymentsDeployment tab - Redeploy/Promote issue22.3, 23.1Added LoggersData
DataloaderOptimize the Dataloader Pro job logs in the rabit cs log23.1Code FixUse Case
nCinoUnable to create Feature Migration Template on Debt Schedule object22.3, 23.1Code FixUse Case
All ModulesInvalid Email ID22.3, 23.1Code FixUse Case
CI Jobs, Deployments, Version Control, AdminOrg Sync diff report differs for the same source org compared to different orgs.23.1Code FixUse Case *
DataloaderUrgent: AutoRABIT is down23.1Code FixUse Case
Version ControlIssue with Block button during Merge Conflict23.1Code FixUse Case
CI JobsCI job deployment failing: Restriction rules deployed as moderation rule and made the deployment bugged23.1Code FixUse Case
CI JobsUrgent: Rollback of specific components - Issue23.1Code FixUse Case
CI JobsUnexpected behavior when disabling component category on rollback destructive changes.23.1Code FixUse Case
SFDXError while using Scratch Org Management tab23.1Code FixUse Case
All ModulesARM<>ULP Integration Issues23.1Code FixUse Case
Version ControlAuto-reject on commit validation for SCA & Auto-reject setting in Merge23.1Code FixUse Case
#### 15 November 2023
ModuleSummaryFix VersionResolutionCause
CI JobsCI Job is not picking up changes committed on the branch, indicating "No modifications made."23.1Code FixUse Case
DeploymentsOrg Synchronization – constructive & destructive changes are not working together23.1Code FixUse Case
AdminSync error between ARM and GIT23.1Code FixUse Case
Version ControlDeployment validation not working correctly during new EZ-Merge23.1Code FixUse Case
CI JobsMerging only revision in the CI job build not working23.1Code FixUse Case
#### 12 November 2023 **(ARM v. 23.1.7)**
ModuleSummaryFix Version(s)ResolutionCause
DeploymentsDuring Org Sync, file names are being repeated as part of the deployment results.23.1Code FixUse Case
DeploymentsUser is unable to see the Deployment History.23.1Code FixUse Case
CI Jobs & DeploymentsUser is unable to deploy static resource.23.1Code FixUse Case
ReportsScheduled Code Coverage Reports are running at the wrong time.23.1Code FixUse Case
nCinoUser is unable to create Feature Migration Template on Debt Schedule object.22.3, 23.1Code FixUse Case
DataloaderUser is unable to upload files and update records; system logs user out instead.23.1Code FixUse Case
Version ControlUser is getting timeouts in merge screen.23.1Code FixUse Case
#### 5 November 2023 **(ARM v. 23.1.6)**
ModuleSummaryFix Version(s)ResolutionCause
All ModulesSF CLI version upgrade to 2.14.623.1Code FixEnhancement
Environment ProvisioningView environment provisioning templates22.3 & 23.1Code FixEnhancement
AdminBranching baseline is not picking all components from production22.3 & 23.1Code FixUse Case
DeploymentsHelp with destructive change22.3 & 23.1Code FixUse Case
Version ControlMerge request is failing due to validation credentials22.3 & 23.1Code FixUse Case
CI Jobs, DeploymentsIssues with a release – related to Feature Flag - not automatically deployed: STANDARD_VALUE_SET_DELTA22.3 & 23.1Code FixData
Version ControlApproval button is not visible after successful merge validation22.3 & 23.1Code FixData
Version ControlCreate artifact: not completed23.1Code FixData
AdminAutoRABIT login not working23.1Code FixUse Case
Version ControlError pop-up during merge type selection as Commit Label in EZ-Merge23.1Code FixData
CI JobsAutoRABIT AccelQ Integration/ bhg-inc.com23.1Code FixUse Case
CI Jobs
Developer API for CI Jobs History not returning latest results.		23.1Code FixUse Case
nCinoAbility to trigger nCino CI jobs using REST API23.1Code FixCustomer Request
CI JobsFor run test automation scripts job: More than one cycle is not displayed in the individual job history23.1Code FixUse Case
Version ControlUnable to delete feature branch under merge request, getting internal server error23.1Code FixUse Case
Version ControlUnable to view the entry of recently created merge request in the merge request history screen23.1Code FixUse Case
Version ControlCriteria met ALM's not getting fetched under merge request23.1Code FixUse Case
nCinoInstead of POST methods need to change the GET23.1Code FixCustomer 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 branc**h 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 **queu**e. * 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 item**s. * 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**.\ [**Read more →**](/product-guides/arm/arm-administration/user-management/manage-users-account-settings) #### 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.\ [**Read more →**](/product-guides/arm/arm-features/automation-and-ci/ci-job-list) #### 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.\ ![image.png](https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-I1GT03M7.png) *** ### 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. [**Read more →**](/product-guides/arm/arm-features/version-control/change-labels/release-labels) #### 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.\ [**Read more →**](/product-guides/arm/arm-administration/search-and-substitute) #### 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.\ [**Read more →**](/product-guides/arm/arm-administration/user-management/users-roles-and-permissions) #### 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.\ [**Read more →**](#4-dataloader-clone-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 [HERE](/product-guides/arm/arm-features/reports/static-code-analysis) 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 [HERE](https://knowledgebase.autorabit.com/docs/single-dataloader) 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)**
ModuleSummaryStatusFix Version(s)ResolutionCause

Deployment

Vlocity Deployment issue

QA Passed

22.3, 23.1

Code Fix

Use Case

Version ControlNot fetching merges when trying to create a release label for Vlocity componentsQA Passed22.3Code FixUse Case
#### 21 January 2024 **(ARM v. 22.3.53)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

22.3
23.1

Code Fix

Use Case
#### 14 January 2024 **(ARM v. 22.3.52)**
ModuleSummaryFix Version(s)ResolutionCause
MODULESUMMARYFIXVERSIONRESOLUTIONCAUSE
Admin

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

22.3

Code Fix

Use Case

DeploymentsDeployment status failed when deploying Vlocity components22.3 23.1

Code Fix

Use Case

**10 December 2023** **(ARM 22.3.51)**
ModuleSummaryVersion(s)ResolutionCause
nCinoUser is unable to do nCino Feature Deployments
* Requires documentation

23.1, 22.3

Code Fix

Use Case

AdminGetting ‘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 | NA | No Code Fix - Added Loggers | Data | | Deployments | Org sync not completing | NA | No Code Fix - Added Loggers | Data | | Dataloader | Corrected a spelling mistake in ARM steps. | 23.1, 22.3 | Code Fix | Use Case | | Dataloader | Corrected data seeding error preventing upsert | 23.1, 22.3 | Code Fix | Use Case | | 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)**
ModuleSummaryFix Version(s)ResolutionCause

CI Jobs

Post activities, particular job status showing as FAILED in ARM even job execution completed with succeed22.3Code FixUse Case

Admin

Getting empty Configuration under "Configure Default SCA Baseline Branches"22.3Code FixUse Case

Admin

Able to view empty role under permissions22.3Code FixUse Case
#### 19 November 2023 **(ARM v. 22.3.48)**
ModuleSummaryFix VersionResolutionCause

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 ID22.3, 23.1

Code Fix

Use Case

#### 15 November 2023
ModuleSummaryFix VersionResolutionCause
DeploymentsPage unresponsive in new deployment for "previous deployment" as source type22.3Code FixUse Case
#### 12 November 2023 **(ARM v. 22.3.47)**
ModuleSummaryFix Version(s)ResolutionCause
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)**
ModuleSummaryFix Version(s)ResolutionCause
All ModulesNew User Creation22.3

Code Fix

Change Request

Environment ProvisioningView environment provisioning templates

22.3 & 23.1

Code Fix

Enhancement

AdminBranching baseline is not picking all components from production

22.3 & 23.1

Code Fix

Use Case

DeploymentsHelp with destructive change

22.3 & 23.1

Code Fix

Use Case

Version ControlMerge request is failing due to validation credentials

22.3 & 23.1

Code Fix

Use Case

CI Jobs, DeploymentsIssues with a release – related to Feature Flag not automatically set: STANDARD_VALUE_SET_DELTA

22.3 & 23.1

Code Fix

Data

Version ControlApproval 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)** **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 **ProcessInpu**t 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: 1. 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. 2. Implemented a code fix associated with the **version control** module for a use-case error in which **ALM working items were not loading**. 3. Implemented a code fix for a use-case error pertaining to the **version control** module for an **approval email notification error**. 4. 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. 5. 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. 6. 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. 7. Implemented a code fix related to the **nCino** module error: | **LLC\_BI\_\_Schedule\_Section\_\_c migration issue#1** | | ------------------------------------------------------- | 8. 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. 9. 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 ([#73824](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000114206402)). * 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 ([#72073](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112029001)). * Fixed an issue where user was trying to create an connect an **Active Directory** but it kept failing ([#73582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113941053)). * 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 ([#73371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113607033) and [#56084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091215009)). * 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 ([#71444](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111273077)). * 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 ([#71367](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111185001)). * Fixed an issue where deploying test classes from manual deployment was throwing an out of memory error ([#71872](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111679026)). * 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 ([#72181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112197081)). * 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** ([#72811](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112765004)). * 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 ([#72817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112807012)). * Fixed an issue where the **Git author** was overridden by ARM ([#71393](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111202442)). * 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** ([#73515](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113850003)). * 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 e**xternal 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 ([#71947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111886005)). * 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` ([#72217](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112229003)). * 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 ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * 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 ([#72751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112682583)). * Fixed an issue where CI job deployment was failing because the build was picking duplicate **Layout** values ([#71214](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110698400)). * Fixed an issue where unwanted metadata changes were observed in the **package.xml** file while performing a commit ([#72089](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112054140) and [#71820](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111655842)). * Fixed an issue where **Branching Baseline** was not picking all the components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * 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 ([#58549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095408144) and [#38339](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064118003)). * Fixed an issue with **nCino** where CI jobs that used a **Deployment** from **Version Control** were failing when the build was triggered ([#71914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111840343)). * 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 ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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 ([#70787](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110191524)). * Fixed an issue where **Destructive Changes** wasn't working as expected while performing an **Entire Branch** merge ([#68882](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107824070)). * Enhanced the ALM management feature by adding an option to sync **Smart Commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * Fixed an issue with **CI Jobs** **Destructive Sharing Rule** was not deploying to the Salesforce org ([#71183](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110703254)). * Fixed an issue where user could not disable the **Smart Commits-Sync** option for a repository branch in the **VC repos section** ([#70854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110258586)). * Improved the **New Merge** screen by removing the **Validate Deployment** option from the UI if **Vlocity** is selected ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * Enhanced the **Credentials** module by adding **SSH Cetificate** option for **Git Authentication** ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * 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 ([#70400](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109643126)). * Fixed an issue where **Branching Baseline** was taking longer than expected ([#67814](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777192)). * Fixed an issue where using the **AutoDraft** functionality in **EZ-Commit** was resulting in a malformed exception in the UI ([#70458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109706018)). * Fixed an issue where **Branching baseline** was not picking all components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * Fixed an issue where **prevalidation merge** failed with empty metadata package even though there were changes in **File Diff** ([#32256](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000049822310)). * Fixed an issue where entire **ARM** application was down temporarily ([#70658](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110024189)). * Fixed an issue where **Merge** was **auto-rejected** due to an empty package because the **metadata folder path** not being specified under branch settings ([#69788](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108851098)). * 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` ([#70868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110350003)). * Fixed an issue where users weren't receiving **SCA reports** by email even though the reports were running ([#70751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110137323)). * Fixed an issue where while performing new **EZ-Commit**, user edited one line using review artifact option but **Diff** did not capture the same ([#70270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109345141)). * 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 ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * Fixed an issue where CI Job was picking changes one build but not for the other, and the logs weren't capturing this ([#69164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108123319)). * 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 ([#67654](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106594374)). * Fixed an issue where user merged a new component using a single revision merge but the merge missed to perform a CodeScan analysis ([#70391](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109502039)). * 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 ([#70351](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109465295)). * Fixed a UI issue where **OK** button to reject an EZ-Merge was not working ([#70041](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108965683)). * Fixed an issue where a field was available in the package but still Validation was throwing error that the field was missing ([#69831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108972528)). * Fixed an issue with **DataLoader** where multiple jobs were not processing parallelly when user loaded a large number of jobs to the queue ([#62559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100372446)). * 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` ([#69831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108972528)). * 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`. ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * Enhanced the **VC Repos** page by introducing a feature that allows users to **sync external smart commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * 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 ([#69772](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108841212)). * 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 ([#68012](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107136001)). * 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 ([#69614](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108583086)). * 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 ([#47794](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081201667)). * Fixed an issue with nCino where CI job filter changes on templates were not taking effect after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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** ([#48644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082753293)). * Enhanced **Vlocity CI jobs** by allowing **Local Compilation** for **Omniscript** and **Flexcard** objects ([#55641](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090230148) and [#50301](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084720103)). * Fixed an issue where user was unable to use the **Redeploy/Promote** option after ten iterations of an existing **Deployment** label ([#69084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108041156)). * 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 ([#67826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777838)). * 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 ([#67818](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777588)). * Fixed an issue where **EZ-Merge** was failing with `NullPointerException` ([#67502](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106282031)). * 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?`** ([#65565](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104611176)). * Fixed an issue where **Revert** commits were failing without any error messages ([#68771](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107671065)). * 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 ([#68939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107912007)). * Fixed a UI bug where when user unchecked **Validate deployment** option in **EZ-Merge**, the **Run destructive changes** checkbox was hidden ([#68750](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107699066)). * 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 ([#65680](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104849001)). * 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 ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 ([#59458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096457374)). * 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 ([#66587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105697158)). * Fixed an issue where **Git backup job** was failing due to unsupported metadata ([#66536](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105610003)). * Fixed an issue where scheduled CI jobs were getting queued or not getting triggered as per schedule ([#57749](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093607144)). * Fixed an issue where **Quick action** was not picked for destructive changes ([#65058](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104091725)). * 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 ([#63234](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101513612)). * Fixed an issue where user using **non-SFDX** repo with **Custom API** enabled failed to pick the changes in the CI job ([#64497](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103321171)). * Fixed an issue where **Release label** displayed **commit revisions** older than 30 days even when the **No. of days** filter was set as **30** ([#63845](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102526769)). * Fixed an issue where a user had trouble creating **artifact** for a **release label** ([#65557](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104667180)). * 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 ([#65625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104812001)). * 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 ([#66655](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105749754)). * Fixed an issue with **nCino** where CI job build status is displayed as **Completed** for a failed job ([#64479](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103318168)). * Fixed an issue with **nCino** where attachements to `nFORMS__Form_Template__c` failed to get deployed ([#65242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104379896)). * Fixed an issue where user was unable to initiate **static code analysis** on a Salesforce Org ([#51559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085951433)). * Fixed an issue with **New EZ- Commit** where while using **Custom YAML** file the page was taking much longer to load than usual ([#65742](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104883025)). * Fixed an issue where **Merge** was happening on incorrect files ([#64485](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103318553)). * 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 ([#65058](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104091725)). * 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)` ([#60914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097801217) and [#65855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105051054)). * Fixed an issue where **WebStoreTemplates** object was not available for deployment ([#65854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104921177)). * Fixed an issue where **Merge Request XML** file was conflicting with an error `No conflict data found for this block` ([#65164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104169938)). * Fixed an issue where **Release label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * 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 ([#64612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103417610)). * Fixed an issue where user was unable to merge the code from one branch to another branch. ([#65570](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104676278)). * Fixed an issue where **Ignore Missing Visibility** settings not working on **EZ-Merge** validation ([#65162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104186080)). * Fixed an issue where user was loading multiple **DataLoader** jobs but it was not processing parallelly ([#62559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100372446)). * 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` ([#64228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103003760)). * Fixed an issue where multiple deployment requests were being generated while performing **Org Sync** if the user selected all components instead of a few ([#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where **Rollback API** threw a **200** response but the Rollback immediately failed in the ARM UI ([#65146](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104115380)). * Fixed an issue where SCA report Failed to run using the **Codescan Plugin** with the following Salesforce error `384187622-16951 (-673032061)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151)). * Fixed an issue where users were having trouble logging in to ARM due to an error `Session Invalid` ([#64965](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103959064), [#65052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104090509), and [#64969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104016027)). * 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** ([#64094](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102809037)). * Fixed an issue where **Auto-draft** was taking much longer than expected to retrieve the metadata in **EZ-Commit** ([#65109](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104022403), [#65007](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104076001), [#64950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103943001), [#64510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103338015), [#64645](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103513158), [#64161](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102852098), and [#64523](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103361369)). * 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 ([#64185](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102875003)). * 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 ([#64150](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102831529)). * Fixed an issue where user was unable to retrieve **MutingPermissionSet** using the **SFDX** repository ([#64141](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102573686)). * Fixed an issue where the **Release Label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * Fixed an issue where **Sharing Rule Set** metadata type was found in the **Deployment** module but not in the **Version Control** module ([#65060](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104102165)). * 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 ([#65091](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104040481)). * 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 ([#63554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101980029)). * 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 ([#63272](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101591692)). * Fixed an issue where user was unable to deploy a CI job with the **RelationshipGraphDefinition** components ([#64145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102836208)). * Fixed an issue where **Validate** deployment was displayed as **failed** in UI and the database, but was successful as per the logs ([#63868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102596005)). * Fixed an issue with **Review Artifact** where similar custom fields from different objects were not populating correctly and switching to other fields ([#63676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102181836)). * 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 ([#63544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101947159)). * Fixed an issue where user chose **Exclude Metadata Type** for a particular metadata type during a **CI Job**, but it was still deployed ([#62966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101046005)). * Fixed an issue where user was unable to perform **Destructive Commit** with **PermissionSetGroups** metadata type ([#63172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101463001)). * Fixed an issue where users weren't receiving emails after setting up **Mail Settings** ([#55070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089394047)). * Fixed an issue where there was a discrepancy between **EZ-Commit** and **Commit templates** while retrieving **Email Template** metadata members ([#61696](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099121314)). * Fixed an issue where **Merge Labels** were taking much longer than expected ([#62625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100474287)). * Fixed an issue where user tried to commit the changes without validation and UI displayed an error `Another commit is in progress` ([#61930](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099562127)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the **Commits History** page ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Fixed an issue where **Merge** was not auto-rejected when validation criteria was not met ([#62287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100008338)). * Enhanced **nCino** by adding an option to specify **Baseline Revision** in **Continuous Integration** for **Version Control** to perform feature deployments ([#43642](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073759034) and [#44506](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074950579)). * Enhanced **nCino** by allowing users to deploy nCino **CI build** to multiple target sandboxes ([#41763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070674305)). * 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 ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Enhanced the **Release Label** creation by increasing the range of retrievable commit history ([#61714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099129934)). * Fixed an issue where user was unable to use **Release Labels** to perform **Deployment**, and it failed while trying to **Create Artifact** ([#59429](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096450140)). * Fixed an issue where users with non-admin access were unable to register branches in **EZ-Commit** since upgrading to version 22.3 ([#62723](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100650673), [#62949](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101016055), [#62979](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010456), and [#62969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010302)). * 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 ([#61403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098537015)). * 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 ([#60531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097360001)). * Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs ([#61079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097987087)). * Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in **EZ-Commit** ([#56188](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091240174)). * Fixed an issue where user was customer trying to register a **Salesforce Org** with **Custom URL** but it was failing with an error ([#62192](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099509581)). * Fixed an issue where user was unable to remove **Revisions**/**Commit Labels** from a **Release label** ([#59152](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096005470) and [#61578](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098950203)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed an issue where user user uploaded a **YAML file** to retrieve the **Vlocity components** but ALL metadata types were retrieved and displayed ([#61181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248158)). * Fixed an issue where the same merge could be approved and rejected by different users simultaneously ([#60859](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097787146)). * 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** ([#61551](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098913200)). * 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 ([#59082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096042290)). * Fixed an issue where **Dependency** order defined in **json** file was being changed on every commit but it was not supposed to ([#57731](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556797)). * Fixed an issue where **Create Artifact** was not working as expected while using **Release Label** ([#61607](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098932152)). * 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 ([#61751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248378)). * Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes ([#61736](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099207347)). * 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 ([#57318](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092768029)). * Fixed an issue with **Backup from Org CI Jobs** where **PermissionSet User Permissions** were being deleted ([#59674](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096685144)). * Fixed an issue where **Org to Org Deployment** for **Profiles** including **Deploy Profile Access Settings for selected components only** was not working as expected ([#60559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097375154)). * Fixed an issue where **Post Destruct** fields were also added to **Pre Destruct** despite the user setting it to post ([#61162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248005)). * Fixed an issue where user set the **Max depth** value as '0' under **Vlocity Configuration Settings** but it was retrieving all level dependancy components ([#57501](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093212471)). * Fixed an issue with DataLoader where the **Credit Memo Template** migration was not deploying after user upgraded their instance ([#57676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093470003)). * Fixed an issue where user selected **Custom Metadata** members (records), but **EZ-Commit** was failing to generate **File Diff** with `Null` error ([#59709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096706005)). * Fixed an issue where **Merge** was taking longer than usual, and then failing with `Null Exception` ([#60757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097574427)). * Fixed an issue where **EZ-Commits** and **EZ-Merges** were taking much longer than usual ([#58098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094302292)). #### 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` ([#60597](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097399881)). * 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` ([#59050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095999076)). * Fixed an issue where **Reports** deployment validation failed in **EZ-Merge** but was successful in **EZ-Commit** and **Deployment** modules ([#57714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093587003)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error `null` at **Diff** ([#59919](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096907001)). * 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 ([#59359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096219627)). * Fixed an issue where commit was running for longer and remained **in-progress** and **validation check log** is also in progress ([#59199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096003630)). * Fixed an issue where commits with SFDX metadata structure are **failing** in metadata **retrieval stage** ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * Fixed an issue where user couldn't create a managed package with the selected ancestor ([#59044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095985421)). * Fixed an issue where **CI Job** was occasionally failing with the error `BUILD FAILED` ([#57647](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093370172)). * Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user ([#55438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089958034)). * 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 ([#59040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095982206)). * 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 ([#58044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094164003)). * Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error: `Invalid Private Key` ([#59244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096134293)). * Fixed an issue where user has created a Commit label but it was not available while trying to perform an **EZ-Merge** ([#55176](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089550097)). * Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff ([#59114](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096048883)). * Fixed an issue where user was getting an error while trying to create a new branch in GitHub ([#59193](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096138920)). For more information, click [here](https://knowledgebase.autorabit.com/docs/faqs-version-control?highlight=$%20ssh-keygen%20-t%20rsa%20-b%204096%20-C#why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh). * 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 ([#59402](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096425001)). * 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` ([#59028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095867179)). * 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 ([#58998](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095876003)). * 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 ([#59014](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095898340)). * 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 ([#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556)). * Fixed an issue with user received 6 notifications for a failed **CI Job** instead of 1 ([#58436](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095199003)). * Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error: `Lower Region` ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * 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 ([#51268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085726862)). * Fixed an issue where while performing destructive changes in **EZ-Commit**, it was creating **package.xml** in root path folder in **SFDX** structure ([#57868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093790001)). * 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 ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189)). * Fixed a build bug where **CI Job Build** was failing during package preparation **step 5** failing while commiting **DecisionMatrixDefinition** and throwing an error ([#58376](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095049142)). * 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\ ([#58478](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095251543)). * Fixed an issue where generating **Diff** for a **Commit Label** was taking much longer than expected ([#55220](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591780)). * Fixed an issue where **Code coverage** job was running **4 hours** earlier than scheduled every time services were restarted ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * 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 ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * Fixed an issue where **Merge validation** failed to process when there was a **Flow** metadata ([#58244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094983001), [#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556), and [#58438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095210005)). * 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 ([#57898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093797903)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). * Fixed an issue where AutoRABIT **SSH credentials** were failing with an error `Auth failed` while trying to connect with **AWS CodeCommit** ([#53694](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087714369)). * Fixed an issue where **EZ-Commit Diff** was taking approximately 4 hours while **Refactoring CustomField**, which is much longer than expected ([#56650](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091636348)). * 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 ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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 ([#53980](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087981132)). * 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 ([#55995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091129007)). * Fixed an issue where **Profile Diff** is working as expected for **Selective Deployment**, but not while using the same profile in the profile manager ([#52868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087005140)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189), [#55754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090487029)). * Fixed an issue where **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). *** ## **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. [**Read more →**](/product-guides/arm/troubleshoot/how-tos/notifications-mail-server-settings) #### 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 [HERE](https://pmd.github.io/latest/pmd_next_major_development.html#list-of-currently-deprecated-rules) 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. [**Read more →**](/product-guides/arm/arm-administration/user-management/manage-users-account-settings) #### 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. [**Read more →**](#3-hashicorp-vault-integration) #### 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. [**Read more →**](/product-guides/arm/arm-administration/user-management/salesforce-api-version) #### 6. Merge to multiple branches With this release, you can choose to **merge** from one **source branch** to multiple **destination branches** upon successful deployment. [**Read more →**](/product-guides/arm/arm-features/automation-and-ci/create-a-new-ci-job/deploy-from-sfdx-branch-to-a-salesforce-org) #### 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. [**Read more →**](/product-guides/arm/arm-administration/alm-management) ### 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 ([#71947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111886005)). * 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` ([#72217](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112229003)). * 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 ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * 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 ([#72751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112682583)). * Fixed an issue where CI job deployment was failing because the build was picking duplicate **Layout** values ([#71214](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110698400)). * Fixed an issue where unwanted metadata changes were observed in the **package.xml** file while performing a commit ([#72089](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112054140) and [#71820](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111655842)). * Fixed an issue where **Branching Baseline** was not picking all the components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * 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 ([#58549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095408144) and [#38339](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064118003)). * Fixed an issue with **nCino** where CI jobs that used a **Deployment** from **Version Control** were failing when the build was triggered ([#71914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111840343)). * 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: * Fixed an issue where wrong **timezone** region was displaying for users ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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: * Fixed an issue where user was having trouble while deploying **LighteningMessageChannel** components ([#70787](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110191524)). * Fixed an issue where **Destructive Changes** wasn't working as expected while performing an **Entire Branch** merge ([#68882](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107824070)). * Enhanced the ALM management feature by adding an option to sync **Smart Commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * Fixed an issue with **CI Jobs** **Destructive Sharing Rule** was not deploying to the Salesforce org ([#71183](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110703254)). * Fixed an issue where user could not disable the **Smart Commits-Sync** option for a repository branch in the **VC repos section** ([#70854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110258586)). * Improved the **New Merge** screen by removing the **Validate Deployment** option from the UI if **Vlocity** is selected ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * Enhanced the **Credentials** module by adding **SSH Cetificate** option for **Git Authentication** ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * 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 user was getting a validation deployment error while performing release label deployment ([#70400](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109643126)). * Fixed an issue where **Branching Baseline** was taking longer than expected ([#67814](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777192)). * Fixed an issue where using the **AutoDraft** functionality in **EZ-Commit** was resulting in a malformed exception in the UI ([#70458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109706018)). * Fixed an issue where **Branching baseline** was not picking all components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * Fixed an issue where **prevalidation merge** failed with empty metadata package even though there were changes in **File Diff** ([#32256](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000049822310)). * Fixed an issue where entire **ARM** application was down temporarily ([#70658](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110024189)). * Fixed an issue where **Merge** was **auto-rejected** due to an empty package because the **metadata folder path** not being specified under branch settings ([#69788](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108851098)). * 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` ([#70868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110350003)). * Fixed an issue where users weren't receiving **SCA reports** by email even though the reports were running ([#70751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110137323)). * Fixed an issue where while performing new **EZ-Commit**, user edited one line using review artifact option but **Diff** did not capture the same ([#70270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109345141)). * 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 where **validation jobs** on **Pull Requests** weren't getting triggered ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 CI job deployments were failing with the error, `Error 405 Only POST allowed` ([#64228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103003760)). * Fixed an issue where multiple deployment requests were being generated while performing **Org Sync** if the user selected all components instead of a few ([#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where **Rollback API** threw a **200** response but the Rollback immediately failed in the ARM UI ([#65146](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104115380)). * Fixed an issue where SCA report Failed to run using the **Codescan Plugin** with the following Salesforce error `384187622-16951 (-673032061)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151)). * Fixed an issue where users were having trouble logging in to ARM due to an error `Session Invalid` ([#64965](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103959064), [#65052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104090509), and [#64969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104016027)). * 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** ([#64094](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102809037)). * Fixed an issue where **Auto-draft** was taking much longer than expected to retrieve the metadata in **EZ-Commit** ([#65109](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104022403), [#65007](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104076001), [#64950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103943001), [#64510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103338015), [#64645](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103513158), [#64161](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102852098), and [#64523](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103361369)). * 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 ([#64185](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102875003)). * 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 ([#64150](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102831529)). * Fixed an issue where user was unable to retrieve **MutingPermissionSet** using the **SFDX** repository ([#64141](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102573686)). * Fixed an issue where the **Release Label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * Fixed an issue where **Sharing Rule Set** metadata type was found in the **Deployment** module but not in the **Version Control** module ([#65060](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104102165)). * 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 ([#65091](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104040481)). * 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 **Static Code Anaysis** was failing due to missing property tag in **Apex PMD** rules file, but the UI log wasn't displaying this error ([#63554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101980029)). * 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 ([#63272](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101591692)). * Fixed an issue where user was unable to deploy a CI job with the **RelationshipGraphDefinition** components ([#64145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102836208)). * Fixed an issue where **Validate** deployment was displayed as **failed** in UI and the database, but was successful as per the logs ([#63868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102596005)). * Fixed an issue with **Review Artifact** where similar custom fields from different objects were not populating correctly and switching to other fields ([#63676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102181836)). * 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 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 ([#63544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101947159)). * Fixed an issue where user chose **Exclude Metadata Type** for a particular metadata type during a **CI Job**, but it was still deployed ([#62966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101046005)). * Fixed an issue where user was unable to perform **Destructive Commit** with **PermissionSetGroups** metadata type ([#63172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101463001)). * Fixed an issue where users weren't receiving emails after setting up **Mail Settings** ([#55070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089394047)). * Fixed an issue where there was a discrepancy between **EZ-Commit** and **Commit templates** while retrieving **Email Template** metadata members ([#61696](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099121314)). * Fixed an issue where **Merge Labels** were taking much longer than expected ([#62625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100474287)). * Fixed an issue where user tried to commit the changes without validation and UI displayed an error `Another commit is in progress` ([#61930](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099562127)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the **Commits History** page ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Fixed an issue where **Merge** was not auto-rejected when validation criteria was not met ([#62287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100008338)). * Enhanced **nCino** by adding an option to specify **Baseline Revision** in **Continuous Integration** for **Version Control** to perform feature deployments ([#43642](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073759034) and [#44506](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074950579)). * Enhanced **nCino** by allowing users to deploy nCino **CI build** to multiple target sandboxes ([#41763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070674305)). * 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 a UI bug in **Profile Manager** where **User Permissions** differences are shown in the report but not in the UI ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Enhanced the **Release Label** creation by increasing the range of retrievable commit history ([#61714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099129934)). * Fixed an issue where user was unable to use **Release Labels** to perform **Deployment**, and it failed while trying to **Create Artifact** ([#59429](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096450140)). * Fixed an issue where users with non-admin access were unable to register branches in **EZ-Commit** since upgrading to version 22.3 ([#62723](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100650673), [#62949](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101016055), [#62979](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010456), and [#62969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010302)). * 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 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 ([#61403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098537015)). * 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 ([#60531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097360001)). * Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs ([#61079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097987087)). * Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in **EZ-Commit** ([#56188](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091240174)). * Fixed an issue where user was customer trying to register a **Salesforce Org** with **Custom URL** but it was failing with an error ([#62192](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099509581)). * Fixed an issue where user was unable to remove **Revisions**/**Commit Labels** from a **Release label** ([#59152](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096005470) and [#61578](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098950203)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed an issue where user user uploaded a **YAML file** to retrieve the **Vlocity components** but ALL metadata types were retrieved and displayed ([#61181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248158)). * Fixed an issue where the same merge could be approved and rejected by different users simultaneously ([#60859](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097787146)). * 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 user was unable to download success/failure reports in **Single Dataloader** ([#61551](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098913200)). * 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 ([#59082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096042290)). * Fixed an issue where **Dependency** order defined in **json** file was being changed on every commit but it was not supposed to ([#57731](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556797)). * Fixed an issue where **Create Artifact** was not working as expected while using **Release Label** ([#61607](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098932152)). * 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 ([#61751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248378)). * Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes ([#61736](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099207347)). * 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: * Fixed an issue where SFDX module creation log shows that deployment is successful but the module creation had failed ([#57318](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092768029)). * Fixed an issue with **Backup from Org CI Jobs** where **PermissionSet User Permissions** were being deleted ([#59674](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096685144)). * Fixed an issue where **Org to Org Deployment** for **Profiles** including **Deploy Profile Access Settings for selected components only** was not working as expected ([#60559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097375154)). * Fixed an issue where **Post Destruct** fields were also added to **Pre Destruct** despite the user setting it to post ([#61162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248005)). * Fixed an issue where user set the **Max depth** value as '0' under **Vlocity Configuration Settings** but it was retrieving all level dependancy components ([#57501](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093212471)). * Fixed an issue with DataLoader where the **Credit Memo Template** migration was not deploying after user upgraded their instance ([#57676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093470003)). * Fixed an issue where user selected **Custom Metadata** members (records), but **EZ-Commit** was failing to generate **File Diff** with `Null` error ([#59709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096706005)). * Fixed an issue where **Merge** was taking longer than usual, and then failing with `Null Exception` ([#60757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097574427)). * Fixed an issue where **EZ-Commits** and **EZ-Merges** were taking much longer than usual ([#58098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094302292)). #### 29 January 2023 **(ARM v22.2.15)**\ 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` ([#60597](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097399881)). * 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` ([#59050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095999076)). * Fixed an issue where **Reports** deployment validation failed in **EZ-Merge** but was successful in **EZ-Commit** and **Deployment** modules ([#57714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093587003)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error `null` at **Diff** ([#59919](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096907001)). * 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: * 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 ([#59359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096219627)). * Fixed an issue where commit was running for longer and remained **in-progress** and **validation check log** is also in progress ([#59199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096003630)). * Fixed an issue where commits with SFDX metadata structure are **failing** in metadata **retrieval stage** ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * Fixed an issue where user couldn't create a managed package with the selected ancestor ([#59044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095985421)). * Fixed an issue where **CI Job** was occasionally failing with the error `BUILD FAILED` ([#57647](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093370172)). * Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user ([#55438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089958034)). * 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 ([#59040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095982206)). * 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 ([#58044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094164003)). * Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error: `Invalid Private Key` ([#59244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096134293)). * Fixed an issue where user has created a Commit label but it was not available while trying to perform an **EZ-Merge** ([#55176](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089550097)). * Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff ([#59114](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096048883)). * Fixed an issue where user was getting an error while trying to create a new branch in GitHub ([#59193](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096138920)). For more information, click [here](https://knowledgebase.autorabit.com/docs/faqs-version-control?highlight=$%20ssh-keygen%20-t%20rsa%20-b%204096%20-C#why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh). * 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 ([#59402](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096425001)). * 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` ([#59028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095867179)). * 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 ([#58998](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095876003)). * 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 ([#59014](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095898340)). * 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 an issue where **Merge validation** failed to process when there was a **Flow** metadata ([#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556)). * Fixed an issue with user received 6 notifications for a failed **CI Job** instead of 1 ([#58436](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095199003)). * Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error: `Lower Region` ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * 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 ([#51268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085726862)). * Fixed an issue where while performing destructive changes in **EZ-Commit**, it was creating **package.xml** in root path folder in **SFDX** structure ([#57868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093790001)). * 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 an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189)). * Fixed a build bug where **CI Job Build** was failing during package preparation **step 5** failing while commiting **DecisionMatrixDefinition** and throwing an error ([#58376](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095049142)). * 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\ ([#58478](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095251543)). * Fixed an issue where generating **Diff** for a **Commit Label** was taking much longer than expected ([#55220](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591780)). * Fixed an issue where **Code coverage** job was running **4 hours** earlier than scheduled every time services were restarted ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * 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 user was unable to create **Environment Provisioning** templates for multiple component types ([#57898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093797903)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). * Fixed an issue where AutoRABIT **SSH credentials** were failing with an error `Auth failed` while trying to connect with **AWS CodeCommit** ([#53694](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087714369)). * Fixed an issue where **EZ-Commit Diff** was taking approximately 4 hours while **Refactoring CustomField**, which is much longer than expected ([#56650](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091636348)). * 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 **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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: * 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 ([#53980](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087981132)). * 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 ([#55995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091129007)). * Fixed an issue where **Profile Diff** is working as expected for **Selective Deployment**, but not while using the same profile in the profile manager ([#52868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087005140)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189), [#55754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090487029)). * Fixed an issue where **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). #### 11 December 2022 **(ARM v22.2.8)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue where multiple metadata types where not able to retrieve ([#56668](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091694003)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * 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). * Fixed an issue where user was creating the **feature template** for some of the **nCino** objects but it was taking too long to **retrieve** the objects from **Source Org** ([#53915](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087934809)). * 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 **Flexi pages** were not picked up in a **CI Job** even after the commit with same set of metadata was excluded by user ([#54518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088461033)). * Fixed an issue where **Abort** function to stop **Provar** jobs was not working as expected ([#55511](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090032787)). * Fixed an issue where production backup **CI Job** was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error `java.lang.NullPointerException: null` ([#55213](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591408)). * Fixed an issue where all **Slack Notifications** were selected by default and user was unable to unselect all at once ([#55817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090727146)). * Fixed an issue where **SFI components** were not being fetched both in **Commit** and **Deployment** modules ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue with **DataLoader Pro** where user selected a field as **External ID** in a job and saved it, but the saved entry was lost and user was unable to map it ([#55011](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089299148)). * Fixed an issue where **Deployment validation** in **Prevalidation Commit** fails because profile validation automatically picks **User Permissions** even though **Remove User Permissions** option is selected ([#54941](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088985107)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where **Release Label Merge** was failing and throwing the following error: `fatal: bad revision` ([#55000](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089278434)). * Fixed an issue with **EZ-Commit** where user was unable to upload a **Custom YAML** file ([#55826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090770005)). * Fixed an issue where the **Vlocity Component** option under **Fetch Changes** is not populating for sub-users with roles that have all permissions and access ([#54962](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089032619)). * 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). * Fixed an issue where user was performing a merge operation and validating the package on the **target org** but the validation was failing with multiple errors ([#55541](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090145025)). #### 27 November 2022 **(ARM v22.2.6)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was trying to migrate **Products**, **Pricebooks**, and its entries but the **Deploy** was failing for **Pricebook** and throwing the following error: `INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--` ([#55263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089652641)). * Fixed an issue with **nCino** where user was trying to create a custom feature template including **product objects** as well as **product line** but the deployment was failing with the following error: `Required fields are missing: [LLC_BI_Product_Line_c]` ([#51209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085641324)). * Fixed an issue with **nCino** where **CI Job** was stuck in **Build Success** status ([#53605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087564091)). * Fixed an issue where **CI Job** build was failing with a **NullPointerException** ([#55204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089616148)). * Fixed an issue where the **Repository Branch** was unavailable to select to run the **Merge** process after selecting **On successful deployment** option ([#55537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090158003)). * Fixed an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * Fixed an issue with **EZ-Commit** where user was trying to perform a **destructive commit** using **Autodraft** option, but was unable to select **deleted components** under the **Deleted** tab ([#55507](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089979335) and [#55651](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090293003)). * Fixed an issue where user was getting a **NullPointerException** when trying to resolve a **Merge conflict** ([#55137](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089410195)). * Fixed an issue with **nCino** where the **UTF-8 Encoding Flag** was not displayed in the pop-up during **Re-Deployments** (internal ticket). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was able to create a **Delegated Group** but was unable to add a **Delegated Admin** user to the group using **Environment Provisioning** ([#55266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089705014)). #### 20 November 2022 **(ARM v22.2.5)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing **Prevalidation Commit** but commits in the repository have different components than the ones shown in **Diff** before the commit ([#52307](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086491044)). * Fixed an issue with **Install an Unlocked or Managed Package from a Version Control Branch** where CI job getting an exception and the build status was showing as successful but the **Scratch Org** was not being created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **CI Job** shows that the ALM status has been updated successfully but on **Azure ALM** it is not updated ([#54669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088657005)). * Fixed an issue where **Test Automation CI Jobs** were failing due to **InitializeDriver** & **quit methods** ([#45878](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077372830)). * Fixed a bug where user was able to access certain branches in the **Deployment** module to which he did not have access under **Profile Settings** ([#54879](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089011291)). * Fixed an issue with **CI Jobs** where the build failed with **Checkout** conflict for an **.svg file** ([#54172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088252005)). * 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). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was unable to add another branch to **Azure** in the **ALM MGMT Repository mappings** ([#55133](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089433593)). * Fixed an issue where the **Destructive** commit **Diff** was including more components than selected ([#54795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088780309)). * Fixed an issue where a merge got stuck for a long time and the **Commit ID** was reflected in **BitBucket** but unavailable to select for release label deployment ([#52964](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087060140)). #### 13 November 2022 **(ARM v22.2.4)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the user was trying to create an **Extract** process in **DataLoader** but after validating the query the application was throwing an error: `not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted` ([#54648](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088630160)). * Fixed an issue with **CI Jobs** where **External Credential** metadata was not identified during **Deployment** ([#53939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087955144)). * Fixed a UI bug where user was performing an **org to org deployment** using **package.xml** file and the components were successfully deployed and also verified on Salesforce target, but the status on ARM was still **In-Progress** ([#50459 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375)and [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue with **DX CI Jobs** where user is not getting details of faulty commit revisions in the notification ([#54063](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088015242)). * Fixed an issue with **Profile Manager** where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend ([#53706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704963)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * Fixed a bug where **Merge Commit** validation was not considering special characters like %,#, etc. as a value and throwing the following error: `Merge comment should not contain an empty space` ([#54512](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088479003)). * Fixed an issue where ARM was slowing at different phases in the **EZ-Commit** module ([#50503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084910726)). * Fixed an issue where Git check response was not delivered for validation **CI Job** even though user has added the comment for a **Pull request** in the remote repository ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). #### 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 an issue where the **Deployment** module page was loading very slowly and then throwing an error: `Page Unresponsive` ([#53675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704191)). * 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 with the **Deployment** module where user initiated a **Deployment** without selecting the **Do not Include Skip Members** option, but this option was auto-enabled and skipped the member at the time of deployment ([#53747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087811296)). * Fixed an issue with **Modularization** where user creating a module and selected the **Ignore installed components** check box but the installed components were not ignored causing the deployment to fail ([#53703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087755311)). * Fixed an issue with **AccelQ Test Automation** where test case fails but the error details pop-up is not showing the details of the error that caused the failure ([#54224](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088281589)). * Fixed an issue where user is setting up the **Apex PMD rules** as **Priority 1** & **Priority 2** in the **CI Job** but the SCA Report is showing the **Priority 3, P4 & P5** which wasn't selected ([#54017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087969396)). * Fixed an issue where the **Git** check response was not delivered for a validation **CI Job** ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). * Fixed an issue where the **Deleted Report** metadata components were not found in the **EZ-Commit** ([#53119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087247293)). * 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 an issue where triggering a **CI Job** in **Objects** was resulting in an ambiguous error in the **CI Job Build** ([#53066](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087190013), [#52955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087099268), [#53631](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087579265)). * Fixed an issue where all **CI Jobs** were failing and throwing the error: `Validation Checking failed Version Control Mappings not found for Repo: SA Repo and Branch: bugfix/Bugfix_PQT_Rel_Validation` ([#52945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087098136), [#52950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087101272), [#52757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086925007)). * 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 Hub**dropdown list was displayed in the **Deploy** section (internal ticket). * Fixed an issue with **AccelQ** where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as **Not Run** instead of **Success** or **Failure** even if the jobs have been successfully completed ([#50181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084509148)). * Fixed a **Page Unresponsive** issue while creating a new **Release Label** by adding a feature to list limited results on each page ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where a merge got auto-approved and was in **Merged Not Commit** status ([#52398](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086586845), [#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed an issue where user created a **Release Label**, performed a **Merge** operation, committed changes to the target branch, and created two revisions in the **Github** branch.\ But ARM was throwing an error while applying merge stage and only on the revision generated ([#51364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085859319)). * Fixed an issue where **EZ-Commit** initiation was stuck with the error: `Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out` ([#52550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086834002)). * Fixed an issue where user was not able to select the orgs in the **EZ-Commit** drop down ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001), [#51219](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085620605)). * 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 **CI Job** was successful but was including components from **GIT revisions** from old deleted branches ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error: `Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field` ([#48626](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082749181)). * Fixed an issue where **CI Job** was getting an exception, **Build** status was showing as *successful*, but **Scratch Org** not getting created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **Managed Package** was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version ([#48311](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223305)). * 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 **Custom Template Creation** failed and the **Logs** did not record the reason for failure ([#52147](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086277150)). * Fixed an issue where the **Created By** value was not visible in **Dataloader**, **Dataloader Pro DL Config**, and the **TestEnv History** page (internal ticket). * Fixed an issue where the **Comment Box** was not accepting more than **100 characters** while rejecting a **Commit**, but was working as expected while approving a commit ([#51384](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085891476)). * Fixed an issue with **Apex Test Class Config.** in **SF MGMT ORG** where the **Fetch Current Set**, **Add Manually**, and **Auto Populate** options were throwing an error: `Error 200` ([#52408](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086578687), [#52328](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086485900)). * Fixed an issue where user set **Commit validation Criteria** to **Auto reject after 7 days** but the older Pre-validation commits are not auto rejected after 7 days ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user cannot add **Skip** members manually and it is failing due to **special characters** being included ([#53139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087266642)). #### 16 October 2022 **(ARM v22.2.0)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where skipped members were present in many components but only **Report Metadata** was failing during **Deployment** ([#51040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085433814)). * Fixed an issue where **CI Job** was getting stuck in **In Progress** status but the log showed that the deployment was successful ([#51140](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085583019)). * Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time ([#50630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085136003)). * Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in **In Progress** status in ARM ([#50435](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084823763)). * Fixed an issue where user raised a **Pull request** on a branch and was getting a webhook response, but CI Job build was not triggered ([#51592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085996953)). * Fixed a UI bug where **Add to dashboard** button was unavailable for widgets ([#52333](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086514169)). * 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). * Fixed an issue where **Custom Email Template** was not working for **Email notifications** ([#47484](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080506162)). * Fixed an issue where user was testing **SSH Connection** but the application was throwing an error: `invalid privateKey` ([#50940](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371198)). * Fixed an issue with **nCino** where **UI Log** was not generated for failed CI Jobs ([#50442](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084795478)). * Fixed an issue where **New EZ-Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue where **Audit Logs** were not generating via **Postman Services** ([#50221](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084545179)). * Fixed an issue where **Commits** were getting stuck and throwing the following error: `No credential have been found with Name:git`, but was not reflecting in the UI log ([#51713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086127001)). * Fixed an issue with **Workspace Settings** where unused workspaces were not being cleared despite selecting **Clear all workspaces which are not used in last 7 days** ([#50164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084481079)). * Fixed an issue where user was performing a **Prevalidation EZ-Commit** and found that some **Layout Assignments** were deleted though those layouts were not part of the commit ([#50945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371456)). * Fixed an issue with **nCino** where migration was failing due to errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). *** ## **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.
[**Read more →**](/product-guides/arm/arm-features/version-control/ez-merge/squash-and-merge) #### 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.
[**Read more →**](/product-guides/arm/arm-features/salesforce-dx/import-an-unlocked-managed-package) **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. ![Dev hub.gif](https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/Dev%20hub.gif) [**Read more →**](/product-guides/arm/arm-features/salesforce-dx/registering-a-devhub) #### 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.
[**Read more →**](/product-guides/arm/arm-features/automation-and-ci/ci-job-rollback) *** ### 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.
[**Read more →**](/product-guides/arm/arm-administration/user-management/users-roles-and-permissions) #### 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.
[**Read more →**](/product-guides/arm/arm-features/version-control/merge-approvals) #### 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: * Fixed an issue where wrong **timezone** region was displaying for users ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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 where **validation jobs** on **Pull Requests** weren't getting triggered ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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 **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue where multiple metadata types where not able to retrieve ([#56668](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091694003)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * 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). * Fixed an issue where user was creating the **feature template** for some of the **nCino** objects but it was taking too long to **retrieve** the objects from **Source Org** ([#53915](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087934809)). * 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 **Flexi pages** were not picked up in a **CI Job** even after the commit with same set of metadata was excluded by user ([#54518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088461033)). * Fixed an issue where **Abort** function to stop **Provar** jobs was not working as expected ([#55511](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090032787)). * Fixed an issue where production backup **CI Job** was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error `java.lang.NullPointerException: null` ([#55213](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591408)). * Fixed an issue where all **Slack Notifications** were selected by default and user was unable to unselect all at once ([#55817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090727146)). * Fixed an issue where **SFI components** were not being fetched both in **Commit** and **Deployment** modules ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue with **DataLoader Pro** where user selected a field as **External ID** in a job and saved it, but the saved entry was lost and user was unable to map it ([#55011](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089299148)). * Fixed an issue where **Deployment validation** in **Prevalidation Commit** fails because profile validation automatically picks **User Permissions** even though **Remove User Permissions** option is selected ([#54941](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088985107)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where **Release Label Merge** was failing and throwing the following error: `fatal: bad revision` ([#55000](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089278434)). * Fixed an issue with **EZ-Commit** where user was unable to upload a **Custom YAML** file ([#55826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090770005)). * Fixed an issue where the **Vlocity Component** option under **Fetch Changes** is not populating for sub-users with roles that have all permissions and access ([#54962](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089032619)). * 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). * Fixed an issue where user was performing a merge operation and validating the package on the **target org** but the validation was failing with multiple errors ([#55541](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090145025)). #### 27 November 2022 **(ARM v22.1.35)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was trying to migrate **Products**, **Pricebooks**, and its entries but the **Deploy** was failing for **Pricebook** and throwing the following error: `INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--` ([#55263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089652641)). * Fixed an issue with **nCino** where user was trying to create a custom feature template including **product objects** as well as **product line** but the deployment was failing with the following error: `Required fields are missing: [LLC_BI_Product_Line_c]` ([#51209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085641324)). * Fixed an issue with **nCino** where **CI Job** was stuck in **Build Success** status ([#53605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087564091)). * Fixed an issue where **CI Job** build was failing with a **NullPointerException** ([#55204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089616148)). * Fixed an issue where the **Repository Branch** was unavailable to select to run the **Merge** process after selecting **On successful deployment** option ([#55537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090158003)). * Fixed an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * Fixed an issue with **EZ-Commit** where user was trying to perform a **destructive commit** using **Autodraft** option, but was unable to select **deleted components** under the **Deleted** tab ([#55507](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089979335) and [#55651](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090293003)). * Fixed an issue where user was getting a **NullPointerException** when trying to resolve a **Merge conflict** ([#55137](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089410195)). * Fixed an issue with **nCino** where the **UTF-8 Encoding Flag** was not displayed in the pop-up during **Re-Deployments** (internal ticket). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was able to create a **Delegated Group** but was unable to add a **Delegated Admin** user to the group using **Environment Provisioning** ([#55266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089705014)). #### 20 November 2022 **(ARM v22.1.34)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing **Prevalidation Commit** but commits in the repository have different components than the ones shown in **Diff** before the commit ([#52307](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086491044)). * Fixed an issue with **Install an Unlocked or Managed Package from a Version Control Branch** where CI job getting an exception and the build status was showing as successful but the **Scratch Org** was not being created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **CI Job** shows that the ALM status has been updated successfully but on **Azure ALM** it is not updated ([#54669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088657005)). * Fixed an issue where **Test Automation CI Jobs** were failing due to **InitializeDriver** & **quit methods** ([#45878](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077372830)). * Fixed a bug where user was able to access certain branches in the **Deployment** module to which he did not have access under **Profile Settings** ([#54879](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089011291)). * Fixed an issue with **CI Jobs** where the build failed with **Checkout** conflict for an **.svg file** ([#54172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088252005)). * 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). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was unable to add another branch to **Azure** in the **ALM MGMT Repository mappings** ([#55133](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089433593)). * Fixed an issue where the **Destructive** commit **Diff** was including more components than selected ([#54795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088780309)). * Fixed an issue where a merge got stuck for a long time and the **Commit ID** was reflected in **BitBucket** but unavailable to select for release label deployment ([#52964](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087060140)). #### 13 November 2022 **(ARM v22.1.33)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the user was trying to create an **Extract** process in **DataLoader** but after validating the query the application was throwing an error: `not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted` ([#54648](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088630160)). * Fixed an issue with **CI Jobs** where **External Credential** metadata was not identified during **Deployment** ([#53939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087955144)). * Fixed a UI bug where user was performing an **org to org deployment** using **package.xml** file and the components were successfully deployed and also verified on Salesforce target, but the status on ARM was still **In-Progress** ([#50459 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375)and [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue with **DX CI Jobs** where user is not getting details of faulty commit revisions in the notification ([#54063](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088015242)). * Fixed an issue with **Profile Manager** where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend ([#53706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704963)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * Fixed a bug where **Merge Commit** validation was not considering special characters like %,#, etc. as a value and throwing the following error: `Merge comment should not contain an empty space` ([#54512](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088479003)). * Fixed an issue where ARM was slowing at different phases in the **EZ-Commit** module ([#50503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084910726)). * Fixed an issue where Git check response was not delivered for validation **CI Job** even though user has added the comment for a **Pull request** in the remote repository ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). #### 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 an issue where the **Deployment** module page was loading very slowly and then thrwing an error: `Page Unresponsive` ([#53675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704191)). * 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 with the **Deployment** module where user initiated a **Deployment** without selecting the **Do not Include Skip Members** option, but this option was auto-enabled and skipped the member at the time of deployment ([#53747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087811296)). * Fixed an issue with **Modularization** where user creating a module and selected the **Ignore installed components** check box but the installed components were not ignored causing the deployment to fail ([#53703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087755311)). * Fixed an issue with **AccelQ Test Automation** where test case fails but the error details pop-up is not showing the details of the error that caused the failure ([#54224](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088281589)). * Fixed an issue where user is setting up the **Apex PMD rules** as **Priority 1** & **Priority 2** in the **CI Job** but the SCA Report is showing the **Priority 3, P4 & P5** which wasn't selected ([#54017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087969396)). * Fixed an issue where the **Git** check response was not delivered for a validation **CI Job** ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). * Fixed an issue where the **Deleted Report** metadata components were not found in the **EZ-Commit** ([#53119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087247293)). * 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 an issue where triggering a **CI Job** in **Objects** was resulting in an ambiguous error in the **CI Job Build** ([#53066](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087190013), [#52955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087099268), [#53631](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087579265)). * Fixed an issue where all **CI Jobs** were failing and throwing the error: `Validation Checking failed Version Control Mappings not found for Repo: SA Repo and Branch: bugfix/Bugfix_PQT_Rel_Validation` ([#52945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087098136), [#52950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087101272), [#52757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086925007)). * 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 Hub**dropdown list was displayed in the **Deploy** section (internal ticket). * Fixed an issue with **AccelQ** where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as **Not Run** instead of **Success** or **Failure** even if the jobs have been successfully completed ([#50181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084509148)). * Fixed a **Page Unresponsive** issue while creating a new **Release Label** by adding a feature to list limited results on each page ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where a merge got auto-approved and was in **Merged Not Commit** status ([#52398](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086586845), [#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed an issue where user created a **Release Label**, performed a **Merge** operation, committed changes to the target branch, and created two revisions in the **Github** branch.\ But ARM was throwing an error while applying merge stage and only on the revision generated ([#51364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085859319)). * Fixed an issue where **EZ-Commit** initiation was stuck with the error: `Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out` ([#52550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086834002)). * Fixed an issue where user was not able to select the orgs in the **EZ-Commit** drop down ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001), [#51219](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085620605)). * 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 **CI Job** was successful but was including components from **GIT revisions** from old deleted branches ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error: `Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field` ([#48626](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082749181)). * Fixed an issue where **CI Job** was getting an exception, **Build** status was showing as *successful*, but **Scratch Org** not getting created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **Managed Package** was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version ([#48311](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223305)). * 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 **Custom Template Creation** failed and the **Logs** did not record the reason for failure ([#52147](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086277150)). * Fixed an issue where the **Created By** value was not visible in **Dataloader**, **Dataloader Pro DL Config**, and the **TestEnv History** page (internal ticket). * Fixed an issue where the **Comment Box** was not accepting more than **100 characters** while rejecting a **Commit**, but was working as expected while approving a commit ([#51384](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085891476)). * Fixed an issue with **Apex Test Class Config.** in **SF MGMT ORG** where the **Fetch Current Set**, **Add Manually**, and **Auto Populate** options were throwing an error: `Error 200` ([#52408](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086578687), [#52328](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086485900)). * Fixed an issue where user set **Commit validation Criteria** to **Auto reject after 7 days** but the older Pre-validation commits are not auto rejected after 7 days ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user cannot add **Skip** members manually and it is failing due to **special characters** being included ([#53139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087266642)). #### 16 October 2022 **(ARM v22.1.29)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where skipped members were present in many components but only **Report Metadata** was failing during **Deployment** ([#51040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085433814)). * Fixed an issue where **CI Job** was getting stuck in **In Progress** status but the log showed that the deployment was successful ([#51140](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085583019)). * Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time ([#50630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085136003)). * Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in **In Progress** status in ARM ([#50435](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084823763)). * Fixed an issue where user raised a **Pull request** on a branch and was getting a webhook response, but CI Job build was not triggered ([#51592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085996953)). * Fixed a UI bug where **Add to dashboard** button was unavailable for widgets ([#52333](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086514169)). * 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). * Fixed an issue where **Custom Email Template** was not working for **Email notifications** ([#47484](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080506162)). * Fixed an issue where user was testing **SSH Connection** but the application was throwing an error: `invalid privateKey` ([#50940](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371198)). * Fixed an issue with **nCino** where **UI Log** was not generated for failed CI Jobs ([#50442](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084795478)). * Fixed an issue where **New EZ-Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue where **Audit Logs** were not generating via **Postman Services** ([#50221](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084545179)). * Fixed an issue where **Commits** were getting stuck and throwing the following error: `No credential have been found with Name:git`, but was not reflecting in the UI log ([#51713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086127001)). * Fixed an issue with **Workspace Settings** where unused workspaces were not being cleared despite selecting **Clear all workspaces which are not used in last 7 days** ([#50164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084481079)). * Fixed an issue where user was performing a **Prevalidation EZ-Commit** and found that some **Layout Assignments** were deleted though those layouts were not part of the commit ([#50945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371456)). * Fixed an issue with **nCino** where migration was failing due to errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). #### 09 October 2022 **(ARM v22.1.28)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue with **nCino** where user was getting errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). * Fixed an issue where user noticed discrepancy in the **Conflict Resolution Log** ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). #### 02 October 2022 **(ARM v22.1.27)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where components were successfully deployed, but deployment status was still showing **In-Progress** in ARM ([#50459](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375), [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where CI Jobs were getting stuck and throwing the following error: `Too many open files` ([#44319](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074784001), [#49273](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074784001)). * Fixed an issue where **email notification** wasn't sent for some of the **CI Jobs** ([#48028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081639899)). * Fixed an issue where the Custom label and remote site setting URLs were not getting updated by ARM through **Environmental Provisioning** ([#49612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083684001)). * Fixed an issue with **Vlocity** where selecting one component from a GIT repository was causing all the components from the category to get selected ([#49806](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084007005)). * Fixed an issue with **ALM Mgmt.** where item status was not retrieved properly for **Merge Request**, but was working as expected for **EZ-Merge** ([#50628](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085133005)). * Fixed a UI bug where **Release Labels** were showing duplicate **Time Stamps** ([#51205](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085689003)). * Fixed an issue where old **Commit Labels** were not getting auto-rejected after 7 days as the user had configured under **Commit Validation Criteria** ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user was getting an error pop-up on the **Permissions** and the **SF ORG MGMNT** pages, and the SF org and VC repo mappings were lost in the profile section of a role ([#49108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083164265)). #### 26 September 2022 **(ARM v22.1.26)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where **Provar** test job was throwing an error while in queue ([#49797](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083986945)). * 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). * Fixed an issue with **Branching Baseline** where some of the custom object metadata nodes were deleted from the repository ([#47239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080102001), [#47270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080113166)). * Fixed an issue with **EZ-Merge** where **Diff** was not being generated even though there were file changes between the source branch and the destination branch ([#50323](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084689471)). * Fixed a UI bug in **DataLoader** where user was switching from **Graphical View** to **Grid View** but **Graphical View** options were still being displayed ([#50431](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084822478)). * Fixed an issue with **nCino** where the **Insert/Update With Null Values** option was not getting updated for CI jobs ([#50259](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084641005)). * Fixed an issue where users were unable to **re-authenticate** the **Salesforce Org** after refreshing their personal sandboxes ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001)). * Fixed an issue where **Environment Provisioning Template** was not functioning as expected for **Custom Labels** containing URL ([#47892](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081421793)). * Fixed an issue with **EZ-Commit** where user was trying to deploy **Permission Sets** and **Profiles** together, and the pre-validation process was stuck in **In-Progress** status ([#49340](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083456001)). * Fixed an issue where old **Commit Labels** were not getting auto-rejected as configured ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). #### 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). * Fixed an issue where user was unable to reset the AutoRABIT password, and was getting an error: `getAttribute: Session already invalidated` ([#50145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084391472)). * Fixed an issue where **CI Jobs** was not picking the right number of components unless the user cancelled the build and retriggered it ([#47164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921675)),([#46981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079504156)). * Fixed an issue where the user tried to merge to the Dev branch but the **CI Job** failed and was throwing a **Duplicate** error ([#49661](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083729177)). * Fixed an issue where user was trying to install **Unlocked Package** via **CI Job** but it was failing and throwing the following error: `ERROR 178928269770891:275 - For input string: "0-2" java.lang.NumberFormatException: For input string: "0-2"` ([#50093](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084341003)). * Enhanced **Vlocity** loggers for **Branching Baseline** by displaying to the user **Status Count** of **Remaining**, **Success**, **Error** and **Ignored** (internal ticket). * Fixed an issue where **Test Connection** was failing on the **Version Control Summary** page under the **Admin** module ([#49299](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083372346)). * Fixed an issue with **Prevalidation Merge** by increasing the **SCA Response timeout** from **50 minutes** to **5 hours** ([#48613](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082720068)). * Fixed an issue where merging **Master Branch** with the **Production** branch was throwing the following error: `No merge head specified` ([#46594](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078825001)). * Fixed a bug where **New A-Z Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue with **Autorabit Commit Label** related to **Permission Sets Deployment** ([#48709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082892203)). #### 11 September 2022 **(ARM v22.1.24)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was selecting a single package to import, but all available package versions were being imported ([#49426](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083542359)). * Fixed an issue with **Profile Manager** where user was comparing a profile but the deployment was not starting ([#48620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082696017)). * Fixed an issue where deploying components with profiles was not working as expected and throws the following error: `Duplicate layoutAssignment:PersonAccount (PersonAccount.Person_Prospect)` ([#49021](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083082001)). * Fixed an issue where custom metadata records were not being selected during deployment ([#49167](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083203846)). * Fixed an issue in **Version Control Commit Labels** history where **Created By** and **Created Date** values were exchanged (internal ticket). * Fixed an issue where user was getting an error while trying to deploy **Vlocity Metadata** using **CI Jobs** ([#47568](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080830005)). * Fixed an issue where **Branching Baseline** was not retrieving **Workflow Metadata types** ([#49403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083447017)). * Fixed an issue where **Release Label** failed to load revisions from a particular branch and the browser was hanging and throwing an *Out of memory* error ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where **EZ-Commit** was not getting auto-rejected when **CodeScan** analysis failed, even though user select the option to run **Static Code Analysis** ([#47155](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921059)). * Fixed an issue where merge was failing at the **Validate Deploy** step even before selecting the org to validate ([#49724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083898393)). * Fixed an issue where **Layout** was being removed from the **Diff** while deploying **Profile** changes with related **Layouts** and **RecordTypes** ([#48268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082045983)). * Fixed multiple issues with **CodeScan<>ARM** Integration ([#49605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083671017)). #### 04 September 2022 **(ARM v22.1.23)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing a new deployment but getting an error when using the **Compare Orgs & Deploy** button ([#48707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860460), [#48676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860003), [#48737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082918005), [#48734](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082914003)). * Fixed an issue where the CI job was not working as expected and throws the following error: `java.lang.NullPointerException: null` ([#48706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860315)). * Fixed an issue where few fields were not being analyzed in CodeScan SFDX. User was selecting Custom Fields, Apex Classes, and Record Types in E-Z Commit, but Static Code Analysis was only Apex Classes ([#48547](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082584398)). * Fixed an issue where dashboards and reports were changing to **Destructive** and getting deleted ([#48119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081915009)). * Fixed an issue where discrepancies for **Document**, **Assignment Rule** and **AutoResponseRule** metadata types content was observed in **package.xml** for SFDX and non-SFDX CI Jobs ([#47017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079534439)). * Fixed an issue where the Dataloader Pro Jobsfailing and throws the following error: `java.lang.NullPointerException: null` ([#49170](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083182317), [#49283](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083331025), [#49331](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083407003), [#49199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083182597)). * Fixed an issue where nCino CI Jobs via RBC were failing during parallel deployment. Instead of falling in queue, the first job was failing while the other succeeded, and the user had to retrigger the failed job ([#47335](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080272507)). * 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 after upgrading the AR instance, deployment jobs kept removing the custom metadata access on the **Permission Sets** ([#48296](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082147005)). * Fixed an issue where **Org difference** jobs were running for more than 24 hours ([#48324](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223730)). * Fixed an issue where Environment provisioning template was not working when trying to update custom label values that contain URL, and the incorrect value was being updated in the org ([#47892](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081421793)). * 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 user was trying to validate the commit using single revision, but was getting an **Empty Package** error even though there were changed files in the commit ([#47530](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080730150)). * Fixed an issue where DataLoader Pro jobs were failing with an error **duplicate value found: SetupOwnerId duplicates value on record with id** for the custom setting **Multichannel\_Settings\_vod\_\_c**, even though there is no field mapped with name **SetupOwnerId** ([#48230](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081981779)). * 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 where EZ Commit Logs and Change Labels were not displaying for some of the commit labels ([#45364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076464250)). * Fixed an issue where the user was not able to see the deployment report because the build was failing when only custom fields were being selected without the related object ([#45663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077048275)). * Fixed an issue where merge request was being auto rejected if the selected approver was no longer with AR ([#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed a bug where user had enabled Squash and Merge while performing a new merge, but the Squash and Merge option was not displayed after the Merge Request was approved ([#48246](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082046388)). * Fixed an issue in CI Jobs deployments where Bulk API option for **Attachments** was throwing an error (internal ticket). * Fixed an issue where **nCino CI Jobs** were failing the first time and completing the second time successfully ([#46545](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078644141)). #### 21 August 2022 **(ARM v22.1.21)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the CI job build was getting stuck in **In-progress** status ([#47934](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081483565)). * Fixed an issue where **RunSpecifiedTest** level execution was failing with Test classes dependency errors ([#47666](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081029378)). * 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). * Fixed an issue where entire branch merge was failing with multiple common ancestor errors ([#47334](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080237436)). * 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 where Standard fields are not retreiving when included in **package.xml**, and retrieving through **E-Z Commit (Package Manifest)** option ([#47961](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081505333)). * 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 with the **Profile Manager** where the user were unable to select the default app permission during the profile deployment ([#47462](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080494273)). * Fixed an issue where the merge revisions were missing from the CI jobs ([#46862](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079287922)). * Fixed an issue where the users were unable to commit **Vlocity card** from one org to another org in ARM ([#44938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075743019)). * 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). * Fixed an issue where the ALM integration was not working when the files are pushed with special characters in their name ([#47414](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080454001)). * Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS ([#46844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079276142)). * Fixed an issue where the users while deploying a destructive XML file from one sandbox to another, is getting auto rejected ([#47714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081149440), [#47747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081187577)). #### 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 an issue where after triggering the CI job, the **File Changes** and **Check-ins** results mismatched ([#40119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067784313)). * Fixed an issue where the package created to deploy ExperienceBundle misses some of the folder and metadata files contained in it ([#46692](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079024001)). * Fixed the below deployment-related issues: * Unable to find commits that are part of a Release Label while performing a new deployment ([#47337](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080246444)) * Unable to retrieve components from a Release Label during deployment ([#47534](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080713440)) * Changes are not deployed to the destination org which are part of a Release Label ([#46908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079358877)) * Fixed an issue where the users while deploying a destructive XML file from one sandbox to another, is getting auto rejected ([#47714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081149440), [#47747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081187577)). * Fixed an issue where the deployment failed to initiate when search and substitute rules are selected ([#47802](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081320007)). * Fixed an issue where the status log .csv files are inconsistent for deployment via CI jobs (internal ticket). * Fixed an issue where the users were unable to process the migration of RBC object (nForce\_\_Views\_\_c) using the nCino CI jobs, feature template migration, or the Dataloader Pro jobs ([#47098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079761055)). * Fixed an issue where while deploying a **nCino-User Interface** template, only partial records are deployed and no deployment logs are generated ([#47494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080488668)). * Fixed an issue where the users, while performing an EZ-Commit by enabling the run SCA option, the CodeScan analysis is getting failed, but EZ-Commit is not getting auto-rejected ([#47155](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921059)). #### 31 July 2022 **(ARM v22.1.18)**\ This is a maintenance release. The following items were fixed and/or added: * Upgraded the Spring and AWS libraries on ARM for addressing the Spring vulnerability ([#46970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079471289)). * Fixed an issue where the users were unable to login to ARM via SSO (internal ticket). * Fixed an issue where the ARM is not able to fetch any component using the release label ([#46662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078894834)). * Fixed an issue where the baselining of branches has wiped out the records types for many records, and the users were forced to do manual changes to the Record types ([#42719](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072309163)). * Fixed an issue where the ARM allows to associate only one branch to one package, and not able to build beta package versions from various branches. This is now fixed ([#46841](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262193)). * Fixed an issue where the CI job, while deploying manage packages, is installing all the manage packages instead of installing a single package ([#46832](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262054)). * Fixed an issue where the links on the **CI Job log** screen are redirected to the user's login page instead of redirecting to user's Salesforce org screen ([#47151](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079912283)). * Salesforce API version 55 (Beta support) is upgraded. The label is modified throughout ARM application to Salesforce API version 55.0 ([#47404](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080386152)). * Duplicate classes from the ARM repo has been removed (internal ticket). * Fixed an issue with the **Profile Manager** where the user were unable to select the default app permission during the profile deployment ([#47462](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080494273)). * Fixed an issue where the merge revisions were missing from the CI jobs ([#46862](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079287922)). * Fixed an issue where the users were unable to commit **Vlocity card** from one org to another org in ARM ([#44938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075743019)). * 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). * Fixed an issue where the ALM integration was not working when the files are pushedwith special characters in their name ([#47414](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080454001)). * Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS ([#46844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079276142)). * Fixed an issue where the merge was getting failed with the following error: `Fetch operation is failed due to some runtime exceptions from Git` ([#46773](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079094055)). * Fixed an issue where the username and passwords fields were not editable for users registered in ARM with basic authentication ([#47099](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079788018)). #### 24 July 2022 **(ARM v22.1.17)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where when user triggers a code coverage run in the production environment, the action takes more time than expected. Also, the total time taken for the task completion is shown inaccurate in the log report ([#44544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075040590), [#43527](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073512143)). * Fixed an issue where the CI job was not working as expected and throws the following error: `java.lang.OutOfMemoryError: Java heap space` ([#47182](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079988001), [#47190](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079988142), [#47209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080017264), [#47191](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079950166)). * Fixed an issue where the **Rollback settings** were not getting saved in the **My Account** page (internal ticket). * Fixed a bug where the users could not edit/modify their CI jobs when the build was in progress ([#43538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073573003)). * Fixed an issue with the permissionsets where instead of delta changes, the Permissionset retrieving entire file from the branch and causing dependency issues ([#46846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262334)). * 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. * Fixed an issue where while editing an existing nCino CI Job, the version control is not automatically choosing the previous repository set. This is causing the selected nCino Templates to reset ([#46952](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079432380)). * Fixed an issue where the ALM labels were missing from the ALM Label lists page ([#44410](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074860453)). * Fixed an issue where the settings related with user permissions were erased ([#46472](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078507457)). * Fixed an issue where the users when performed EZ-Commit using a package manifest file, doesn't include managed components that are in the **package.xml** file ([#47083](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079769291)). #### 17 July 2022 **(ARM v22.1.16)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the Execute Anonymous Apex metadata is not working as expected when configured as Environment Provisioning template ([#46817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079248146)). * 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 merge prevalidations were auto rejected with status as **Approval Pending** ([#46665](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078888152), [#46864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079289063)). * 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 users failed to enable the pull request support for their version control repositories ([#46336](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078290172)). * Fixed an issue where the re-use previously validated commit label takes more time to load ([#46171](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077992017)). * 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 a bug marked deployment as failed, whereas the log report says successful ([#46737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079038631)). * 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 the users could not edit/modify their CI jobs when the build was in progress ([#43538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073573003)). * Fixed an issue where entering the package installation key in `Install an Unlocked or Managed Package from Version Control Branch` CI Job gets altered when manually entered or pasted ([#46836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079265163)). * Fixed an issue where the user could not run the static code scan report on GitHub with APEX PMD Lint Scanner metadata type ([#46781](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079122007)). * Fixed an issue with the CodeScan analysis report that failed when running from ARM ([#44404](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074862389)). * Fixed an issue where the user could not fetch the latest CI job weekly reports ([#42587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072104139)). * Enhanced the Dataloader Pro, where the attachments are now supported ([#41077](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299001)). * 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 with the EZ-Merge, where merging the main branch to the dev branch failed with a `No merge head specified` error ([#46594](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078825001)). * Fixed an issue that throws `Schema as invalid` error while running the branching baseline operation ([#46593](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078805109)). * Fixed an issue where the merge failed using a single revision ([#46491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078644005), [#45764](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077211038)). * 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). * Fixed an EZ-Commit issue where additional permissions were removed from Profiles metadata type, which is not a part of the commit ([#44543](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075040441)). #### 03 July 2022 **(ARM v22.1.14)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the deployment via CI job picked unnecessary components for deletion ([#44204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074533873)). * Fixed the issue where the user when trying to delete a component in **Community** metadata type, deletes the whole Community rather than its components ([#43698](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073869007)). * Fixed an issue where DevHub registration in ARM was failing ([#46208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078056108)). * 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 deployment using **Commit/Release Label** was not working ([#46419](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078496053)). * Fixed an issue where the mapping more than one class to same test class is not recognized by ARM during commit/merge operation ([#46396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078430859), [#45159](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076223139)). * Fixed an issue where the CI job builds were failing because of missing revisions ([#45532](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076855001), [#46352](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078378003)). * Fixed an issue where the **Compact Layout** were not getting deployed and throws undefined error([#46592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078798022)). * Fixed an issue where the ALM statuses were not updated/rolled back post CI job rollback completion ([#45945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077581145)). * Fixed an issue where the destructive changes were not working as expected for the CI jobs ([#46216](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078049311)). * Fixed an issue where the ARM failed to update the Audit fields when trying to run nCino feature deployment ([#46356](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078401001)). * Fixed an issue where our internal team were not able to register their credentials on one of the ARM SAAS instances ([#46315](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078239277)). * Fixed an issue where prevalidation commits were getting failed due to credential issues. The following error was thrown `No credentials found` ([#46274](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078213003), [#46098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077754153)). * Fixed a bug where the deleted components were tagged as **UC (UnChanged)** instead of **D (Deleted)** in the EZ-Commit ([#46087](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077760173)). * 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). * Fixed an issue where the merge using single revision (baseline revision) receives the metadata schema error ([#46570](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078699087)). * Fixed an issue where the merges were getting failed and throws the `Schema is invalid for the file` error ([#45768](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077202614)). * Fixed an issue where the exported users list contained inaccurate information ([#44782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075451374)). #### 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 **Spread Template** in the **nCino** module was not working as expected ([#45078](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076003188)). * 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 the issue where the **Disable Workflow** template in the **Environment Provisioning** module was not working as expected ([#46195](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078049157)). * Fixed an issue where the creation of a scratch org were getting failed. The fix has been deployed to in this weekly release ([#46021](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077690007)). * Fixed an issue where the users were unable to use the **release label** for deployment ([#45415](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076584626)). * Fixed an issue where the users were not able to register same DevHub with two different usernames ([#46208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078056108)). * Fixed an issue where the CI Job was picking the deleted components from GitHub branch although the **Prepare Destructive Changes** checkbox was not selected. This caused the deployment to fail ([#42553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072012015)). * Fixed an issue where the users were not able to view their GitHub branches in the ARM application ([#46044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077690473), [#46353](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078386013)). * Fixed an issue where the CI Job for backing up from org to the version control branch was failing with null pointer exception error ([#45646](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072012015)). * Fixed an issue where the **EZ-Commits**, when included **Profile**, was not working as expected ([#45902](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077441170)). * Fixed an issue where the commits were getting stuck at the delta stage ([#45101](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076070023)). * 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 an issue where the Dalaloader Pro job is failing with `Required field missing on "nCino_Screen__c" object`, however the user were able to view the `Screen__c` object has a value in their source org ([#45139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076158018)). * Fixed an issue where the user were not able to save the Dataloader Pro jobs and throws the `JAVA.NullPointerException` error ([#46385](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078393786)). * 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 CI job build **ToRevision** number was mismatched in the **CI Job Results** and the **CI Build Info** page ([#45580](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076910037)). * Fixed an issue where the request parameters were empty in the **nCino Feature Commit History** screen ([#45855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077344165)). * 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 user were unable to fetch the latest CI job weekly reports ([#42587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072104139)). * Fixed an issue where the **Diff report** in the **Merge Request** was not working as expected ([#45315](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076389550)). * Fixed an issue where the user ran the branching baseline operation by excluding the Managed package components, however, the **Package.xml** file still had all the managed package components listed in it ([#45125](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076117289)). * Fixed an issue where the code coverage report was being generated at a different time than what was scheduled ([#45703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077145009)). * Fixed an issue where the exported users list contained inaccurate information ([#44782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075451374)). * 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). * Fixed an issue where the user while performing **EZ-Commit** with SonarQube code analysis was getting failed with `Failed to run the sonar-scanner: null` error ([#46070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077717988)). #### 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 branching baseline feature for profile was not working as expected ([#44615](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075179971), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed an issue where the Dataloader Pro jobs were failing with no error message ([#44620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075206808), [#44264](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074669005)). * Fixed the issue where the Dataloader Pro jobs was not working as expected ([#43966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301291)). * Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the *notes* and *attachment* of the Credit Memo from source to the destination environment ([#40990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069124041)) * 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: * Fixed an issue where the picklist values failed to retrieve while preparing the CI job build ([#44117](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074423001), [#44029](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074323857)). * Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "**Remove User Permissions**" ([#44027](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074328464)). * Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade ([#44032](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074275828)) * Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels ([#44028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074327108)). * Fixed an issue with EZ-commit features where the metadata file was causing the JAXM marshall exception (invalid XML format) error ([#43864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074126263), [#43513](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073481411)). * Fixed an issue where the quick deployment functionality was not working as expected ([#42521](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071941125)). * Fixed an issue where the users could not view the commits list to merge them into a release label ([#43718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). * Fixed an issue where the code coverage reports fail to include all the classes in the CSV file ([#42848](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072441595), [#39582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066807003)). #### 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 branching baseline feature for profile was not working as expected ([#44615](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075179971), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed an issue where the Dataloader Pro jobs were failing with no error message ([#44620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075206808), [#44264](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074669005)). * Fixed the issue where the Dataloader Pro jobs was not working as expected ([#43966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301291)). * Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the *notes* and *attachment* of the Credit Memo from source to the destination environment ([#40990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069124041)) * 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 performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 15 May 2022 **(ARM v22.1.7)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). #### 08 May 2022 **(ARM v22.1.6)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 01 May 2022 **(ARM v22.1.5)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the picklist values failed to retrieve while preparing the CI job build ([#44117](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074423001), [#44029](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074323857)). * Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "**Remove User Permissions**" ([#44027](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074328464)). * Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade ([#44032](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074275828)) * Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels ([#44028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074327108)). * Fixed an issue with EZ-commit features where the metadata file was causing the JAXM marshall exception (invalid XML format) error ([#43864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074126263), [#43513](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073481411)). * Fixed an issue where the quick deployment functionality was not working as expected ([#42521](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071941125)). * Fixed an issue where the users could not view the commits list to merge them into a release label ([#43718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). * Fixed an issue where the code coverage reports fail to include all the classes in the CSV file ([#42848](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072441595), [#39582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066807003)). * Fixed an issue where the commits triggered in ARM shows a different author in Azure DevOps ([#44225](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074591143), [#43503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073518014)). * Fixed a bug where selecting the "**Deployment**" icon after signing in to the ARM application caused the user to log off and on and return to the home page ([#44040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301863)). * Fixed a bug where the check-ins display the wrong number of files changed during commit ([#40119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067784313)). * Fixed an issue in the TAF module where nothing pops up when you click on the "**View Log**" button ([#42020](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071114057), [#40284](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067992205)). * Fixed an issue where the users while accessing the help center from ARM application, receiving the **({"result":"failure","cause":"E105 - Request Delayed"})** error ([#43579](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652168)). * Fixed a bug where the commits was getting failed due to SCM (Software Configuration Management) authentication failure ([#42276](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071577005)). * Fixed a bug where the merge operations ran for more than 12 hours and later failed ([#38755](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065037173), [#42874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072544001), [#38913](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065383003)). * Fixed an issue where extra metadata members are picked up for the profile component during the EZ-Commit process ([#41361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069919263)). * Fixed an issue where the users could not use commit template for the deployment ([#43995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074325045), [#43586](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073635324), [#43905](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074163310), [#43407](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073339003)). #### 24 April 2022 **(ARM v22.1.4)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 17 April 2022 **(ARM v22.1.3)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue for the Chrome browser where the ApexPMD ruleset was not uploading incorrectly (under the **Plugins** section). For other browsers, it was working as expected ([#42954](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072670003)). * Fixed the issue with the merge where the changes present in the source branches were not picked up, and therefore latest changes did not reflect on the destination branch ([#43553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073610001), [#43598](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073662177), [#43595](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073653614), [#43593](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652863), [#43591](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073629096), [#43580](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652300), [#43574](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073651134)). * Fixed an issue where the Salesforce-DX deployment and rollback mismatches ([#35947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000057045040)) * Added the criteria to trigger the callout URL post-deployment. If you set it to *success*, the callout URL is activated if the salesforce deployment is successful ([#38990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065571472)). * Enabled feature flag settings to select between classic ARM and Salesforce CLI process to generate package manifest. * Fixed an issue where the commit validation is successful for an empty field, whereas the CI job fails ([#43324](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073218067)). * Fixed an issue where the deleted metadata components were showing under the **"File Changes"** tab but did not appear under the **"Destructive Changes"** column while carrying out a manual deployment ([#41670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070494027)). * Fixed Dataloader Pro job issue where the job is completed successfully without loading all ancestors/master objects data to the destination environment ([#43276](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073123039)). * Fixed branching baseline issue where all metadata from the production org were not copied to the version control repo/branch ([#42938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072633029), [#42685](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072244001), [#42955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072644308), [#42445](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071818001), [#43038](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072780490), [#42753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072314347), [#42242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071424143), [#42766](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072375048), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed the below nCino issues: * Unable to proceed with feature deployment using an existing community feature migration template due to the following error: **"No External Id field exist in source org."** This is now fixed and working as expected ([#43263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073131047)). * 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 an issue where the **Abort** option was showing for completed CI jobs ([#38177](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063673463), [#39052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065705011), [#38992](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564443), [#39682](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066942137)). * 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 an issue where deleting a custom field was affecting other custom objects where the globalpicklistvalue is shared by multiple objects ([#42782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072370556)). * Fixed a bug where the users were not able to view specific values under the standard value sets in the **New EZ-Commit** screen ([#41773](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070686445)). * Fixed a bug where the **New EZ-Commit > Deleted Component** tab throws a null error on expanding the metadata types. * Fixed a bug where the deploying records via record based configurations (RBC) was throwing error: **"No external Id field exists in the source org"** ([#43263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073131047)). * Fixed an issue where creating a new nCino feature migration template takes longer than expected ([#41855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070869289)). * 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 **skip members** feature was not working for the Version Control, Deployments, and CI Job module ([#41531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221221)). * Fixed an issue where the users were receiving layout permissions errors when using **Prevalidation Commit**. * The SCA option where not working when users use the EZ commit/ Merge operation. The issue has now been fixed ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * Fixed an issue where the users were unable to generate the deployment report and received validations errors for EZ-Merge operation ([#41639](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423671)). * Fixed an issue where the users were unable to update any changes in the permission section. * Fixed an issue where the non-licensed users were receiving the deployment email failure notification for the unsuccessful deployment ([#41705](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070543145)). * Fixed an issue where the users were unable to use the nCino feature after the ARM was upgraded to v21.6 ([#41108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069360251)). #### 27 March 2022 **(ARM v22.1.0)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the users were unable to switch the tab from the **Test Coverage** to the **Class Coverage** in the **Apex test results** page ([#41455](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070062179)). * Fixed an issue where the users were unable to save Salesforce settings in the **My Account** screen ([#41329](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069835104)). * Fixed an issue where the users were not able to save the exclude metadata types in the **My Account** page ([#41529](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221075)). * Fixed an issue where the users were not able to create a new ALM project for Azure repository ([#41554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070326013), [#41630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423082)). * Fixed an issue where the users having difficulty with the **datamigration.properties** file while creating a new instance ([#41510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070231024)). *** ## ARM Release Notes **21.6** **Date of Release:** ***21 November 2021*** **On this page:** 1. [New Features](#new-features) 2. [Enhancements](#enhancements) 3. [Improvements](#improvements) 4. [Changelogs](#changelogs) ### New Features #### Pull Request Support for Azure DevOps Pull request is a feature that allows you to review code and provide feedback before merging it into the master branch. Previously, we had GitHub and Bitbucket support. We've included support for Azure DevOps in this release. ([Learn More](/product-guides/arm/arm-features/version-control/external-pull-request/pull-request-support-for-azure-cloud)) * 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 an issue where the users were unable to deploy release labels ([#40600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068395530)). * Fixed the following SSO errors: * Unable to use SSO for AutoRABIT authentication ([#37767](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062637173)). * Unable to log in via SSO in the chrome and the firefox browser. * Fixed "**domain name does not exist**" error ([#41853](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070865403)). * Fixed a bug where users were getting an undefined error for the standard templates while editing the CI job. * Fixed an issue where the status of the AutoRABIT ExternalId field was showing as processing, but it was marked as completed in the log report ([#40669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068569430)). * Fixed a bug that restricted users from using Dataloader Pro's **Auditable Standard** field feature ([#40794](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068711163)). * Fixed an issue where the users were unable to replace attachment records in the destination org. * Fixed an issue where the attachments were not completely deployed in the target environment ([#41208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069667003)). * Fixed an issue where users were unable to deploy the nCino feature from org to org using the **nCino-Forms** **standard template** ([#38764](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065055277)). * Fixed an issue where the users were unable to **stop/delete** the data loader running jobs ([#39556](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066791149)). * Fixed an issue where the users when attempting to initiate the deployment, were failing with the **"Failed to initiate deployment request"** error ([#40620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068429999)). * Fixed an issue where the users were unable to perform the branching baseline operation ([#41622](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070417055)). * Fixed an issue where the users were not able to configure the approver's lists on the **New Merge Request** screen ([#41844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070874003)). * Fixed an issue where the users trying to revert a commit for a commit label was getting failed ([#39613](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066805855)). #### 06 Mar 2022 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **skip members** feature was not working for the Version Control, Deployments, and CI Job module ([#41531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221221)). * Fixed an issue where the users were receiving layout permissions errors when using **Prevalidation Commit**. * The SCA option was not working when users use the EZ-Commit/merge operation. The issue has now been fixed ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * Fixed an issue where the users were unable to generate the deployment report and received validations errors for the EZ-Merge operation ([#41639](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423671)). * Fixed an issue where the users were unable to update any changes in the permission section. * Fixed an issue where the non-licensed users were receiving the deployment email failure notification for the unsuccessful deployment ([#41705](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070543145)). * Fixed an issue where the users were unable to use the nCino feature after the ARM was upgraded to v21.6 ([#41108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069360251)). #### 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 switch the tab from the **Test Coverage** to the **Class Coverage** on the **Apex test results** page ([#41455](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070062179)). * Fixed an issue where the users were unable to save Salesforce settings in the **My Account** screen ([#41329](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069835104)). * Fixed an issue where the users were not able to save the excluded metadata types on the **My Account** page ([#41529](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221075)). * Fixed an issue where the users were not able to create a new ALM project for the Azure repository ([#41554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070326013), [#41630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423082)). * Fixed an issue where the users having difficulty with the **datamigration.properties** file while creating a new instance ([#41510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070231024)). * Fixed an issue where the users when trying to start a deployment, it was getting failed with the "**Failed to start deployment request** error" ([#40620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068429999)). * Fixed an issue where the users were unable to revert the commits using AutoRABIT ([#39957](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067378384)). * Fixed an issue where the users were not able to use the "**Files Changed**" functionality on the **Merge Request History** page ([#41456](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070069155)). * Fixed an issue where the users were unable to delete the changes made in the version control branch via AutoRABIT ([#39130](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065873001)). * Fixed a bug that prevented users from performing commit and merge operations in AutoRABIT ([#39129](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065834119)). * Fixed an issue where the external objects with lookup relationships were not getting displayed under the child objects in the Dataloader Pro ([#41084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299165)). * 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: * Fixed an issue where the users were unable to see the commits ID in the release label ([#41284](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069797001)). * Fixed an issue where the users were unable to view their permission details in the Users and Roles tab ([#41043](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069219179)). * Fixed an issue where users were not able to delete the changes made in the source branch using AutoRABIT ([#39130](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065873001)). * Fixed an issue where the branching baseline for a profile and branch to branch merge was not working ([#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * There was an AutoRABIT performance issue that caused searching for revisions, validations, and commits to taking a long time. It has now been fixed ([#39129](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065834119)). * Fixed an issue where users were not able to commit their changes to the branch ([#39269](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066103022)). * When users attempted to update changes in the target org using the profile manager, the deployment getting failed. It has now been fixed ([#40599](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068421379)). * Fixed an issue where users were unable to switch from a credential-based login to an SSO-based login ([#40871](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068784190)). * AutoRABIT instances were not supporting the Salesforce API 54 version. It has now been fixed. ([#40921](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068957023)). * When a user performs a pre-validation commit on the Azure repository branches, it creates a duplicate external commit with the same revision ID. This issue has now been fixed ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). #### 13 Feb 2022 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **"Group By"** functionality was not fetching the correct CI job results ([#38870](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069460109)). * Fixed an issue where the deployment status of CI Job has failed in logs but the process is still in-progress stage ([#40805](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068697958)). * Fixed an issue where the users were unable to use the SCA for LWC components unlike apex class, triggers, and aura bundle ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * When a pull request is in progress, the job is not triggered for additional changes committed before the work is completed. This is now fixed ([#38877](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065276358)). * Fixed a bug where the users were facing challenges while merging the entire branch changes to the target environment ([#39451](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066611145)). * Fixed an issue where the File Diff shows full component (especially Aura, LWC components) as a change instead of delta changes ([#39351](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066320276)). * 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 an issue where the data loader pro throws the error **"Error creating output directory: configs"** while uploading data from one environment to another ([#40832](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068736307)). * Fixed an issue where the external object-related lookups were unable to verify the relationship associated with the external objects in the destination org ([#41084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299165)). * 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: * The **"Commit"** button was not available for the merge request label job. ([#38876](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065275014)). * 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 an issue where the admin was unable to assign permissions to its sub-users. This is now working as expected ([#40017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067565003)). * Fixed an issue where the validation rule automation was not working for the **Environment Provisioning** module ([#41035](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069198519), ([#40991](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069108736)). * Fixed an issue where the data loader pro job is not able to load data for objects with fields exceeding limits([#38790](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085228)). * Fixed an issue where the users were unable to register the existing branches to AutoRABIT ([#40894](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068809067)). * Fixed an issue where the EZ-Merge was showing status as failed in the AutoRABIT application however, in the Salesforce environment the status shows as success ([#40673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068536502)). * 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 **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as their parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 where the users were unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 unable to generate the code coverage log report from the **Report** Module ([#38717](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064939344)). * Fixed an issue where the users were unable to upload the package.xml file to resolve the merge conflict ([#39960](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067372236)). * Fixed an issue where the users were able to commit the changes although the validation got failed. ([#38228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063775343)). * Fixed an issue where the user was unable to perform the **Enable/Disable validation rule** on the Managed package object using the environment provisioning functionality ([#40297](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068017532)). * Fixed a bug where the user was unable to deploy the **Email Template** on their target environment ([#40241](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067922013)). * Fixed an issue where users were unable to upload/migrate the knowledge articles from one sandbox to another sandbox ([#37922](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063030291)). * 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 where the users were unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as their parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 an issue where the CI Job builds are getting stuck and no log information was displayed ([#39052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065705011), [#38992](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564443), [#39682](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066942137)). * Fixed an issue where the conflicted files downloaded were incorrect during the merge process ([#39364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066317317)). * Fixed an issue where the aura components were not getting retrieved while carrying out the branching baseline operation ([#38610](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064710558)). * 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. * Fixed an issue where the users were able to find the **Abort** option even when the CI Job had been completed successfully ([#38177](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063673463)). #### 26 Dec 2021 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as the parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 where the user was unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 when the user is trying to perform pre-validation commit for report metadata, it is getting added under emailservice functions in diff report ([#37925](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063067009), [#38581](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064666105), [#38880](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065272149), [#38734](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064981980)). * Fixed an issue where the case *entitlementProcess-meta.xml* files were not picked up during deployment ([#39069](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065734191), [#38361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064187022)). * Fixed an issue where the deployment report is getting failed while doing prevalidation merge with the report folder. * Fixed an issue where users were unable to retrieve a package which has more than 1000 components ([#38737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064985007)). * Fixed a bug where a null pointer exception was thrown while loading in Dataloader Pro ([#38286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063928003)). * Fixed an issue where the entitlement process is getting removed from Package.xml ([#39097](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065777009)). * Fixed an issue where the external commits did not show up on the release label ([#38822](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065151262)). * Fixed a bug that displays the wrong statuses in the test reports ([#39008](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065572975), [#38986](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564303)). * Fixed an issue where the code coverage percent is not available in the case of SFDX merge operation. * Fixed an issue where the data loader pro jobs were not able to load data for objects with fields exceeding 800 ([#38790](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085228)). * 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 when pre- and post-destructive changes were added to the process, it caused the deployment to fail ([#38330](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064040175), [#38721](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064967175)). * Fixed a bug where for fewer CI jobs, the **Older** button was disabled. This has now been enabled and is working as expected ([#39050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065702042)). * Fixed an issue in the SFDX module that prevented commits from being executed using scratch org ([#38789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076258)). * Fixed an issue where the external commits were not displayed when creating release labels or merging single revisions. This is now working as it should ([#38822](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065151262)). * Fixed an issue where users were unable to run SCA within the reports module due to an error stating **"Invalid mapping credentials."** In addition, the number of issues indicated in the Ez-commit process does not match the CodeScan analysis ([#38917](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065373386)). * Fixed a bug where single data loader jobs couldn't be edited and there was a mapped field cache issue ([#38753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065026084)). * 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 nCino objects deployment issue during using nCino CI Jobs ([#39375](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000058591003)). * Fixed an issue where the custom object is being listed during CI Job operation but not during Ez-commit ([#38361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064187022)). * Fixed Ez-merge issue which shows different results in AutoRABIT when compared to the production environment ([#38831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065181230)). * Fixed an issue where the users were unable to extract deleted records and threw **"Malformed Query Fault"** error ([#38448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064441154)). * Fixed an issue where the pull request support with BitBucket was not working properly. This is now fixed ([#38644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064828044)). * Fixed a bug in the merge request and pull request validation builds which were unable to list the changed components whereas the CI Job build was able to pick them up ([#37095](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060661017), [38713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064936484)). * Fixed an issue where the org administrator was unable to assign hub level permissions to its sub-users ([#38898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065336005)). * Fixed wrong metadata identification for deletion issue ([#37703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062453147)). * Fixed an issue where the user was unable to update **"Configuration For recordTypes picklistValues"** ([#38901](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065355005)). * Fixed API version error in the CI Job screen ([#36550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059178003)). * Fixed CI build failing issue ([#38630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064788278)). * Fixed EZ-Commit issue where the file diff was throwing an error due to credential scope issue ([#38950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065446001), [38795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065077341)). * Fixed an issue where duplicate entries were seen while creating release labels ([#37300](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061440253)). * Fixed a bug where the user was unable to click on the **OK** button on the **Merge Request History** screen ([#38781](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085003)). * 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 quick deployment feature was not working as expected and was throwing **"Invalid Login"** error ([#37802](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062709159)). * Fixed a bug where the merge request validation was getting failed ([#37095](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060661017)). * Fixed an issue where the commit search was not working as expected in the **Version Control** module ([#36548](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059165111)). * Fixed an issue where the users were facing invalid credentials issue while updating the src as metadata folder path in-branch settings **(Admin > VC' Repos)** ([#38727](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064939824)). * Fixed an issue where the pull request support for BitBucket was not working properly as expected ([#38644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064828044)). * Fixed an issue where the deployment shows failed status although there are no failures and the items did get moved to the destination org. This is now working as expected ([#37774](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062644015), [#38363](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064201151)). * Fixed an issue where the user was not able to retrieve the metadata to deploy the changes using AutoRABIT's deployment feature. * Fixed data loader pro issue which was throwing unknown error while migrating the data objects ([#38566](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064649001)). *** ## **ARM Release Notes 21.5** **Date of Release: 29 August 2021** **On this page:** 1. [Enhancements](https://knowledgebase.autorabit.com/arm/docs/arm-release-notes-215#enhancements) 2. [Changelogs](https://knowledgebase.autorabit.com/arm/docs/arm-release-notes-215#changelogs) 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 an issue where no metadata was found while validating the components from the master branch to the production environment ([#38612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064709627), [#38587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064645657), [#38571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064639413), [#38537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064517581), [#38552](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064584042), [#38549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064544537)) * Fixed revision based deployment issue ([#38386](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064283007)) * Fixed an issue where the commit labels changes are not reflected in the release label ([#38569](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064646158)) * Fixed an issue where the salesforce deployment from GIT to SFDC was not working ([#38558](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064639001)) * Fixed deployment issue where no components were being retrieved via *Single Revision* or *Revision Range* ([#38550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064581003), [#38546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064558188)) * Fixed a bug where the deployment CI Job occurs multiple times ([#37454](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061960003)). * Fixed the search and substitute deletion rule issue ([#38410](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064291165)). * 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 user couldn't delete a job with special characters in its name ([#38332](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064061141)) * Fixed SFDX deployment and rollback mismatches issue ([#35947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000057045040)). * Fixed a bug where when attempting to commit the deletion of 19 profiles, a Diff Report listing of 20 profiles was generated. ([#38303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063932311)). * Fixed code coverage report discrepancy issue ([#36282](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000058168335)). * 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: * The deleted sharing rules were not showing up in the EZ-Commit Deleted tab, which was fixed ([#37747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062586019)) * Fixed a bug where the older commits were not accessible for merge ([#38242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063785008)). * Fixed an issue where when deploying a new custom object, an error *"Profile Search Layout: - System Administrator - not appropriate for object XXXXXX"* was thrown ([#37897](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062972201)). * Fixed a merge conflict issue([#37950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063128003)). * Fixed a commit label issue ([#38275](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063874030)). * Fixed an issue with SSO where users had to log in twice before being able to use the AutoRABIT application ([#36634](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059319963)). * The issue with the SSO domain has been fixed ([#37232](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061168477)). * Fixed data loader audit logs issue ([#37688](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062385762)). * Fixed an issue where the users were unable to exclude *EmbeddedServiceLiveAgent* from CI Job ([#38261](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063818321)). * Fixed an issue where the user couldn't delete a job with special characters in its name ([#38332](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064061141)). * Fixed an issue where users were unable to compare profiles using the *Profile Manager* feature in the *Deployment* module ([#36978](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060367023)). * In CI Jobs, a bug with the *"Group By"* filter was fixed ([#38132](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063522197)). * Fixed an issue where the community site was not getting deployed ([#38226](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063775199)). * 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. # Release Notes 25 ## Release Notes 25.2.7 **Release Date: 24 August 2025** Highlights: Fixes to EZ-Commit translations, webhook API token status, and rollback iterations. #### Bug Fixes 1. **EZ Commit – Case Values Removed from CustomObjectTranslation**\ Resolved an issue where case values were being removed from the CustomObjectTranslation file when performing multiple EZ-Commits under Japanese language. The problem was caused by unmarshalling and marshalling logic comparing values incorrectly. The comparison logic has been updated to rely on additional fields to properly support translations for different languages.\ (Support Case: 142756) 2. **Webhooks – API Token Last Access Not Updating**\ Fixed an issue where webhook API tokens continued to display “Never Accessed” even after recent runs triggered by CI jobs. The backend logic has been corrected to update and display the last access time accurately.\ (Support Case: 149685) 3. **Rollback – Iteration and Components Not Available After Revert**\ Addressed an issue where rolling back a previously deployed iteration caused both the iteration and its components to disappear. A change event has been added to ensure iterations and components are available after a revert rollback.\ (Support Case: 150209) *** ## 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 [Release Notes](https://knowledgebase.autorabit.com/release-notes/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.3-release-notes) 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 [Release Notes](https://knowledgebase.autorabit.com/overview/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.2-release-notes) 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. I*mpacted 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 [Release Notes](https://knowledgebase.autorabit.com/overview/release-notes/ncino-release-notes/release-notes-25.1#ncino--data-loader-25.1.0-release-notes) for nCino + Data Loader improvements. # Release Notes 24 ## 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 ``, ``, and ``. 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: 1. **Deployment History Display**: * Vlocity deployments now appear correctly in the deployment history, ensuring users can track and review their deployments without issues. 2. **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. 1. **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." 2. **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: 1. **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. 2. **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. 1. **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 2. **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. 3. **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. 1. **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. 2. **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: 1. **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. 2. **Layout Fix**: The layout issue where five columns were displayed instead of six during profile comparisons has been addressed. 3. **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. 1. **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. 2. **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. 3. **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 1. In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability. 2. SOAP to REST services were upgraded. 3. Third-party libraries were upgraded. *** ## ARM Release Notes 24.1 **June 2024** **Version 24.1 – Enhancements and Improvements** ### Enhancements 1. **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.
2. **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.
3. **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.
4. **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.
5. **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.
6. **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. 1. In this release, we revolutionized the system by converting all JSP pages into a RESTful API, enhancing modularity, scalability, and interoperability. 2. SF CLI Version upgrade to 2.41.8 3. 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. 4. 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. 5. Upgrade of third-party libraries 6. 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. 7. 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 1. 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 2. 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 3. 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. 4. 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 5. 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** 1. 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 2. 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 3. 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 4. 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 5. 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. 6. 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. 7. 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 8. 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 9. 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 10. 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 11. 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 12. 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 13. 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 14. 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 15. 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 16. 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. 17. 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** 1. 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 2. 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 3. 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. 4. 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** 1. 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 2. 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 3. 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. 4. 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** 1. 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 2. 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. 3. 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. 4. 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. 5. 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. 6. 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 \[+]). 7. 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. 8. 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. 9. 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 10. 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 11. 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 12. 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. 13. 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 14. 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 15. 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 16. 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 17. 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 18. 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** 1. A data error reported in version 23.1 with the Version Control module that resulted in version control being deleted was resolved in both 23.1 and 24.1 through adding loggers. Support ticket #114503 2. A use-case error reported in version 23.1 with the Version Control module in which the user was unable to use an existing conflicted file, which resulted in reraising merge requests, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115084 3. A use-case error reported in version 23.1, which resulted in an issue with the Data Loader module in which the software was not inserting the correct record type, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #114076 4. A use-case error reported in version 23.1 with the nCino module in which rollbacks were only partially being completed was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115204 5. 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 6. 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 7. 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 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 2. 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 3. 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 4. 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. 5. 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. 6. 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. 7. 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 [nCino release 24.1](/release-notes/release-notes/ncino-release-notes/release-notes-24.1) notes as well. # Release Notes 23 ## ARM Release Notes 23.1 **September 2023** **Version 23.1 – New Features, Enhancements, and Improvements** **Supports Provar** Current Version: 2.10.1 **Supports Apex PMD** Current Version: 7.0.0 ### New Features **1. Automatic Merge after Successful CI Build**\ We know that understanding and managing version control can sometimes be a challenge. ARM offers the flexibility to cherry-pick branch revisions for merge or deployment. Now you can automate this process of cherry-picking the revisions in CI Jobs as a post-deployment step. The '**Run Merge process on successful deployment**' feature keeps track of builds in source branches and merges them into a designated destination branch if they meet the configured criteria (for example, if the build is successful). Rather than requiring manual effort, upstream merges may now be automated by the **Salesforce Release Manager** using revision numbers that were determined as part of a build cycle in CI jobs. Users will be notified via email of the success or failure of the automated merge process. **2. Create and Install an Unlocked Package Version from a Version Control Branch**\ Use ARM CI intelligence to create a package version, build using the SFDX project structure in a Version Control branch, and install the same in the destination org of your choice—all from the same page. You can now generate an unlocked package version automatically through the CI job, and as part of the deployment, it is deployed in the same build cycle. Until the 22.2 version, it picked the latest package version that was already successfully created in ARM. When users create a CI job using this option, ARM checks the Version Control. If there is a change, it builds a new version on top of the packages. Once the package is created, then the deployment is triggered automatically. **3. Create Connected Apps**\ ARM now gives access to users to create and maintain their OAuth credentials. Users can set up the **Connected Apps** for Jira OAuth and register the credentials with ARM. You can add, edit, and delete your Jira login credentials instead of contacting AutoRABIT to manage the connected apps. Once created, simply provide us with the connected app details like **Client ID** and **Secret Keys**. We use these details to connect as an ALM and test the connection. **4. RESTricted Emails**\ The new **RESTricted Emails** section on the **Notifications** page of the Admin module helps ensure that ARM-related emails are not sent to deactivated users. Admins can either add users to this list manually or deactivate the respective users from the **Users** page of the Admin module, and they will be automatically added to this list. These users will not receive ANY emails including deactivation, forgotten password, reset password, jobs executed in the application, etc. Admins can also use the same two methods to reactivate a user and remove them from this list. There is also a provision for an Admin to remove all users from the **RESTricted Emails** list at once. **5. Dependency Analyzer**\ Dependency Analyzer helps you understand the dependencies among various components in your Salesforce org. It allows you to analyze the relationships among objects, fields, classes, triggers, and other metadata components. With Quality Gates, ARM helps Salesforce developers run multiple checks to understand if and how their commits can break a Salesforce org. Currently, we enforce the following gates: * SAST, SSPM, and AST (Static Code Analysis, Salesforce Security Posture Management, and Application Security Testing) * Deployment Validation * File Change Footprint * Peer-to-Peer Code Review With the introduction of the Dependency Analyzer, we can offer a fourth gate, Dependency Check, which will allow users to see what they are missing due to Salesforce specificity. We have introduced the Dependency Analyzer in CI Jobs for now, and this is just a start at bringing this functionality to the remaining modules soon. Users now have the option to ‘**Run Metadata Dependency on Failed Deployments**’ to view the results of failed metadata components with their dependencies and download them in Manifest and XML formats. **6. ServiceNow – ALM Management**\ The ARM–ServiceNow integration automatically posts updates to ServiceNow tickets. It makes tracking the status of your user stories and support tickets faster and easier. Tasks can be organized by project, allowing an organization to track issues within projects transparently. ServiceNow will make information more easily accessible and workflows more streamlined, reducing the time and effort required to manage and resolve service requests. Additionally, the integration will allow teams to work more effectively, improving collaboration and communication. ### Enhancements 1. **Salesforce Spring (API 57.0) & Summer (API 58.0) Support**\ AutoRABIT supports the most recent API 57.0 & API 58.0 versions in this release to keep our product updated with Salesforce updates. The most recent API version is intended for customizing and developing tools to manage the metadata model. 2. **Exporting Selected User Details**\ Users with Admin access can now choose the fields they want to include while exporting users' details to a CSV file. While selecting the Export option, the list of available fields is displayed. Admins can select and deselect the required fields by clicking the corresponding checkbox. Some of the fields are selected by default for ease of use. Admins can always deselect these fields if they are not required. Thus, based on the teams with whom they will be shared, Admins can customize the fields in the list. 3. **More Info on CI Jobs and Info**\ Users are now able to view the CI Jobs they created in the CI Job List screen to date inside ARM. The list is displayed in chronological order with the most recent jobs listed at the top. 4. **'Created and Requested by' in Deployment UI**\ Users are now able to view the ‘Created by’ and ‘Triggered by’ fields in the Deployment home screen without scrolling through multiple screens for this info, enabling monitoring of the deployment’s real-time progress. [Read more](/product-guides/arm/arm-features/deployment) 5. **Self-Service Connected App Setup for Jira OAuth in ARM**\ We've introduced a self-service feature allowing users to set up Jira OAuth-connected apps in ARM autonomously. With guidance from our user manual's Connected App guide, users can effortlessly create and register their app credentials, eliminating the need for support team assistance. Users can quickly establish a robust connection by inputting the generated Client ID and Server Key into ARM's settings. 6. **Unified Admin Roles**\ We’re excited to introduce a streamlined and more efficient Admin experience. We’ve consolidated the roles of Super Admin and Registered Admin into a single empowered Admin role. This change means Admins now have a unified set of tools and permissions, streamlining tasks and creating a more user-friendly Admin experience. 7. **CI Jobs List and Results: Filter and Export Option**\ We've enhanced the platform with a user-friendly quick filter and export feature in response to user feedback. This functionality empowers administrators, release managers, and users to efficiently organize and analyze data by alphabet or date, facilitating faster insights and informed decision-making. 8. **Create Artifact: Release label more than 180 days**\ In the Create Artifact section, users can now generate a Release Label and have the flexibility to choose an extended timeframe of over 180 days for retrieving comprehensive commit history data. This enhancement offers users a broader historical perspective, facilitating more in-depth analysis and tracking of commits for their projects. 9. **Enhanced security and user experience. (NEW)**\ The new features focus on enhancing security and user experience. They include a single-user session control to prevent multiple active sessions under the same username, automatic logout for inactivity to bolster security, and support for multiple tabs or pages in the same browser, improving user productivity and maintaining the environment's integrity. ### Improvements This update has implemented significant performance upgrades to enhance the tool's efficiency and responsiveness. These enhancements encompass optimized queries and leverage new technologies, collectively resulting in a smoother, faster user experience. #### 31 July 2024 **ARM 23.1.40** 1. A code fix was applied to the CI Jobs module of versions 23.1 and 24.1 related to a use-case error causing the CI Jobs History report to not generate. Support ticket #116943 #### 24 July 2024 **ARM 23.1.39** 1. A code fix was applied to the Version Control module in version 23.1 related to a use-case error in which the merge completion was taking too long. Support ticket #113102 2. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which an issue was occurring with the system administrator lite. Support ticket #117297 3. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to see the metadata through the single revision deployment. Support ticket #116919 4. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error in which the user was not able to deploy the Einstein Prediction builder. Support ticket #116909 5. A code fix was applied to the Admin module of versions 23.1 and 24.1 due to a use-case error with users losing access. Support ticket #111830 6. A code fix was applied to the Version Control module of versions 23.1 and 24.1 due to a use-case error requiring multiple revisions on an ALM work item. Support ticket #117810 7. A code fix was applied to the Deployments module of versions 23.1 and 24.1 due to a use-case error with the new profile compare feature. Support ticket #117309 8. A code fix was applied to the Deployments module of version 23.1 due to a use-case error with 'add additional member' showing duplicates when expanding the toggle. Internal request. 9. A code fix was applied to the Version Control module of version 23.1 due to a use-case error with users getting an error for a commits tab external pull request using Bit bucket repo. Internal request. #### 17 July 2024 **ARM 23.1.38** 1. A code fix was applied to the nCino module in version 23.1 related to a use-case error in which Data Loader Pro was not fetching the child object. Support ticket #115313 #### 10 July 2024 **ARM 23.1.37** 1. A use-case error identified in version 23.1 required a code fix, which was applied in versions 23.1 and 24.1 to the Deployment and Version Control modules, to correct a scenario in an org-to-org full-profile deployment where it was not capturing package visibility and permissions. Support ticket #110760 2. A use-case error identified a code fix needed to the Reports module of version 23.1 to fix a product test class in which the weekly scheduled job failed. Support ticket #115654 3. A code fix was applied to versions 23.1 and 24.1 due to a use-case error identified in version 23.1 where commits were failing with a 'no credentials mapped' error in the Version Control module. Support ticket #116704 4. A code fix was applied to the Admin module in version 23.1 related to a use-case scenario that required additional support to create the ARM instance from scratch. Support ticket #117015 5. A code fix was applied to the Deployment module in version 23.1 due to a use-case error in which the user was unable to get the popup while deploying using package.xml as the source. Support ticket #116967 #### **3 & 7 July 2024** **ARM 23.1.36** 1. A use-case scenario identified an error in version 23.1 with metadata retrieval from the repository failing in the Deployment module, which was resolved in versions 23.1 and 24.1. Support ticket #115818 2. A code fix identified in version 23.1 was applied to correct a use-case error in the Version Control module of version 23.1 related to commit templates. Support tickets #116124, #116138 3. A code fix identified in version 23.1 by internal request ticket was applied to the Admin and CI jobs modules in versions 23.1 and 24.1 to upgrade v61 (Beta) to v61. 4. A use-case error in version 23.1 required a code fix to version 23.1 Deployment and Version Control modules due to an org comparison not showing diff results. Support tickets #112752, #116025 #### 26 June 2024 **ARM 23.1.35** 1. A data error reported in version 23.1 with the Version Control module that resulted in version control being deleted was resolved in both 23.1 and 24.1 through adding loggers. Support ticket #114503 2. A use-case error reported in version 23.1 with the Version Control module in which the user was unable to use an existing conflicted file, which resulted in reraising merge requests, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115084 3. A use-case error reported in version 23.1, which resulted in an issue with the Data Loader module in which the software was not inserting the correct record type, was resolved in both 23.1 and 24.1 through a code fix. Support ticket #114076 4. A use-case error reported in version 23.1 with the nCino module in which rollbacks were only partially being completed was resolved in both 23.1 and 24.1 through a code fix. Support ticket #115204 #### 12 June 2024 **ARM 23.1.34** 1. A code fix was performed due to a use-case error related to the CI Jobs module in which nCino CI Jobs were not triggered by metadata CI Jobs on success. Support ticket #113887 2. A code fix was performed due to a use-case error related to the Version Control module in which the API response from CodeScan returned a page not found (404) error in ARM. Support tickets #108895, #115120, #114434 3. A code fix was performed due to a use-case error related to the Deployment module in which the Deployment button was not enabled in AutoRABIT after validation. Support ticket #107108 4. A code fix was performed due to a use-case error related to the Deployment module in which the user was unable to deploy a Bot from a Branch to a sandbox. Support ticket #11497 5. A code fix was performed due to a use-case error related to the Version Control module in which an ALM work item was not displaying in the merge. Support ticket #113626 6. A code fix was performed due to a use-case error related to the Admin module in which a user was unable to implement ARM and Zoho desk integration with JWT. 7. A code fix was performed due to a use-case error related to the Version Control module in which a user was unable to perform EZ-Commits. Support ticket #114441 8. A code fix was performed due to a use-case error related to the Version Control module in which the previously validated commit label showed to add a date instead of the label dropdown. Support ticket #115249 9. A code fix was performed due to a use-case error related to the Reports module that required us to fix recursive errors. 10. A code fix was performed due to a use-case error related to the Data Loader module in which the master-child relationships were not being applied when loaded through Data Loader Pro. Support ticket #111780 11. A code fix was performed due to a use-case error related to the nCino module in which the CI job was not updating templated objects and object record count when the checkout was not taken from version control. Support ticket #112704 12. A code fix was performed due to a use-case error related to the nCino module wherein CI Jobs for nCino RBC feature migrations were failing. Support ticket #114991 13. A code fix was performed to the Admin module as a result of a change request related to users being unable to log in to AutoRABIT. Support tickets #115392, #113300 #### 5 June 2024 **ARM 23.1.33** 1. A code fix was applied to all modules prompted by an internal change request in preparation for support of the Salesforce Summer '24 release. This will require updates to internal documentation. 2. A code fix was applied to the Deployments module resulting from an internal request to correct a use-case error in which a deployment failure and document discrepancy were encountered, with subsequent deployment attempts unsuccessful. 3. A code fix was applied to the Version Control module initiated by a use-case error in which the team encountered an ALM commit issue related to the label name when testing a user story. Support ticket #113308 4. A code fix was applied to the Version Control module related to a use-case error occurring when processing merge conflicts. Support ticket #113606 5. A code fix was applied to the Admin module related to a data error in which the branching baseline was not updating the LWCs in the branch. Support ticket #113174 6. A code fix was applied to the Data Loader module related to a configuration error causing Data Loader to not work as expected. Support ticket #113575 7. A code fix was applied to the ARM module related to a use-case audit logging API error with start time and end time issues occurring when fetching logs. #113739 #### 29 May 2024 **ARM 23.1.32** 1. A code fix was applied to the Version Control module to resolve a use-case error in which the user cannot approve or reject a Merge Request when the label name contains a "+" symbol. When the merge label contains unsupported characters, the merge label is not submitted as expected and the validation message displays the supported characters. Support ticket #112715 2. A code fix was applied to the Admin module related to a use-case error occurring when modifying the Team Administrator, it created duplicate Teams, consuming existing licenses. Support ticket #109457 3. A code fix was applied to the CI Jobs module due to a use-case error in which a Checkmarx scan was not matching up and breaking the build. Support ticket #105217 4. A code fix was applied to the CI Jobs module due to a use-case error occurring when multiple CI jobs run on GitHub PRs, AutoRABIT reports incorrectly that the jobs were successful. \* Issue requires updated documentation. Support ticket #111955 5. A code fix was applied to the Version Control module related to a use-case error in which Mock Deployment criteria check lines were not logged in the UI during the Prevalidation Deployment refresh, but they do appear after auto-rejection and subsequent refresh. 6. A code fix was applied to the Deployment module to correct a use-case error occurring when selecting and deselecting ApexClass and CustomField metadata types, the Deploy pop-up incorrectly displayed "All components are selected" for ApexClass instead of the list of selected components. 7. A code fix was applied to the Version Control module to correct a use-case error displaying unwanted characters, such as different language letters, like “— in the message: "Please wait†when a compare and commit is in progress." 8. A code fix was applied to the Version Control module due to a use-case PrevalidationMerge error occurring when the user was trying to approve a Merge Label through an API with an auto-rejected label, the status changed from "Auto-reject" to "Commit." 9. A code fix was applied to the Version Control module after a user observed three gaps/issues in Commit Templates: 1) Data Table Change in the Commit Template under the 'All Metadata' tab should also sync across all three places, like Deployments, VC Commit, and Commit Template under the 'All Metadata' tab for data table changes. 2) Folder-Related Members Visibility: Folder-related all members are not visible when selecting the folder. This does not sync with EZ Commit All Metadata, from new commit all members. When selecting the folder, all respective folder-related members are visible but not included in the Commit Template when selecting the same Salesforce org. 3) Input Search Dropdown Missing for selecting Folders. 10. A code fix was applied to the Data Loader module concerning a use-case error in which the user was unable to create a project journey with a BIC\_\_c field using "LookUp via" feature. Support ticket #110111 #### 22 May 2024 **(ARM 23.1.31)** 1. A code fix was applied to the Version Control module due to a use-case error related to EZ-Commits and EZ-Merges not taking the master branch, even when Baseline Branch "master" is selected. #107151 2. A code fix was applied to the Version Control module due to a use-case error in which reverting a commit failed. #112094 3. A code fix was applied to the Version Control module due to a use-case error related to the system failing to select multiple reports. #112381, #112812 4. A code fix was applied to the Deployment module due to a data error in which the org sync was not completing. #111545 5. A code fix was applied to the Deployment module due to a data error in which there was a problem in component selection during deployment. #111892 6. A code fix was applied to the Deployment module due to a data error in which the selected items tab was now showing the selected components, as well as the search filter not always being visible. #112095 #### 15 May 2024 **(ARM 23.1.30)** 1. Code fix applied to Deployments module due to user receiving error message: INVALID\_LOGIN: Invalid username or password or security token or API version or user locked out. #111008 2. Code fix applied to Version Control module due to user not being able to see the merge request label name in BitBucket after merging. This required a feature flag, MERGE\_STRATEGY\_ENABLE\_NON\_FF, which is not enabled by default and must be enabled. #110541 3. Code fix applied to the Deployments module related to user experiencing Redeploy/Promote hanging if previous deployment used specified tests. This requires a feature flag, AR\_33697\_ENABLE\_APEX\_TEST\_GET\_CALL, which is not enabled by default and must be enabled. #110764 4. Code fix applied to Deployments module related to email templates of type Visualforce not being added to the package.xml when deploying. #110762 5. Internal - Code fix applied to Version Control module due to DX Package Directory Selection lists not being visible when configuration changes from Vlocity SF org and Vlocity repo to DX Repo. 6. Code fix applied to Version Control module related to an auto-rejected merge label being pushed to a remote repository. #112244 #### 7 May 2024 **(ARM 23.1.29)**
ModuleSummaryStatusFix VersionResolutionCause

Version Control

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

QA Passed

23.1

Code fix

Configuration

Version Control

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

QA Passed

23.1

Code fix

Use case

Version Control

Commit Issue with Custom Page Web Links Deletions

QA Passed

23.1

Code fix

Use case

Version Control

Configure Gated Check-Ins Report for Deployment Validation

QA Passed

23.1

Code fix

Use case

Version Control

Improve Performance of All Metadata Components Screen

QA Passed

23.1

Code fix

Use case

Administration

EBR User Metrics

Done

23.1

Code fix

EBR Change Request

Data Loader

Data Loader Pro jobs not picking up Records

Customer Coordination

23.1

Added Loggers

Use case

#### 29 April 2024 **(ARM 23.1.28)**
ModuleSummaryStatusFix VersionResolutionCause

Deployments

Getting error on deployments

QA Passed

23.1

Code fix

Use case

CI Jobs

Skip member is not working

QA Passed

23.1

Code fix

Use case

Version Control

EZ-Commits failing

QA Passed

23.1

Code fix

Use case

Version Control

Static resources not identified by ARM SCA

QA Passed

23.1

Code fix

Use case

Version Control

Merge showing as no modifications

QA Passed

23.1

Code fix

Use case

Version Control

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

QA Passed

23.1

Code fix

Use case

Reports

Inquiries regarding report module

QA Passed

23.1

Code fix

Use case

Deployments

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

QA Passed

23.1

Code fix

Use case

CI Jobs

Build did not include second revision

Requires Customer Coordination

 Loggers addedLoggers added

CI Jobs

Run test based on changes, noticed issues

Requires Customer Coordination

Loggers addedLoggers added

nCino

IDs of parents/children and records not resolving

QA Passed

23.1

Code fix

Use case

#### 24 April 2024 **(ARM 23.1.27)**
ModuleSummaryResolutionCause

Version Control

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

Code fix

Use case

Version Control

Release Label: Package is not preparing

Code fix

Use case

Reports

Weekly Reports tab error

Code fix

Use case

Deployments

Backups not being created for user

Code fix

Use case

Version Control

Code Scan Analysis not showing in AR ARM tool - UI

Code fix

Use case

Version Control

setting default repository

Code fix

Use case

Deployments

ExternalCredentialPrincipalAccess (permissionSet) is ignored on a git revision deployment

Code fix

Use case

Version Control

Unknow error while merging site components

Code fix

Use case

CI Jobs

CI Job does not deploy all components

Code fix

Use case

Admin

SSH connectivity issue

Code fix

Use case

Version Control

request_closure_duration_mins mismatch for the merges

Code fix

Use case

Reports

B2C Prod Code Scan report

Code fix

Use case

nCino

AR issues

Added Loggers

Use case

Dataloader

User Object Requiring ALL Fields for Uploads

Added Loggers

Use case

#### 14 April 2024 **(ARM 23.1.26)**
ModuleSummaryStatusVersionResolutionCause
DeploymentsOrg Sync issue with case componentsQA Passed23.1Code fixUse case
DeploymentsB2C Org sync diff mail notification issueQA Passed23.1Code fixUse case
CI Jobs, DeploymentsEinstein Chatbot Deployments FailingQA Passed23.1Code fixUse case
Adminlog files are not presentQA Passed23.1Code fixUse case
DeploymentsDeployments are not workingQA Passed23.1Code fixUse case
CI Jobs, DeploymentsFailed to initiate the deploymentQA Passed23.1Code fixUse case
Version controlProfile commit progress delayQA Passed23.1Code fixUse case
AdminTeam Administrator modifications creating duplicate Teams and consuming existing licensesQA Passed23.1Code fixUse case
Version controlIssue Retrieving Components QA Passed23.1Code fixUse case
Version controlRelease Label Stuck while building ArtifactRequires Customer CoordinationLoggers added
Deploymentsutils.js was not deployed as part of packageRequires Customer CoordinationLoggers added
nCinoVersion control record deployments to Salesforce Environments falling offQA Passed23.1Code FixUse case
nCinoLack of Consistency in Filter Functionality Across Feature Management, Deployment History, Commit History, and CI JobsQA Passed23.1Code FixUse case
Version controlUnable to view the Autodraft date and managed package changes dropdownQA Passed23.1Code FixUse case
AdminSuper Admin EBR Token Security Enhancement Done23.1Code fixInternal change request
#### 3 April 2024 **(ARM 23.1.25)**
ModuleSummaryResolutionCause
Reports, CI Jobs, Deployments, Version ControlARM overwrites any exclusions set up in CodeScan UI * Requires documentation.

Code Fix

Change Request

DeploymentsSingle revision deployment taking longer time to retrieve revision

Code Fix

Use Case

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

Code Fix

Use Case

Version ControlGetting empty revision when performing single revision merge with no modifications

Code Fix

Use Case

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

Code Fix

Use Case

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

Code Fix

Use Case

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

Code Fix

Use Case

nCinoVersion control record deployments to Salesforce environments dropping offCode FixUse Case
#### 27 March 2024 **(ARM 23.1.24)**
ModuleSummaryStatusVersion ReportedFix Version(s)ResolutionCause

Deployments

Org Sync question on Moderation Rule difference

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to create EZ-Commit for the new user

QA Passed

23.1

23.1

Code Fix

Use Case

Reports

Problem with scheduled code coverage reports

QA Passed

23.1

23.1

Code Fix

Use Case

Deployments

Profile Comparer - Taking too long to deploy

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Issue in Merging

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Incorrect merge status issue

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

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

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Vlocity DataPacks not being baselined

QA Passed

23.1

23.1

Code Fix

Use Case

Admin

Getting stuck in loading when trying to Expand ALM mappings

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

CI Deploy job link throwing pop-up error message

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

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

Customer Coordination

23.1

NA

No Code FixLoggers Added

nCino

Data Loader Pro jobs failing for Lead

QA Passed

23.1

23.1

Code Fix

Use Case

nCino

nCino Deployment History - search filter criteria is not working

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unnecessary select all checkbox is showing in added and modified tab

QA Passed

23.1

23.1

Code Fix

Use Case

Version Control

Unable to view created credentials

QA Passed

23.1

23.1

Code Fix

Use Case

CI Jobs

Returns all CI Jobs History to EBR Data irrespective of active

Done

23.1

23.1

Code Fix

Internal change request in EBR Data Visibility

nCino

Feature Deployment Issue with Salesforce Org Version Control

QA Passed

23.1

23.1

Code Fix

Use Case

Data Loader Pro

Issue with Audit Fields

QA Passed

23.1

23.1

Code Fix

Use Case

Admin, Version ControlUnable to register the same repository twice *

REQUIRES FEATURE FLAG:
SKIP_DUPLICATE_REPOSITORY_REGISTRATION_CHECK		QA Passed23.123.1Code FixUse Case
CI JobsError Message: Cannot invoke "String.startsWith(String)" because the return value of "com.autorabit.entity.admin.UserProject.getProjectType()" is null. Support ticket # 109042QA Passed23.123.1Code FixUse Case
#### 20 March 2024 **(ARM v. 23.1.23)**
ModuleSummaryStatusFix VersionResolutionCause

CI Jobs

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

QA Passed

23.1

Code Fix

Use Case

Version Control

Regarding unable to approve commit request

QA Passed

23.1

Code Fix

Use Case

Version Control

Very slow commits

QA Passed

23.1

Code Fix

Use Case

Version Control

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

QA Passed

23.1

Code Fix

Use Case

Version Control

Issues after Branching Baseline

Requires Customer Coordination

Added Loggers

No Code Fix

Reports

Static Code Analysis fails with timeout error

Requires Customer Coordination

Post fix awaiting customer confirmation.

Code Fix for SF CL timeout configuration.

Admin

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

QA Passed

23.1

Code Fix

Use Case

CI Jobs, Deployments

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

QA Passed

23.1

Code Fix

Use Case

Flow Center

Enable SSL for the Kafka used to communicate with FlowCenter.

QA Passed

23.1

Code Fix

 Use Case

nCino

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

QA Passed

23.1

Code Fix

Use Case

Data Loader Pro

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

QA Passed

23.1

Code Fix

Use Case

#### **13 March 2024** **(ARM v. 23.1.22)**
ModuleSummaryFix VersionResolutionCause
DeploymentsProfile Comparer was taking too long to deploy

23.1

Code Fix

Use Case

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

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

23.1

Code Fix

Use Case

DeploymentspackExport is not failing when selecting data packs

23.1

Code Fix

Use Case

CI JobsStatus Check API working incorrectly on UI

23.1

Code Fix

Use Case

CI JobsIssue when deploying the release to the master branch

23.1

Code Fix

Use Case

Version ControlIssue 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 ControlIntermittent issue with the Merge screen

23.1

Code Fix

Use Case

Version ControlCommit Labels within EZ-Merge no longer sorted by latest Commits

23.1

Code Fix

Use Case

ReportsCodeScan analysis discrepancies in APAC Prod * Requires documentation update

23.1

Code Fix

Use Case

Version ControlTerritory metadata type is not fetched as destructive changes during EZ-Commit.23.1Code FixUse Case
DataloaderDataloader Pro was not copying over Contact fields when migrating data

23.1

Code Fix

Use Case

DataloaderWhen 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 JobsDeployment stuck23.1Code FixUse Case
#### 6 March 2024 **(ARM v. 23.1.21)**
ModuleSummaryVersionResolutionCause

ARM

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

23.1

Code Fix

Use Case

Deployments

Org Sync issue

23.1

Code Fix

Use Case

Admin

Unable to Log in to AutoRABIT via Okta

23.1

Code Fix

Use Case

Version Control

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

23.1

Code Fix

Use Case

Version Control

EZ-Commit Salesforce Org Authors not completed

23.1

Code Fix

Use Case

CI Jobs

Dashboards and reports were overwritten after the deployment to PROD

23.1

Code Fix

Use Case

Admin

Suggestion-SF org UI

23.1

Code Fix

Use Case

Reports

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

23.1

Code Fix

Use Case

Admin

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

23.1

Code Fix

Use Case

Version Control

Added metrics in ARM DB

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

nCino

CI Jobs Build Page - Pagination displayed as "undefined"

23.1

Code Fix

Use Case

nCino

nCino CI jobs - Date Literals Value not being populated

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

nCino

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

23.1

Code Fix

Use Case

Dataloader

Unable to migrate related EmailMessage records of Case

23.1

Code Fix

Use Case

CI JobsUnable to view API 59 version in CI configuration under API version dropdown.23.1Code FixUse Case
#### 28 February 2024 **(ARM v. 23.1.20)** | Module | Summary | Resolution | Cause | Feature Flag | | -------------------------------------- | ------------------------------------------------------------------------------------- | -------------------------------- | ------------------------------------- | ----------------------------------------- | |

Admin

| Login Error |

Code Fix

|

Use Case

|

| |

Ci Jobs

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

Code Fix

|

Use Case

|

| |

ARM

| SF CLI version upgrade to 2.28.6 for ARM 23.1 instances |

Code Fix

|

Change Request

|

| |

Version Control

| Able to approve auto-rejected merge from email |

Code Fix

|

Use Case

|

| |

Version Control

| PersonAccount AutoRABIT bug |

Code Fix

|

Use Case

|

| |

CI Jobs

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

Code Fix

|

Use Case

|

| |

SFDX

| Error on create package version and install type of job. |

Code Fix

|

Use Case

| AR\_33235\_SKIP\_UPDATE\_PACKAGE\_COMMAND | |

Dataloader

| CPQ Dataload in Developer Sandbox - Errors |

Code Fix

|

Use Case

|

| |

nCino

| nCino CI Job issue |

Code Fix

|

Use Case

|

| |

Dataloader

| Invalid CSV file. Please check for blank columns. |

Code Fix

|

Use Case

|

| |

Dataloader

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

Code Fix

|

Use Case

|

| |

Version Control

| Getting Undefined Error for target branch in External Pull request |

Code Fix

|

Use Case

|

| |

Version Control

| Unable to resolve conflicts in release label merge. |

Code Fix

|

Use Case

|

| |

Flow Center

| Search & Substitute rules are not applied in the pipelines. |

Code Fix

|

Use Case

|

| #### 21 February 2024 **(ARM v. 23.1.19)** | 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)**
ModuleSummaryStatusFix Version(s)ResolutionCauseFeature enabled by defaultFeature Flag Name

Deployments

Upgrade to 23.1.16 + Ubuntu OS Upgrade

QA Passed

23.1

Code Fix

Use Case

NO

NO

Dashboards

ARM dashboard

QA Passed

23.1

Code Fix

Use Case

NO

NO

Deployments

Org sync - Scheduler not working

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Commit failing without any logs

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Single-revision merge taking a long time

Customer Coordination [Added Loggers]

No Code Fix - Added Loggers

No Code Fix - Added Loggers

Data

NO

NO

Version Control

Package.xml fetching the Excluded components during Commit

QA Passed

23.1

Code Fix

Use Case

NO

NO

Deployments

Smart checkbox redeployment

QA Passed

23.1

Code Fix

Change Request

NO

NO

Version Control

PG and ARM instances not working as expected

QA Passed

23.1

Code Fix

Use Case

NO

FILE_SYNC_WITH_OPTIMISTIC_LOCK

Version Control

Commit not getting detected

QA Passed

23.1

Code Fix

Use Case

NO

NO

Version Control

Error while trying to select the revision from branch

QA Passed

23.1

Code Fix

Use Case

NO

NO

#### 7 February 2024 **(ARM v. 23.1.17)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

nCinoPartial error on CI Job - nCino-Fee TemplateQA Passed23.1Code FixUse Case
#### 28 January 2024 **(ARM v. 23.1.16)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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 ProMultiple issues during data maskingCustomer Coordination – Added Loggers23.1No Code Fix – Added LoggersData
#### 21 January 2024 **(ARM v. 23.1.15)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

23.1

Code Fix

Use Case

Version Control

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

23.1

Code Fix

Use Case

Version Control

Finding WaveDataflow components for commitQA Passed

23.1

Code Fix

Use Case

Admin

Error: Access token as failed while doing a branching baselineQA Passed

23.1

Code Fix

Use Case

CI Jobs

Provar version upgradeQA Passed

23.1

No Code Fix – Only Configuration change for specific customerCustomer-specific

Version Control

Initial commit failingCustomer CoordinationNo Code Fix – Added LoggersData

Admin

Users’ permissions are being reset.Customer CoordinationNo Code Fix – Added Loggers

Data

CI Jobs, Version Control, Admin, DeploymentsAdding authentication check on web hook APIsQA 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 DeploymentsQA Passed

22.3
23.1

Code Fix

Use Case
#### 14 January 2024 **(ARM v. 23.1.14)**
ModuleSummaryFix Version(s)ResolutionCause
MODULESUMMARYFIX VERSIONRESOLUTIONCAUSE
Version Control Internal - Default SCA branch not reflected while merging 23.1

Code Fix

Use Case

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

DeploymentsDeployment status failed when deploying Vlocity components 22.3, 23.1

Code Fix

Use Case

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

23.1

Code Fix

Use Case

DeploymentsBrazil Prod to UAT deployment issue

23.1

Code Fix

Use Case

nCino Metadata update is failing

23.1

Code Fix

Use Case

Version ControlCommit not progressing

23.1

No Code Fix - Loggers Added

Data
#### 7 January 2024 **(ARM v. 23.1.13)**
ModuleSummaryFix VersionResolutionCause

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)**
ModuleSummaryFix VersionResolutionCause

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)**
ModuleSummaryVersion(s)ResolutionCause

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

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

23.1, 22.3

Code Fix

Use Case

Version ControlUnable 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 | NA | No Code Fix - Added Loggers | Data | | Deployments | Org sync not completing | NA | No Code Fix - Added Loggers | Data | | Dataloader | Corrected a spelling mistake in ARM steps. | 23.1, 22.3 | Code Fix | Use Case | | Dataloader | Corrected data seeding error preventing upsert | 23.1, 22.3 | Code Fix | Use Case | | Reports | Getting ‘cannot invoke "String.length()" because of "text" is “null”’ error when performing the ‘Get latest reports’ in Weekly reports | 23.1 | Code Fix | Use Case | | Reports | When navigating to Static Code Analysis screen from Reports module, getting the “comparison method violates its general contract!” error. | 23.1 | Code Fix | Data | | Version Control | On DX branch release label artifact execution, on deleted components, the destructive changes artifact preparation is not generated. | 23.1 | Code Fix | Use Case | | nCino | On-premise testing: CI Job with template option failed due to "data and metadata retrieval failed” error | 23.1, 22.3 | Code Fix | Use Case | | CI Jobs | Failed to deploy destructive changes though CI jobs. | 23.1 | Code Fix | Use Case | #### 26 November 2023 **(ARM v 23.1.9)**
ModuleSummaryFix Version(s)ResolutionCause
AdminBranching baseline issue23.1Code FixUse Case
CI JobsThe new feature of merging only revision in the CI job build is not working23.1Code FixUse Case
CI JobsCI job filter not working properly23.1Code FixUse Case
Version ControlCommit not getting detected23.1Code FixUse Case
Version ControlRejecting a commit is merging the changes23.1Code FixUse Case
AdminUnable to save Pull Request Plugin config23.1Code FixUse Case
Version ControlAR commit File Diff process is failing with errors23.1Code FixUse Case
Version ControlMerge auto-rejected but CI job triggered23.1Code FixUse Case
AdminChanging role from Dev to Admin shows orgs and branches in New EZ- Commit without mapping under profile23.1Code FixUse Case
Version Control and DeploymentRelease Label Artifact not including code for a commit23.1Loggers AddedData
DataloaderDataloader Pro jobs causing huge threads pileup23.1EnhancementUse Case
CI JobsData 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.1Code FixUse Case
Version ControlWhile submitting the ALM commit with these “<ALM Issue ID>“, “{ALM Issue ID}” ALM patterns, unable to submit the commit23.1Code FixUse Case
DeploymentsSub-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" error23.1Code FixUse Case
Version ControlWith Release label deployment, the flow-meta.xml retrieval issue both constructive and destructive23.1Code FixUse Case
#### 22 November 2023
ModuleSummaryFix Version(s)ResolutionCauseEnabled by default?Feature Flag Name
Version ControlBranch Protection Policy enforced and behavior of EZ- merge23.1Code FixUse CaseNOGIT_LOGGEDIN_USER_AS_COMMIT_USER
Version ControlIssue while creating feature branches in EZ - Commit screen23.1Code FixUse Case
Version ControlUpload File option not available during EZ- commit with Option package manifest23.1Code FixUse Case
#### 19 November 2023 **(ARM v. 23.1.8)**
ModuleSummaryFix VersionResolutionCause
DeploymentsDeployment tab - Redeploy/Promote issue22.3, 23.1Added LoggersData
DataloaderOptimize the Dataloader Pro job logs in the rabit cs log23.1Code FixUse Case
nCinoUnable to create Feature Migration Template on Debt Schedule object22.3, 23.1Code FixUse Case
All ModulesInvalid Email ID22.3, 23.1Code FixUse Case
CI Jobs, Deployments, Version Control, AdminOrg Sync diff report differs for the same source org compared to different orgs.23.1Code FixUse Case *
DataloaderUrgent: AutoRABIT is down23.1Code FixUse Case
Version ControlIssue with Block button during Merge Conflict23.1Code FixUse Case
CI JobsCI job deployment failing: Restriction rules deployed as moderation rule and made the deployment bugged23.1Code FixUse Case
CI JobsUrgent: Rollback of specific components - Issue23.1Code FixUse Case
CI JobsUnexpected behavior when disabling component category on rollback destructive changes.23.1Code FixUse Case
SFDXError while using Scratch Org Management tab23.1Code FixUse Case
All ModulesARM<>ULP Integration Issues23.1Code FixUse Case
Version ControlAuto-reject on commit validation for SCA & Auto-reject setting in Merge23.1Code FixUse Case
#### 15 November 2023
ModuleSummaryFix VersionResolutionCause
CI JobsCI Job is not picking up changes committed on the branch, indicating "No modifications made."23.1Code FixUse Case
DeploymentsOrg Synchronization – constructive & destructive changes are not working together23.1Code FixUse Case
AdminSync error between ARM and GIT23.1Code FixUse Case
Version ControlDeployment validation not working correctly during new EZ-Merge23.1Code FixUse Case
CI JobsMerging only revision in the CI job build not working23.1Code FixUse Case
#### 12 November 2023 **(ARM v. 23.1.7)**
ModuleSummaryFix Version(s)ResolutionCause
DeploymentsDuring Org Sync, file names are being repeated as part of the deployment results.23.1Code FixUse Case
DeploymentsUser is unable to see the Deployment History.23.1Code FixUse Case
CI Jobs & DeploymentsUser is unable to deploy static resource.23.1Code FixUse Case
ReportsScheduled Code Coverage Reports are running at the wrong time.23.1Code FixUse Case
nCinoUser is unable to create Feature Migration Template on Debt Schedule object.22.3, 23.1Code FixUse Case
DataloaderUser is unable to upload files and update records; system logs user out instead.23.1Code FixUse Case
Version ControlUser is getting timeouts in merge screen.23.1Code FixUse Case
#### 5 November 2023 **(ARM v. 23.1.6)**
ModuleSummaryFix Version(s)ResolutionCause
All ModulesSF CLI version upgrade to 2.14.623.1Code FixEnhancement
Environment ProvisioningView environment provisioning templates22.3 & 23.1Code FixEnhancement
AdminBranching baseline is not picking all components from production22.3 & 23.1Code FixUse Case
DeploymentsHelp with destructive change22.3 & 23.1Code FixUse Case
Version ControlMerge request is failing due to validation credentials22.3 & 23.1Code FixUse Case
CI Jobs, DeploymentsIssues with a release – related to Feature Flag - not automatically deployed: STANDARD_VALUE_SET_DELTA22.3 & 23.1Code FixData
Version ControlApproval button is not visible after successful merge validation22.3 & 23.1Code FixData
Version ControlCreate artifact: not completed23.1Code FixData
AdminAutoRABIT login not working23.1Code FixUse Case
Version ControlError pop-up during merge type selection as Commit Label in EZ-Merge23.1Code FixData
CI JobsAutoRABIT AccelQ Integration/ bhg-inc.com23.1Code FixUse Case
CI Jobs
Developer API for CI Jobs History not returning latest results.		23.1Code FixUse Case
nCinoAbility to trigger nCino CI jobs using REST API23.1Code FixCustomer Request
CI JobsFor run test automation scripts job: More than one cycle is not displayed in the individual job history23.1Code FixUse Case
Version ControlUnable to delete feature branch under merge request, getting internal server error23.1Code FixUse Case
Version ControlUnable to view the entry of recently created merge request in the merge request history screen23.1Code FixUse Case
Version ControlCriteria met ALM's not getting fetched under merge request23.1Code FixUse Case
nCinoInstead of POST methods need to change the GET23.1Code FixCustomer 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 branc**h 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 **queu**e. * 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 item**s. * 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. # Release Notes 22 ## 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**.\ [**Read more →**](/product-guides/arm/arm-administration/user-management/manage-users-account-settings) #### 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.\ [**Read more →**](/product-guides/arm/arm-features/automation-and-ci/ci-job-list) #### 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.\ ![image.png](https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/image-I1GT03M7.png) *** ### 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. [**Read more →**](/product-guides/arm/arm-features/version-control/change-labels/release-labels) #### 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.\ [**Read more →**](/product-guides/arm/arm-administration/search-and-substitute) #### 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.\ [**Read more →**](/product-guides/arm/arm-administration/user-management/users-roles-and-permissions) #### 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.\ [**Read more →**](#4-dataloader-clone-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 [HERE](/product-guides/arm/arm-features/reports/static-code-analysis) 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 [HERE](https://knowledgebase.autorabit.com/docs/single-dataloader) 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)**
ModuleSummaryStatusFix Version(s)ResolutionCause

Deployment

Vlocity Deployment issue

QA Passed

22.3, 23.1

Code Fix

Use Case

Version ControlNot fetching merges when trying to create a release label for Vlocity componentsQA Passed22.3Code FixUse Case
#### 21 January 2024 **(ARM v. 22.3.53)**
ModuleSummaryStatusFix Version(s)ResolutionCause

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

22.3
23.1

Code Fix

Use Case
#### 14 January 2024 **(ARM v. 22.3.52)**
ModuleSummaryFix Version(s)ResolutionCause
MODULESUMMARYFIXVERSIONRESOLUTIONCAUSE
Admin

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

22.3

Code Fix

Use Case

DeploymentsDeployment status failed when deploying Vlocity components22.3 23.1

Code Fix

Use Case

**10 December 2023** **(ARM 22.3.51)**
ModuleSummaryVersion(s)ResolutionCause
nCinoUser is unable to do nCino Feature Deployments
* Requires documentation

23.1, 22.3

Code Fix

Use Case

AdminGetting ‘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 | NA | No Code Fix - Added Loggers | Data | | Deployments | Org sync not completing | NA | No Code Fix - Added Loggers | Data | | Dataloader | Corrected a spelling mistake in ARM steps. | 23.1, 22.3 | Code Fix | Use Case | | Dataloader | Corrected data seeding error preventing upsert | 23.1, 22.3 | Code Fix | Use Case | | 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)**
ModuleSummaryFix Version(s)ResolutionCause

CI Jobs

Post activities, particular job status showing as FAILED in ARM even job execution completed with succeed22.3Code FixUse Case

Admin

Getting empty Configuration under "Configure Default SCA Baseline Branches"22.3Code FixUse Case

Admin

Able to view empty role under permissions22.3Code FixUse Case
#### 19 November 2023 **(ARM v. 22.3.48)**
ModuleSummaryFix VersionResolutionCause

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 ID22.3, 23.1

Code Fix

Use Case

#### 15 November 2023
ModuleSummaryFix VersionResolutionCause
DeploymentsPage unresponsive in new deployment for "previous deployment" as source type22.3Code FixUse Case
#### 12 November 2023 **(ARM v. 22.3.47)**
ModuleSummaryFix Version(s)ResolutionCause
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)**
ModuleSummaryFix Version(s)ResolutionCause
All ModulesNew User Creation22.3

Code Fix

Change Request

Environment ProvisioningView environment provisioning templates

22.3 & 23.1

Code Fix

Enhancement

AdminBranching baseline is not picking all components from production

22.3 & 23.1

Code Fix

Use Case

DeploymentsHelp with destructive change

22.3 & 23.1

Code Fix

Use Case

Version ControlMerge request is failing due to validation credentials

22.3 & 23.1

Code Fix

Use Case

CI Jobs, DeploymentsIssues with a release – related to Feature Flag not automatically set: STANDARD_VALUE_SET_DELTA

22.3 & 23.1

Code Fix

Data

Version ControlApproval 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)** **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 **ProcessInpu**t 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: 1. 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. 2. Implemented a code fix associated with the **version control** module for a use-case error in which **ALM working items were not loading**. 3. Implemented a code fix for a use-case error pertaining to the **version control** module for an **approval email notification error**. 4. 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. 5. 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. 6. 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. 7. Implemented a code fix related to the **nCino** module error: | **LLC\_BI\_\_Schedule\_Section\_\_c migration issue#1** | | ------------------------------------------------------- | 8. 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. 9. 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 ([#73824](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000114206402)). * 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 ([#72073](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112029001)). * Fixed an issue where user was trying to create an connect an **Active Directory** but it kept failing ([#73582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113941053)). * 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 ([#73371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113607033) and [#56084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091215009)). * 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 ([#71444](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111273077)). * 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 ([#71367](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111185001)). * Fixed an issue where deploying test classes from manual deployment was throwing an out of memory error ([#71872](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111679026)). * 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 ([#72181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112197081)). * 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** ([#72811](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112765004)). * 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 ([#72817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112807012)). * Fixed an issue where the **Git author** was overridden by ARM ([#71393](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111202442)). * 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** ([#73515](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000113850003)). * 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 e**xternal 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 ([#71947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111886005)). * 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` ([#72217](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112229003)). * 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 ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * 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 ([#72751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112682583)). * Fixed an issue where CI job deployment was failing because the build was picking duplicate **Layout** values ([#71214](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110698400)). * Fixed an issue where unwanted metadata changes were observed in the **package.xml** file while performing a commit ([#72089](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112054140) and [#71820](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111655842)). * Fixed an issue where **Branching Baseline** was not picking all the components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * 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 ([#58549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095408144) and [#38339](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064118003)). * Fixed an issue with **nCino** where CI jobs that used a **Deployment** from **Version Control** were failing when the build was triggered ([#71914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111840343)). * 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 ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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 ([#70787](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110191524)). * Fixed an issue where **Destructive Changes** wasn't working as expected while performing an **Entire Branch** merge ([#68882](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107824070)). * Enhanced the ALM management feature by adding an option to sync **Smart Commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * Fixed an issue with **CI Jobs** **Destructive Sharing Rule** was not deploying to the Salesforce org ([#71183](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110703254)). * Fixed an issue where user could not disable the **Smart Commits-Sync** option for a repository branch in the **VC repos section** ([#70854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110258586)). * Improved the **New Merge** screen by removing the **Validate Deployment** option from the UI if **Vlocity** is selected ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * Enhanced the **Credentials** module by adding **SSH Cetificate** option for **Git Authentication** ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * 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 ([#70400](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109643126)). * Fixed an issue where **Branching Baseline** was taking longer than expected ([#67814](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777192)). * Fixed an issue where using the **AutoDraft** functionality in **EZ-Commit** was resulting in a malformed exception in the UI ([#70458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109706018)). * Fixed an issue where **Branching baseline** was not picking all components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * Fixed an issue where **prevalidation merge** failed with empty metadata package even though there were changes in **File Diff** ([#32256](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000049822310)). * Fixed an issue where entire **ARM** application was down temporarily ([#70658](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110024189)). * Fixed an issue where **Merge** was **auto-rejected** due to an empty package because the **metadata folder path** not being specified under branch settings ([#69788](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108851098)). * 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` ([#70868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110350003)). * Fixed an issue where users weren't receiving **SCA reports** by email even though the reports were running ([#70751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110137323)). * Fixed an issue where while performing new **EZ-Commit**, user edited one line using review artifact option but **Diff** did not capture the same ([#70270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109345141)). * 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 ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * Fixed an issue where CI Job was picking changes one build but not for the other, and the logs weren't capturing this ([#69164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108123319)). * 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 ([#67654](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106594374)). * Fixed an issue where user merged a new component using a single revision merge but the merge missed to perform a CodeScan analysis ([#70391](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109502039)). * 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 ([#70351](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109465295)). * Fixed a UI issue where **OK** button to reject an EZ-Merge was not working ([#70041](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108965683)). * Fixed an issue where a field was available in the package but still Validation was throwing error that the field was missing ([#69831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108972528)). * Fixed an issue with **DataLoader** where multiple jobs were not processing parallelly when user loaded a large number of jobs to the queue ([#62559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100372446)). * 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` ([#69831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108972528)). * 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`. ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * Enhanced the **VC Repos** page by introducing a feature that allows users to **sync external smart commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * 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 ([#69772](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108841212)). * 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 ([#68012](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107136001)). * 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 ([#69614](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108583086)). * 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 ([#47794](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081201667)). * Fixed an issue with nCino where CI job filter changes on templates were not taking effect after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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** ([#48644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082753293)). * Enhanced **Vlocity CI jobs** by allowing **Local Compilation** for **Omniscript** and **Flexcard** objects ([#55641](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090230148) and [#50301](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084720103)). * Fixed an issue where user was unable to use the **Redeploy/Promote** option after ten iterations of an existing **Deployment** label ([#69084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108041156)). * 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 ([#67826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777838)). * 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 ([#67818](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777588)). * Fixed an issue where **EZ-Merge** was failing with `NullPointerException` ([#67502](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106282031)). * 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?`** ([#65565](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104611176)). * Fixed an issue where **Revert** commits were failing without any error messages ([#68771](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107671065)). * 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 ([#68939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107912007)). * Fixed a UI bug where when user unchecked **Validate deployment** option in **EZ-Merge**, the **Run destructive changes** checkbox was hidden ([#68750](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107699066)). * 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 ([#65680](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104849001)). * 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 ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 ([#59458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096457374)). * 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 ([#66587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105697158)). * Fixed an issue where **Git backup job** was failing due to unsupported metadata ([#66536](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105610003)). * Fixed an issue where scheduled CI jobs were getting queued or not getting triggered as per schedule ([#57749](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093607144)). * Fixed an issue where **Quick action** was not picked for destructive changes ([#65058](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104091725)). * 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 ([#63234](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101513612)). * Fixed an issue where user using **non-SFDX** repo with **Custom API** enabled failed to pick the changes in the CI job ([#64497](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103321171)). * Fixed an issue where **Release label** displayed **commit revisions** older than 30 days even when the **No. of days** filter was set as **30** ([#63845](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102526769)). * Fixed an issue where a user had trouble creating **artifact** for a **release label** ([#65557](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104667180)). * 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 ([#65625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104812001)). * 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 ([#66655](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105749754)). * Fixed an issue with **nCino** where CI job build status is displayed as **Completed** for a failed job ([#64479](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103318168)). * Fixed an issue with **nCino** where attachements to `nFORMS__Form_Template__c` failed to get deployed ([#65242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104379896)). * Fixed an issue where user was unable to initiate **static code analysis** on a Salesforce Org ([#51559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085951433)). * Fixed an issue with **New EZ- Commit** where while using **Custom YAML** file the page was taking much longer to load than usual ([#65742](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104883025)). * Fixed an issue where **Merge** was happening on incorrect files ([#64485](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103318553)). * 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 ([#65058](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104091725)). * 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)` ([#60914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097801217) and [#65855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105051054)). * Fixed an issue where **WebStoreTemplates** object was not available for deployment ([#65854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104921177)). * Fixed an issue where **Merge Request XML** file was conflicting with an error `No conflict data found for this block` ([#65164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104169938)). * Fixed an issue where **Release label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * 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 ([#64612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103417610)). * Fixed an issue where user was unable to merge the code from one branch to another branch. ([#65570](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104676278)). * Fixed an issue where **Ignore Missing Visibility** settings not working on **EZ-Merge** validation ([#65162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104186080)). * Fixed an issue where user was loading multiple **DataLoader** jobs but it was not processing parallelly ([#62559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100372446)). * 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` ([#64228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103003760)). * Fixed an issue where multiple deployment requests were being generated while performing **Org Sync** if the user selected all components instead of a few ([#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where **Rollback API** threw a **200** response but the Rollback immediately failed in the ARM UI ([#65146](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104115380)). * Fixed an issue where SCA report Failed to run using the **Codescan Plugin** with the following Salesforce error `384187622-16951 (-673032061)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151)). * Fixed an issue where users were having trouble logging in to ARM due to an error `Session Invalid` ([#64965](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103959064), [#65052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104090509), and [#64969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104016027)). * 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** ([#64094](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102809037)). * Fixed an issue where **Auto-draft** was taking much longer than expected to retrieve the metadata in **EZ-Commit** ([#65109](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104022403), [#65007](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104076001), [#64950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103943001), [#64510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103338015), [#64645](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103513158), [#64161](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102852098), and [#64523](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103361369)). * 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 ([#64185](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102875003)). * 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 ([#64150](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102831529)). * Fixed an issue where user was unable to retrieve **MutingPermissionSet** using the **SFDX** repository ([#64141](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102573686)). * Fixed an issue where the **Release Label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * Fixed an issue where **Sharing Rule Set** metadata type was found in the **Deployment** module but not in the **Version Control** module ([#65060](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104102165)). * 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 ([#65091](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104040481)). * 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 ([#63554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101980029)). * 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 ([#63272](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101591692)). * Fixed an issue where user was unable to deploy a CI job with the **RelationshipGraphDefinition** components ([#64145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102836208)). * Fixed an issue where **Validate** deployment was displayed as **failed** in UI and the database, but was successful as per the logs ([#63868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102596005)). * Fixed an issue with **Review Artifact** where similar custom fields from different objects were not populating correctly and switching to other fields ([#63676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102181836)). * 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 ([#63544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101947159)). * Fixed an issue where user chose **Exclude Metadata Type** for a particular metadata type during a **CI Job**, but it was still deployed ([#62966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101046005)). * Fixed an issue where user was unable to perform **Destructive Commit** with **PermissionSetGroups** metadata type ([#63172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101463001)). * Fixed an issue where users weren't receiving emails after setting up **Mail Settings** ([#55070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089394047)). * Fixed an issue where there was a discrepancy between **EZ-Commit** and **Commit templates** while retrieving **Email Template** metadata members ([#61696](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099121314)). * Fixed an issue where **Merge Labels** were taking much longer than expected ([#62625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100474287)). * Fixed an issue where user tried to commit the changes without validation and UI displayed an error `Another commit is in progress` ([#61930](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099562127)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the **Commits History** page ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Fixed an issue where **Merge** was not auto-rejected when validation criteria was not met ([#62287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100008338)). * Enhanced **nCino** by adding an option to specify **Baseline Revision** in **Continuous Integration** for **Version Control** to perform feature deployments ([#43642](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073759034) and [#44506](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074950579)). * Enhanced **nCino** by allowing users to deploy nCino **CI build** to multiple target sandboxes ([#41763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070674305)). * 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 ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Enhanced the **Release Label** creation by increasing the range of retrievable commit history ([#61714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099129934)). * Fixed an issue where user was unable to use **Release Labels** to perform **Deployment**, and it failed while trying to **Create Artifact** ([#59429](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096450140)). * Fixed an issue where users with non-admin access were unable to register branches in **EZ-Commit** since upgrading to version 22.3 ([#62723](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100650673), [#62949](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101016055), [#62979](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010456), and [#62969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010302)). * 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 ([#61403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098537015)). * 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 ([#60531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097360001)). * Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs ([#61079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097987087)). * Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in **EZ-Commit** ([#56188](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091240174)). * Fixed an issue where user was customer trying to register a **Salesforce Org** with **Custom URL** but it was failing with an error ([#62192](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099509581)). * Fixed an issue where user was unable to remove **Revisions**/**Commit Labels** from a **Release label** ([#59152](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096005470) and [#61578](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098950203)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed an issue where user user uploaded a **YAML file** to retrieve the **Vlocity components** but ALL metadata types were retrieved and displayed ([#61181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248158)). * Fixed an issue where the same merge could be approved and rejected by different users simultaneously ([#60859](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097787146)). * 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** ([#61551](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098913200)). * 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 ([#59082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096042290)). * Fixed an issue where **Dependency** order defined in **json** file was being changed on every commit but it was not supposed to ([#57731](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556797)). * Fixed an issue where **Create Artifact** was not working as expected while using **Release Label** ([#61607](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098932152)). * 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 ([#61751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248378)). * Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes ([#61736](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099207347)). * 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 ([#57318](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092768029)). * Fixed an issue with **Backup from Org CI Jobs** where **PermissionSet User Permissions** were being deleted ([#59674](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096685144)). * Fixed an issue where **Org to Org Deployment** for **Profiles** including **Deploy Profile Access Settings for selected components only** was not working as expected ([#60559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097375154)). * Fixed an issue where **Post Destruct** fields were also added to **Pre Destruct** despite the user setting it to post ([#61162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248005)). * Fixed an issue where user set the **Max depth** value as '0' under **Vlocity Configuration Settings** but it was retrieving all level dependancy components ([#57501](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093212471)). * Fixed an issue with DataLoader where the **Credit Memo Template** migration was not deploying after user upgraded their instance ([#57676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093470003)). * Fixed an issue where user selected **Custom Metadata** members (records), but **EZ-Commit** was failing to generate **File Diff** with `Null` error ([#59709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096706005)). * Fixed an issue where **Merge** was taking longer than usual, and then failing with `Null Exception` ([#60757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097574427)). * Fixed an issue where **EZ-Commits** and **EZ-Merges** were taking much longer than usual ([#58098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094302292)). #### 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` ([#60597](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097399881)). * 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` ([#59050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095999076)). * Fixed an issue where **Reports** deployment validation failed in **EZ-Merge** but was successful in **EZ-Commit** and **Deployment** modules ([#57714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093587003)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error `null` at **Diff** ([#59919](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096907001)). * 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 ([#59359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096219627)). * Fixed an issue where commit was running for longer and remained **in-progress** and **validation check log** is also in progress ([#59199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096003630)). * Fixed an issue where commits with SFDX metadata structure are **failing** in metadata **retrieval stage** ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * Fixed an issue where user couldn't create a managed package with the selected ancestor ([#59044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095985421)). * Fixed an issue where **CI Job** was occasionally failing with the error `BUILD FAILED` ([#57647](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093370172)). * Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user ([#55438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089958034)). * 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 ([#59040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095982206)). * 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 ([#58044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094164003)). * Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error: `Invalid Private Key` ([#59244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096134293)). * Fixed an issue where user has created a Commit label but it was not available while trying to perform an **EZ-Merge** ([#55176](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089550097)). * Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff ([#59114](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096048883)). * Fixed an issue where user was getting an error while trying to create a new branch in GitHub ([#59193](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096138920)). For more information, click [here](https://knowledgebase.autorabit.com/docs/faqs-version-control?highlight=$%20ssh-keygen%20-t%20rsa%20-b%204096%20-C#why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh). * 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 ([#59402](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096425001)). * 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` ([#59028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095867179)). * 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 ([#58998](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095876003)). * 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 ([#59014](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095898340)). * 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 ([#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556)). * Fixed an issue with user received 6 notifications for a failed **CI Job** instead of 1 ([#58436](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095199003)). * Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error: `Lower Region` ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * 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 ([#51268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085726862)). * Fixed an issue where while performing destructive changes in **EZ-Commit**, it was creating **package.xml** in root path folder in **SFDX** structure ([#57868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093790001)). * 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 ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189)). * Fixed a build bug where **CI Job Build** was failing during package preparation **step 5** failing while commiting **DecisionMatrixDefinition** and throwing an error ([#58376](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095049142)). * 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\ ([#58478](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095251543)). * Fixed an issue where generating **Diff** for a **Commit Label** was taking much longer than expected ([#55220](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591780)). * Fixed an issue where **Code coverage** job was running **4 hours** earlier than scheduled every time services were restarted ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * 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 ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * Fixed an issue where **Merge validation** failed to process when there was a **Flow** metadata ([#58244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094983001), [#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556), and [#58438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095210005)). * 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 ([#57898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093797903)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). * Fixed an issue where AutoRABIT **SSH credentials** were failing with an error `Auth failed` while trying to connect with **AWS CodeCommit** ([#53694](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087714369)). * Fixed an issue where **EZ-Commit Diff** was taking approximately 4 hours while **Refactoring CustomField**, which is much longer than expected ([#56650](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091636348)). * 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 ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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 ([#53980](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087981132)). * 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 ([#55995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091129007)). * Fixed an issue where **Profile Diff** is working as expected for **Selective Deployment**, but not while using the same profile in the profile manager ([#52868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087005140)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189), [#55754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090487029)). * Fixed an issue where **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). *** ## **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. [**Read more →**](/product-guides/arm/troubleshoot/how-tos/notifications-mail-server-settings) #### 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 [HERE](https://pmd.github.io/latest/pmd_next_major_development.html#list-of-currently-deprecated-rules) 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. [**Read more →**](/product-guides/arm/arm-administration/user-management/manage-users-account-settings) #### 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. [**Read more →**](#3-hashicorp-vault-integration) #### 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. [**Read more →**](/product-guides/arm/arm-administration/user-management/salesforce-api-version) #### 6. Merge to multiple branches With this release, you can choose to **merge** from one **source branch** to multiple **destination branches** upon successful deployment. [**Read more →**](/product-guides/arm/arm-features/automation-and-ci/create-a-new-ci-job/deploy-from-sfdx-branch-to-a-salesforce-org) #### 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. [**Read more →**](/product-guides/arm/arm-administration/alm-management) ### 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 ([#71947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111886005)). * 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` ([#72217](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112229003)). * 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 ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * 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 ([#72751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112682583)). * Fixed an issue where CI job deployment was failing because the build was picking duplicate **Layout** values ([#71214](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110698400)). * Fixed an issue where unwanted metadata changes were observed in the **package.xml** file while performing a commit ([#72089](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000112054140) and [#71820](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111655842)). * Fixed an issue where **Branching Baseline** was not picking all the components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * 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 ([#58549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095408144) and [#38339](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064118003)). * Fixed an issue with **nCino** where CI jobs that used a **Deployment** from **Version Control** were failing when the build was triggered ([#71914](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111840343)). * 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: * Fixed an issue where wrong **timezone** region was displaying for users ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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: * Fixed an issue where user was having trouble while deploying **LighteningMessageChannel** components ([#70787](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110191524)). * Fixed an issue where **Destructive Changes** wasn't working as expected while performing an **Entire Branch** merge ([#68882](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000107824070)). * Enhanced the ALM management feature by adding an option to sync **Smart Commits** ([#58904](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095643142)). * Fixed an issue with **CI Jobs** **Destructive Sharing Rule** was not deploying to the Salesforce org ([#71183](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110703254)). * Fixed an issue where user could not disable the **Smart Commits-Sync** option for a repository branch in the **VC repos section** ([#70854](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110258586)). * Improved the **New Merge** screen by removing the **Validate Deployment** option from the UI if **Vlocity** is selected ([#70993](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110549364)). * Enhanced the **Credentials** module by adding **SSH Cetificate** option for **Git Authentication** ([#67725](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106632579)). * 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 user was getting a validation deployment error while performing release label deployment ([#70400](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109643126)). * Fixed an issue where **Branching Baseline** was taking longer than expected ([#67814](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106777192)). * Fixed an issue where using the **AutoDraft** functionality in **EZ-Commit** was resulting in a malformed exception in the UI ([#70458](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109706018)). * Fixed an issue where **Branching baseline** was not picking all components from production ([#70720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110077004)). * Fixed an issue where **prevalidation merge** failed with empty metadata package even though there were changes in **File Diff** ([#32256](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000049822310)). * Fixed an issue where entire **ARM** application was down temporarily ([#70658](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110024189)). * Fixed an issue where **Merge** was **auto-rejected** due to an empty package because the **metadata folder path** not being specified under branch settings ([#69788](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000108851098)). * 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` ([#70868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110350003)). * Fixed an issue where users weren't receiving **SCA reports** by email even though the reports were running ([#70751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110137323)). * Fixed an issue where while performing new **EZ-Commit**, user edited one line using review artifact option but **Diff** did not capture the same ([#70270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109345141)). * 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 where **validation jobs** on **Pull Requests** weren't getting triggered ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 CI job deployments were failing with the error, `Error 405 Only POST allowed` ([#64228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103003760)). * Fixed an issue where multiple deployment requests were being generated while performing **Org Sync** if the user selected all components instead of a few ([#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where **Rollback API** threw a **200** response but the Rollback immediately failed in the ARM UI ([#65146](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104115380)). * Fixed an issue where SCA report Failed to run using the **Codescan Plugin** with the following Salesforce error `384187622-16951 (-673032061)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151)). * Fixed an issue where users were having trouble logging in to ARM due to an error `Session Invalid` ([#64965](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103959064), [#65052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104090509), and [#64969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104016027)). * 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** ([#64094](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102809037)). * Fixed an issue where **Auto-draft** was taking much longer than expected to retrieve the metadata in **EZ-Commit** ([#65109](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104022403), [#65007](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104076001), [#64950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103943001), [#64510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103338015), [#64645](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103513158), [#64161](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102852098), and [#64523](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103361369)). * 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 ([#64185](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102875003)). * 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 ([#64150](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102831529)). * Fixed an issue where user was unable to retrieve **MutingPermissionSet** using the **SFDX** repository ([#64141](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102573686)). * Fixed an issue where the **Release Label** failed while creating the artifact ([#64491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000103297164)). * Fixed an issue where **Sharing Rule Set** metadata type was found in the **Deployment** module but not in the **Version Control** module ([#65060](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104102165)). * 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 ([#65091](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000104040481)). * 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 **Static Code Anaysis** was failing due to missing property tag in **Apex PMD** rules file, but the UI log wasn't displaying this error ([#63554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101980029)). * 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 ([#63272](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101591692)). * Fixed an issue where user was unable to deploy a CI job with the **RelationshipGraphDefinition** components ([#64145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102836208)). * Fixed an issue where **Validate** deployment was displayed as **failed** in UI and the database, but was successful as per the logs ([#63868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102596005)). * Fixed an issue with **Review Artifact** where similar custom fields from different objects were not populating correctly and switching to other fields ([#63676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102181836)). * 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 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 ([#63544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101947159)). * Fixed an issue where user chose **Exclude Metadata Type** for a particular metadata type during a **CI Job**, but it was still deployed ([#62966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101046005)). * Fixed an issue where user was unable to perform **Destructive Commit** with **PermissionSetGroups** metadata type ([#63172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101463001)). * Fixed an issue where users weren't receiving emails after setting up **Mail Settings** ([#55070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089394047)). * Fixed an issue where there was a discrepancy between **EZ-Commit** and **Commit templates** while retrieving **Email Template** metadata members ([#61696](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099121314)). * Fixed an issue where **Merge Labels** were taking much longer than expected ([#62625](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100474287)). * Fixed an issue where user tried to commit the changes without validation and UI displayed an error `Another commit is in progress` ([#61930](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099562127)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed a UI bug where there was a discrepancy in the timestamp displayed for a commit in the **Commits History** page ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Fixed an issue where **Merge** was not auto-rejected when validation criteria was not met ([#62287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100008338)). * Enhanced **nCino** by adding an option to specify **Baseline Revision** in **Continuous Integration** for **Version Control** to perform feature deployments ([#43642](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073759034) and [#44506](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074950579)). * Enhanced **nCino** by allowing users to deploy nCino **CI build** to multiple target sandboxes ([#41763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070674305)). * 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 a UI bug in **Profile Manager** where **User Permissions** differences are shown in the report but not in the UI ([#61672](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099032670)). * Enhanced the **Release Label** creation by increasing the range of retrievable commit history ([#61714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099129934)). * Fixed an issue where user was unable to use **Release Labels** to perform **Deployment**, and it failed while trying to **Create Artifact** ([#59429](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096450140)). * Fixed an issue where users with non-admin access were unable to register branches in **EZ-Commit** since upgrading to version 22.3 ([#62723](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000100650673), [#62949](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101016055), [#62979](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010456), and [#62969](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101010302)). * 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 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 ([#61403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098537015)). * 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 ([#60531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097360001)). * Fixed an issue where user performed a pre-validation commit and each process like file diff, validate deploy happened thrice as per the logs ([#61079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097987087)). * Fixed an issue where user was unable to select master branch as the parent branch while creating a new branch in **EZ-Commit** ([#56188](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091240174)). * Fixed an issue where user was customer trying to register a **Salesforce Org** with **Custom URL** but it was failing with an error ([#62192](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099509581)). * Fixed an issue where user was unable to remove **Revisions**/**Commit Labels** from a **Release label** ([#59152](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096005470) and [#61578](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098950203)). * 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 ([#61791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248821) and [#61970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099521745)). * Fixed an issue where user user uploaded a **YAML file** to retrieve the **Vlocity components** but ALL metadata types were retrieved and displayed ([#61181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248158)). * Fixed an issue where the same merge could be approved and rejected by different users simultaneously ([#60859](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097787146)). * 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 user was unable to download success/failure reports in **Single Dataloader** ([#61551](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098913200)). * 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 ([#59082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096042290)). * Fixed an issue where **Dependency** order defined in **json** file was being changed on every commit but it was not supposed to ([#57731](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556797)). * Fixed an issue where **Create Artifact** was not working as expected while using **Release Label** ([#61607](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098932152)). * 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 ([#61751](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099248378)). * Fixed an issue where meta.xml file was not deleted from the repository after committing the destructive changes ([#61736](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099207347)). * 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: * Fixed an issue where SFDX module creation log shows that deployment is successful but the module creation had failed ([#57318](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092768029)). * Fixed an issue with **Backup from Org CI Jobs** where **PermissionSet User Permissions** were being deleted ([#59674](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096685144)). * Fixed an issue where **Org to Org Deployment** for **Profiles** including **Deploy Profile Access Settings for selected components only** was not working as expected ([#60559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097375154)). * Fixed an issue where **Post Destruct** fields were also added to **Pre Destruct** despite the user setting it to post ([#61162](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000098248005)). * Fixed an issue where user set the **Max depth** value as '0' under **Vlocity Configuration Settings** but it was retrieving all level dependancy components ([#57501](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093212471)). * Fixed an issue with DataLoader where the **Credit Memo Template** migration was not deploying after user upgraded their instance ([#57676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093470003)). * Fixed an issue where user selected **Custom Metadata** members (records), but **EZ-Commit** was failing to generate **File Diff** with `Null` error ([#59709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096706005)). * Fixed an issue where **Merge** was taking longer than usual, and then failing with `Null Exception` ([#60757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097574427)). * Fixed an issue where **EZ-Commits** and **EZ-Merges** were taking much longer than usual ([#58098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094302292)). #### 29 January 2023 **(ARM v22.2.15)**\ 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` ([#60597](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097399881)). * 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` ([#59050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095999076)). * Fixed an issue where **Reports** deployment validation failed in **EZ-Merge** but was successful in **EZ-Commit** and **Deployment** modules ([#57714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093587003)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Fixed an issue where user initiated the prevalidation commit by enabling the destructive type but the deployment failed with an error `null` at **Diff** ([#59919](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096907001)). * 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: * 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 ([#59359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096219627)). * Fixed an issue where commit was running for longer and remained **in-progress** and **validation check log** is also in progress ([#59199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096003630)). * Fixed an issue where commits with SFDX metadata structure are **failing** in metadata **retrieval stage** ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * Fixed an issue where user couldn't create a managed package with the selected ancestor ([#59044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095985421)). * Fixed an issue where **CI Job** was occasionally failing with the error `BUILD FAILED` ([#57647](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093370172)). * Fixed an issue where CI job was taking the last modified user name if trigger through API instated of taking API token user ([#55438](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089958034)). * 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 ([#59040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095982206)). * 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 ([#58044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000094164003)). * Fixed an issue where user was using SSH credential in AutoRABIT but it was throwing the following error: `Invalid Private Key` ([#59244](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096134293)). * Fixed an issue where user has created a Commit label but it was not available while trying to perform an **EZ-Merge** ([#55176](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089550097)). * Fixed an issue where user was not getting file Diff to commit the previously validated commit label and getting an error in the Diff ([#59114](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096048883)). * Fixed an issue where user was getting an error while trying to create a new branch in GitHub ([#59193](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096138920)). For more information, click [here](https://knowledgebase.autorabit.com/docs/faqs-version-control?highlight=$%20ssh-keygen%20-t%20rsa%20-b%204096%20-C#why-am-i-getting-an-error-while-trying-to-register-github-repository-with-ssh). * 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 ([#59402](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000096425001)). * 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` ([#59028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095867179)). * 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 ([#58998](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095876003)). * 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 ([#59014](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095898340)). * 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 an issue where **Merge validation** failed to process when there was a **Flow** metadata ([#58309](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095079556)). * Fixed an issue with user received 6 notifications for a failed **CI Job** instead of 1 ([#58436](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095199003)). * Fixed an issue where user was trying to register branches to AutoRABIT through GitHub, but was getting the following error: `Lower Region` ([#58888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095619252)). * 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 ([#51268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085726862)). * Fixed an issue where while performing destructive changes in **EZ-Commit**, it was creating **package.xml** in root path folder in **SFDX** structure ([#57868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093790001)). * 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 an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189)). * Fixed a build bug where **CI Job Build** was failing during package preparation **step 5** failing while commiting **DecisionMatrixDefinition** and throwing an error ([#58376](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095049142)). * 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\ ([#58478](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095251543)). * Fixed an issue where generating **Diff** for a **Commit Label** was taking much longer than expected ([#55220](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591780)). * Fixed an issue where **Code coverage** job was running **4 hours** earlier than scheduled every time services were restarted ([#54837](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088878005)). * 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 user was unable to create **Environment Provisioning** templates for multiple component types ([#57898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093797903)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). * Fixed an issue where AutoRABIT **SSH credentials** were failing with an error `Auth failed` while trying to connect with **AWS CodeCommit** ([#53694](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087714369)). * Fixed an issue where **EZ-Commit Diff** was taking approximately 4 hours while **Refactoring CustomField**, which is much longer than expected ([#56650](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091636348)). * 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 **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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: * 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 ([#53980](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087981132)). * 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 ([#55995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091129007)). * Fixed an issue where **Profile Diff** is working as expected for **Selective Deployment**, but not while using the same profile in the profile manager ([#52868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087005140)). * 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** ([#55208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591189), [#55754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090487029)). * Fixed an issue where **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * 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` ([#57238](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092610150)). #### 11 December 2022 **(ARM v22.2.8)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue where multiple metadata types where not able to retrieve ([#56668](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091694003)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * 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). * Fixed an issue where user was creating the **feature template** for some of the **nCino** objects but it was taking too long to **retrieve** the objects from **Source Org** ([#53915](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087934809)). * 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 **Flexi pages** were not picked up in a **CI Job** even after the commit with same set of metadata was excluded by user ([#54518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088461033)). * Fixed an issue where **Abort** function to stop **Provar** jobs was not working as expected ([#55511](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090032787)). * Fixed an issue where production backup **CI Job** was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error `java.lang.NullPointerException: null` ([#55213](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591408)). * Fixed an issue where all **Slack Notifications** were selected by default and user was unable to unselect all at once ([#55817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090727146)). * Fixed an issue where **SFI components** were not being fetched both in **Commit** and **Deployment** modules ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue with **DataLoader Pro** where user selected a field as **External ID** in a job and saved it, but the saved entry was lost and user was unable to map it ([#55011](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089299148)). * Fixed an issue where **Deployment validation** in **Prevalidation Commit** fails because profile validation automatically picks **User Permissions** even though **Remove User Permissions** option is selected ([#54941](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088985107)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where **Release Label Merge** was failing and throwing the following error: `fatal: bad revision` ([#55000](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089278434)). * Fixed an issue with **EZ-Commit** where user was unable to upload a **Custom YAML** file ([#55826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090770005)). * Fixed an issue where the **Vlocity Component** option under **Fetch Changes** is not populating for sub-users with roles that have all permissions and access ([#54962](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089032619)). * 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). * Fixed an issue where user was performing a merge operation and validating the package on the **target org** but the validation was failing with multiple errors ([#55541](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090145025)). #### 27 November 2022 **(ARM v22.2.6)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was trying to migrate **Products**, **Pricebooks**, and its entries but the **Deploy** was failing for **Pricebook** and throwing the following error: `INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--` ([#55263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089652641)). * Fixed an issue with **nCino** where user was trying to create a custom feature template including **product objects** as well as **product line** but the deployment was failing with the following error: `Required fields are missing: [LLC_BI_Product_Line_c]` ([#51209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085641324)). * Fixed an issue with **nCino** where **CI Job** was stuck in **Build Success** status ([#53605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087564091)). * Fixed an issue where **CI Job** build was failing with a **NullPointerException** ([#55204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089616148)). * Fixed an issue where the **Repository Branch** was unavailable to select to run the **Merge** process after selecting **On successful deployment** option ([#55537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090158003)). * Fixed an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * Fixed an issue with **EZ-Commit** where user was trying to perform a **destructive commit** using **Autodraft** option, but was unable to select **deleted components** under the **Deleted** tab ([#55507](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089979335) and [#55651](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090293003)). * Fixed an issue where user was getting a **NullPointerException** when trying to resolve a **Merge conflict** ([#55137](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089410195)). * Fixed an issue with **nCino** where the **UTF-8 Encoding Flag** was not displayed in the pop-up during **Re-Deployments** (internal ticket). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was able to create a **Delegated Group** but was unable to add a **Delegated Admin** user to the group using **Environment Provisioning** ([#55266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089705014)). #### 20 November 2022 **(ARM v22.2.5)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing **Prevalidation Commit** but commits in the repository have different components than the ones shown in **Diff** before the commit ([#52307](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086491044)). * Fixed an issue with **Install an Unlocked or Managed Package from a Version Control Branch** where CI job getting an exception and the build status was showing as successful but the **Scratch Org** was not being created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **CI Job** shows that the ALM status has been updated successfully but on **Azure ALM** it is not updated ([#54669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088657005)). * Fixed an issue where **Test Automation CI Jobs** were failing due to **InitializeDriver** & **quit methods** ([#45878](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077372830)). * Fixed a bug where user was able to access certain branches in the **Deployment** module to which he did not have access under **Profile Settings** ([#54879](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089011291)). * Fixed an issue with **CI Jobs** where the build failed with **Checkout** conflict for an **.svg file** ([#54172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088252005)). * 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). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was unable to add another branch to **Azure** in the **ALM MGMT Repository mappings** ([#55133](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089433593)). * Fixed an issue where the **Destructive** commit **Diff** was including more components than selected ([#54795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088780309)). * Fixed an issue where a merge got stuck for a long time and the **Commit ID** was reflected in **BitBucket** but unavailable to select for release label deployment ([#52964](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087060140)). #### 13 November 2022 **(ARM v22.2.4)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the user was trying to create an **Extract** process in **DataLoader** but after validating the query the application was throwing an error: `not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted` ([#54648](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088630160)). * Fixed an issue with **CI Jobs** where **External Credential** metadata was not identified during **Deployment** ([#53939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087955144)). * Fixed a UI bug where user was performing an **org to org deployment** using **package.xml** file and the components were successfully deployed and also verified on Salesforce target, but the status on ARM was still **In-Progress** ([#50459 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375)and [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue with **DX CI Jobs** where user is not getting details of faulty commit revisions in the notification ([#54063](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088015242)). * Fixed an issue with **Profile Manager** where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend ([#53706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704963)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * Fixed a bug where **Merge Commit** validation was not considering special characters like %,#, etc. as a value and throwing the following error: `Merge comment should not contain an empty space` ([#54512](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088479003)). * Fixed an issue where ARM was slowing at different phases in the **EZ-Commit** module ([#50503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084910726)). * Fixed an issue where Git check response was not delivered for validation **CI Job** even though user has added the comment for a **Pull request** in the remote repository ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). #### 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 an issue where the **Deployment** module page was loading very slowly and then throwing an error: `Page Unresponsive` ([#53675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704191)). * 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 with the **Deployment** module where user initiated a **Deployment** without selecting the **Do not Include Skip Members** option, but this option was auto-enabled and skipped the member at the time of deployment ([#53747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087811296)). * Fixed an issue with **Modularization** where user creating a module and selected the **Ignore installed components** check box but the installed components were not ignored causing the deployment to fail ([#53703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087755311)). * Fixed an issue with **AccelQ Test Automation** where test case fails but the error details pop-up is not showing the details of the error that caused the failure ([#54224](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088281589)). * Fixed an issue where user is setting up the **Apex PMD rules** as **Priority 1** & **Priority 2** in the **CI Job** but the SCA Report is showing the **Priority 3, P4 & P5** which wasn't selected ([#54017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087969396)). * Fixed an issue where the **Git** check response was not delivered for a validation **CI Job** ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). * Fixed an issue where the **Deleted Report** metadata components were not found in the **EZ-Commit** ([#53119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087247293)). * 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 an issue where triggering a **CI Job** in **Objects** was resulting in an ambiguous error in the **CI Job Build** ([#53066](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087190013), [#52955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087099268), [#53631](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087579265)). * Fixed an issue where all **CI Jobs** were failing and throwing the error: `Validation Checking failed Version Control Mappings not found for Repo: SA Repo and Branch: bugfix/Bugfix_PQT_Rel_Validation` ([#52945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087098136), [#52950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087101272), [#52757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086925007)). * 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 Hub**dropdown list was displayed in the **Deploy** section (internal ticket). * Fixed an issue with **AccelQ** where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as **Not Run** instead of **Success** or **Failure** even if the jobs have been successfully completed ([#50181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084509148)). * Fixed a **Page Unresponsive** issue while creating a new **Release Label** by adding a feature to list limited results on each page ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where a merge got auto-approved and was in **Merged Not Commit** status ([#52398](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086586845), [#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed an issue where user created a **Release Label**, performed a **Merge** operation, committed changes to the target branch, and created two revisions in the **Github** branch.\ But ARM was throwing an error while applying merge stage and only on the revision generated ([#51364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085859319)). * Fixed an issue where **EZ-Commit** initiation was stuck with the error: `Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out` ([#52550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086834002)). * Fixed an issue where user was not able to select the orgs in the **EZ-Commit** drop down ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001), [#51219](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085620605)). * 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 **CI Job** was successful but was including components from **GIT revisions** from old deleted branches ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error: `Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field` ([#48626](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082749181)). * Fixed an issue where **CI Job** was getting an exception, **Build** status was showing as *successful*, but **Scratch Org** not getting created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **Managed Package** was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version ([#48311](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223305)). * 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 **Custom Template Creation** failed and the **Logs** did not record the reason for failure ([#52147](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086277150)). * Fixed an issue where the **Created By** value was not visible in **Dataloader**, **Dataloader Pro DL Config**, and the **TestEnv History** page (internal ticket). * Fixed an issue where the **Comment Box** was not accepting more than **100 characters** while rejecting a **Commit**, but was working as expected while approving a commit ([#51384](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085891476)). * Fixed an issue with **Apex Test Class Config.** in **SF MGMT ORG** where the **Fetch Current Set**, **Add Manually**, and **Auto Populate** options were throwing an error: `Error 200` ([#52408](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086578687), [#52328](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086485900)). * Fixed an issue where user set **Commit validation Criteria** to **Auto reject after 7 days** but the older Pre-validation commits are not auto rejected after 7 days ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user cannot add **Skip** members manually and it is failing due to **special characters** being included ([#53139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087266642)). #### 16 October 2022 **(ARM v22.2.0)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where skipped members were present in many components but only **Report Metadata** was failing during **Deployment** ([#51040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085433814)). * Fixed an issue where **CI Job** was getting stuck in **In Progress** status but the log showed that the deployment was successful ([#51140](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085583019)). * Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time ([#50630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085136003)). * Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in **In Progress** status in ARM ([#50435](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084823763)). * Fixed an issue where user raised a **Pull request** on a branch and was getting a webhook response, but CI Job build was not triggered ([#51592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085996953)). * Fixed a UI bug where **Add to dashboard** button was unavailable for widgets ([#52333](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086514169)). * 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). * Fixed an issue where **Custom Email Template** was not working for **Email notifications** ([#47484](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080506162)). * Fixed an issue where user was testing **SSH Connection** but the application was throwing an error: `invalid privateKey` ([#50940](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371198)). * Fixed an issue with **nCino** where **UI Log** was not generated for failed CI Jobs ([#50442](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084795478)). * Fixed an issue where **New EZ-Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue where **Audit Logs** were not generating via **Postman Services** ([#50221](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084545179)). * Fixed an issue where **Commits** were getting stuck and throwing the following error: `No credential have been found with Name:git`, but was not reflecting in the UI log ([#51713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086127001)). * Fixed an issue with **Workspace Settings** where unused workspaces were not being cleared despite selecting **Clear all workspaces which are not used in last 7 days** ([#50164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084481079)). * Fixed an issue where user was performing a **Prevalidation EZ-Commit** and found that some **Layout Assignments** were deleted though those layouts were not part of the commit ([#50945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371456)). * Fixed an issue with **nCino** where migration was failing due to errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). *** ## **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.
[**Read more →**](/product-guides/arm/arm-features/version-control/ez-merge/squash-and-merge) #### 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.
[**Read more →**](/product-guides/arm/arm-features/salesforce-dx/import-an-unlocked-managed-package) **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. ![Dev hub.gif](https://cdn.document360.io/8711f4e7-c040-4616-aac9-d947f87e4619/Images/Documentation/Dev%20hub.gif) [**Read more →**](/product-guides/arm/arm-features/salesforce-dx/registering-a-devhub) #### 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.
[**Read more →**](/product-guides/arm/arm-features/automation-and-ci/ci-job-rollback) *** ### 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.
[**Read more →**](/product-guides/arm/arm-administration/user-management/users-roles-and-permissions) #### 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.
[**Read more →**](/product-guides/arm/arm-features/version-control/merge-approvals) #### 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: * Fixed an issue where wrong **timezone** region was displaying for users ([#71553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111412006)). * Fixed an issue where the **EZ-Commits report file** displayed the file count but not the components count ([#71538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111479094)). * Fixed an issue where clone build jobs were taking between 10 and 25 minutes, which is much longer than expected ([#70227](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000109182447)). * Fixed an issue where CI job build failed to show changes in the org after deployment ([#70791](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110120443) and [#71956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111861212)). * Fixed an issue where CI job to generate **Code Coverage Report** was not reflected in the org or in the e-mail notification ([#72042](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111983230)). * 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 ([#71266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000110960210)). * Enhanced **DataLoader** by adding the ability to **field mapping** through the lookup fields ([#58480](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000095290579)). * 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` ([#71303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111030174)). * Enhanced the **nCino filter criteria** by adding the ability to search and filter labels using the whole or partial name ([#71826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000111666181)). * 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 where **validation jobs** on **Pull Requests** weren't getting triggered ([#67538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106410313), [#67494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106382311), and [#67448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106353830)). * Fixed an issue where Salesforce components were showing under the **Apex Test Success** tab in the **Deployment** module, which is not expected behavior ([#67537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253424)). * 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 ([#63571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000102024066)). * Fixed an issue where user was unable to register a branch even though **Test Connection** was successful ([#67023](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105968682)). * Fixed an issue where ARM wasn't fetching the **ApexClass Tests** related to **ApexTriggers** upon selecting **Run Tests Based On Changes** option ([#67503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106378846)). * 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)` ([#61676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000099101151) and [#67675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604299)). * 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 ([#67549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106253579), [#66910](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106035058), [#67724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106597223), [#67720](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106570720), [#66881](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936162), and [#67667](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106604150)). * Fixed an issue where triggered **CI jobs** were taking too long to build, and also slowing down ARM altogether ([#66846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105989569)). * Fixed an issue where if the file name contained spaces, **Commit Validation** via **VS Code** plugin was unable to detect the file ([#63518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000101868754)). * Fixed an issue where **Search & Substitute** was not updating the value for a **custom label** in the SF org ([#66809](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000105936001)). * Fixed an issue where there was a discrepancy between the changes captured in the ARM **Diff** and the repos in **BitBucket** ([#60596](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000097396243)). * Fixed an issue where the SF org **URL** is not displaying the updated one under **Profile** ([#67718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106581101)). * Fixed an issue with **nCino** where CI job filter changes on templates are not reflecting after saving ([#66956](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000106067470)). * 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 **Provar** jobs were failing due to incorrect files being copied from customer repository branch to Provar project directory ([#56662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091635358)). * Fixed an issue where user triggered a **CI Job** but it deployed with many more components than expected ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * 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** ([#57732](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000093556923)). * 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` ([#57371](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880162)). * 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 ([#57263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092661381)). * 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 ([#57359](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092880015)). * Fixed multiple issues where user was having trouble creating **new package version** from **previous ancestor** version ([#55707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090251366)). * Fixed an issue where **Merge** is **failing** with the following error: `failed to push some refs to 'https://github.com/salesforce-align/SFDX.git'` ([#55939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090999346)). * Fixed an issue where the **Standard Field Account.name** is displayed in the deleted components list ([#57396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000092927781)). * Fixed an issue where the **prevalidation commit** failed at **delta** stage ([#55763](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090435979)). * 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 **SFI components** were not getting fetched in **Commit** and **Deployment** module ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue where multiple metadata types where not able to retrieve ([#56668](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000091694003)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where user performed a **merge** and sent it for **approval**, but it was not available under the **Commit history** tab ([#53759](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087839030)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * 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). * Fixed an issue where user was creating the **feature template** for some of the **nCino** objects but it was taking too long to **retrieve** the objects from **Source Org** ([#53915](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087934809)). * 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 **Flexi pages** were not picked up in a **CI Job** even after the commit with same set of metadata was excluded by user ([#54518](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088461033)). * Fixed an issue where **Abort** function to stop **Provar** jobs was not working as expected ([#55511](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090032787)). * Fixed an issue where production backup **CI Job** was not picking all the changes, and when user modified the job configuration and retriggered the job, the application was throwing the following error `java.lang.NullPointerException: null` ([#55213](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089591408)). * Fixed an issue where all **Slack Notifications** were selected by default and user was unable to unselect all at once ([#55817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090727146)). * Fixed an issue where **SFI components** were not being fetched both in **Commit** and **Deployment** modules ([#55139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089491921)). * Fixed an issue with **DataLoader Pro** where user selected a field as **External ID** in a job and saved it, but the saved entry was lost and user was unable to map it ([#55011](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089299148)). * Fixed an issue where **Deployment validation** in **Prevalidation Commit** fails because profile validation automatically picks **User Permissions** even though **Remove User Permissions** option is selected ([#54941](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088985107)). * Fixed an issue where user was performing a single **Merge** with only two approval process, but while selecting **SCA**, process is auto rejected ([#55671](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090263086)). * Fixed an issue where **Commit Label** is not **Auto rejected** when the **validation criteria** is not met ([#55670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090311201)). * Fixed an issue where **Release Label Merge** was failing and throwing the following error: `fatal: bad revision` ([#55000](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089278434)). * Fixed an issue with **EZ-Commit** where user was unable to upload a **Custom YAML** file ([#55826](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090770005)). * Fixed an issue where the **Vlocity Component** option under **Fetch Changes** is not populating for sub-users with roles that have all permissions and access ([#54962](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089032619)). * 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). * Fixed an issue where user was performing a merge operation and validating the package on the **target org** but the validation was failing with multiple errors ([#55541](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090145025)). #### 27 November 2022 **(ARM v22.1.35)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was trying to migrate **Products**, **Pricebooks**, and its entries but the **Deploy** was failing for **Pricebook** and throwing the following error: `INSUFFICIENT_ACCESS_ON_CROSS_REFERENCE_ENTITY: insufficient access rights on cross-reference id:--` ([#55263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089652641)). * Fixed an issue with **nCino** where user was trying to create a custom feature template including **product objects** as well as **product line** but the deployment was failing with the following error: `Required fields are missing: [LLC_BI_Product_Line_c]` ([#51209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085641324)). * Fixed an issue with **nCino** where **CI Job** was stuck in **Build Success** status ([#53605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087564091)). * Fixed an issue where **CI Job** build was failing with a **NullPointerException** ([#55204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089616148)). * Fixed an issue where the **Repository Branch** was unavailable to select to run the **Merge** process after selecting **On successful deployment** option ([#55537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090158003)). * Fixed an issue where **Admin** was able to see the **Teams** field under **ALM Integration** but the same field was unavailable for sub-users ([#55153](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089465059)). * Fixed an issue with **EZ-Commit** where user was trying to perform a **destructive commit** using **Autodraft** option, but was unable to select **deleted components** under the **Deleted** tab ([#55507](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089979335) and [#55651](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000090293003)). * Fixed an issue where user was getting a **NullPointerException** when trying to resolve a **Merge conflict** ([#55137](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089410195)). * Fixed an issue with **nCino** where the **UTF-8 Encoding Flag** was not displayed in the pop-up during **Re-Deployments** (internal ticket). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was able to create a **Delegated Group** but was unable to add a **Delegated Admin** user to the group using **Environment Provisioning** ([#55266](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089705014)). #### 20 November 2022 **(ARM v22.1.34)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing **Prevalidation Commit** but commits in the repository have different components than the ones shown in **Diff** before the commit ([#52307](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086491044)). * Fixed an issue with **Install an Unlocked or Managed Package from a Version Control Branch** where CI job getting an exception and the build status was showing as successful but the **Scratch Org** was not being created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **CI Job** shows that the ALM status has been updated successfully but on **Azure ALM** it is not updated ([#54669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088657005)). * Fixed an issue where **Test Automation CI Jobs** were failing due to **InitializeDriver** & **quit methods** ([#45878](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077372830)). * Fixed a bug where user was able to access certain branches in the **Deployment** module to which he did not have access under **Profile Settings** ([#54879](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089011291)). * Fixed an issue with **CI Jobs** where the build failed with **Checkout** conflict for an **.svg file** ([#54172](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088252005)). * 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). * Fixed an issue where during an EZ-Commit, complete information about some of the members of WaveDataflow metadata type was not retreived from the Salesforce Org ([#49753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083936148)). * Fixed an issue where **Quick Merge** was throwing the following error after clicking **Validate & Merge**: `Please Select Valid revision` ([#53932 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087946912)). * Fixed an issue with **EZ-Commit** where **Autodraft** feature was taking too long and eventually failing when user was trying to retrieve components ([#48257](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082041269)). * Fixed an issue where user was unable to add another branch to **Azure** in the **ALM MGMT Repository mappings** ([#55133](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000089433593)). * Fixed an issue where the **Destructive** commit **Diff** was including more components than selected ([#54795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088780309)). * Fixed an issue where a merge got stuck for a long time and the **Commit ID** was reflected in **BitBucket** but unavailable to select for release label deployment ([#52964](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087060140)). #### 13 November 2022 **(ARM v22.1.33)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the user was trying to create an **Extract** process in **DataLoader** but after validating the query the application was throwing an error: `not supported; requires @DynamoDBTyped or @DynamoDBTypeConverted` ([#54648](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088630160)). * Fixed an issue with **CI Jobs** where **External Credential** metadata was not identified during **Deployment** ([#53939](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087955144)). * Fixed a UI bug where user was performing an **org to org deployment** using **package.xml** file and the components were successfully deployed and also verified on Salesforce target, but the status on ARM was still **In-Progress** ([#50459 ](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375)and [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue with **DX CI Jobs** where user is not getting details of faulty commit revisions in the notification ([#54063](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088015242)). * Fixed an issue with **Profile Manager** where the deployment is not showing any progress in the logger detail in front end. It was updated only after completion of the deployment job at backend ([#53706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704963)). * Enhanced the **Conflict Resolution Log** by adding additional loggers like strategy chosen to resolve the conflict and which user did the resolution ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). * Fixed a bug where **Merge Commit** validation was not considering special characters like %,#, etc. as a value and throwing the following error: `Merge comment should not contain an empty space` ([#54512](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088479003)). * Fixed an issue where ARM was slowing at different phases in the **EZ-Commit** module ([#50503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084910726)). * Fixed an issue where Git check response was not delivered for validation **CI Job** even though user has added the comment for a **Pull request** in the remote repository ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). #### 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 an issue where the **Deployment** module page was loading very slowly and then thrwing an error: `Page Unresponsive` ([#53675](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087704191)). * 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 with the **Deployment** module where user initiated a **Deployment** without selecting the **Do not Include Skip Members** option, but this option was auto-enabled and skipped the member at the time of deployment ([#53747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087811296)). * Fixed an issue with **Modularization** where user creating a module and selected the **Ignore installed components** check box but the installed components were not ignored causing the deployment to fail ([#53703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087755311)). * Fixed an issue with **AccelQ Test Automation** where test case fails but the error details pop-up is not showing the details of the error that caused the failure ([#54224](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000088281589)). * Fixed an issue where user is setting up the **Apex PMD rules** as **Priority 1** & **Priority 2** in the **CI Job** but the SCA Report is showing the **Priority 3, P4 & P5** which wasn't selected ([#54017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087969396)). * Fixed an issue where the **Git** check response was not delivered for a validation **CI Job** ([#53036](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087171146)). * Fixed an issue where the **Deleted Report** metadata components were not found in the **EZ-Commit** ([#53119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087247293)). * 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 an issue where triggering a **CI Job** in **Objects** was resulting in an ambiguous error in the **CI Job Build** ([#53066](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087190013), [#52955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087099268), [#53631](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087579265)). * Fixed an issue where all **CI Jobs** were failing and throwing the error: `Validation Checking failed Version Control Mappings not found for Repo: SA Repo and Branch: bugfix/Bugfix_PQT_Rel_Validation` ([#52945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087098136), [#52950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087101272), [#52757](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086925007)). * 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 Hub**dropdown list was displayed in the **Deploy** section (internal ticket). * Fixed an issue with **AccelQ** where running a test execution was successful even before the jobs were completed in AccelQ, but the status was always showing as **Not Run** instead of **Success** or **Failure** even if the jobs have been successfully completed ([#50181](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084509148)). * Fixed a **Page Unresponsive** issue while creating a new **Release Label** by adding a feature to list limited results on each page ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where a merge got auto-approved and was in **Merged Not Commit** status ([#52398](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086586845), [#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed an issue where user created a **Release Label**, performed a **Merge** operation, committed changes to the target branch, and created two revisions in the **Github** branch.\ But ARM was throwing an error while applying merge stage and only on the revision generated ([#51364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085859319)). * Fixed an issue where **EZ-Commit** initiation was stuck with the error: `Unable to fetch Salesforce Org users. Reason: Invalid login: invalid user name or password or security token or api version or user locked out` ([#52550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086834002)). * Fixed an issue where user was not able to select the orgs in the **EZ-Commit** drop down ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001), [#51219](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085620605)). * 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 **CI Job** was successful but was including components from **GIT revisions** from old deleted branches ([#46983](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079512053)). * Fixed an issue where user was performing a production deployment using CI job for an object, but it failed with the following error: `Cannot set sharingModel to ControlledByParent on a CustomObject without a MasterDetail relationship field` ([#48626](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082749181)). * Fixed an issue where **CI Job** was getting an exception, **Build** status was showing as *successful*, but **Scratch Org** not getting created ([#50702](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085126029)). * Fixed an issue where **Managed Package** was picking the wrong ancestor by adding a feature to manually select the preferred ancestor while creating a package version ([#48311](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223305)). * 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 **Custom Template Creation** failed and the **Logs** did not record the reason for failure ([#52147](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086277150)). * Fixed an issue where the **Created By** value was not visible in **Dataloader**, **Dataloader Pro DL Config**, and the **TestEnv History** page (internal ticket). * Fixed an issue where the **Comment Box** was not accepting more than **100 characters** while rejecting a **Commit**, but was working as expected while approving a commit ([#51384](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085891476)). * Fixed an issue with **Apex Test Class Config.** in **SF MGMT ORG** where the **Fetch Current Set**, **Add Manually**, and **Auto Populate** options were throwing an error: `Error 200` ([#52408](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086578687), [#52328](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086485900)). * Fixed an issue where user set **Commit validation Criteria** to **Auto reject after 7 days** but the older Pre-validation commits are not auto rejected after 7 days ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user cannot add **Skip** members manually and it is failing due to **special characters** being included ([#53139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000087266642)). #### 16 October 2022 **(ARM v22.1.29)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where skipped members were present in many components but only **Report Metadata** was failing during **Deployment** ([#51040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085433814)). * Fixed an issue where **CI Job** was getting stuck in **In Progress** status but the log showed that the deployment was successful ([#51140](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085583019)). * Fixed an issue where GitHub login credentials were not working when user triggered a CI Job for the second time ([#50630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085136003)). * Fixed an issue where CI Job has failed in the Salesforce org, but still stuck in **In Progress** status in ARM ([#50435](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084823763)). * Fixed an issue where user raised a **Pull request** on a branch and was getting a webhook response, but CI Job build was not triggered ([#51592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085996953)). * Fixed a UI bug where **Add to dashboard** button was unavailable for widgets ([#52333](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086514169)). * 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). * Fixed an issue where **Custom Email Template** was not working for **Email notifications** ([#47484](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080506162)). * Fixed an issue where user was testing **SSH Connection** but the application was throwing an error: `invalid privateKey` ([#50940](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371198)). * Fixed an issue with **nCino** where **UI Log** was not generated for failed CI Jobs ([#50442](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084795478)). * Fixed an issue where **New EZ-Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue where **Audit Logs** were not generating via **Postman Services** ([#50221](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084545179)). * Fixed an issue where **Commits** were getting stuck and throwing the following error: `No credential have been found with Name:git`, but was not reflecting in the UI log ([#51713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000086127001)). * Fixed an issue with **Workspace Settings** where unused workspaces were not being cleared despite selecting **Clear all workspaces which are not used in last 7 days** ([#50164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084481079)). * Fixed an issue where user was performing a **Prevalidation EZ-Commit** and found that some **Layout Assignments** were deleted though those layouts were not part of the commit ([#50945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085371456)). * Fixed an issue with **nCino** where migration was failing due to errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). #### 09 October 2022 **(ARM v22.1.28)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue with **nCino** where user was getting errors with **Standard Screen** and **UI Templates** ([#50432](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084739297)). * Fixed an issue where user noticed discrepancy in the **Conflict Resolution Log** ([#47559](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080771349)). #### 02 October 2022 **(ARM v22.1.27)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where components were successfully deployed, but deployment status was still showing **In-Progress** in ARM ([#50459](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084807375), [#51288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085799424)). * Fixed an issue where CI Jobs were getting stuck and throwing the following error: `Too many open files` ([#44319](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074784001), [#49273](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074784001)). * Fixed an issue where **email notification** wasn't sent for some of the **CI Jobs** ([#48028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081639899)). * Fixed an issue where the Custom label and remote site setting URLs were not getting updated by ARM through **Environmental Provisioning** ([#49612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083684001)). * Fixed an issue with **Vlocity** where selecting one component from a GIT repository was causing all the components from the category to get selected ([#49806](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084007005)). * Fixed an issue with **ALM Mgmt.** where item status was not retrieved properly for **Merge Request**, but was working as expected for **EZ-Merge** ([#50628](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085133005)). * Fixed a UI bug where **Release Labels** were showing duplicate **Time Stamps** ([#51205](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000085689003)). * Fixed an issue where old **Commit Labels** were not getting auto-rejected after 7 days as the user had configured under **Commit Validation Criteria** ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). * Fixed an issue where user was getting an error pop-up on the **Permissions** and the **SF ORG MGMNT** pages, and the SF org and VC repo mappings were lost in the profile section of a role ([#49108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083164265)). #### 26 September 2022 **(ARM v22.1.26)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where **Provar** test job was throwing an error while in queue ([#49797](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083986945)). * 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). * Fixed an issue with **Branching Baseline** where some of the custom object metadata nodes were deleted from the repository ([#47239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080102001), [#47270](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080113166)). * Fixed an issue with **EZ-Merge** where **Diff** was not being generated even though there were file changes between the source branch and the destination branch ([#50323](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084689471)). * Fixed a UI bug in **DataLoader** where user was switching from **Graphical View** to **Grid View** but **Graphical View** options were still being displayed ([#50431](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084822478)). * Fixed an issue with **nCino** where the **Insert/Update With Null Values** option was not getting updated for CI jobs ([#50259](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084641005)). * Fixed an issue where users were unable to **re-authenticate** the **Salesforce Org** after refreshing their personal sandboxes ([#48533](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082553001)). * Fixed an issue where **Environment Provisioning Template** was not functioning as expected for **Custom Labels** containing URL ([#47892](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081421793)). * Fixed an issue with **EZ-Commit** where user was trying to deploy **Permission Sets** and **Profiles** together, and the pre-validation process was stuck in **In-Progress** status ([#49340](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083456001)). * Fixed an issue where old **Commit Labels** were not getting auto-rejected as configured ([#49874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084033082)). #### 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). * Fixed an issue where user was unable to reset the AutoRABIT password, and was getting an error: `getAttribute: Session already invalidated` ([#50145](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084391472)). * Fixed an issue where **CI Jobs** was not picking the right number of components unless the user cancelled the build and retriggered it ([#47164](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921675)),([#46981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079504156)). * Fixed an issue where the user tried to merge to the Dev branch but the **CI Job** failed and was throwing a **Duplicate** error ([#49661](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083729177)). * Fixed an issue where user was trying to install **Unlocked Package** via **CI Job** but it was failing and throwing the following error: `ERROR 178928269770891:275 - For input string: "0-2" java.lang.NumberFormatException: For input string: "0-2"` ([#50093](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000084341003)). * Enhanced **Vlocity** loggers for **Branching Baseline** by displaying to the user **Status Count** of **Remaining**, **Success**, **Error** and **Ignored** (internal ticket). * Fixed an issue where **Test Connection** was failing on the **Version Control Summary** page under the **Admin** module ([#49299](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083372346)). * Fixed an issue with **Prevalidation Merge** by increasing the **SCA Response timeout** from **50 minutes** to **5 hours** ([#48613](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082720068)). * Fixed an issue where merging **Master Branch** with the **Production** branch was throwing the following error: `No merge head specified` ([#46594](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078825001)). * Fixed a bug where **New A-Z Merge** was throwing an error ([#46754](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079012711)). * Fixed an issue with **Autorabit Commit Label** related to **Permission Sets Deployment** ([#48709](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082892203)). #### 11 September 2022 **(ARM v22.1.24)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was selecting a single package to import, but all available package versions were being imported ([#49426](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083542359)). * Fixed an issue with **Profile Manager** where user was comparing a profile but the deployment was not starting ([#48620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082696017)). * Fixed an issue where deploying components with profiles was not working as expected and throws the following error: `Duplicate layoutAssignment:PersonAccount (PersonAccount.Person_Prospect)` ([#49021](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083082001)). * Fixed an issue where custom metadata records were not being selected during deployment ([#49167](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083203846)). * Fixed an issue in **Version Control Commit Labels** history where **Created By** and **Created Date** values were exchanged (internal ticket). * Fixed an issue where user was getting an error while trying to deploy **Vlocity Metadata** using **CI Jobs** ([#47568](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080830005)). * Fixed an issue where **Branching Baseline** was not retrieving **Workflow Metadata types** ([#49403](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083447017)). * Fixed an issue where **Release Label** failed to load revisions from a particular branch and the browser was hanging and throwing an *Out of memory* error ([#48563](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082627224)). * Fixed an issue where **EZ-Commit** was not getting auto-rejected when **CodeScan** analysis failed, even though user select the option to run **Static Code Analysis** ([#47155](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921059)). * Fixed an issue where merge was failing at the **Validate Deploy** step even before selecting the org to validate ([#49724](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083898393)). * Fixed an issue where **Layout** was being removed from the **Diff** while deploying **Profile** changes with related **Layouts** and **RecordTypes** ([#48268](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082045983)). * Fixed multiple issues with **CodeScan<>ARM** Integration ([#49605](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083671017)). #### 04 September 2022 **(ARM v22.1.23)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where user was performing a new deployment but getting an error when using the **Compare Orgs & Deploy** button ([#48707](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860460), [#48676](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860003), [#48737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082918005), [#48734](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082914003)). * Fixed an issue where the CI job was not working as expected and throws the following error: `java.lang.NullPointerException: null` ([#48706](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082860315)). * Fixed an issue where few fields were not being analyzed in CodeScan SFDX. User was selecting Custom Fields, Apex Classes, and Record Types in E-Z Commit, but Static Code Analysis was only Apex Classes ([#48547](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082584398)). * Fixed an issue where dashboards and reports were changing to **Destructive** and getting deleted ([#48119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081915009)). * Fixed an issue where discrepancies for **Document**, **Assignment Rule** and **AutoResponseRule** metadata types content was observed in **package.xml** for SFDX and non-SFDX CI Jobs ([#47017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079534439)). * Fixed an issue where the Dataloader Pro Jobsfailing and throws the following error: `java.lang.NullPointerException: null` ([#49170](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083182317), [#49283](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083331025), [#49331](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083407003), [#49199](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000083182597)). * Fixed an issue where nCino CI Jobs via RBC were failing during parallel deployment. Instead of falling in queue, the first job was failing while the other succeeded, and the user had to retrigger the failed job ([#47335](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080272507)). * 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 after upgrading the AR instance, deployment jobs kept removing the custom metadata access on the **Permission Sets** ([#48296](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082147005)). * Fixed an issue where **Org difference** jobs were running for more than 24 hours ([#48324](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082223730)). * Fixed an issue where Environment provisioning template was not working when trying to update custom label values that contain URL, and the incorrect value was being updated in the org ([#47892](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081421793)). * 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 user was trying to validate the commit using single revision, but was getting an **Empty Package** error even though there were changed files in the commit ([#47530](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080730150)). * Fixed an issue where DataLoader Pro jobs were failing with an error **duplicate value found: SetupOwnerId duplicates value on record with id** for the custom setting **Multichannel\_Settings\_vod\_\_c**, even though there is no field mapped with name **SetupOwnerId** ([#48230](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081981779)). * 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 where EZ Commit Logs and Change Labels were not displaying for some of the commit labels ([#45364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076464250)). * Fixed an issue where the user was not able to see the deployment report because the build was failing when only custom fields were being selected without the related object ([#45663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077048275)). * Fixed an issue where merge request was being auto rejected if the selected approver was no longer with AR ([#48084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081784401)). * Fixed a bug where user had enabled Squash and Merge while performing a new merge, but the Squash and Merge option was not displayed after the Merge Request was approved ([#48246](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000082046388)). * Fixed an issue in CI Jobs deployments where Bulk API option for **Attachments** was throwing an error (internal ticket). * Fixed an issue where **nCino CI Jobs** were failing the first time and completing the second time successfully ([#46545](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078644141)). #### 21 August 2022 **(ARM v22.1.21)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the CI job build was getting stuck in **In-progress** status ([#47934](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081483565)). * Fixed an issue where **RunSpecifiedTest** level execution was failing with Test classes dependency errors ([#47666](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081029378)). * 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). * Fixed an issue where entire branch merge was failing with multiple common ancestor errors ([#47334](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080237436)). * 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 where Standard fields are not retreiving when included in **package.xml**, and retrieving through **E-Z Commit (Package Manifest)** option ([#47961](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081505333)). * 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 with the **Profile Manager** where the user were unable to select the default app permission during the profile deployment ([#47462](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080494273)). * Fixed an issue where the merge revisions were missing from the CI jobs ([#46862](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079287922)). * Fixed an issue where the users were unable to commit **Vlocity card** from one org to another org in ARM ([#44938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075743019)). * 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). * Fixed an issue where the ALM integration was not working when the files are pushed with special characters in their name ([#47414](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080454001)). * Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS ([#46844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079276142)). * Fixed an issue where the users while deploying a destructive XML file from one sandbox to another, is getting auto rejected ([#47714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081149440), [#47747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081187577)). #### 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 an issue where after triggering the CI job, the **File Changes** and **Check-ins** results mismatched ([#40119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067784313)). * Fixed an issue where the package created to deploy ExperienceBundle misses some of the folder and metadata files contained in it ([#46692](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079024001)). * Fixed the below deployment-related issues: * Unable to find commits that are part of a Release Label while performing a new deployment ([#47337](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080246444)) * Unable to retrieve components from a Release Label during deployment ([#47534](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080713440)) * Changes are not deployed to the destination org which are part of a Release Label ([#46908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079358877)) * Fixed an issue where the users while deploying a destructive XML file from one sandbox to another, is getting auto rejected ([#47714](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081149440), [#47747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081187577)). * Fixed an issue where the deployment failed to initiate when search and substitute rules are selected ([#47802](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000081320007)). * Fixed an issue where the status log .csv files are inconsistent for deployment via CI jobs (internal ticket). * Fixed an issue where the users were unable to process the migration of RBC object (nForce\_\_Views\_\_c) using the nCino CI jobs, feature template migration, or the Dataloader Pro jobs ([#47098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079761055)). * Fixed an issue where while deploying a **nCino-User Interface** template, only partial records are deployed and no deployment logs are generated ([#47494](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080488668)). * Fixed an issue where the users, while performing an EZ-Commit by enabling the run SCA option, the CodeScan analysis is getting failed, but EZ-Commit is not getting auto-rejected ([#47155](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079921059)). #### 31 July 2022 **(ARM v22.1.18)**\ This is a maintenance release. The following items were fixed and/or added: * Upgraded the Spring and AWS libraries on ARM for addressing the Spring vulnerability ([#46970](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079471289)). * Fixed an issue where the users were unable to login to ARM via SSO (internal ticket). * Fixed an issue where the ARM is not able to fetch any component using the release label ([#46662](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078894834)). * Fixed an issue where the baselining of branches has wiped out the records types for many records, and the users were forced to do manual changes to the Record types ([#42719](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072309163)). * Fixed an issue where the ARM allows to associate only one branch to one package, and not able to build beta package versions from various branches. This is now fixed ([#46841](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262193)). * Fixed an issue where the CI job, while deploying manage packages, is installing all the manage packages instead of installing a single package ([#46832](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262054)). * Fixed an issue where the links on the **CI Job log** screen are redirected to the user's login page instead of redirecting to user's Salesforce org screen ([#47151](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079912283)). * Salesforce API version 55 (Beta support) is upgraded. The label is modified throughout ARM application to Salesforce API version 55.0 ([#47404](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080386152)). * Duplicate classes from the ARM repo has been removed (internal ticket). * Fixed an issue with the **Profile Manager** where the user were unable to select the default app permission during the profile deployment ([#47462](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080494273)). * Fixed an issue where the merge revisions were missing from the CI jobs ([#46862](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079287922)). * Fixed an issue where the users were unable to commit **Vlocity card** from one org to another org in ARM ([#44938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075743019)). * 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). * Fixed an issue where the ALM integration was not working when the files are pushedwith special characters in their name ([#47414](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080454001)). * Fixed an issue where the commit labels was getting auto-rejected while committing Profile FLS ([#46844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079276142)). * Fixed an issue where the merge was getting failed with the following error: `Fetch operation is failed due to some runtime exceptions from Git` ([#46773](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079094055)). * Fixed an issue where the username and passwords fields were not editable for users registered in ARM with basic authentication ([#47099](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079788018)). #### 24 July 2022 **(ARM v22.1.17)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where when user triggers a code coverage run in the production environment, the action takes more time than expected. Also, the total time taken for the task completion is shown inaccurate in the log report ([#44544](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075040590), [#43527](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073512143)). * Fixed an issue where the CI job was not working as expected and throws the following error: `java.lang.OutOfMemoryError: Java heap space` ([#47182](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079988001), [#47190](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079988142), [#47209](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000080017264), [#47191](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079950166)). * Fixed an issue where the **Rollback settings** were not getting saved in the **My Account** page (internal ticket). * Fixed a bug where the users could not edit/modify their CI jobs when the build was in progress ([#43538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073573003)). * Fixed an issue with the permissionsets where instead of delta changes, the Permissionset retrieving entire file from the branch and causing dependency issues ([#46846](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079262334)). * 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. * Fixed an issue where while editing an existing nCino CI Job, the version control is not automatically choosing the previous repository set. This is causing the selected nCino Templates to reset ([#46952](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079432380)). * Fixed an issue where the ALM labels were missing from the ALM Label lists page ([#44410](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074860453)). * Fixed an issue where the settings related with user permissions were erased ([#46472](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078507457)). * Fixed an issue where the users when performed EZ-Commit using a package manifest file, doesn't include managed components that are in the **package.xml** file ([#47083](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079769291)). #### 17 July 2022 **(ARM v22.1.16)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the Execute Anonymous Apex metadata is not working as expected when configured as Environment Provisioning template ([#46817](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079248146)). * 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 merge prevalidations were auto rejected with status as **Approval Pending** ([#46665](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078888152), [#46864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079289063)). * 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 users failed to enable the pull request support for their version control repositories ([#46336](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078290172)). * Fixed an issue where the re-use previously validated commit label takes more time to load ([#46171](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077992017)). * 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 a bug marked deployment as failed, whereas the log report says successful ([#46737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079038631)). * 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 the users could not edit/modify their CI jobs when the build was in progress ([#43538](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073573003)). * Fixed an issue where entering the package installation key in `Install an Unlocked or Managed Package from Version Control Branch` CI Job gets altered when manually entered or pasted ([#46836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079265163)). * Fixed an issue where the user could not run the static code scan report on GitHub with APEX PMD Lint Scanner metadata type ([#46781](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000079122007)). * Fixed an issue with the CodeScan analysis report that failed when running from ARM ([#44404](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074862389)). * Fixed an issue where the user could not fetch the latest CI job weekly reports ([#42587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072104139)). * Enhanced the Dataloader Pro, where the attachments are now supported ([#41077](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299001)). * 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 with the EZ-Merge, where merging the main branch to the dev branch failed with a `No merge head specified` error ([#46594](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078825001)). * Fixed an issue that throws `Schema as invalid` error while running the branching baseline operation ([#46593](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078805109)). * Fixed an issue where the merge failed using a single revision ([#46491](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078644005), [#45764](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077211038)). * 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). * Fixed an EZ-Commit issue where additional permissions were removed from Profiles metadata type, which is not a part of the commit ([#44543](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075040441)). #### 03 July 2022 **(ARM v22.1.14)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the deployment via CI job picked unnecessary components for deletion ([#44204](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074533873)). * Fixed the issue where the user when trying to delete a component in **Community** metadata type, deletes the whole Community rather than its components ([#43698](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073869007)). * Fixed an issue where DevHub registration in ARM was failing ([#46208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078056108)). * 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 deployment using **Commit/Release Label** was not working ([#46419](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078496053)). * Fixed an issue where the mapping more than one class to same test class is not recognized by ARM during commit/merge operation ([#46396](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078430859), [#45159](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076223139)). * Fixed an issue where the CI job builds were failing because of missing revisions ([#45532](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076855001), [#46352](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078378003)). * Fixed an issue where the **Compact Layout** were not getting deployed and throws undefined error([#46592](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078798022)). * Fixed an issue where the ALM statuses were not updated/rolled back post CI job rollback completion ([#45945](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077581145)). * Fixed an issue where the destructive changes were not working as expected for the CI jobs ([#46216](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078049311)). * Fixed an issue where the ARM failed to update the Audit fields when trying to run nCino feature deployment ([#46356](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078401001)). * Fixed an issue where our internal team were not able to register their credentials on one of the ARM SAAS instances ([#46315](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078239277)). * Fixed an issue where prevalidation commits were getting failed due to credential issues. The following error was thrown `No credentials found` ([#46274](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078213003), [#46098](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077754153)). * Fixed a bug where the deleted components were tagged as **UC (UnChanged)** instead of **D (Deleted)** in the EZ-Commit ([#46087](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077760173)). * 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). * Fixed an issue where the merge using single revision (baseline revision) receives the metadata schema error ([#46570](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078699087)). * Fixed an issue where the merges were getting failed and throws the `Schema is invalid for the file` error ([#45768](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077202614)). * Fixed an issue where the exported users list contained inaccurate information ([#44782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075451374)). #### 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 **Spread Template** in the **nCino** module was not working as expected ([#45078](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076003188)). * 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 the issue where the **Disable Workflow** template in the **Environment Provisioning** module was not working as expected ([#46195](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078049157)). * Fixed an issue where the creation of a scratch org were getting failed. The fix has been deployed to in this weekly release ([#46021](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077690007)). * Fixed an issue where the users were unable to use the **release label** for deployment ([#45415](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076584626)). * Fixed an issue where the users were not able to register same DevHub with two different usernames ([#46208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078056108)). * Fixed an issue where the CI Job was picking the deleted components from GitHub branch although the **Prepare Destructive Changes** checkbox was not selected. This caused the deployment to fail ([#42553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072012015)). * Fixed an issue where the users were not able to view their GitHub branches in the ARM application ([#46044](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077690473), [#46353](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078386013)). * Fixed an issue where the CI Job for backing up from org to the version control branch was failing with null pointer exception error ([#45646](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072012015)). * Fixed an issue where the **EZ-Commits**, when included **Profile**, was not working as expected ([#45902](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077441170)). * Fixed an issue where the commits were getting stuck at the delta stage ([#45101](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076070023)). * 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 an issue where the Dalaloader Pro job is failing with `Required field missing on "nCino_Screen__c" object`, however the user were able to view the `Screen__c` object has a value in their source org ([#45139](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076158018)). * Fixed an issue where the user were not able to save the Dataloader Pro jobs and throws the `JAVA.NullPointerException` error ([#46385](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000078393786)). * 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 CI job build **ToRevision** number was mismatched in the **CI Job Results** and the **CI Build Info** page ([#45580](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076910037)). * Fixed an issue where the request parameters were empty in the **nCino Feature Commit History** screen ([#45855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077344165)). * 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 user were unable to fetch the latest CI job weekly reports ([#42587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072104139)). * Fixed an issue where the **Diff report** in the **Merge Request** was not working as expected ([#45315](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076389550)). * Fixed an issue where the user ran the branching baseline operation by excluding the Managed package components, however, the **Package.xml** file still had all the managed package components listed in it ([#45125](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000076117289)). * Fixed an issue where the code coverage report was being generated at a different time than what was scheduled ([#45703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077145009)). * Fixed an issue where the exported users list contained inaccurate information ([#44782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075451374)). * 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). * Fixed an issue where the user while performing **EZ-Commit** with SonarQube code analysis was getting failed with `Failed to run the sonar-scanner: null` error ([#46070](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000077717988)). #### 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 branching baseline feature for profile was not working as expected ([#44615](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075179971), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed an issue where the Dataloader Pro jobs were failing with no error message ([#44620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075206808), [#44264](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074669005)). * Fixed the issue where the Dataloader Pro jobs was not working as expected ([#43966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301291)). * Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the *notes* and *attachment* of the Credit Memo from source to the destination environment ([#40990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069124041)) * 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: * Fixed an issue where the picklist values failed to retrieve while preparing the CI job build ([#44117](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074423001), [#44029](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074323857)). * Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "**Remove User Permissions**" ([#44027](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074328464)). * Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade ([#44032](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074275828)) * Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels ([#44028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074327108)). * Fixed an issue with EZ-commit features where the metadata file was causing the JAXM marshall exception (invalid XML format) error ([#43864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074126263), [#43513](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073481411)). * Fixed an issue where the quick deployment functionality was not working as expected ([#42521](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071941125)). * Fixed an issue where the users could not view the commits list to merge them into a release label ([#43718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). * Fixed an issue where the code coverage reports fail to include all the classes in the CSV file ([#42848](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072441595), [#39582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066807003)). #### 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 branching baseline feature for profile was not working as expected ([#44615](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075179971), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed an issue where the Dataloader Pro jobs were failing with no error message ([#44620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000075206808), [#44264](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074669005)). * Fixed the issue where the Dataloader Pro jobs was not working as expected ([#43966](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301291)). * Fixed an issue where the users while performing org to org migration of nCino record based configurations, all the related items are getting carried over except the *notes* and *attachment* of the Credit Memo from source to the destination environment ([#40990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069124041)) * 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 performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 15 May 2022 **(ARM v22.1.7)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). #### 08 May 2022 **(ARM v22.1.6)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 01 May 2022 **(ARM v22.1.5)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the picklist values failed to retrieve while preparing the CI job build ([#44117](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074423001), [#44029](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074323857)). * Fixed the issue for the SFDX jobs where the user permissions were picked up for the deployment even if the user opts for "**Remove User Permissions**" ([#44027](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074328464)). * Fixed an issue where new tags gets automatically added for the sharing rules after the ARM 22.1 upgrade ([#44032](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074275828)) * Fixed an issue where the SFDX CI job picked up extra content for workflow and custom labels ([#44028](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074327108)). * Fixed an issue with EZ-commit features where the metadata file was causing the JAXM marshall exception (invalid XML format) error ([#43864](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074126263), [#43513](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073481411)). * Fixed an issue where the quick deployment functionality was not working as expected ([#42521](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071941125)). * Fixed an issue where the users could not view the commits list to merge them into a release label ([#43718](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). * Fixed an issue where the code coverage reports fail to include all the classes in the CSV file ([#42848](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072441595), [#39582](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066807003)). * Fixed an issue where the commits triggered in ARM shows a different author in Azure DevOps ([#44225](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074591143), [#43503](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073518014)). * Fixed a bug where selecting the "**Deployment**" icon after signing in to the ARM application caused the user to log off and on and return to the home page ([#44040](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074301863)). * Fixed a bug where the check-ins display the wrong number of files changed during commit ([#40119](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067784313)). * Fixed an issue in the TAF module where nothing pops up when you click on the "**View Log**" button ([#42020](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071114057), [#40284](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067992205)). * Fixed an issue where the users while accessing the help center from ARM application, receiving the **({"result":"failure","cause":"E105 - Request Delayed"})** error ([#43579](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652168)). * Fixed a bug where the commits was getting failed due to SCM (Software Configuration Management) authentication failure ([#42276](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071577005)). * Fixed a bug where the merge operations ran for more than 12 hours and later failed ([#38755](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065037173), [#42874](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072544001), [#38913](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065383003)). * Fixed an issue where extra metadata members are picked up for the profile component during the EZ-Commit process ([#41361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069919263)). * Fixed an issue where the users could not use commit template for the deployment ([#43995](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074325045), [#43586](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073635324), [#43905](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074163310), [#43407](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073339003)). #### 24 April 2022 **(ARM v22.1.4)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where performing a validation merge on the Azure repository branch creates the merge label and an external commit label with the same name and the same revision number ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). * Fixed an issue where the package deployment job was not triggered automatically once the validation was successful ([#43779](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074011003), [#43789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000074031001)). * Fixed the issue where the **DiscoveryAIModel** metadata type was unsupported, which caused the CI jobs to fail ([#42981](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072630620)). * Fixed an issue where the users were unable to fetch the standard fields from the custom objects ([#43378](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073288005)) * Fixed an issue where the ARM user interface gets distorted when the zoom is 100% ([#43735](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073906153)). * Fixed an issue where the ALM workflow was mismatched ([#43775](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073985001)). * Fixed **Spring4Shell vulnerability** by upgrading the Spring Boot version to 2.6.6 for the AR Agent ([#43584](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073648538)). * Fixed an issue where the "**invalid session**" error occurs when the user tries to delete and resave the cloned CI job. * Fixed an issue where the **Conflict Resolution** screen was not showing all the merge conflicts ([#43663](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073767313)). * Fixed an issue where the CI job build status fails with "**java.util.ConcurrentModificationException**" error when running the nCino feature migration templates ([#40752](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068643005)). * Fixed an issue with the Dataloader Pro job where the users, when trying to migrate the case object along with feed item & feed comment, the ARM application throws the "**invalid cross reference id**" error ([#43703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073896030)). * Fixed an issue where the merge process, after being sucessful, did not display the code coverage report ([#42079](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071200468)). #### 17 April 2022 **(ARM v22.1.3)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue for the Chrome browser where the ApexPMD ruleset was not uploading incorrectly (under the **Plugins** section). For other browsers, it was working as expected ([#42954](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072670003)). * Fixed the issue with the merge where the changes present in the source branches were not picked up, and therefore latest changes did not reflect on the destination branch ([#43553](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073610001), [#43598](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073662177), [#43595](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073653614), [#43593](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652863), [#43591](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073629096), [#43580](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073652300), [#43574](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073651134)). * Fixed an issue where the Salesforce-DX deployment and rollback mismatches ([#35947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000057045040)) * Added the criteria to trigger the callout URL post-deployment. If you set it to *success*, the callout URL is activated if the salesforce deployment is successful ([#38990](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065571472)). * Enabled feature flag settings to select between classic ARM and Salesforce CLI process to generate package manifest. * Fixed an issue where the commit validation is successful for an empty field, whereas the CI job fails ([#43324](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073218067)). * Fixed an issue where the deleted metadata components were showing under the **"File Changes"** tab but did not appear under the **"Destructive Changes"** column while carrying out a manual deployment ([#41670](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070494027)). * Fixed Dataloader Pro job issue where the job is completed successfully without loading all ancestors/master objects data to the destination environment ([#43276](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073123039)). * Fixed branching baseline issue where all metadata from the production org were not copied to the version control repo/branch ([#42938](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072633029), [#42685](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072244001), [#42955](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072644308), [#42445](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071818001), [#43038](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072780490), [#42753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072314347), [#42242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000071424143), [#42766](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072375048), [#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * Fixed the below nCino issues: * Unable to proceed with feature deployment using an existing community feature migration template due to the following error: **"No External Id field exist in source org."** This is now fixed and working as expected ([#43263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073131047)). * 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 an issue where the **Abort** option was showing for completed CI jobs ([#38177](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063673463), [#39052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065705011), [#38992](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564443), [#39682](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066942137)). * 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 an issue where deleting a custom field was affecting other custom objects where the globalpicklistvalue is shared by multiple objects ([#42782](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000072370556)). * Fixed a bug where the users were not able to view specific values under the standard value sets in the **New EZ-Commit** screen ([#41773](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070686445)). * Fixed a bug where the **New EZ-Commit > Deleted Component** tab throws a null error on expanding the metadata types. * Fixed a bug where the deploying records via record based configurations (RBC) was throwing error: **"No external Id field exists in the source org"** ([#43263](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000073131047)). * Fixed an issue where creating a new nCino feature migration template takes longer than expected ([#41855](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070869289)). * 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 **skip members** feature was not working for the Version Control, Deployments, and CI Job module ([#41531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221221)). * Fixed an issue where the users were receiving layout permissions errors when using **Prevalidation Commit**. * The SCA option where not working when users use the EZ commit/ Merge operation. The issue has now been fixed ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * Fixed an issue where the users were unable to generate the deployment report and received validations errors for EZ-Merge operation ([#41639](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423671)). * Fixed an issue where the users were unable to update any changes in the permission section. * Fixed an issue where the non-licensed users were receiving the deployment email failure notification for the unsuccessful deployment ([#41705](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070543145)). * Fixed an issue where the users were unable to use the nCino feature after the ARM was upgraded to v21.6 ([#41108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069360251)). #### 27 March 2022 **(ARM v22.1.0)**\ This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the users were unable to switch the tab from the **Test Coverage** to the **Class Coverage** in the **Apex test results** page ([#41455](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070062179)). * Fixed an issue where the users were unable to save Salesforce settings in the **My Account** screen ([#41329](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069835104)). * Fixed an issue where the users were not able to save the exclude metadata types in the **My Account** page ([#41529](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221075)). * Fixed an issue where the users were not able to create a new ALM project for Azure repository ([#41554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070326013), [#41630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423082)). * Fixed an issue where the users having difficulty with the **datamigration.properties** file while creating a new instance ([#41510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070231024)). # Release Notes 21 ## ARM Release Notes **21.6** **Date of Release:** ***21 November 2021*** **On this page:** 1. [New Features](#new-features) 2. [Enhancements](#enhancements) 3. [Improvements](#improvements) 4. [Changelogs](#changelogs) ### New Features #### Pull Request Support for Azure DevOps Pull request is a feature that allows you to review code and provide feedback before merging it into the master branch. Previously, we had GitHub and Bitbucket support. We've included support for Azure DevOps in this release. ([Learn More](/product-guides/arm/arm-features/version-control/external-pull-request/pull-request-support-for-azure-cloud)) * 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 an issue where the users were unable to deploy release labels ([#40600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068395530)). * Fixed the following SSO errors: * Unable to use SSO for AutoRABIT authentication ([#37767](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062637173)). * Unable to log in via SSO in the chrome and the firefox browser. * Fixed "**domain name does not exist**" error ([#41853](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070865403)). * Fixed a bug where users were getting an undefined error for the standard templates while editing the CI job. * Fixed an issue where the status of the AutoRABIT ExternalId field was showing as processing, but it was marked as completed in the log report ([#40669](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068569430)). * Fixed a bug that restricted users from using Dataloader Pro's **Auditable Standard** field feature ([#40794](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068711163)). * Fixed an issue where the users were unable to replace attachment records in the destination org. * Fixed an issue where the attachments were not completely deployed in the target environment ([#41208](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069667003)). * Fixed an issue where users were unable to deploy the nCino feature from org to org using the **nCino-Forms** **standard template** ([#38764](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065055277)). * Fixed an issue where the users were unable to **stop/delete** the data loader running jobs ([#39556](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066791149)). * Fixed an issue where the users when attempting to initiate the deployment, were failing with the **"Failed to initiate deployment request"** error ([#40620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068429999)). * Fixed an issue where the users were unable to perform the branching baseline operation ([#41622](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070417055)). * Fixed an issue where the users were not able to configure the approver's lists on the **New Merge Request** screen ([#41844](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070874003)). * Fixed an issue where the users trying to revert a commit for a commit label was getting failed ([#39613](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066805855)). #### 06 Mar 2022 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **skip members** feature was not working for the Version Control, Deployments, and CI Job module ([#41531](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221221)). * Fixed an issue where the users were receiving layout permissions errors when using **Prevalidation Commit**. * The SCA option was not working when users use the EZ-Commit/merge operation. The issue has now been fixed ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * Fixed an issue where the users were unable to generate the deployment report and received validations errors for the EZ-Merge operation ([#41639](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423671)). * Fixed an issue where the users were unable to update any changes in the permission section. * Fixed an issue where the non-licensed users were receiving the deployment email failure notification for the unsuccessful deployment ([#41705](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070543145)). * Fixed an issue where the users were unable to use the nCino feature after the ARM was upgraded to v21.6 ([#41108](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069360251)). #### 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 switch the tab from the **Test Coverage** to the **Class Coverage** on the **Apex test results** page ([#41455](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070062179)). * Fixed an issue where the users were unable to save Salesforce settings in the **My Account** screen ([#41329](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069835104)). * Fixed an issue where the users were not able to save the excluded metadata types on the **My Account** page ([#41529](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070221075)). * Fixed an issue where the users were not able to create a new ALM project for the Azure repository ([#41554](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070326013), [#41630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070423082)). * Fixed an issue where the users having difficulty with the **datamigration.properties** file while creating a new instance ([#41510](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070231024)). * Fixed an issue where the users when trying to start a deployment, it was getting failed with the "**Failed to start deployment request** error" ([#40620](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068429999)). * Fixed an issue where the users were unable to revert the commits using AutoRABIT ([#39957](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067378384)). * Fixed an issue where the users were not able to use the "**Files Changed**" functionality on the **Merge Request History** page ([#41456](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000070069155)). * Fixed an issue where the users were unable to delete the changes made in the version control branch via AutoRABIT ([#39130](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065873001)). * Fixed a bug that prevented users from performing commit and merge operations in AutoRABIT ([#39129](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065834119)). * Fixed an issue where the external objects with lookup relationships were not getting displayed under the child objects in the Dataloader Pro ([#41084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299165)). * 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: * Fixed an issue where the users were unable to see the commits ID in the release label ([#41284](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069797001)). * Fixed an issue where the users were unable to view their permission details in the Users and Roles tab ([#41043](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069219179)). * Fixed an issue where users were not able to delete the changes made in the source branch using AutoRABIT ([#39130](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065873001)). * Fixed an issue where the branching baseline for a profile and branch to branch merge was not working ([#40836](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068737067)). * There was an AutoRABIT performance issue that caused searching for revisions, validations, and commits to taking a long time. It has now been fixed ([#39129](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065834119)). * Fixed an issue where users were not able to commit their changes to the branch ([#39269](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066103022)). * When users attempted to update changes in the target org using the profile manager, the deployment getting failed. It has now been fixed ([#40599](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068421379)). * Fixed an issue where users were unable to switch from a credential-based login to an SSO-based login ([#40871](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068784190)). * AutoRABIT instances were not supporting the Salesforce API 54 version. It has now been fixed. ([#40921](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068957023)). * When a user performs a pre-validation commit on the Azure repository branches, it creates a duplicate external commit with the same revision ID. This issue has now been fixed ([#39287](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141740)). #### 13 Feb 2022 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **"Group By"** functionality was not fetching the correct CI job results ([#38870](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069460109)). * Fixed an issue where the deployment status of CI Job has failed in logs but the process is still in-progress stage ([#40805](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068697958)). * Fixed an issue where the users were unable to use the SCA for LWC components unlike apex class, triggers, and aura bundle ([#39288](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141955)). * When a pull request is in progress, the job is not triggered for additional changes committed before the work is completed. This is now fixed ([#38877](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065276358)). * Fixed a bug where the users were facing challenges while merging the entire branch changes to the target environment ([#39451](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066611145)). * Fixed an issue where the File Diff shows full component (especially Aura, LWC components) as a change instead of delta changes ([#39351](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066320276)). * 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 an issue where the data loader pro throws the error **"Error creating output directory: configs"** while uploading data from one environment to another ([#40832](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068736307)). * Fixed an issue where the external object-related lookups were unable to verify the relationship associated with the external objects in the destination org ([#41084](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069299165)). * 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: * The **"Commit"** button was not available for the merge request label job. ([#38876](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065275014)). * 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 an issue where the admin was unable to assign permissions to its sub-users. This is now working as expected ([#40017](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067565003)). * Fixed an issue where the validation rule automation was not working for the **Environment Provisioning** module ([#41035](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069198519), ([#40991](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000069108736)). * Fixed an issue where the data loader pro job is not able to load data for objects with fields exceeding limits([#38790](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085228)). * Fixed an issue where the users were unable to register the existing branches to AutoRABIT ([#40894](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068809067)). * Fixed an issue where the EZ-Merge was showing status as failed in the AutoRABIT application however, in the Salesforce environment the status shows as success ([#40673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068536502)). * 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 **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as their parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 where the users were unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 unable to generate the code coverage log report from the **Report** Module ([#38717](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064939344)). * Fixed an issue where the users were unable to upload the package.xml file to resolve the merge conflict ([#39960](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067372236)). * Fixed an issue where the users were able to commit the changes although the validation got failed. ([#38228](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063775343)). * Fixed an issue where the user was unable to perform the **Enable/Disable validation rule** on the Managed package object using the environment provisioning functionality ([#40297](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000068017532)). * Fixed a bug where the user was unable to deploy the **Email Template** on their target environment ([#40241](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000067922013)). * Fixed an issue where users were unable to upload/migrate the knowledge articles from one sandbox to another sandbox ([#37922](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063030291)). * 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 where the users were unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as their parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 an issue where the CI Job builds are getting stuck and no log information was displayed ([#39052](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065705011), [#38992](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564443), [#39682](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066942137)). * Fixed an issue where the conflicted files downloaded were incorrect during the merge process ([#39364](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066317317)). * Fixed an issue where the aura components were not getting retrieved while carrying out the branching baseline operation ([#38610](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064710558)). * 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. * Fixed an issue where the users were able to find the **Abort** option even when the CI Job had been completed successfully ([#38177](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063673463)). #### 26 Dec 2021 This is a maintenance release. The following items were fixed and/or added: * Fixed an issue where the **commit approvers** were not receiving email notifications due to the commit prevalidation being stuck in-progress. ([#38908](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065375104)). * Fixed an issue where the users were not able to select the master branch as the parent branch while registering existing branches from the repository in AutoRABIT ([#39082](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065729137)). * 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 the destructive commit components were still displayed for deployment ([#38888](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065298351)). * Fixed a bug where the access token is being printed along with the URL in the **Merge Log** report ([#39546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066761398)). * Fixed an issue where when users expanded the metadata types on the **Profile Manager** screen, they were able to spot duplicate child components. * Fixed an issue where the lookup field values were not picked up while creating the nCino feature migrating template ([#38868](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065239462)). * 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 where the user was unable to close the diff report file in the **Org Synchronization History** screen ([#39149](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065918101)). * Fixed an issue for the SFDX CI Jobs where the metadata types were not excluded without the baseline revision. * Fixed an issue where the release label deployment is adding unselected components in the deployment package ([#39239](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066031923)). * Fixed a bug where the users were unable to delete unwanted Dataloader Pro jobs from AutoRABIT ([#38600](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064711105)). * Fixed a bug where the parallel CI jobs are not working as expected ([#38803](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076930)). * Fixed a bug where the users were unable to generate the code coverage log report from the **Report** module ([#38673](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064853195)). * Fixed a bug where the search box doesn't work well with uppercase and lowercase in the commit label unlike the search in the dropdowns on the **Commit History** page ([#39286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000066141525)). * 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 when the user is trying to perform pre-validation commit for report metadata, it is getting added under emailservice functions in diff report ([#37925](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063067009), [#38581](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064666105), [#38880](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065272149), [#38734](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064981980)). * Fixed an issue where the case *entitlementProcess-meta.xml* files were not picked up during deployment ([#39069](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065734191), [#38361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064187022)). * Fixed an issue where the deployment report is getting failed while doing prevalidation merge with the report folder. * Fixed an issue where users were unable to retrieve a package which has more than 1000 components ([#38737](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064985007)). * Fixed a bug where a null pointer exception was thrown while loading in Dataloader Pro ([#38286](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063928003)). * Fixed an issue where the entitlement process is getting removed from Package.xml ([#39097](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065777009)). * Fixed an issue where the external commits did not show up on the release label ([#38822](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065151262)). * Fixed a bug that displays the wrong statuses in the test reports ([#39008](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065572975), [#38986](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065564303)). * Fixed an issue where the code coverage percent is not available in the case of SFDX merge operation. * Fixed an issue where the data loader pro jobs were not able to load data for objects with fields exceeding 800 ([#38790](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085228)). * 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 when pre- and post-destructive changes were added to the process, it caused the deployment to fail ([#38330](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064040175), [#38721](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064967175)). * Fixed a bug where for fewer CI jobs, the **Older** button was disabled. This has now been enabled and is working as expected ([#39050](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065702042)). * Fixed an issue in the SFDX module that prevented commits from being executed using scratch org ([#38789](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065076258)). * Fixed an issue where the external commits were not displayed when creating release labels or merging single revisions. This is now working as it should ([#38822](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065151262)). * Fixed an issue where users were unable to run SCA within the reports module due to an error stating **"Invalid mapping credentials."** In addition, the number of issues indicated in the Ez-commit process does not match the CodeScan analysis ([#38917](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065373386)). * Fixed a bug where single data loader jobs couldn't be edited and there was a mapped field cache issue ([#38753](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065026084)). * 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 nCino objects deployment issue during using nCino CI Jobs ([#39375](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000058591003)). * Fixed an issue where the custom object is being listed during CI Job operation but not during Ez-commit ([#38361](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064187022)). * Fixed Ez-merge issue which shows different results in AutoRABIT when compared to the production environment ([#38831](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065181230)). * Fixed an issue where the users were unable to extract deleted records and threw **"Malformed Query Fault"** error ([#38448](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064441154)). * Fixed an issue where the pull request support with BitBucket was not working properly. This is now fixed ([#38644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064828044)). * Fixed a bug in the merge request and pull request validation builds which were unable to list the changed components whereas the CI Job build was able to pick them up ([#37095](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060661017), [38713](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064936484)). * Fixed an issue where the org administrator was unable to assign hub level permissions to its sub-users ([#38898](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065336005)). * Fixed wrong metadata identification for deletion issue ([#37703](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062453147)). * Fixed an issue where the user was unable to update **"Configuration For recordTypes picklistValues"** ([#38901](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065355005)). * Fixed API version error in the CI Job screen ([#36550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059178003)). * Fixed CI build failing issue ([#38630](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064788278)). * Fixed EZ-Commit issue where the file diff was throwing an error due to credential scope issue ([#38950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065446001), [38795](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065077341)). * Fixed an issue where duplicate entries were seen while creating release labels ([#37300](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061440253)). * Fixed a bug where the user was unable to click on the **OK** button on the **Merge Request History** screen ([#38781](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000065085003)). * 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 quick deployment feature was not working as expected and was throwing **"Invalid Login"** error ([#37802](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062709159)). * Fixed a bug where the merge request validation was getting failed ([#37095](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060661017)). * Fixed an issue where the commit search was not working as expected in the **Version Control** module ([#36548](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059165111)). * Fixed an issue where the users were facing invalid credentials issue while updating the src as metadata folder path in-branch settings **(Admin > VC' Repos)** ([#38727](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064939824)). * Fixed an issue where the pull request support for BitBucket was not working properly as expected ([#38644](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064828044)). * Fixed an issue where the deployment shows failed status although there are no failures and the items did get moved to the destination org. This is now working as expected ([#37774](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062644015), [#38363](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064201151)). * Fixed an issue where the user was not able to retrieve the metadata to deploy the changes using AutoRABIT's deployment feature. * Fixed data loader pro issue which was throwing unknown error while migrating the data objects ([#38566](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064649001)). *** ## **ARM Release Notes 21.5** **Date of Release: *****29 August 2021*** **On this page:** 1. [Enhancements](https://knowledgebase.autorabit.com/arm/docs/arm-release-notes-215#enhancements) 2. [Changelogs](https://knowledgebase.autorabit.com/arm/docs/arm-release-notes-215#changelogs) 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 an issue where no metadata was found while validating the components from the master branch to the production environment ([#38612](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064709627), [#38587](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064645657), [#38571](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064639413), [#38537](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064517581), [#38552](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064584042), [#38549](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064544537)) * Fixed revision based deployment issue ([#38386](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064283007)) * Fixed an issue where the commit labels changes are not reflected in the release label ([#38569](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064646158)) * Fixed an issue where the salesforce deployment from GIT to SFDC was not working ([#38558](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064639001)) * Fixed deployment issue where no components were being retrieved via *Single Revision* or *Revision Range* ([#38550](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064581003), [#38546](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064558188)) * Fixed a bug where the deployment CI Job occurs multiple times ([#37454](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061960003)). * Fixed the search and substitute deletion rule issue ([#38410](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064291165)). * 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 user couldn't delete a job with special characters in its name ([#38332](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064061141)) * Fixed SFDX deployment and rollback mismatches issue ([#35947](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000057045040)). * Fixed a bug where when attempting to commit the deletion of 19 profiles, a Diff Report listing of 20 profiles was generated. ([#38303](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063932311)). * Fixed code coverage report discrepancy issue ([#36282](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000058168335)). * 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: * The deleted sharing rules were not showing up in the EZ-Commit Deleted tab, which was fixed ([#37747](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062586019)) * Fixed a bug where the older commits were not accessible for merge ([#38242](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063785008)). * Fixed an issue where when deploying a new custom object, an error *"Profile Search Layout: - System Administrator - not appropriate for object XXXXXX"* was thrown ([#37897](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062972201)). * Fixed a merge conflict issue([#37950](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063128003)). * Fixed a commit label issue ([#38275](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063874030)). * Fixed an issue with SSO where users had to log in twice before being able to use the AutoRABIT application ([#36634](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000059319963)). * The issue with the SSO domain has been fixed ([#37232](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000061168477)). * Fixed data loader audit logs issue ([#37688](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000062385762)). * Fixed an issue where the users were unable to exclude *EmbeddedServiceLiveAgent* from CI Job ([#38261](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063818321)). * Fixed an issue where the user couldn't delete a job with special characters in its name ([#38332](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000064061141)). * Fixed an issue where users were unable to compare profiles using the *Profile Manager* feature in the *Deployment* module ([#36978](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000060367023)). * In CI Jobs, a bug with the *"Group By"* filter was fixed ([#38132](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063522197)). * Fixed an issue where the community site was not getting deployed ([#38226](https://support.autorabit.com/support/autorabit/ShowHomePage.do#Cases/dv/241415000063775199)). * 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. # CodeScan Release Notes
CodeScan offers three primary deployment options: [Cloud](/release-notes/release-notes/codescan-release-notes/cloud-releases), [Self-Hosted](/release-notes/release-notes/codescan-release-notes/on-premise-releases), and [Government](/release-notes/release-notes/codescan-release-notes/ar-govcloud-documentation). Release notes and information are available for each deployment type. {% @mailchimp/mailchimpSubscribe cta="Sign up to receive CodeScan updates!" listId="a085e26e7e" %} # Cloud Releases # Cloud Release Notes 26.0
{% @mailchimp/mailchimpSubscribe cta="Sign up to receive CodeScan updates!" listId="a085e26e7e" %} ## CodeScan Release Notes 26.0.19 **Release Date: 23 August 2026** ### Summary CodeScan 26.0.19 is comprised of the following components: * 1 New Feature * 0 Application Enhancements * 0 New Rules * 0 Rule Enhancements * 0 Rule Deprecations * 0 Fixes Component details are listed in their corresponding sections within this document. ### New Features #### 1. Self-Service Trial Experience (PLG) Added a self-service trial experience that allows new users to sign up for a time-limited CodeScan trial directly from a dedicated trial URL, without requiring manual provisioning or sales involvement. Signup Flow * A dedicated trial signup URL routes new users through Auth0 Universal Login. * Personal email domains (gmail, hotmail, etc.) are blocked via Auth0 validation rules. * On successful signup and email verification, a trial organization is automatically provisioned and the user is assigned as Org Admin. * Signup information (name, email, company, phone) is sent to Salesforce to create a lead with source "CodeScan Cloud Trial". * Users must accept the AutoRABIT EULA during signup via a required checkbox, followed by an in-app EULA acceptance popup on first login. Trial Organization Configuration * Trial organizations are provisioned with configurable constraints: * Default duration: 14 days * Default maximum users: 3 * Trial settings are configurable at the instance level by super admins through the Billing page: * Trial duration (in weeks) * Integration user count * Standard user count * Feature/plugin access toggles * Trial organizations do not have access to nCino, Audit Logging, MuleSoft, or AI features by default. * Salesforce integration is disabled for trial organizations — the Salesforce project type is removed from the Create Project dialog, and the Salesforce Connections administration menu is hidden. * The Billing page is hidden for non-root users in trial organizations. Trial User Experience * A persistent banner at the top of the screen displays the remaining trial time ("Trial - X days left" or "Trial - ends today"). * Users can invite others to their trial organization. Invited users are added to the inviting organization only — no personal organizations are created for invited users. * User licensing limits (standard and platform users) are enforced during invitations and member management. Trial Expiry & Cleanup * Automated email notifications are sent at three milestones: * 7 days before trial expiration * 1 day before trial expiration * On the day the trial ends * After the trial period ends, the organization is archived for 30 days, then permanently deleted. * Trial users are permanently disabled after cleanup. Their email addresses are stored to prevent re-creation of trial accounts using the same email. **Outcome** * Enables product-led growth by removing friction from the trial onboarding process. * Provides configurable, time-limited trial access with clear expiry communication. * Prevents the platform performance issues previously caused by mass personal organization creation. *** ## CodeScan Release Notes 26.0.18 **Release Date: 16 August 2026** ### Summary CodeScan 26.0.18 is comprised of the following components: * 0 New Features * 0 Application Enhancements * 0 New Rules * 0 Rule Enhancements * 0 Rule Deprecations * 1 Fix Component details are listed in their corresponding sections within this document. ### Fix #### 1. GitHub App Authentication and Token Refresh Improvements Resolved multiple issues where GitHub App integration analyses would fail with authentication errors after the initial access token expired, affecting both Pull Request analysis and manual analysis runs. a. Unauthorized Status After 24 Hours Fixed an issue where GitHub Pull Request analysis reported "Unauthorized" status with "Bad credentials" (HTTP 401) errors when analyses were triggered more than 24 hours after the initial GitHub App connection. Re-creating the GitHub App temporarily resolved the issue, but the failure would recur. b. Refresh Token Expiry After \~8 Hours Fixed an issue where both Manual Analysis and Pull Request Analysis failed with "The refresh token passed is incorrect or expired" after approximately 8 hours following a successful analysis. The access token refresh mechanism has been corrected to automatically obtain new tokens when existing tokens expire. **Outcome** * Restores reliable, long-running GitHub App integration without requiring re-authorization. * Ensures consistent authentication for both Pull Request and manual analyses regardless of elapsed time. * Eliminates the need to re-create GitHub App connections as a workaround. *** ## CodeScan Release Notes 26.0.17 **Release Date: 2 August 2026** ### Summary AutoRABIT CodeScan 26.0.17 is comprised of the following 3 components: * 3 New Features * 0 Application Enhancements * 0 New Rules * 0 Rule Enhancements * 0 Rule Deprecations * 0 Fixes Component details are listed in their corresponding sections within this document. ### New Features #### AI Code Assistant (Pilot) Introducing the AI Code Assistant: an AI-powered code remediation capability built directly into CodeScan. The AI Code Assistant can generate fixes for common Apex rule violations, present changes in a side-by-side diff view for your review, and deliver approved fixes through automatically created Pull Requests. {% hint style="info" %} The AI Code Assistant is currently available as a Pilot feature. To learn more or request access, please contact your AutoRABIT Customer Success representative. {% endhint %} #### AI Credits, Usage Monitoring & Billing Added AI credit management capabilities to support AI features consumption tracking and governance. Key highlights: * AI credits integrated with subscription billing for accurate consumption tracking * Real-time AI usage indicator in the top navigation bar with color-coded thresholds (Healthy, Low, Critical) and hover tooltip showing exact credit counts * New AI Billing administration page (Administration → AI Billing) with a summary bar and searchable per-user consumption table with color-coded progress bars * Organization-level daily execution limits with clear notifications when limits are reached * Bulk assignment governance — maximum 10 issues per bulk action {% hint style="info" %} The AI Billing page is visible only to organizations with licensed AI features. {% endhint %} #### CodeScan MCP (Pilot) Introducing the CodeScan MCP Server: a hosted endpoint that brings CodeScan analysis data directly into the AI coding assistants developers already use, such as GitHub Copilot, Cursor, and Claude Desktop. Once connected, you can stay in your editor and query CodeScan conversationally: * Check which projects are passing or failing their quality gate * Drill into issues, security hotspots, rules, and measures without opening the web UI * Look up organizations, projects, branches, pull requests, and analysis job details as you code * Pull CodeScan data into your own reporting or review workflow on demand {% hint style="info" %} The CodeScan MCP Server is currently available as a Pilot feature. To learn more or request access, please contact your AutoRABIT Customer Success representative. {% endhint %} *** ## CodeScan Release Notes 26.0.16 **Release Date: 19 July 2026** ### Summary AutoRABIT CodeScan 26.0.16 is comprised of the following 4 components: * 0 New Features * 1 Application Enhancement * 0 New Rules * 0 Rule Enhancements * 0 Rule Deprecations * 3 Fixes Component details are listed in their corresponding sections within this document. ### Application Enhancements 1. **Added Support for Salesforce Refresh Token Rotation (RTR)** Enhanced the Salesforce integration to support Refresh Token Rotation (RTR) for OAuth authentication. Salesforce now enables Refresh Token Rotation by default for newly created External Client Applications (ECAs). With RTR enabled, refresh tokens are rotated after use instead of remaining static. This enhancement updates the CodeScan Salesforce integration to correctly manage rotating refresh tokens, ensuring uninterrupted authentication for new and existing Salesforce connections. **Behavior** The Salesforce integration now: * Supports refresh token rotation for OAuth-based Salesforce connections. * Automatically manages refresh token updates during token renewal. * Maintains connection health across successive token refresh cycles. * Supports both RTR-enabled and non-RTR Salesforce External Client Applications. * Continues to use existing authentication flows for previously configured Salesforce connections. **Compatibility Improvements** The enhancement provides compatibility with: * Salesforce Production organizations * Salesforce Sandbox organizations * Newly created External Client Applications with Refresh Token Rotation enabled * Existing External Client Applications with Refresh Token Rotation disabled Support is available across Salesforce analysis workflows, including: * Main branch analysis * Comparison branch analysis * Scheduled analyses **Outcome** * Ensures compatibility with Salesforce's latest OAuth security model. * Prevents unnecessary reauthorization for long-lived Salesforce connections. * Improves the reliability of Salesforce project analysis across repeated authentication cycles. * Maintains backward compatibility with existing Salesforce integrations while supporting new Salesforce security defaults. ### Fixes 1. **Improved SOQL in Loops Rule Accuracy** Resolved an issue where the Avoid SOQL in Loops rule (*sf:AvoidSoqlInLoops*) could incorrectly report violations for certain method invocation patterns, resulting in false positives. Previously, the rule could identify SOQL or DML operations as being executed within a loop based solely on nested method call analysis, even when the queried method was not actually invoked from a looping execution path. In some scenarios, method calls originating from Apex test classes could also be included in the analysis, contributing to incorrect findings. **Behavior** The rule has been enhanced to improve analysis accuracy by validating the actual execution path before reporting nested-call violations. Improvements include: * Reduced false positives for SOQL and DML operations that are not executed within loop constructs. * Improved evaluation of nested method invocation chains. * Improved validation to ensure nested-call violations are reported only when a genuine loop execution path exists. **Improved Diagnostics** The rule now provides more accurate reporting by distinguishing between nested method calls and actual SOQL/DML execution within loops, reducing misleading violations for valid code. **Outcome** * Reduces false positives reported by the Avoid SOQL in Loops rule. * Improves accuracy of data flow and nested-call analysis. * Provides developers with more reliable and actionable rule findings. * Improves confidence in SOQL and DML loop detection for complex Apex applications. 2. **Clarified Configuration Limits for SOQL/DML Inside Loops Rule** Updated the documentation for the Avoid SOQL/DML Inside Loops rule (*sf:AvoidSoqlInLoops*) to clearly communicate the supported configuration limits for method traversal depth. Previously, the rule parameter documentation did not specify the recommended maximum value for the maxMethodTraversalDepth parameter, which could lead to unsupported or excessive configuration values being entered. **Documentation Improvements** The parameter description has been updated to clearly indicate the supported range for method traversal depth, helping administrators configure the rule appropriately. The updated default guidance: * MaxMethodTraversalDepth = 5 * MaxMethodVisitedCount = 200 **Outcome** * Provides clearer guidance for configuring method traversal depth. * Helps administrators understand the recommended operating limits for the rule. * Improves usability of Quality Profile configuration. * Reduces the likelihood of unsupported rule parameter configurations. 3. **Updated Guidance for Custom Field Requirement Configuration Rule** Updated the documentation and messaging for the Custom Field Security in Standard Object rule (*sfmeta:CustomFieldSecurityInStandardObject*) to provide clearer guidance on the recommended approach for configuring required custom fields on Salesforce standard and shared objects. Previously, the rule messaging did not clearly explain why marking custom fields as required at the schema level could have unintended consequences across different data entry mechanisms. The following rule metadata has been updated: * Title: Use the Page Layout to mark the custom field as required. * Message: Use the Page Layout to mark the custom field as required. * Description: Expanded to clarify that custom fields on standard and shared objects should be marked as required through page layouts rather than at the schema (system) level. The updated guidance explains that using page layouts limits the requirement to users interacting through the Salesforce UI, while avoiding unintended impacts on other data entry points, such as: * APIs * Data Loader * Apex * Integrations **Outcome** * Provides clearer remediation guidance for Salesforce administrators. * Encourages Salesforce best practices for configuring required custom fields. * Helps prevent unintended validation issues across integrations and automated processes. * Improves the usability and clarity of rule findings. *** ## CodeScan Release Notes 26.0.15 **Release Date: 05 July 2026** ### Summary CodeScan 26.0.15 is comprised of the following 5 components: * 1 New Feature * 1 New Rule * 1 Rule Enhancement * 2 Fixes Component details are listed in their corresponding sections within this document. ### New Features 1. **CodeScan now has “salesforce-project-only” tags for Rules with SF queries** **Description** Several CodeScan rules perform queries directly against Salesforce to execute their analysis. These rules require an active Salesforce project connection and cannot be used in a standard static analysis context. To improve discoverability and filterability, the tag salesforce-project-only should be added to each of these rules. The following rules require this tag: * sfmeta:NcinoDuplicateLabels * sfmeta:NcinoComponentNamingDuplicate * sfmeta:NcinoIntUserConfig * sfmeta:NcinoDeprecatedFields * sfmeta:NcinoDuplicateLookupKeys * sfmeta:NcinoFeeTemplateScreenSection * sfmeta:NcinoNullLookupKeys * sfmeta:NcinoProductFeatureNotExist * sfmeta:NcinoProductFeatureSharing * sfmeta:NcinoNullCollateral * sfmeta:ExcessivePageLayout * sfmeta:CheckSystemAdministrator * sfmeta:CustomProfilesPermission **Value** Users working in non-Salesforce-connected environments are exposed to rules that will never produce valid results for their project type. By tagging these rules with salesforce-project-only, users can quickly filter them in or out of their rule sets, reducing noise and improving the overall rule browsing experience. It also makes it clearer to new users why certain rules may not be firing. **Acceptance Criteria** * The tag salesforce-project-only is added to all 13 rules listed above. * The tag appears on the rule detail page for each affected rule in the CodeScan UI. * Users can filter the rules list by the tag salesforce-project-only and only the 13 listed rules (and any others previously tagged) are returned. * No existing tags on any of the affected rules are removed or modified. * The tag is consistent in formatting (lowercase, hyphenated) with salesforce-project-only across all rules. * A smoke test has been performed to confirm the tag is visible and filterable in a non-production environment before release. We have verified that the tag "salesforce-project-only" has been added to all 13 rules, and that the tag is visible, consistent, and filterable in the CodeScan UI. #### Test Scenarios Validated: 1: Tag presence — All 13 rules have "salesforce-project-only" tag * sfmeta:NcinoDuplicateLabels * sfmeta:NcinoComponentNamingDuplicate * sfmeta:NcinoIntUserConfig * sfmeta:NcinoDeprecatedFields * sfmeta:NcinoDuplicateLookupKeys * sfmeta:NcinoFeeTemplateScreenSection * sfmeta:NcinoNullLookupKeys * sfmeta:NcinoProductFeatureNotExist * sfmeta:NcinoProductFeatureSharing * sfmeta:NcinoNullCollateral * sfmeta:ExcessivePageLayout * sfmeta:CheckSystemAdministrator * sfmeta:CustomProfilesPermission 2: Tag visible on rule detail page for each affected rule 3: Filter by "salesforce-project-only" returns all 13 rules 4: No existing tags removed or modified on any of the 13 rules 5: Issue got triggered for a random rule, working as expected. Hence closing this user story. ### New Rules 1. **New CodeScan Metadata Rule: “Communities With Guest Access”** {Rule ID: sfmeta:CommunityGuestUserAccess"} **Description** Identify Salesforce Experience Cloud communities (Network metadata) that allow guest user access and correlate them with associated Guest User Profile metadata to detect excessive permissions (object, field, or Apex access). The rule flags communities where unauthenticated users may access or modify sensitive data. **Hypothesis** If a community allows guest access and the associated guest user profile has elevated permissions, then sensitive data or functionality may be exposed to unauthenticated users, leading to potential data breaches or unauthorized actions. #### EXACT CONDITIONS TO FLAG A. Object-Level Permissions From: \ Flag if ANY of the following: * allowRead = true on standard objects: * Account * Contact * Lead * User * OR any custom object (\_\_c) OR * Any of these are true: * allowCreate = true * allowEdit = true * allowDelete = true B. Field-Level Access (Sensitive Data Exposure) From: \ Flag if: * readable = true for sensitive fields like: * Contact.Email * Contact.Phone * Lead.Email * Any field matching patterns: * \*Email\* * \*Phone\* * \*SSN\* * \*Password\* This is your PII exposure condition C. Apex Class Access (Public Logic Exposure) From: \ Flag if: \true\ Especially risky if: * Classes expose: * @AuraEnabled * REST endpoints Parameters should be displayed as shown below: Note: Regarding fields, the functionality should work as PII rule. **Value / Purpose** * Detects real-world data exposure risks from misconfigured guest access * Prevents unauthenticated access to sensitive objects and fields * Ensures secure configuration of Experience Cloud communities * Reduces risk of public data leaks and compliance violations * Provides context-aware, high-confidence vulnerability detection **Acceptance Criteria** Name: Community Guest User Has Excessive Permissions \ Key: CommunityGuestUserAccess \ **Description**: This rule identifies Salesforce Experience Cloud communities that allow guest access and where the associated Guest User Profile has elevated permissions such as object-level permissions (read, create, edit, delete), field-level access to sensitive data, or Apex class access. This may expose sensitive data to unauthenticated users. Type: Vulnerability \ Severity: Critical \ Message: Guest user profile has elevated permissions in a community, which may expose sensitive data or allow unauthorized actions. \ Tags: salesforce, security CWE : 732 Remediation: 15 Minutes {% hint style="info" %} NOTE: This is a project-level rule. {% endhint %} **Verification**: We have verified the new Salesforce Metadata rule "CommunityGuestUserAccess" (Communities With Guest Access) and have validated via the following scenarios: * Rule correctly detects communities with guest access enabled. * Flags guest user profiles with elevated object-level permissions (read, create) on standard objects. * Flags guest user profiles with elevated object-level permissions (read, create) on custom objects. * Identifies sensitive/PII field-level access (Email, Phone, SSN patterns) on guest profiles. * Detects enabled Apex class access on guest profiles. * Configurable parameters (Sensitive Fields, Include Custom Objects) work as expected. * Rule severity correctly classified as Critical Vulnerability. * Above scenarios verified with Comparison branch as well, work as expected. * Re-run & Run manual verified regarding the new changes, both work as expected. **Notes**: * To get the rule triggered correctly, make sure to add “Network” in codescan.cloud.packageTypes and “network” & “profile” in sonar.sfmeta.file.suffixes in project settings. * To give guest users access to the site's APIs, enable “Allow guest users to access public APIs” in Salesforce> Setup > all Sites > Workspaces > Administration > Preferences (or Builder > Settings > Public access) * To take away guest users access to the site's APIs, disable “Allow guest users to access public APIs” in Salesforce> Setup > all Sites > Workspaces > Administration > Preferences (Also verify Builder > Settings > Public access is disabled) * For custom sensitive/PII field-level access, configure “Filed Name” in the rule parameters. ( Field name and Field label can be different, get field name from sf org) All verification use cases passed successfully, the rule is working as expected, and no issues were reported during verification. ### Rule Enhancements 1. **Enhanced logic in CodeScan Apex rule “Unused Formal Parameter” to address common false positives {Rule ID: sf:UnusedFormalParameter}** **Description** Several customers had reported false positives associated with this rule. Upon analysis, we determined that at the Salesforce level, when parameters are consumed as SOQL bind variables inside a dynamically built query string, these parameters are generally used (and resolved from local scope at runtime). \ \ CodeScan was flagging them because its bind-detection only covers the IN :var form passed as a direct argument — not as strings built through the QueryFactory chain. As such, we enhanced the rule logic to ensure that the rule (sf:UnusedFormalParameter) will not raise a violation when a method parameter is referenced as a SOQL bind variable within a string passed to dynamic SOQL execution. The rule shall recognize bind variable usage for operators such as =, !=, >, <, >=, <=, and IN. Existing support for IN :variable patterns shall remain unchanged. A violation shall still be reported when a method parameter is genuinely unused. We have verified that the rule sf:UnusedFormalParameter no longer raises false positives for formal parameters consumed as SOQL/SOSL bind variables (:var) in dynamic query patterns including fflib\_QueryFactory and Database.query(). ### Fixes 1. **Fixed grammatical error in CodeScan Project Summary Report** **Description of issue:** Misspelling in Project Report **Details**: When users access the second page of a CodeScan Project report, there was a grammatical error in the error message: "There is no any issues in the project analysis yet." We have updated error message to now display: “There are currently no issues in the project analysis.” We have verified that the error messages have been properly updated to “There are currently no issues in the project analysis.” in the project reports. All reports are working as expected. * Verified in the new project’s report * Verified in the old project’s report * Verified in the scheduled cron job reports 2. **Fixed issue with CSV Export where the "Status Marked By" Column was empty for Bulk Operations** **Summary** The "Status Marked By" column in the CSV Issue Export is empty when issue statuses are changed via bulk operations (api/issues/bulk\_change). The column works correctly when statuses are changed via single-issue operations (api/issues/do\_transition). **Expected Result** The "Status Marked By" column should display the name of the user who performed the bulk status change for all affected issues. We analyzed the "Status Marked By” population logic and found that bulk status change records were being skipped due to a startsWith() check. Updated the logic to correctly process bulk change entries and populate the user information. With this logic change, this issue has been fully remediated. **Scenarios Validated:** 1. Bulk status change to CONFIRMED – "Status Marked By" column correctly populated with the user name 2. Bulk status change to EXCEPTION – Column populated as expected 3. Bulk status change to FALSE\_POSITIVE – Column populated as expected 4. Bulk status change to ACCEPTED – Column populated as expected 5. Mixed bulk + single-issue transitions in same CSV export – Both reflect correct user names 6. Multiple bulk operations by different users – Each row shows the respective user who performed the action 7. Single-issue regression – No regression, column still works correctly for single transitions 8. Re-transition after bulk change – "Status Marked By" updates to the latest user 9. Issues with no status change – "Status Marked By" appropriately empty only for untouched issues - OPEN Status Verified the same scenarios with Root-level admin, working as expected.\ Verified the same scenarios with PR, working as expected. *** ## CodeScan Release Notes 26.0.14 **Release Date: 28 June 2026** ### Summary CodeScan 26.0.14 is comprised of the following components: * 1 Fix Component details are listed in their corresponding sections within this document. ### Fixes 1. **Resolved CI Jobs Analyzing Entire Codebase Instead of Delta Changes** Fixed an issue where CodeScan CI jobs could analyze the entire repository instead of only the files modified in the current pull request or commit. Previously, delta analysis was not consistently applied in certain CI execution scenarios, causing CodeScan to process all files in the repository. This could result in longer analysis times, increased resource consumption, and findings unrelated to the current code changes. **Behavior** * CI jobs now correctly analyze only the files included in the current delta (changed files). * Delta analysis is consistently applied across supported CI integrations. * Unmodified files are excluded from analysis when delta scanning is enabled. * Analysis execution time and resource utilization are reduced for incremental scans. * Results are focused on issues introduced or affected by the current changes. **Outcome** Improves CI pipeline performance and ensures analysis results remain relevant to the code changes being reviewed. *** ## CodeScan Release Notes 26.0.13 **Release Date: 21 June 2026** ### Summary CodeScan 26.0.13 is comprised of the following 6 components: * 0 New Features * 1 Application Enhancements * 1 New Rule * 2 Rule Enhancements * 0 Rule Deprecations * 2 Fixes Component details are listed in their corresponding sections within this document. ### Application Enhancements 1. **Enhanced CSV Export Reporting for Issues and Security Hotspots** Enhanced CSV export reporting for both Issues and Security Hotspots to provide additional information for ownership tracking, exception management, auditing, and compliance reporting. Previously, CSV exports contained limited information, requiring users to manually retrieve assignment, severity, and exception details from within the CodeScan application. **New Export Fields** Issue and Security Hotspot CSV exports now include: * Severity * Assigned To * Assigned Date * Exception Expiry Date * Exception Reason Exported data reflects the current state of issues and hotspots at the time of export. **Exception Reason Tracking Improvements** Issue exception reasons are now stored separately from standard issue comments, improving traceability and reporting accuracy. Previously, exception reasons for Issues were stored using the same change type as standard comments, making it difficult to distinguish exception justifications from normal discussion history. **Reporting Improvements** The enhanced exports provide greater visibility into: * Severity classification * Ownership and assignment history * Exception lifecycle management * Expiring exceptions * Compliance and audit reporting activities Issue CSV exports now clearly distinguish between: * Issue Comments * Exception Reasons Fields are clearly labeled and consistently formatted within the generated CSV files. The updated exports provide users with improved visibility into severity, ownership, exception status, and exception lifecycle details, making it easier to perform external analysis, compliance reviews, and governance activities. **Outcome** * Improves auditability and compliance reporting. * Provides greater visibility into issue and hotspot ownership. * Simplifies exception tracking and lifecycle management. * Reduces the need to manually gather information from multiple areas of the platform. * Enhances offline analysis and reporting workflows. ### New Rules 1. **Connected App Missing Description** Added a new Salesforce Metadata rule to identify Connected Apps that do not have a defined description in metadata. Connected Apps without descriptions can be difficult to govern because administrators may not have enough context about the app’s purpose, ownership, or access usage. **Rule Details** * Rule key: *ConnectedAppMissingDescription* * Type: Code Smell * Default Severity: Major * Remediation effort: 2 minutes * Tags: salesforce **Behavior** The rule raises a violation when a Connected App metadata file does not contain a valid description. Violations are raised when the description is: * Missing * Empty * Self-closing * Commented out * Whitespace-only * Defined only in an unrelated nested location The rule does not raise a violation when a valid description is present, including descriptions with multiline text or special characters. **Message** *Connected App does not have a description defined. Add a description for better governance and traceability.* **Outcome** * Improves governance and documentation of Salesforce Connected Apps. * Helps identify orphaned, unmanaged, or poorly documented integrations. * Supports security audits and compliance reviews. * Provides better visibility into app purpose and ownership. ### Rule Enhancements **1. Improved Rule Engine Stability and Error Handling** Improved the stability and resilience of Apex rule execution by addressing multiple edge cases that could result in internal exceptions being exposed in analysis logs. Previously, certain rule evaluation scenarios could generate internal exceptions during analysis, resulting in Java stack traces being written to logs. Although analysis often completed successfully, these errors could lead to incomplete rule evaluation and reduced confidence in results. Edge cases addressed: * *SOQL Injection Rule Stability* Improved handling of Apex data-flow analysis scenarios that could previously result in internal type-casting exceptions during rule evaluation. * *LocaleInOldApiRule Stability* Improved handling of chained method invocations such as DateTime.now().format()to prevent internal rule execution errors while analyzing valid Apex code. * *Defensive Null Handling Across Rule Execution* Enhanced null-safety handling for multiple Apex rules, including: * Unescaped Output * SOQL Injection * Avoid SOQL in Loops Additional validation and defensive checks were introduced to ensure rule execution can safely handle unresolved AST and semantic-analysis paths without exposing internal exceptions. **Outcome** * Improves overall rule engine stability. * Prevents internal implementation details from appearing in analysis logs. * Reduces the risk of incomplete rule evaluation. * Provides more reliable and professional analysis output. * Improves confidence in analysis results for Apex projects. 2. **Enhanced Documentation for Sensitive PII Field Detection Rule** Updated the documentation and guidance for the Identify Potential Sensitive PII Fields rule (sf:SecurePIIFields) to provide clearer information about the types of data covered by the rule and how organizations can extend detection coverage. **Documentation Improvements** The updated rule description now clarifies that certain standard Salesforce objects may contain sensitive personal information, including: * Contact * Lead * User * Account * Person Account * Opportunity Examples of potentially sensitive data include: * Names * Email addresses * Phone numbers * Physical addresses * Birth dates * Other personal identifiers The documentation also highlights the importance of protecting this information in accordance with privacy and security regulations such as: * GDPR * CCPA * HIPAA **Configuration Guidance** Organizations can define additional sensitive field names through rule parameters, including: * SSN * Social\_Security\_Number * Credit\_Card * Passport and other organization-specific fields that may contain regulated personal information. **Outcome** * Improves understanding of the rules' purpose and scope. * Provides clearer guidance for identifying and protecting sensitive data. * Helps organizations extend detection coverage to custom fields. * Supports privacy, security, and compliance initiatives through improved rule documentation. ### Fixes 1. **Resolved SAML Login Issue with Uppercase Organization Domains** Fixed an issue where users could be unable to log in when the organization's domain name contained uppercase letters. Previously, the SAML login flow treated organization domains as case-sensitive. As a result, valid domains entered with uppercase or mixed-case characters could fail authentication, even though domain names should be handled case-insensitively. **Behavior** * Organization domain matching is now handled case-insensitively during SAML login. * SAML connection creation now stores organization domain names consistently in lowercase. * Domains entered in lowercase, uppercase, or mixed case are handled correctly. * Leading and trailing spaces in domain input are handled safely. * Invalid domains continue to be rejected as expected. **Outcome** * Improves SAML login reliability for organizations using mixed-case or uppercase domain entries. * Aligns organization domain handling with standard case-insensitive domain behavior. * Prevents valid users from being blocked due to domain capitalization differences. 2. **Resolved Salesforce Integration Error When Using Previous Test Run Results** Fixed an issue that could prevent Salesforce integrations from running successfully when configured to use unit test results from a previous execution. Previously, analyses configured with the *Use previous run* option could fail while attempting to retrieve historical test execution data. **Behavior** * Corrected the retrieval of previous unit test execution results. * Improved handling of Salesforce test coverage queries and historical test result lookups. * Analysis now successfully reuses previously executed unit test results when available. * Organizations without prior test execution history are handled gracefully. **Outcome** * Improves the reliability of Salesforce integrations using previously executed unit tests. * Prevents failures caused by test result retrieval errors. * Reduces unnecessary test execution by allowing the successful reuse of historical test results. * Provides more resilient handling of organizations with limited or no prior test execution history. *** ## CodeScan Release Notes 26.0.12 **Release Date: 7 June 2026** ### Summary CodeScan 26.0.12 is comprised of the following 8 components: * 3 Application Enhancements * 1 New Rule * 1 Rule Enhancement * 3 Fixes Component details are listed in their corresponding sections within this document. ### Application Enhancements 1. **Instance-Level Severity Masking** {% hint style="info" %} NOTE: This feature is only available to customers who have a dedicated instance. It is not available for customers who are deployed on our SaaS multi-tenant instances. {% endhint %} Added support for instance-level severity masking, allowing CodeScan Administrators to centrally customize how severity labels are displayed across the platform while preserving underlying severity values, analysis behavior, and reporting logic. Previously, severity labels were displayed using the default values throughout CodeScan and could not be customized at the instance level. This enhancement introduces centralized severity masking that is consistently applied across the Web UI, reports, exports, APIs, and IDE plugins. **Behavior** * Administrators can configure severity label mappings through the Admin UI. * Severity masking settings are stored and managed at the instance level. * Severity mappings are exposed through secure APIs and applied consistently across the platform. * Custom severity labels are displayed throughout: * Web UI * Reports * CSV exports * SARIF exports * IDE plugins * Default severity labels are automatically used when no severity masking configuration exists. * Changes are applied immediately without requiring a refresh. **Supported Default Severity Labels** * Blocker * Critical * Major * Minor * Info **Validation** * Validation is enforced at both API and UI levels. * Invalid severity mappings are rejected with clear error messages. * Only administrators can modify severity masking settings. * Unauthorized users are restricted from making configuration changes. **Functional Integrity** Severity masking affects display labels only. The following behaviors remain unchanged: * Underlying severity values * Issue counts and metrics * Quality Gate evaluations * Severity-based sorting * Severity-based filtering * Analysis processing * Reporting calculations * Export generation * SARIF standards compliance * IDE plugin workflows * Downstream integrations **Outcome** * Provides consistent severity representation across the entire CodeScan platform. * Enables centralized governance of severity terminology. * Reduces inconsistencies between Web UI, reports, exports, and IDE plugins. * Preserves existing functionality and compatibility with integrations. 2. **Exception Expiry Notifications** Added subscription-based exception expiry notifications for Issues and Security Hotspots, enabling users to receive automated reminders before approved exceptions reach their expiry date. **Subscription Management** Users can now manage exception expiry notification preferences through: Profile → My Account → Notifications Notification options are available in: * Overall Notifications * Project Notifications * Project-level notification settings Users can enable or disable exception expiry notifications based on their preferences. **Reminder Notifications** Subscribed users receive automated email reminders for Issues and Security Hotspots with approved exceptions. Notifications are sent: * One week before expiry * One business day before expiry Business-day scheduling is automatically applied. **Notification Controls** Notifications respect: * User notification preferences * Project notification settings * User permission settings Notifications are not sent for: * Archived organizations * Deleted projects * Unsubscribed users **Outcome** * Helps teams proactively review exceptions before they expire. * Reduces the risk of unnoticed expired exceptions. * Improves compliance and governance processes. * Provides users direct control over exception-related notifications. 3. **Rules Evaluation Export Report** Added a new Rules Evaluation Export Report that provides visibility into all rules evaluated during a scan, including scans where no issues are detected. **Behavior** A new export option, CSV Rules Evaluation Report, is available from the More menu. Users can select: * Project * Branch and export a report containing all rules evaluated during the selected scan. **Report Contents** The report includes: * rule\_key * rule\_name * rule\_language * rule\_category * rule\_severity * issues\_found Rules are included regardless of whether violations were detected. **Outcome** * Improves auditability and compliance reporting. * Provides visibility into scan coverage. * Allows users to validate rule execution even when no issues are found. * Preserves historical accuracy based on the quality profiles used during the scan. ### New Rules 1. **Connected App Uses High-Risk OAuth Scopes** Added a new Salesforce Metadata security rule to identify Connected Apps configured with high-risk OAuth scopes that may grant excessive or persistent access to organizational data and APIs. **Rule Details** * Rule key: *ConnectedAppHighRiskScopes* * Type: Vulnerability * Default Severity: Major * CWE: CWE-272 * Remediation effort: 10 minutes **Behavior** The rule analyzes Salesforce Connected App metadata and raises a violation when high-risk OAuth scopes are detected within the Connected App configuration. The following OAuth scopes are currently identified as high-risk: * full * api * refresh\_token When one or more of these scopes are present, the rule reports the detected values in the violation message. **Message** *Connected App contains high-risk OAuth scopes: {scopes}. Review and restrict access.* **Outcome** * Helps security teams identify over-privileged Salesforce integrations. * Improves visibility into Connected Apps that may expose organizational data through excessive OAuth permissions. * Encourages implementation of least-privilege access principles. * Reduces the risk of unauthorized or persistent access through overly permissive OAuth scope configurations. ### Rule Enhancements 1. **Enhanced Avoid Calling SOQL and DML Inside Loops Rule** Enhanced the *sf:AvoidSoqlInLoops* rule to optionally detect Salesforce platform methods that consume SOQL queries internally when executed within loops. **New Parameter** | Parameter | Default | Description | | ----------------- | ------- | -------------------------------------------------------------------- | | checkInternalSoql | false | Checks for methods with internal SOQL consumption used within loops. | **Behavior** When enabled, the rule identifies supported platform methods that may consume hidden SOQL queries inside loops, for example: * Messaging APIs * UserInfo APIs * FeatureManagement APIs * Approval APIs * Flow invocation APIs * ConnectApi operations * Visualforce content APIs Outcome * Improves detection of governor limit risks. * Identifies hidden SOQL consumption. * Helps developers avoid query-limit violations. * Preserves existing behavior unless explicitly enabled. ### Fixes 1. **GitHub Enterprise Integration Improvements** Resolved multiple GitHub App integration issues affecting project creation, Pull Request analysis, and commit status reporting. a. GitHub App Installation Flow * Fixed an issue where organization members could receive a 404 error during GitHub App installation and project creation workflows. b. Pull Request Analysis Scope * Fixed an issue where PR analysis could process unrelated base branch files when the GitHub App lacked required permissions to retrieve changed PR files. * Required permission (PR): Read c. Commit Status Reporting * Fixed an issue where CodeScan could not publish analysis status updates to GitHub Pull Requests due to insufficient GitHub App permissions. * Required permission (Commit statuses): Read & Write Outcome * Improves GitHub project onboarding. * Ensures PR analysis processes only changed files. * Restores CodeScan status reporting on Pull Requests. * Improves support for all types of environments. {% hint style="info" %} **GitHub App Permission Update** **As** part of this release, we have updated the permissions required by the CodeScan GitHub App. GitHub will send a permission update request to any account or organization that has the CodeScan GitHub App installed. \ The account or organization Owner should review and approve this request in GitHub:\ Settings → GitHub Apps (or Applications → Installed GitHub Apps → CodeScan → Review Request) \ Once the request is approved, no further action is required. {% endhint %} 2. **Resolved User Invitation and Group Assignment Issues** Fixed issues in the user invitation workflow where invited or re-created users were not being assigned correctly to organizations and default groups. Previously: * Users invited from an organization were not always added to that organization after signup. * Users who were deleted or deactivated from the UI and later re-created were not added back to the default Members group. * This could prevent invited users from accessing the expected organization context after completing signup. **Behavior** * New users now follow the invite link flow correctly after signup and are added to the intended organization. * Email verification handling was updated so first-time signup flows redirect users through the invite workflow as expected. * Re-created users are now added back to the default Members group after activation. * Invite validation and post-login handling were improved to ensure organization and group membership are applied correctly. **Outcome** * Ensures invited users are added to the correct organization after signup. * Restores default group assignment for users who are re-created after deletion or deactivation. * Improves reliability of onboarding and access management workflows. 3. **Analysis Permission Validation Improvements** Fixed an issue where users with valid scan permissions could receive unauthorized errors when executing analyses. **Behavior** * Improved user-level scan permission validation. * Improved group-level scan permission validation. * Corrected effective permission evaluation during analysis startup. **Outcome** * Prevents false authorization failures. * Improves the reliability of project analysis execution. * Ensures consistent permission enforcement across user and group access models. *** ## CodeScan Release Notes 26.0.11 **Release Date: 24 May 2026** ### Summary CodeScan 26.0.11 is comprised of the following 10 components: * 1 Application Enhancements * 1 New Rule * 8 Fixes Component details are listed in their corresponding sections within this document. ### Application Enhancements **1. Severity Selection for Custom Security Hotspots** Added support for assigning severity levels when creating or editing custom Security Hotspot rules. Previously, severity levels were available for standard Security Hotspot rules, but custom Security Hotspots did not provide a severity selection option. This created inconsistency in rule configuration and made it harder for users to prioritize custom hotspot findings. **Behavior** * Severity selection is now available during custom Security Hotspot rule creation. * Severity can also be configured when editing custom Security Hotspots. * Supported severity values include: * Blocker * Critical * Major * Minor * Info * Custom Security Hotspots now follow the same severity flow as standard rules. * Severity filters on the Rules page correctly return matching custom Security Hotspots. **Outcome** * Provides consistent severity configuration across standard and custom Security Hotspot rules. * Improves risk prioritization for custom security findings. * Enhances filtering accuracy and rule management usability. {% hint style="info" %} NOTE: Severity selection wasn’t available for custom Security Hotspots. To ensure consistency across standard and custom rules, we expanded functionality, and users can now select and assign a severity level during the creation and editing of custom Security Hotspots. {% endhint %} ### New Rules **1. Avoid Plain Text Values in External Credential Parameters** Added a new Salesforce Metadata security rule to detect plain text values in External Credential parameter values. **Rule Details** * Rule key: *sfmeta:ExternalCredentialPlainTextValue* * Type: Vulnerability * Default Severity: Critical * CWE: CWE-798 * Remediation effort: 5 minutes **Behavior** The rule raises a violation when an External Credential metadata file contains a static plain text value in a *parameterValue* field. The rule does not raise a violation when: * parameterValue uses a dynamic merge field reference. * The sibling parameterName is Content-Type. * The file does not contain any parameterValue fields. **Message** *Plain text value detected in parameterValue field. Use a dynamic merge field reference instead to avoid exposing sensitive credentials.* **Outcome** Helps prevent sensitive credentials such as API keys, client IDs, and authentication tokens from being exposed in source control. ### Fixes 1. **Improved Handling for Invalid Base Branches in Comparison and Pull Request Analysis** Fixed an issue where analyses configured with branch comparison or pull request parameters could create invalid comparison branches and display unclear errors when the specified base branch did not exist. **Affected Parameters** Comparison Analysis: * sonar.comparison.base * sonar.comparison.branch Pull Request Analysis: * sonar.pullRequest.branch * sonar.pullRequest.key * sonar.pullRequest.base Previously, when an invalid or nonexisting base branch was provided: * Analysis did not fail immediately. * A 404 error appeared later in analysis logs. * Invalid comparison or PR branches could still appear in the dashboard. * Users received limited visibility into the root cause. **Behavior** * Analysis now validates base branch existence before proceeding. * Comparison and PR branches are no longer created when the base branch is invalid or missing. * Analysis fails gracefully with clear and verbose error messaging in logs. * Failure occurs earlier in the analysis lifecycle whenever possible. **Validation** Validated across multiple integrations and analysis entry points, including: * Sonar Scanner * SFDX Scanner * GitHub Analysis * GitLab Analysis * Salesforce Integration * Bitbucket * GitHub Actions * Copado Integration * Azure DevOps Pipelines * IDE Plugin workflows **Outcome** * Prevents invalid branch artifacts from being created in the dashboard. * Improves troubleshooting with clearer failure visibility. * Provides more reliable branch comparison and pull request analysis behavior across integrations. 2. **Improved Validation for Comparison Branch Analysis Without Main Branch Baseline** Fixed an issue in Salesforce Integration where comparison branch analysis could complete successfully even when the configured main branch had not been analyzed. Previously, users could create and analyze comparison branches without a valid analyzed baseline branch. This resulted in inconsistent behavior where: * The analysis appeared as successfully completed. * Quality Gate and metric calculations could not be computed. * The UI displayed the error: * *metric.level.NOT\_COMPUTED* **Behavior** * Comparison branch creation and analysis validation was improved to ensure a valid analyzed main branch exists before processing. * Users are now prevented from creating comparison branches when the main branch analysis is incomplete or interrupted. * Improved user-facing messaging was added for incomplete analysis states. * Instead of displaying technical metric computation errors, the UI now shows a clearer status message: * *Branch is not yet analyzed* **Validation** Validated through Salesforce Integration workflows using scenarios where: * Main branch analysis was not executed. * Main branch analysis was interrupted. * Comparison branch analysis was interrupted. Confirmed that: * Comparison branch analysis no longer proceeds without a valid baseline. * Invalid comparison states are blocked correctly. * User-facing messages are displayed consistently without metric computation errors. **Outcome** * Prevents inconsistent comparison analysis states. * Improves reliability of branch comparison workflows. * Provides clearer and more user-friendly error handling for missing baseline scenarios. 3. **Support for Special Characters in Salesforce Organization Names** Fixed an issue where project creation could fail when Salesforce Organization Names contained special characters such as registered trademark (®) or trademark (™) symbols. Previously, organizations using special characters in the Salesforce Organization Name could encounter the following error during project creation: *Error attempting to apply attribute converter* This could result in partially created projects with missing associated data such as issues, code, and analysis information. **Behavior** * Special characters in Salesforce Organization Names are now properly supported. * UTF-8 safe handling was added for organization name processing and database conversion logic. * Attribute conversion handling was improved to prevent failures during project creation. * Input validation and sanitization were enhanced while preserving expected functionality. **Validation** Validated using Salesforce organizations containing special characters including: * ® * ™ * Other UTF-8 supported characters Verified successful project creation without attribute converter failures or data inconsistencies. **Outcome** * Prevents project creation failures caused by special characters in organization names. * Eliminates incomplete project records and reduces manual database cleanup. * Improves onboarding reliability and overall customer experience. 4. **Resolved Salesforce Connection Deletion Issue with Special Characters in Connection Names** Fixed an issue where creating a Salesforce connection using special characters in the connection name could trigger attribute converter errors and unexpectedly remove existing Salesforce connections from the application. Previously, when users created a Salesforce connection with characters such as ® in the connection name: * The create request failed with an attribute converter error. * Existing Salesforce connections could disappear from the UI. * The new connection was not created correctly. **Behavior** * Salesforce connection names now properly support special characters and UTF-8 input handling. * Existing Salesforce connections remain unaffected during new connection creation. * Attribute converter handling was improved to prevent unintended data impact. * Validation and persistence behavior were stabilized for connection management workflows. **Validation** Validated by creating Salesforce connections using special characters including: * ® * ™ * Other supported UTF-8 characters Confirmed that: * New connections are created successfully. * Existing Salesforce connections remain intact. * No attribute converter errors occur in API or UI flows. **Outcome** * Prevents accidental removal of existing Salesforce connections. * Improves reliability of Salesforce connection management. * Enhances support for organizations using special characters in naming conventions. 5. **Resolved Duplicate Email Notifications and Organization Deletion Exceptions** Fixed issues related to organization deletion workflows where duplicate email notifications and unexpected exceptions could occur during archive cleanup processing. Previously, under specific conditions involving missing Quality Gate associations: * Organizations could become inaccessible from the UI while still remaining in the database. * Both success and exception notification emails could be triggered for the same deletion event. * Instance Admin users were unable to fully remove affected organizations through the UI or API. * Exceptions could occur during cleanup processing when Quality Gate data was missing. The issue was identified in the Delete Archive Job flow, where: * Exception emails were incorrectly triggered for all organizations instead of only failed deletions. * Missing presence validation for Quality Gate data caused runtime exceptions during processing. **Behavior** * Email notifications are now triggered correctly based on actual deletion outcomes. * Exception notifications are sent only for failed deletion scenarios. * Additional validation checks were added before accessing Quality Gate data. * Organization cleanup handling was improved to prevent inconsistent deletion states. **Validation** Validated organization deletion workflows under scenarios involving missing or invalid Quality Gate associations. Confirmed that: * Organizations are removed cleanly without residual inaccessible records. * Duplicate email notifications no longer occur. * No exceptions are triggered during archive cleanup processing. * Instance Admin deletion workflows behave correctly. **Outcome** * Improves reliability of organization deletion workflows. * Prevents inconsistent organization states between UI and database records. * Reduces unnecessary exception notifications and administrative overhead. 6. **Resolved Stack Overflow Issue in Field Level Security Rule Analysis** Fixed an issue where project analysis could become stuck or fail due to a stack overflow error in the Field Level Security rule during Apex analysis. Previously, specific Apex files containing deeply nested or recursive method call patterns could trigger repeated recursive evaluation within the *FieldLevelSecurityRule*, resulting in: * Stack overflow exceptions during analysis. * Excessively long analysis execution times. * Analysis workflows appearing stuck or unresponsive. **Behavior** * Improved handling of recursive and nested method traversal within the Field Level Security rule. * Added safeguards to prevent stack overflow conditions during rule evaluation. * Analysis now completes successfully for previously failing customer scenarios. **Validation** Validated using customer-reported files and additional large project analysis scenarios. Confirmed that: * Stack overflow errors no longer occur during analysis. * Analysis workflows complete successfully without interruption. * Existing Field Level Security rule detection behavior continues to function correctly. **Outcome** * Improves stability and reliability of Apex security analysis. * Prevents analysis failures caused by recursive execution paths. * Reduces risk of stalled or incomplete project analysis workflows. 7. **Fix for Incorrect "No Scan Access for Project" Error During Analysis Execution** Fixed an issue where analysis jobs were failing to proceed and displaying the error message: **"No scan access for project"**.\ The access validation logic for analysis jobs was updated to correctly verify user scan permissions before initiating the scan process. **Previous Behavior** When users attempted to run an analysis on certain projects, the scan would not progress further and would fail with a **"No scan access for project"** error, even in scenarios where valid access should have been permitted. **Validation** * Verified analysis execution for users with valid scan permissions. * Confirmed that the access validation logic correctly handles project-level scan authorization. * Tested scenarios for both authorized and unauthorized users to ensure expected behavior. * Ensured analysis jobs now proceed successfully when appropriate access is available. **Outcome** Users with valid project scan access can now successfully start and complete analysis jobs without encountering the erroneous **"No scan access for project"** failure. The fix improves reliability and accuracy of permission validation during scan execution. 8. Resolved “No Scan Access for Project” Error During Analysis Execution Fixed an issue where project analysis could fail to start and remain stuck while displaying the error: *No scan access for project* **Previous Behavior** When users attempted to run an analysis on certain projects, the scan would not progress further and would fail with a "No scan access for project" error, even in scenarios with valid access. **Validation** * Verified analysis execution for users with valid scan permissions. * Confirmed that the access validation logic correctly handles project-level scan authorization. * Tested scenarios for both authorized and unauthorized users to ensure expected behavior. * Ensured analysis jobs now proceed successfully when appropriate access is available. **Outcome** Users with valid project scan access can now successfully start and complete analysis jobs without encountering "No scan access for project" error. The fix improves reliability and accuracy of permission validation during scan execution. *** ## CodeScan Release Notes 26.0.10 **Release Date: 17 May 2026** ### Summary CodeScan 26.0.10 is comprised of the following 2 components: * 2 Fixes Component details are listed in their corresponding sections within this document. ### Fixes #### 1. Resolved “No Scan Access for Project” Errors Caused by Expired Salesforce Tokens Fixed an issue where users could encounter a “No scan access for project”/ “expired access/refresh token” error when running scans against Salesforce-connected projects after Salesforce authentication token expiration. The issue affected environments using Salesforce connected app integrations where expired or invalid access/refresh tokens prevented scan authorization and project access validation. **Outcome** * Improved handling of expired Salesforce authentication tokens * Restored scan access reliability for affected projects * Reduced scan interruptions caused by token validation failures * Improved compatibility with Salesforce authentication changes introduced in May 2026 #### 2. Resolved Intermittent Delays in PR-Scoped EZ-Commit Analysis Jobs Fixed an issue where PR-scoped EZ-Commit analysis jobs could intermittently remain in the preparing state for an extended period during the “Compute new coverage” step. In affected scenarios, jobs scanning only a small number of Salesforce metadata files could take significantly longer than expected to complete, eventually resulting in a Start Job Timeout from AutoRABIT ARM™. **Outcome** PR-scoped EZ-Commit analysis jobs now complete the new coverage computation step reliably and within the expected processing time. *** ## CodeScan Release 26.0.9 **Release Date: 10 May 2026** ### Summary CodeScan 26.0.9 is comprised of the following 12 components: * 1 New Feature * NOTE: This New Feature consists of 2 components * 4 Application Enhancements * NOTE: 1 of the Application Enhancements consists of 2 components * 2 Rule Enhancements * 3 Fixes Component details are listed in their corresponding sections within this document. ### New Feature **1. Cross-File Analysis in IDE** **a. Configurable Cross-File Analysis in IDE Extensions** Introduced configurable Cross-File Analysis support in the IDE extension to improve rule accuracy for scenarios where analysis depends on context across multiple files. Previously, the IDE extension performed file-wise analysis only, which could miss issues where logic was split across classes, triggers, or dependent files. **Behavior** When Cross-File Analysis is enabled: * The engine traverses relevant files required by cross-file rules. * Only issues related to the currently opened file are displayed in the IDE. * Issues found in other files during traversal are used for context but not shown in the IDE panel. * Traversal is rule-aware and profile-aware to avoid unnecessary scanning. **Optimization** * If a class file is opened, class files are prioritized first. * If no cross-file rules are active in the Quality Profile, full traversal is skipped. * Cross-file analysis is disabled by default to preserve performance. **Outcome** * More accurate detection for interdependent rules. * Reduced missed violations in IDE analysis. * Focused developer feedback without showing unrelated issues. **b. Cross-File Analysis Controls in UI** Added UI controls to enable or disable Cross-File Analysis from project-level settings. **Project-Level Control** Users can enable Cross-File Analysis for individual projects through: Project Settings → General Settings → CodeScan → CodeScan Lang → Cross-file Analysis Control **Outcome** * Project teams can enable the feature only where needed. * Improves usability and configurability of Cross-File Analysis. ### Application Enhancements **1. Issue Exceptions Enhancements** **a. Manual Expiry Date for Exception Issues** Enhanced Exception issue handling by allowing users to manually set an expiry date when marking issue an Exception. **Behavior** Users can: * Select any future expiry date. * Leave expiry unselected, resulting in No Expiry. * Override admin-configured default expiry duration. **System Behavior** * When the selected expiry date is reached, the issue transitions from Exception → Open. * Issues with No Expiry remain in Exception status. * Admin expiry setting changes do not affect issues with manually selected expiry dates. **Validation** Validated across UI, API, functional behavior, admin configuration interaction, auto-transition behavior, and bulk issue transitions. **Outcome** Improves flexibility and aligns Exception handling with existing hotspot expiry workflows. **b. Auto-Assign Expiry Dates for Issue Exceptions** Enhanced Exception issue handling by allowing Admins to configure automatic expiry dates based on issue severity. **Admin Configuration** Instance Admins can enable or disable auto-expiry and configure default expiry duration by severities: * Blocker * Critical * Major * Minor * Info **Behavior** When enabled: * Expiry date is calculated as current date plus configured severity duration. * Expiry is assigned automatically when an issue is moved to Exception. * Auto-assigned expiry is not editable at project or user level. * Existing issues are not affected by later admin configuration changes. **Validation** Validated through UI, API, workflow transitions, invalid input handling, permissions, bulk assignment, time zone behavior, and regression testing. **Outcome** Standardizes SLA handling for exceptions and reduces manual administrative effort. **2. Showing Invited Users in Members List with pending status** We have enhanced user management by showing invited users in the Members list immediately after an invitation is sent:
Previously, invited users did not appear in the Members tab until they accepted the invitation, making it difficult for admins to track pending invites. **Behavior** * Invited users appear under Pending Invitations. * Status is shown as Invited. * Once accepted, status changes from Invited → Active Member. * Empty state displays:\ “No pending invitations. Invite new members to collaborate.” **Validation** Validated at organization level, including multiple invites, invite cleanup after 7 days, DB record creation, UI consistency, and status transition. **Outcome** Improves administrator visibility, reduces duplicate invite confusion, and provides clearer user management. **3. Improved Error Messaging in Invite Module for Existing Users** Enhanced flow where inviting a user who already exists in the organization displayed a generic error message: *“An unknown error occurred”* **Behavior** The UI now displays the actual backend validation message, such as: *“This email already exists in the organization”* **Outcome** Provides clearer feedback and reduces confusion during user invitations. **4. Add Default Salesforce Metadata file suffixes to CodeScan for customers running DX projects** **Description** Previously, we only had default settings for files and projects using the metadata type. This enhancement ensures that CodeScan defaults now cover all types in both metadata and source format. **The new defaults are now:** settings object profile flow workflow permissionset profileSessionSetting sharingRules profilePasswordPolicy settings-meta.xml object-meta.xml field-meta.xml profile-meta.xml flow-meta.xml workflow-meta.xml permissionset-meta.xml profileSessionSetting-meta.xml sharingRules-meta.xml profilePasswordPolicy-meta.xml
### Rule Enhancements **1. Added CVSS Scoring for Security Rules** Enhanced selected security rules by adding standardized CVSS scoring. **Rules Updated:** * Avoid Using Unfiled Public Folders * GitLeaks Secret Detection in Apex Files * GitLeaks Secret Detection in Salesforce Metadata Files * GitLeaks Secret Detection in Visualforce & Lightning Files * Identify Potential Sensitive PII Fields * Resource Injection * Server Side Request Forgery * Validate Flow Run Context Mode **CVSS Details Added** * Base Score * Temporal Score * Environmental Score * Severity Rating * Vector String, where applicable **Validation** Validated in rule details view and CVSS filters. No impact was observed on rule execution or detection logic. **Outcome** Improves severity visibility and helps users prioritize remediation more effectively. **2. Enhanced AvoidDMLInLoops Rule with Interprocedural Analysis** Rule key: sf:AvoidSoqlInLoops Enhanced the Avoid DML/SOQL Inside Loops rule to detect violations across method calls, files, and nested execution paths. Previously, some violations were missed when DML or SOQL was executed indirectly through methods called inside loops. **Scenarios Now Supported** * Recursive call paths * Deep and nested method chains * Cross-class traces * Cross-file scenarios * While-loop scenarios * Transitive call chains such as A → B → C → SOQL/DML **Outcome** Improves rule accuracy and helps detect governor-limit risks that were previously missed. ### Fixes **1. Resolved Tag Filter Issue on CodeScan Rules Page** Fixed an issue where searching for a custom tag on the Rules page returned no results and showed a count of 0 unless additional filters were applied. **Resolution** Corrected tag filtering behavior, so matching rules appear immediately when searching by tag. **Outcome** * Accurate tag counts. * Correct rule results. * No need for extra filtering steps. **2. UI Now Displays Actual Duplicate Project Key Message During Project Creation instead of Generic “Unknown Error” Message** **Description** While creating a project, if the entered project key already exists, the UI displays a generic error message: “An unknown error occurred”. However, the actual API response in the Network tab contains a meaningful validation message stating: *“Could not create Project with key: ‘gitleaks’. A similar key already exists: ‘gitleaks’”*. As such, we have enhanced the UI to now display the backend validation message instead of the generic error so users can clearly understand the reason for the failure.
**3. Resolved Blank Edit Project Settings Page for S3 Integration Projects** Fixed an issue where the Edit Project Settings page appeared blank for S3 integration projects, and console errors were shown. **Outcome** Users can now open and update settings for S3-based projects, including memory allocation, without errors. *** ## CodeScan Release 26.0.8 **Release date: 26 April 2026** ### Summary CodeScan 26.0.8 is comprised of the following 6 components: * 2 Application Enhancements * 4 Fixes * 4 New GitLeaks specific rules introduced Component details are listed in their corresponding sections within this release document. ### Application Enhancements 1. **Updated Bitbucket Integration to Use Workspace-Scoped Repository APIs** Bitbucket integration was updated to replace deprecated repository APIs with workspace-scoped APIs. Now CodeScan fetches repositories by: 1. Retrieving user workspaces 2. Fetching repositories per workspace 3. Aggregating results **Outcomes:** * Continued compatibility with Bitbucket API changes * Failures due to deprecated endpoints prevented * Improved reliability of repository fetching **Validation:** Verified the Bitbucket project analysis. Users are able to see the repos as expected, and the Project analysis and PR analysis are working as expected. 2. **Enhanced Parsering for Methods Named “void”** Earlier, CodeScan parser wouldn’t process Apex methods named **void**. **This enhancement:** * Ensures accurate parsing of valid Apex code * Improves analysis reliability The parser enhancement to support Apex methods named void has been thoroughly validated by QA across multiple scenarios on Preview instance. **Positive Validation Scenarios:** The following valid Apex patterns were tested and are now parsed correctly: * Basic Cases * public void void() {} Method with body statements * Access Modifiers * private void void() {} * protected void void() {} * global void void() {} * Modifiers & Combinations * public static void void() {} * public final static void void() {} * Parameterized Methods * public void void(String name, Integer count) {} * Annotations @AuraEnabled public static void void() {} * Exception Handling Method containing throw statements * Constructor + Method Coexistence Class containing both constructor and method named void * Multiple Methods Classes with multiple methods including one named void * Method Overloading Multiple overloaded methods named void with different parameters * Nested Structures Method inside inner classes * Test Classes @IsTest classes with method named void * Interface & Implementation Context Class implementing interface along with method named void * Formatting Variations Extra spacing in declaration Multiline method signatures Inline and line comments within method declaration **Negative Validation (Expected to Fail – Parser Strictness Maintained)** The following invalid syntaxes were tested and correctly rejected: * Missing method name * public void () {} → Parse error * Duplicate return type * public void void void() {} → Parse error * Missing parentheses * public void void {} → Parse error * Invalid keyword as method name * public void class() {} → Parse error These failures are expected and confirm that parser strictness is preserved. **Conclusion** * Parser now correctly supports void as a valid method name in Apex. * All valid usage patterns are successfully parsed across different contexts. * Invalid syntax continues to be rejected as expected. * No regressions observed in parsing behavior. ### Fixes 1. **Improved Validation for Salesforce User Permissions During ECA Authentication** Fixed an issue where users with insufficient Salesforce permissions could authenticate Salesforce successfully but encountered failures later during analysis. **Resolution:** * Permissions are now validated immediately after authentication * Users without required permissions are blocked early with a clear error message 2. **Resolved 403 Error When Activating Rules in US Instance** Fixed an issue where rule activation failed with a 403 Forbidden error in the US instance. **Result:** Rule activation now works consistently across environments 3. **Resolved “Component cannot be null” Error in Cross Object Formula Overuse Rule** Fixed a runtime error occurring during PR and subset analyses when related metadata files were not included in the scan. **Result:** * Improved stability of rule execution * Graceful handling of missing metadata QA verified the fix in the Preview environment: * Re-ran the same reproduction steps after the fix deployment * Confirmed that the analysis completes successfully without any errors * Overuse Rule now handles the scenario correctly when the parent .object-meta.xml is not part of analyzed sources 4. **Resolved False Positives in Field Level Security Rule for USER\_MODE Queries** Fixed an issue where queries executed in USER\_MODE were incorrectly flagged. **Result:** * Eliminates false positives * Aligns rule behavior with Salesforce FLS enforcement The fix for handling AccessLevel.USER\_MODE has been validated across multiple scenarios on the preview Instance. The following cases were tested and are no longer flagged, as expected: * Direct usage of AccessLevel.USER\_MODE * USER\_MODE via variable assignment * USER\_MODE passed through method parameters * USER\_MODE returned from methods * USER\_MODE used in ternary expressions * Formatting variations of USER\_MODE usage This confirms that the rule now correctly recognizes USER\_MODE across different usage patterns and does not raise false positives when FLS is enforced by Salesforce. #### New GitLeaks Rules in CodeScan CodeScan has implanted new logic within the Rules Engine that can detect GitLeaks vulnerabilities. GitLeaks is a tool for detecting secrets like passwords, API keys, and tokens. We have extended this logic to cover Salesforce specific languages and components. The following rules are introduced: 1. **Rule Name:** GitLeaks Secret Detection in Apex Files\ **Rule ID:** sf:ApexGitLeaksSecrets\ This rule runs GitLeaks on Apex source files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. 2. **Rule Name:** GitLeaks Secret Detection in Salesforce Metadata Files\ **Rule ID:** sfmeta:MetadataGitLeaksSecrets\ **Description:** GitLeaks Secret Detection in Salesforce Metadata Files: This rule runs GitLeaks on Salesforce Metadata files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. 3. **Rule Name:** GitLeaks Secret Detection in Visualforce & Lightning Files\ **Rule ID:** vf:VFLightningGitLeaksSecrets\ **Description:** This rule runs GitLeaks on Visualforce source files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. 4. **Rule Name:** GitLeaks Secret Detection in Javascript\ **Rule ID:** cs-js:javascript-gitLeaks-secrets\ **Description:** This rule runs GitLeaks on Javascript files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. **Summary**\ These rules run GitLeaks on Salesforce source files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. **Availability:**\ This feature is currently available on **AUS and EU instances**.\ *** ## CodeScan Release 26.0.7 **Release Date: 12 April 2026** ### Summary CodeScan 26.0.7 is comprised of the following 8 components: * 3 New Features * 1 Application Enhancement * 4 Fixes Component details are listed in their corresponding sections within this document. ### New Features **1. GitHub Apps Integration for GitHub Enterprise in CodeScan** **Description** Users of GitHub Enterprise can now connect their GitHub Enterprise organization to CodeScan using a GitHub App. This allows CodeScan to securely access repositories, receive webhook events, and perform code analysis without relying on personal access tokens or user-owned credentials. **Benefit** Because CodeScan can now integrate with GitHub Enterprise via a GitHub App, authentication is now more secure, scalable, and enterprise compliant. This reduces credential management issues while enabling reliable multi-repo and multi-org analysis. **Value / Purpose** * Enables enterprise-grade authentication aligned with GitHub’s recommended model. * Supports secure, scalable access across multiple organizations and repositories. * Improves compliance, auditability, and long-term maintainability of CodeScan’s GitHub integrations. We have validated the GitHub Enterprise flow in CodeScan for the following scenarios and verify that all are working as expected: * Main branch analysis * Pull Request analysis * Merge request analysis * Run manual analysis * Re-run analysis * Schedule jobs analysis * Delete analysis * Rename analysis For creating a GitHub App for an Enterprise account, users need to follow the steps outlined in the documentation [CodeScan GitHub Apps Integration (Technical Approach)](https://app.gitbook.com/o/vIHQCTOOUDcNoPic3AQi/s/9vAxMuDrkUkB4OXlH9CL/product-guides/codescan/codescan-integration/codescan-github-apps-integration-for-github-enterprise). Once completed, users need to create an ALM connection in the CodeScan application by providing the following details: * App ID * Client ID * Client Secret After successfully creating the connection with the GitHub Enterprise account, users will be able to run the analysis.
Please note these important TECHNICAL details: 1\. GitHub Apps Authentication Flow Change: After implementing the GitHub Apps feature, the flow of authorization has changed for the user. For the first-time user, they will be navigated to the GitHub apps installation page, where they need to Authorize and Install the app. Then, the user will be navigated to the CodeScan GitHub Integration pop-up to run the analysis. 2\. GitHub Apps - Token Refresh: How it works: * Before API calls, check if token expired * If expired, automatically refresh (generate new JWT → get new token) * NOTE: We have updated all API call methods to support both OAuth and GitHub Apps, and verified that OAuth continues to work (it is backward compatible). * Additionally, analysis execution was verified after 8 hours, confirming that the token refresh mechanism (every 8 hours) is functioning as designed. **2. Added a new {Resolution} Status for Issues – “Exception”** **Description** We have introduced a new **Exception** status in the issue lifecycle that allows users to mark an issue as an approved exception when the organization decides not to remediate it due to valid business or technical reasons. When an issue is moved to the **Exception** status, CodeScan captures and stores the justification for auditing and tracking purposes. The status appears alongside existing issue statuses and is visible in issue details, filters, and reports. NOTE: The following description has been added to the Exception status: “The issue has an approved exception and will be re-reviewed until mitigated or upon exception expiry.“ **Benefit**\ Users are provided with a dedicated **Exception** status, allowing them to clearly differentiate between resolved issues and intentionally accepted risks. This improves issue tracking, compliance transparency, and auditability. **Value / Purpose** * Enables teams to formally document and track approved risk exceptions. * Improves visibility and governance over issues that are intentionally not fixed. Validated this new feature via the following scenarios and have verified that all scenarios are working as expected. 1. Exception status is available in the status list in issues page.
2. Issues status changed to Exception (through single assign and bulk assign).
3. Issues status changed from Exception to Open (Rollback) (through single assign and bulk assign).
4. Able to view the Exception status in CSV Issues export (in list and downloaded CSV).
5. Status visible in a single rule.
6. Comments in Activity.
Comments in the activity section for Exception are able to deleted by the user (after these issues are moved into exception).
Also, user already assigned to issues will remain assigned, even when moved to exception (if issue assigned before moving or while moving the issues to exception). **3. New Email Notifications alert admins when (Pre & Post) Project Analysis Errors occur** **Description** Currently, users receive email notifications primarily for Quality Gate results, but failures occurring during the **project analysis lifecycle** are not communicated. This enhancement aims to include **pre-analysis and post-analysis errors** via email subscriptions, so users can be proactively informed when analysis fails. The scope includes: * **Pre-Analysis Errors** * Queue setup failures * Branch does not exist * Salesforce authentication issues * Authorization token (Auth token) failures * **Post-Analysis Errors** * Compute Engine (CE) job timeout * Cleanup job delays or long-running failures When such errors occur, an email notification is triggered (based on user subscription preferences), providing high-level error details and guidance for resolution. **Benefit** Users are notified about analysis failures (both pre and post stages) via email, enabling them to quickly identify and resolve issues, reducing failed analysis cycles, improving system trust, and decreasing support dependency. **Value / Purpose** * Improves visibility into analysis failures beyond Quality Gate results * Reduces turnaround time for issue resolution Validated that users are able to receive the email notifications for pre/post analysis errors, and verified that these users are able to receive notifications as expected. Several examples have been provided below for illustrative purposes.
Please note these important TECHNICAL details: 1\. We have included the ability for users to Enable / Disable Subscription for Analysis Failure Notifications so that users can manage whether they need to receive failure alerts based on chosen preferences. The system will leverage the **existing subscription-specific UI,** i.e., ***Profile> My Account>Notifications> Overall Notifications,*** to allow users to opt in or opt out of analysis failure notifications.
User preferences will be persisted using APIs, and any changes will be applied immediately when resolving notification recipients for analysis failures. **Benefit** End users can independently manage their own subscriptions for analysis failure notifications,\ then notifications will be **more relevant at an individual level**, reducing alert fatigue while ensuring the right users stay informed. **Value / Purpose** * Empowers **all end users** to manage their own notification preferences. * Reduces **unwanted or noisy alerts** from intermittent analysis failures. **Acceptance Criteria** * The **“Project analysis execution failures”** checkbox is available under **Overall Notifications** for all users. * Users can **enable or disable** the checkbox to manage their personal subscription. * The checkbox state **reflects the user’s current saved preference** on page load. * Any change to the checkbox is **persisted immediatel**y via the notification subscription APIs. * Subscription changes take effect **without page refresh**. * Only users with the checkbox **enabled receive email notifications** when a project analysis execution failure occurs. * Users with the checkbox **disabled do not receive** analysis execution failure notifications. * Changes to the subscription are **applied immediately** during notification recipient resolution. * Users subscribed to get the notification should receive emails for only the projects to which they have access. Users should not get mail notification for projects they are not part of. The ticket “Enable / Disable Subscription for Analysis Failure Notifications” has been verified successfully. * The user is able to view the option “Project analysis execution failure on my administered projects.” * A checkbox is available alongside this option. * The user can enable and disable the checkbox as expected without any issues. Functionality is working as expected.
2\. Triggered Email Notifications are immediately sent to Subscribed Users on Analysis Failure, so they can be promptly informed and subsequently take action without waiting for manual checks or follow-up runs. When an intermittent project analysis failure is detected, the system will **trigger notifications in real time**, resolve recipients using the **Notification Subscribers module**, and send **email notifications containing relevant project context and failure details**. **Benefit** Subscribed users are notified immediately when intermittent analysis failures occur; teams can quickly **identify and address failures faster**, reducing downtime, re-runs, and uncertainty around analysis results. **Value / Purpose** * Provides **timely visibility** into intermittent analysis failures * Ensures notifications are sent **only to subscribed users** * Enables **faster troubleshooting and recovery** ### Application Enhancements **1. Track Cursor IDE Usage in the VS Code Extension** **Description** In our previous release (CodeScan 26.0.6), we delivered a new CodeScan feature that captures the Cursor IDE usage details (User Name, IDE Type = Cursor, Timestamp) within CodeScan Cloud. This allows customers to track IDE adoption, user activity, and engagement trends alongside existing usage data. (You can find more details under “Track Cursor IDE Usage on CodeScan 'IDE USAGE' Page” within those release notes as well as our Knowledge Base.) In this release, we have enhanced this capability within the IDE plug-in, which allows us to more precisely determine whether the user is currently on Cursor or VS Code. We then send this value to CodeScan Cloud. 1. Verified the Cursor plugin using the provided VSIX file across multiple file types: .cls, .page, .java, .js, .trigger, .css, .ts, and .cmp. Violations are displayed as expected. 2. Also verified the IDE Usage page, where Cursor usage is correctly reflected. We have tested and validated with multiple users and verified cross-user usage visibility is working as expected on the IDE Usage page. 3. Additionally, verified the VS Code plugin using the same VSIX file. Violations are displayed correctly for all supported file types, e.g., .cls, .page, .java, .js, .trigger, .css, .ts, .cmp, in the PREVIEW environment. 4. Confirmed that VS Code usage is accurately shown on the IDE Usage page and validated that cross-user usage visibility is also functioning as expected.
### Fixes **1. Fixed issue with rule “Unescaped Error Message XSS” {Rule ID: sf:UnescapedOutput}** **Summary** Several customers were reporting a StackOverflowError for the rule “Unescaped Error Message XSS” {Rule ID: sf:UnescapedOutput} Earlier, the Unescaped Output Rule was able to trace data flow through methods but not through assignment chains effectively. Due to missing/inefficient assignment data flow handling, the rule repeatedly re-entered isSanitized while resolving sanitization status for variables passed through assignments. This resulted in deep recursive calls and ultimately a StackOverflowError, instead of reporting a violation. **Reproduction Analysis:**\ Initial attempts with small assignment chains did not reproduce the issue. The issue was successfully reproduced only with very deep assignment chains (\~5,000 assignments). This indicates that: * The problem is related to **depth of assignment traversal** * Recursive evaluation of isSanitized leads to stack overflow at large depths **Validation** ✔ Rule evaluation now terminates correctly without recursion overflow\ → Verified. No StackOverflowError observed even for deep assignment chains. ✔ isSanitized now handles edge cases without re-entering indefinitely\ → Verified. Deep assignment chains no longer cause recursive overflow. As such, we confirm that the issue has been successfully remediated. The rule now handles deep assignment chains correctly and avoids infinite recursion in isSanitized, without causing a StackOverflowError.
**2. Fixed issue with rule “Avoid Cleartext Transmission of Sensitive Information”** {Rule ID: sf:InsecureEndpoint} **Summary** Previously, the rule InsecureEndpointRule was throwing a ClassCastException due to an invalid cast from ClassNameDeclaration to VariableNameDeclaration when analyzing endpoint expressions involving enum/class references (e.g., MODE.ERASE). **After the fix:** * Proper type checking has been implemented before casting symbol table declarations. * The rule now safely handles enum and class references without making incorrect assumptions. * No runtime exceptions are observed during analysis. **Result:** * No ClassCastException observed. * Rule executes as expected across all tested scenarios. **3. Fixed issue with rule “Field Level Security Vulnerabilities” {Rule ID: sf:FieldLevelSecurity}** **Summary** Previously, the rule FieldLevelSecurityRule was throwing a NullPointerException when analyzing DML operations (Database.update) inside a trigger body due to the absence of an enclosing ASTMethodDeclaration. The failure was a NullPointerException caused by attempting to invoke findChildNodesWithXPath on a null methodDeclaration object within FieldLevelSecurityRule. **After the fix:** * Proper null handling for methodDeclaration has been implemented. * The rule no longer assumes the presence of a method context. * Trigger-based DML scenarios are now handled gracefully without runtime exceptions. **Result**: * No NullPointerException observed. * Rule behaves as expected. **4. Fixed issue with rule “Resource Injection”** {Rule ID: sf:ResourceInjection} **Description** Several customers were reporting a StackOverflowError for the rule “Resource Injection” {Rule ID: sf:ResourceInjection}. Based on the analysis of logs and review of implementation, we uncovered an infinite recursive call in the isSanitized method in the UrlSanitization.java and determined that this is the reason for the StackOverflowError. Previously, the analysis stayed in Running state and logs showed a StackOverflowError for the mutual-recursion flow (methodA -> methodB -> methodA) with no exit condition, ending in req.setEndpoint(url) with the Rule Resource Injection. After the fix, the same code analyzes successfully, completes normally, and no StackOverflowError is observed in logs. **Validation after fix:** * Ran analysis on CodeScan * Analysis completed successfully * Analysis no longer remained in Running state * StackOverflowError was no longer seen in logs As such, we are reporting that this issue has been fully remediated. *** ## CodeScan Release 26.0.6 **Release Date: 29 March 2026** ### Summary CodeScan 26.0.6 is comprised of the following 5 components: * 1 New Feature * 4 Application Enhancements * 1 Fix Component details are listed in their corresponding sections within this document. ### New Features **1. CodeScan Audit Logs API** **Description** Currently, the Audit Logging API is available only for internal use by AutoRABIT. This new feature enables our customers to access audit logs via a secure, user-facing API (which is restricted to organization-level administrators with *Administer System* permissions. The API will allow these authorized org admins to view system and user activity events related to their organization, ensuring appropriate access controls and data isolation. **Hypothesis** If organization administrators are given access to audit logs for their organization, they will be better equipped to monitor platform usage, investigate issues, and meet internal governance or compliance requirements, reducing reliance on CodeScan support for routine operational visibility. **Value / Purpose** * Provides greater transparency and trust for enterprise and security-conscious customers. * Empowers org admins to self-serve audit and usage insights without support intervention. * Supports compliance, security reviews, and internal audits.
**Audit log API** For more details, refer to the [CodeScan API Documentation.](/product-guides/codescan/codescan-api-documentation) ### Application Enhancements **1. Configurable Default User Role for SSO-Provisioned Users** **Description** Currently, users created via SSO are **always provisioned as CodeScan Standard Users**. This creates manual overhead for admins who need certain users to be assigned **Platform User** roles after login. This new feature allows organization admins to configure the default CodeScan user role (Standard User or Platform User) for users provisioned via SSO, including UI updates in SSO setup, back-end role assignment logic, data model impacts, security considerations, and backward compatibility with existing SSO configurations. **How It Works** User type selection directly in the SSO/SAML configuration page to select either Platform Integration Users or Standard users.
The following scenarios have been verified and are working as expected: * **SAML Connection Creation (New Org)** * Created a SAML connection on a new organization. * Verified login with a user. * Result: User was able to log in successfully. * **Platform User Login Validation** * Updated the user type to **Platform User**. * Logged in using a newly created user. * Result: Login was successful, and the user could access **only the My Account page**, as expected for Platform users. * **Standard User Login Validation** * Updated the user type to **Standard User.** * Logged in using the new user. * Result: Login was successful as a **Standard User**. Further, we verified the behavior for the previous user also, and it is working as expected via SAML authentication. **2. Track Cursor IDE Usage on CodeScan 'IDE USAGE' Page** **Description** This CodeScan feature captures the Cursor IDE usage details (User Name, IDE Type = Cursor, Timestamp) within CodeScan Cloud, allowing customers to track IDE adoption, user activity, and engagement trends alongside existing usage data. Additional details regarding the Cursor IDE usage data: * Stored consistently with existing IDE usage records * Viewable using existing filters: * Individual user * All users * Last X days * Can be exported as CSV for reporting and analysis Verified the Cursor IDE Usage on CodeScan in the page 'IDE USAGE' of the Adminstration and confirmed users are able to see the added Cursor symbol through the API call in the UI of the application. We also verified that existing behavior for VS Code and Intellij is working as expected.
**3. Updated Filter Message for Security Hotspot CSV Export** **Description** When exporting Security Hotspots, if the user chooses a list of filters that do not match any security hotspots, the current message displayed was: **"Security Hotspots not found."** We have updated the message to provide greater clarity: **"No Security Hotspots have been found with the current filters."** Verified the updated Security Hotspot export filter message. * The message displayed is **“No Security Hotspots have been found with the current filters,”** instead of **“Security hotspot is not found.”** * Validated exporting Security Hotspots by changing the status to **Acknowledged, Exception, Fixed, and Safe** — the exported count matches the respective status correctly. * Validated exporting Security Hotspots with status **To Review** — the export shows the exact count of items currently in the **To Review** state. All the above scenarios are working as expected.
**4. Automatically generate Callback URL when adding ECA in Salesforce Org** **Description** Currently, while adding an ECA in Salesforce Org, the application does not provide a dynamically generated Callback URL for External Client App (ECA) configuration. * Users are required to manually construct and enter the Callback URL in Salesforce during ECA setup. The system does not display the exact instance-specific Callback URL within the application, nor does it provide a copy-to-clipboard option. * Users will assume the Call back URL as https\://**{{hostname}}**.codescan.io, but the actual Callback URL that needs to be given while creating the ECA could be different. This manual process increases the risk of: * Typographical errors * Missing or incomplete URL entries * Configuration failures due to incorrect Callback URL * Increased onboarding/support effort **As such, we decided to enhance this feature by:** * Automatically generating the Callback URL. * Dynamically constructing it based on the selected/connected instance/environment (e.g., test, preview). * Ensure correct and consistent formatting. * Clearly display the generated Callback URL on the “Add Salesforce Org” screen. * Make it visible at the point of ECA configuration. * Provide a **“Copy”** button next to the generated URL. * Allow one-click copying of the exact URL. * Prevent manual typing errors. Steps Taken Implemented Callback URL button in the UI. Added a custom tooltip, copy icon and copied label when user copies the URL We have verified that **Callback URL** is displayed correctly, and the **Copy** button is working as expected.
{% hint style="info" %} **NOTE:** When hovering over the Callback URL button, the notes are displayed. The notes do not disappear when clicking on the Callback URL. They only disappear when clicking anywhere else on the page. This is the expected behavior. {% endhint %} ### Fixes **Custom Rule creation validation update:** 1. Resolved an inconsistency between custom rule creation and update workflows. Previously, the update flow enforced stricter validation on the description field, restricting certain formats (e.g., descriptions containing HTTP/HTTPS protocols). \ With this fix, the additional validation has been removed from the update flow. Users can now update rule descriptions with any valid content, including URLs or HTTP/HTTPS references, ensuring consistency with the rule creation behavior. *** ## CodeScan Release 26.0.5 **Release Date: 15 March 2026** ### Summary CodeScan 26.0.5 is comprised of the following 8 components: * 4 Application Enhancements * 1 New Rule * 2 Rule Enhancements * 1 Fix Component details are listed in their corresponding sections within this document. ### Application Enhancements **1. CSV ISSUE EXPORT – Added Issue Status User** **Description** Enhanced the Issues CSV export to include a separate column called “**Status Marked By**” that shows the user name of the person who marked the current status of an issue, so that audit/user can clearly understand who last set or changed the issue’s status when reviewing exported data. **Hypothesis** If the CSV export includes the “Status Marked By” column with the corresponding username (or left empty when no status exists), then users will have better traceability and accountability when analyzing issues outside the platform, reducing ambiguity about ownership and status changes.
**Value / Purpose** * Improves transparency and auditability of issue status changes in exported reports. * Enables teams and managers to identify responsibility and follow up more effectively. Verified the following scenarios and confirmed that all are working as expected. * Verified with multiple users, users getting updated as expected. * Verified with root user - status marked by updated as administrator. * Verified by removing org user, name is still shown in CSV - working as expected. * Verified with deactivated user, name is still shown in CSV - working as expected. * Verified with deleted user, the status marked by field is empty. **2. CSV HOTSPOT EXPORT – Added Hotspot Status User** **Description** Enhanced the Security Hotspot CSV export to include a separate column called “**Status Marked By**” that shows the user name of the person who marked the current status of an hotspot, so that audit/user can clearly understand who last set or changed the hotspot’s status when reviewing exported data. **Hypothesis** If the Hotspot CSV export includes the “Status Marked By” column with the corresponding username (or left empty when no status exists), then users will have better traceability and accountability when analyzing hotspots outside the platform, reducing ambiguity about ownership and status changes.
**Value / Purpose** * Improves transparency and auditability of hotspot status changes in exported reports. * Enables teams and managers to identify responsibility and follow up more effectively. Verified the following scenarios are all working as expected. * Verified with multiple users, users getting updated as expected. * Verified with root user - status marked by updated as administrator. * Verified by removing org user, name is still shown in CSV - working as expected. * Verified with deactivated user, name is still shown in CSV - working as expected. * Verified with deleted user, the status marked by field is empty. * Issues: * Also, verified that if user clicked on export after selecting the project and branch - only those security hotspots that are available for review are getting download (not the reviewed ones) * Also, if the user selects only certain reviewed options, all the reviewed getting downloaded. **3. Enhanced CSV Export with Detailed Security Hotspot Statuses** **Description** Enhanced the CSV export for Security Hotspots to include the full set of hotspot statuses—**TO\_REVIEW, SAFE, FIXED, EXCEPTION, ACKNOWLEDGED**—so that the exported data accurately reflects the current review and remediation state instead of the simplified **To\_Review** and **Reviewed** statuses. **Hypothesis** If the CSV Security Hotspots export includes granular and accurate hotspot statuses, users will be able to perform better reporting, auditing, and compliance tracking without relying on the UI or manual interpretation. **Value / Purpose** * Provides **accurate and actionable data** in exports for security reviews and audits. * Enables **better integration** with external reporting, GRC, and compliance tools. Validated the CSV Security Hotspot Export with Detailed Statuses; below is the validation summary of the Exports: * Verified CSV includes each of the listed statuses when present in results. * Verified status values are exported accurately. * Verified export remains consistent with UI status for the same hotspot set. * Confirmed export works for mixed-status datasets and filters/sorting do not alter status values.
**4. Added Closed Issue Statuses to CSV Reports** **Description** Currently, CSV reports do not clearly distinguish closed issue statuses, such as **Closed** and **Removed**. As such, we have enhanced the CSV export functionality to include these closed statuses explicitly in the Status column. The exported CSV now accurately reflects the latest lifecycle state of each issue, including closed states, ensuring consistency with what users see in the UI. **Hypothesis:** If CSV reports include detailed closed statuses (Closed, Removed ), users will gain better visibility into issue resolution outcomes, enabling more accurate reporting, compliance tracking, and stakeholder communication. This will reduce manual effort in categorizing closed issues after export. **Value / Purpose:** * Improves reporting accuracy and transparency. * Supports audit and compliance requirements with clear issue disposition tracking. The enhancement for including closed issue statuses in CSV reports has been validated successfully 1. **Status: FIXED** * When an issue status is manually changed to **FIXED** in the Issues view, the exported CSV report correctly displays the status as **FIXED** in the **Status** column. 2. **Status: CLOSED** * When the source code is modified to resolve the issue and a **new analysis is executed**, the issue is automatically transitioned to **CLOSED**. * The exported CSV report correctly reflects the status as **CLOSED**. 3. **Status: REMOVED** * When the **Quality Profile is modified** such that the rule generating the issue is removed or disabled, and a new **analysis is executed**, the issue status changes to **REMOVED**. * The exported CSV report correctly displays **REMOVED** in the **Status** column. Concluding that the CSV export now accurately reflects the issues, including closed statuses (**FIXED, CLOSED, REMOVED**), ensuring consistency with the UI.
### New Rule **1. New Rule: “Locale Formats in API Versions pre-v45.0” {Rule ID: sf:LocaleInOldApi}** **Description** This rule finds locale methods in Apex classes with API versions below v45.0. Locale formats before Salesforce API v45.0 default to JDK format. Now, locale formats default to ICU. It is recommended to update all components using API versions prior to v45.0 or use locale-neutral methods. Failure to upgrade to API v45.0 or above could result in date and time formatting issues, affecting user experience and functionality. * **Issue Type**: Bug * **Severity**: Major * **Message**: Avoid Using JDK Locale Formats * **Tags**: retired * **Remediation**: 30 minutes Please also refer to the following documentation on Salesforce Help: [JDK Locale Format Retirement and the Enable ICU Locale Formats Salesforce Release Update](https://help.salesforce.com/s/articleView?id=000380618\&type=1) – [Use Locale-Neutral Methods in Code](https://help.salesforce.com/s/articleView?id=xcloud.admin_locales_code_methods.htm\&type=5) The rule sf:LocaleInOldApi was validated for the following methods: * Date.format * Datetime.format * Date.parse * Datetime.parse * Date.toStartOfWeek 1. **Positive Validation (API Version < 45.0)** * Created Apex classes with API version 44.0 and used the above locale-dependent methods. * These cases are expected to be flagged since API versions prior to v45.0 rely on JDK locale formatting. 2. **Negative Validation (API Version ≥ 45.0)** * Created Apex classes with API version 45.0 and above using the same methods. * These cases are not expected to be flagged, since API v45.0+ uses ICU locale formatting by default. 3. **Verification Outcome** * The rule behavior was validated against the defined conditions. * Classes with API versions prior to v45.0 and using locale-dependent methods are considered for detection, while classes with API v45.0+ are treated as compliant.
### Rule Enhancements 1\. Enhanced data flow analysis logic in rule “Avoid Untrusted/Unescaped Variables in DML Query” {Rule ID: sf:SOQLInjection} **Description** **Scenario 1: Sanitized parameter still flagged** * When a variable comes from a method parameter, the rule sometimes reports SOQL Injection **even if the variable is sanitized or overwritten later**. * This happens because the rule uses **DataFlowNode**, which tracks where the variable originally came from. **Scenario 2: “At least once” assignment not detected** * DataFlowNode can detect whether an assignment is inside a condition. * However, in some cases assignments happen **inside loops**, where the variable is still assigned at least once. * DataFlowNode wasn’t originally designed to reliably confirm this loop behavior. * Because of this limitation, these cases could not be properly handled and would likely result in producing false positives. We remediated these issues with this fix, greatly improving the value of the data flow logic in tracing the vulnerability from sink to source. Verified the following scenarios and confirmed that the are all working as expected. * Verified error duplications are thrown - resolved (earlier) * Verified whether a parameter is sanitized using escapeSingleQuotes but still flagged or not - after sanitized, no issue was thrown.
* Verified when a variable is reassigned multiple times - the issue will be thrown based on the last assigned value.
* Verified when a variable is sanitized first and later overwritten with random function. - error thrown. * In a condition, Verified when a variable is sanitized first and later overwritten with random function. - error thrown.
* Verified when a variable is assigned inside a loop before being used in the query. - If loop has non sanitized parameters then issue is thrown * Verified when a user input flows through multiple helper methods before reaching the query. - trace throws error up to 5 params.
**2. Added a new parameter to the rule “Test Class Names Should Include Test”**{Rule ID: sf:TestClassNaming} **Description** Several customers had reported that the CodeScan rule “Sf:testclassnaming” was producing false positives for classes containing “test”. We verified the rule expression, and confirmed that we did not support the naming pattern PR\_TestClassName. Instead, the rule supported only the following naming convention:\ TestClassName - prefix\ ClassNameTest - suffix\ ClassName\_Test - Underscore As such, we enhanced this rule by adding a new parameter to Sf:testclassnaming to define allowed naming conventions. The parameter is called allowedPatterns. The description of the parameter is: “A comma separated string of regular expressions matching allowed naming conventions for test classes.” The default of this parameter is to use the preexisting current functionality of the rule. Further, we decided that the parameter field should never be empty. The value of this parameter is providing customers with the flexibility to add any patterns that they allow as acceptable naming conventions without restriction to our logic. Validated the fix for the Sf:testclassnaming rule by verifying the following scenarios: * Able to see the configurable parameter allowedPatterns (comma-separated regex list) to support custom naming conventions. * Default behavior remains unchanged. * Validation ensures parameter cannot be empty. * Particular Reg expressions given in the allowed parameters skips the violations Accordingly.
### Fixes **1. Set default value to “false” for “is\_archived” column in organizations table.** **Summary of Issue**: Several customers were reporting an issue where users were unable to log in via SAML after their instance was upgraded to 26.0.3\ \ **Cause of Issue**: During our analysis, we identified that, as part of the upgrade process, a database field was unintentionally set to NULL instead of the defined default value. This disrupted the login via SAML. **What was done to resolve**: A query was run to update the Null value to the default value. **What we did to prevent it from happening again**: We have documented the corrective measures required to prevent this scenario in future upgrades. These improvements will be incorporated in an upcoming release to further strengthen the reliability of the upgrade process Verified the database for the orgs table, confirming that the “is\_archived field” is not NULL, and that DBAs are able to see the value set as **false** for all organizations in the environment. Also verified that users who login with SAML are unblocked, which we confirmed by creating a new SAML connection on a new organization. All users are able to log in successfully without any issues. *** ## CodeScan Release 26.0.4 **Release Date: 01 March 2026** {% hint style="info" %} As of release 26.0.4, CodeScan has adopted the External Client App (ECA) flow for Salesforce, replacing our existing Connected Apps flow. Key points: 1. If you have an existing Salesforce org registered, you are using the existing Connected App flow. No action is required at this time, and your analyses will run as expected. 2. Please note that any new Salesforce org you wish to register in CodeScan must use the new [local ECA flow](/product-guides/codescan/getting-started/connection-to-salesforce-with-eca). 3. Please note that if your existing Salesforce orgs need to be reattached, if your tokens expire, or after Sandbox refresh, your Connected App flow will no longer work, and you will need to re-register your org using the[ local ECA flow](https://knowledgebase.autorabit.com/product-guides/codescan/getting-started/connection-to-salesforce-with-eca). Please note that in these circumstances, your comparison branches in Salesforce will need to be set up again. {% endhint %} ### Summary CodeScan 26.0.4 is comprised of the following 2 components: * 1 Application Enhancement * 1 Fix Component details are listed in their corresponding sections within this document. ### New Features There are no New Features in this release. ### Application Enhancements **1. Salesforce External App Connection** **Description** To align with Salesforce Spring ’26 security requirements, CodeScan now offers an authentication flow for External Client Apps (ECA). What’s changed: * CodeScan now supports Salesforce’s updated authentication standards for External Client Apps. * Connectivity remains seamless once authentication is configured. Customer Action Required: * When adding new Salesforce orgs via External Client Apps, the following needs to be provided: * Client ID * Client Secret What stays the same: * No changes to core CodeScan functionality. * No changes to user workflows after successful authentication. This update ensures continued secure and compliant integration with Salesforce orgs under updated platform security requirements. For more detailed information, please review AutoRABIT’s published article “Salesforce OAuth External Client App (ECA) Transition” at ### New Rules There are no New Rules in this release. ### Rule Enhancements There are no Rule Enhancements in this release. ### Rule Deprecations There are no Rule Deprecations in this release. ### Fixes 1\. Fixed issue with data flow analysis logic in rule “Avoid Untrusted/Unescaped Variables in DML Query” {Rule ID: sf:SOQLInjection} **Description** We identified an issue in CodeScan where the Data Flow Trace for a SOQL injection rule where the trace repeatedly shows the same assignment instead of a clean, non-duplicated trace.
We determined the root cause of the issue and updated the rule logic accordingly. With this fix, this issue is now fully remediated.Top of Form Verified the following scenarios and report that the rule is now working as expected. * Verified for duplicated traces : verified along with test instance\ in preview: no duplicated traces
*** ## CodeScan Release 26.0.3 **Release Date: 15 February 2026** ### Summary CodeScan 26.0.3 is comprised of the following 5 components: * 1 New Feature * 2 Application Enhancements * 1 New Rule * 1 Fix Component details are listed in their corresponding sections within this document. ### New Features **1. Expiry Dates for Exception Status on Security Hotspots** **Description** The Exception Status has previously been added to the CodeScan Security hotspots. This new feature allows for configurable expiry dates for the Status. The user wants to add the status with an expiry date so when changing the hotspot status, they can supply a date when the issue will reopen as “To review”. Default will be no expiry. It will stay in the Exception Status until it is moved manually or given an expiry date. **Acceptance Criteria** * The ability to add an expiry date to the Security Hotspot resolution * The HotSpot needs to return to “to review” status when the expiry date is reached. * The expiry is optional and configurable; further, it can be any date in the future. * The Expiry date selector can be the same style as found in the issues page under creation date Verified the Security Hotspot Exception expiry behavior from the CodeScan UI on Staging Environment. * Users can optionally set an expiry date while changing a hotspot status to **Exception**. * Hotspots without an expiry remain in **Exception** status. * Hotspots with an expiry date automatically reappear in “**To review**” after the expiry is reached.
Also verified the scheduled job functionality for the Security Hotspots. * Security Hotspots marked as **Exception** remain unchanged when no expiry date is provided. * When an expiry date is set, the scheduled job automatically transitions the hotspot back to “**To review**” after the expiry is reached.
### Application Enhancements **1. CVSS Metrics: Advanced Calculations** **Description** The current descriptions of our vulnerabilities do not contain the metrics for CVSS. There are multiple variables that determine a CVSS score and with this update, users will now be able to see this level of detail. Use the following vulnerability rule values in CodeScan to provide all necessary inputs for calculating the CVSS score. Vulnerability Rule Details Rule Title: Array is Stored Directly Rule Name: sf:ArrayIsStoredDirectly Type: Vulnerability Language: Apex Description: Constructors and methods receiving arrays should clone objects and store the copy. This prevents future changes from the user affecting the internal functionality. See MITRE, CWE-374 - Passing Mutable Objects to an Untrusted Method CERT, OBJ06-J. - Defensively copy mutable inputs and mutable internal components CERT, OBJ13-J. - Ensure that references to mutable objects are not exposed Rule Message: (Not specified) Severity Level: Major Example: public class Foo { private String \[] x; public void foo (String \[] param) { this.x=param; //Bad: don't do this, make a copy of the array at least. } } Tags: cwe, cert, unpredictable Remediation Effort: 5min-constant\_issue **Additional Information**: Meaning of severity in CodeScan, use this to calculate CIA: BLOCKER has a value of 1 CRITICAL 2 MAJOR 3 MINOR 4 INFO has a value of 5 With this completed, we now provide the following values in tabular form, specify the vector and give the CVSS score: **Base Score Metrics** * Attack Vector (AV) (specify) * Attack Complexity (AC) (specify) * Privileges Required (PR) (specify) * User Interaction (UI) (specify) * Scope (S) (specify) * Confidentiality Impact (C) (specify) * Integrity Impact (I) (specify) * Availability Impact (A) (specify) **Temporal Score Metrics** * Exploit Code Maturity (E) (specify) * Remediation Level (RL) (specify) * Report Confidence (RC) (specify) **Environmental Score Metrics** * Modified Attack Vector (MAV) (specify) * Modified Attack Complexity (MAC) (specify) * Modified Privileges Required (MPR) (specify) * Modified User Interaction (MUI) (specify) * Modified Scope (MS) (specify) * Modified Confidentiality Impact (MC) (specify) * Modified Integrity Impact (MI) (specify) * Modified Availability Impact (MA) (specify) * Confidentiality Requirement (CR) (specify) * Integrity Requirement (IR) (specify) * Availability Requirement (AR) (specify) **CVSS Descriptions UI/UX Update** **2. CVSS: UI/UX Update** **Description** Per the enhancement above, all the CVSS rules are now updated with CVSS score values in the CVSS Break Down tab UI provided (below Metric category specific tabs).
All the below Vector Metric names and values of score table are now visible in above UI
Verified the CVSS UI/UX update via the following scenarios: * The CVSS Breakdown tab correctly shows Base, Temporal, and Environmental score sections. * All vector metric names and values are displayed as per the updated CVSS v3.1 table for CodeScan vulnerability rules (VF, SF, Apex). * Update is visible and working as expected.
### New Rules **1. New Rule: “Avoid Using Unfiled Public Folders” {Rule ID: sf-meta:AvoidUnfiledPublic}** **Description** This rule detects when Salesforce records are stored in unfiled public folders (identified by the path "unfiled$public"). Unfiled public folders pose several security and governance risks: * **Lack of Organization**: Records in unfiled public folders are difficult to manage, locate, and maintain, leading to poor data governance * **Excessive Access**: Public folders are accessible to all users in the organization by default, potentially exposing sensitive data to unauthorized users * **No Access Controls**: Unfiled public folders typically lack granular permission settings, making it impossible to restrict access based on role or profile * **Compliance Risk**: Storing records in unsecured, publicly accessible locations may violate data privacy regulations (GDPR, HIPAA, etc.) * **Audit Trail Issues**: Unfiled public folders make it difficult to track who accessed or modified records Best practices recommend organizing all Salesforce records into properly structured folders with: * Clear naming conventions * Appropriate sharing settings * Role-based access controls * Regular audits and cleanup processes Move metadata from unfiled public folders to dedicated folders with restricted access aligns to business requirements and the principle of least privilege. **Type**: Vulnerability **Message**: Metadata should not be stored in unfiled public folders **Tags**: **CWE**: 732\ **Remediation**: 5 minutes Verified the newly added CodeScan rule **sf-meta:AvoidUnfiledPublic (Avoid Using Unfiled Public Folders**) via the following scenarios: * The rule description is visible in CodeScan and correctly explains the security and governance risks associated with storing Salesforce metadata in unfiled public folders. * The rule is working as expected and consistently raises violations whenever Salesforce metadata is stored under a file path containing /unfiled$public/. * This behavior is expected, as metadata placed in unfiled public folders can lead to unrestricted access, lack of proper organization, and potential compliance concerns. * No issues were observed with the rule configuration or behavior.
### Fixes **1. Fixed issue with rule “Sf:fieldlevelsecurity” where user mode subquery false positive was reported** **Description** If code is running in the user mode, it should not need to check FLS, since user mode already does that. As such, CodeScan should not flag the rule/violation if it is in user mode. Only if it is not in user mode should the rule be triggered. However, several customers have reported that this behavior is not occurring properly. We have determined the root cause, and have concluded that there is an edge case that was not accounted for in our logic. Specifically, when the mode is defined via AccessLevel in the return statement, the rule incorrectly flags it as a violation, resulting in a false positive. For further reference, please see Salesforce Developers - Accesslevel Class [Salesforce Developers](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_class_System_AccessLevel.htm) This scenario wasn’t currently handled by the rule logic but has been addressed with a logic update. The issue has now been fully remediated with this release. Verified the Sf:fieldlevelsecurity – USER\_MODE subquery false positive via several scenarios and confirm that the rule now correctly skips FLS violations when AccessLevel.USER\_MODE is provided via **direct assignment**, including: * Inline usage in Database.getQueryLocator * Simple variable assignment (AccessLevel mode = AccessLevel.USER\_MODE) which resolves the originally reported false positive.
*** ## CodeScan Release 26.0.2 **Release Date: 01 February 2026** ### Summary CodeScan 26.0.2 is comprised of the following 10 components: * 1 New Feature * 3 Application Enhancements * 1 New Rule * 5 Rule Enhancements Component details are listed in their corresponding sections within this document. ### New Features **1. Data Flow Analysis** In our CodeScan 25.1.17 release (Jan 04, 2026), we announced that CodeScan had implanted new logic in some of our rules that detect vulnerabilities. This advanced logic provides precise visibility into where unsafe data originates and how it propagates, helping developers fix vulnerabilities at their source rather than applying superficial patches at the output stage. In that first release, we added this advanced “source to sink” logic in 3 rules: * Unescaped Error Message XSS {Rule ID: sf:UnescapedOutput} * URL Parameters should be Escaped/Sanitized {Rule ID: sf:UnescapedSource} * Avoid Calling SOQL and DML Inside Loops {Rule ID: sf:AvoidSoqlInLoops} In this current CodeScan 26.0.2 release (Feb 01, 2026), we added this advanced “source to sink” logic to 3 additional rules: * Avoid Untrusted/Unescaped Variables in DML Query {Rule ID: sf:SOQLInjection} * JavaScript Reflected XSS {Rule ID: vf:CrossSiteScriptingReflected} * Flow DML Should Not Be Called In Loops {Rule ID: sfmeta:DmlInFlowLoop} You can find specific details about each of these 3 newly updated rules in the “Rule Enhancements” section of these release notes. ### Application Enhancements **1. Updated the UI for the CVSS Filter** **Description** We updated the CVSS filter to a slider (for the values), allowing users to select a single value (pushing both sliders to a single value) or a range of values (pushing both sliders to either end of the required scale). Default should be 0 - 10 (sliders at each end of the scale) We verified the CVVS UI enhancement and have validated that users are able to see the updated Slider in the UI. * CVSS filter is displayed as a slider. * Default range is 0–10. * Supports both single-value and range-based selection. * Results are filtered correctly based on selected values. No functional or UI issues were encountered or reported during testing.
**2. Added the ability to Download/Export IDE Usage Data from the IDE Usage page** **Description** On the IDE Usage page, a “Export CSV” feature has been added. Based on the date filter, the connection list will be downloadable as CSV. Testing was done with 18,000 records to validate performance standards. **Acceptance Criteria** * On hovering over the download button, the application displays “Download the IDE usage history based on current filters.“ * On clicking the download button, download of a CSV file commences and respects the filters the user has selected.
**3. Added Enhanced our logic for Queries in JavaScript to only contain fields that are used** **Description** By including only the necessary fields in queries, developers can optimize the performance of their LWC components. When a query includes only the required fields, the amount of data retrieved from the Salesforce database is minimized, resulting in faster query execution times and reduced network overhead. **Hypothesis:** By limiting the fields in the queries to only those that are required for our LWC components, we expect to observe a significant reduction in query execution times and a decrease in network overhead. Example 1: Retrieve the name of an Account and its owner's Name via getRecord
**Value/Purpose:** The main purpose of this user story is to enhance the performance of LWC components and streamline the data retrieval process from the Salesforce database. By implementing this optimization, the benefits we expect to achieve are faster query execution and improved load times for LWC components. [Drive Consistency and Grow Developer Skills with a Developer Best Practices Checklist](https://developer.salesforce.com/blogs/2022/01/drive-consistency-and-grow-developer-skills-with-a-developer-best-practices-checklist) **Acceptance Criteria** Name: Avoid Querying Fields That Aren’t Used\ Key: cs-js:unused-query-field\ Description: By including only the necessary fields in queries, developers can optimize the performance of their LWC components. Including only required fields reduces the amount of data retrieved from the Salesforce database, resulting in faster query execution times and reduced network overhead. Type: Code Smell\ Severity: Minor\ Message: Avoid using the queries with unused fields\ Tags: performance Validated the newly added CodeScan rule UnusedQueryField via the following scenarios: * Verified that the rule “Avoid Querying Fields That Aren’t Used” is successfully added and visible in CodeScan with correct metadata (rule key, severity, type and tags). * Validated rule behavior using both positive (no-violation) and negative (violation) LWC test cases. * Confirmed that CodeScan correctly flags violations when unused fields are queried and does not report issues when all queried fields are used.
### New Rules **1. New Rule that validates the runInMode (or equivalent context property) of a Flow** **Description** We have created a new rule for Flow metadata that validates the runInMode (or equivalent context property of a Flow). This rule inspects whether the flow is executing in DefaultMode, SystemModeWithSharing, or SystemModeWithoutSharing. If configured to DefaultMode, the rule produces a violation as the default behavior of the rule. The rule ensures that flows explicitly check access permissions and don’t unintentionally run with improper privilege elevation. The developer should be able to override or configure the rule to allow certain modes as exceptions. **Hypothesis:**\ We believe that enforcing stricter validation on Flow execution context will prevent developers from inadvertently exposing sensitive operations or data access when Flows run under unclear or unsafe privilege assumptions. If CodeScan alerts developers when unsafe Flow run modes are used, developers will configure the correct context mode and explicitly handle permissions, leading to fewer security vulnerabilities in customer orgs. *Note*: The runInMode of the flow in Default Mode violations should be given for all the below mentioned flows except Screen Flows, which will include an additional parameter to reduce false positives.
**Value/Purpose:** * Prevent improper access to protected Salesforce objects and records. * Detect misconfigurations where a Flow runs unintentionally in elevated or ambiguous context. **Rule Details** Name: Validate Flow Run Context Mode\ Key: FlowRunContextValidation\ Description: This rule checks the execution context (runInMode) of a Salesforce Flow to ensure that it is not unintentionally configured to run with elevated privileges. Flows running in DefaultMode or SystemModeWithoutSharing can grant broad data access or excessive privileges to users who would normally not have such permissions. This rule enforces that flows explicitly use appropriate run contexts and encourages proper access validation to avoid unauthorized access to protected records or sensitive operations.\ See * [Determining the Flow Running User and Its Execution Context](https://admin.salesforce.com/blog/2022/your-guide-to-determining-the-flow-running-user-and-its-execution-context) - Salesforce * [CWE-282](https://cwe.mitre.org/data/definitions/282.html) - Improper Ownership Management * [CWE-284](https://cwe.mitre.org/data/definitions/284.html) - Improper Access Control Type: Vulnerability\ Severity: Major\ Message: This flow’s execution mode may grant unintended access. Use explicit access checks or adjust the run mode.\ Tags: salesforce, owasp-a1, owasp-a2 Remediation: 5 Minutes Parameter: Name: ignoreScreenFlows\ Description: If enabled, the rule will *ignore* Screen flows using runInMode in DefaultMode. Default: false We validated this newly added CodeScan rule “Validate Flow Run Context Mode (FlowRunContextValidation)” via the following scenarios: * Verified that the rule is successfully added and visible in CodeScan with correct metadata: * Type: Vulnerability * Severity: Major * Parameter: ignoreScreenFlows (default = false) * Validated rule behavior using Flow metadata: * Flows running in Default execution context (identified via environments=Default or equivalent) are correctly flagged with a Major vulnerability. * The violation message and rule key are displayed as expected. * The reported issue correctly points to the affected Flow metadata file.
### Rule Enhancements **1. New Parameter added to rule “Outer Class Explicit Sharing” allowing configurable enforcement of the rule for abstract and virtual classes** **{Rule ID: sf:OuterClassExplicitSharing }** **Description** We have updated the rule sf:OuterClassExplicitSharing to provide a configurable parameter that controls whether violations are raised for abstract and virtual outer classes. With this new parameter, users can avoid false positives in framework or base classes while still having the option to enforce explicit sharing when required by the security standards. **Hypothesis**:\ Introducing a configurable parameter to disable rule enforcement for abstract and virtual outer classes by default will reduce noise in scan results while preserving flexibility for teams that require strict sharing enforcement across all Apex class types. **Value / Purpose:** * Reduces false positives for commonly used base and framework classes * Improves rule adoption and trust by making enforcement intentional **Acceptance Criteria** **Parameter Name: EnableForAbstractAndVirtual** **Description**:\ The violation will be skipped for abstract and virtual outer classes in sf:OuterClassExplicitSharing if marked as false. Default is false. **Default Value:**\ false Verified the newly added parameter via the following scenarios: BEFORE the parameter was added, the rule sf:OuterClassExplicitSharing enforced explicit sharing declarations as follows: 1. Classes declared with with sharing → No violation 2. Classes declared with inherited sharing → No violation 3. Classes without any sharing keyword → Violation raised NOW, a new configurable parameter has been added: **Parameter Name: EnableForAbstractAndVirtual**\ **Default Value**: false This parameter allows to control whether the rule should enforce explicit sharing on abstract and virtual outer classes\ \ \ Current Behavior (After Fix):
This behavior aligns with the intended design: * Reduces noise and false positives by default * Allows stricter enforcement when required by security standards
**Parameter set to False:**
**Parameter set to True:**
**2. Added Data Flow Tracking for SOQL Injection Detection to rule “Avoid Untrusted/Unescaped Variables in DML Query” {Rule ID: sf:SOQLInjection}** **Description** Enhanced the sf:SOQLInjection rule to trace variable origins used in dynamic SOQL queries.\ For example, String field1 = getFilter(); String field2 = 'SELECT Id FROM Account WHERE '; Database.query(field2 + field1); Variables like field1 should be tracked from input to query construction, identifying whether proper escaping or validation occurred before concatenation. We also updated the issue description to show the source of untrusted input, transformations, and the exact sink (query line). **Hypothesis:**\ If the rule details how an input variable flows into a dynamic query without proper sanitization, developers can quickly locate injection vectors and remediate them effectively. **Value/Purpose:**\ Improves developer trust in reported SOQL injection issues by offering context-rich, data flow–backed explanations and reducing guesswork in identifying the unsafe variable. Verified the enhancement for sf:SOQLInjection via the following scenarios: * The rule correctly triggers for Apex code where untrusted input flows into dynamically constructed SOQL queries. * The issue message now includes an updated Data Flow Trace, clearly showing: * the origin/source of the untrusted input, * intermediate assignments / concatenations, and * the exact sink where the query is executed (Database.query).
**3. Enhancement to Cross-Site Scripting (Reflected) Detection with Data Flow Tracing logic** **{Rule ID: vf:CrossSiteScriptingReflected}** **Description** Implemented data flow tracking for the vf:CrossSiteScriptingReflected rule to trace how untrusted input propagates from sources like location.href, location.search, document.location, and window\.location to sinks such as document.write, .innerHTML, or eval(). We also updated the issue description to display the complete source → propagation → sink path, highlighting the flow of potentially malicious data through intermediate variables and functions. **Hypothesis:**\ If the rule can visualize how untrusted user input moves from sources to sinks through variable assignments and transformations, developers will more easily understand and remediate reflected XSS vulnerabilities. **Value/Purpose:**\ This enhancement improves clarity and confidence in issue results, reduces false positives, and empowers developers to identify the exact vulnerable flow within Visualforce pages for faster and more accurate remediation. Verified the enhancement logic of Cross-Site Scripting (Reflected) Detection with Data Flow Tracing via the following scenarios: * Validated that the rule correctly detects reflected XSS vulnerabilities involving untrusted user input. * Validated that the updated issue message now includes a Data Flow Trace that clearly indicates: * The source of untrusted input * Intermediate variable propagation * The final sink where the vulnerability occurs **4. Implemented Data Flow Tracking Logic for rule “Flow DML in Loops”** **{Rule ID: sfmeta:DmlInFlowLoop}** **Description** Enhanced the sfmeta:DmlInFlowLoop rule to include **data flow tracking** that identifies how DML operations (Create, Update, Delete Records) are executed within loop elements in Flows.\ This enhancement should trace data variables flowing from loop iterators to DML elements. We also updated the issue description accordingly to clearly indicate the source and flow of data. Updated Message:\ DML element UPD should not be called in loop loop\_one. Data Flow Trace -\ LOOPS (Loops loop\_one line: 15) →\ DECISION (decisions DEC line: 4) →\ RECORD UPDATES (recordUpdates UPD line: 29) **Hypothesis:**\ If we add data flow tracking to detect DML operations triggered inside loops, developers will gain better visibility into where and how loop data is used in DML actions, helping them refactor Flows for better performance. **Value/Purpose:**\ Improves the accuracy and clarity of Flow DML-in-loop detections, helping developers understand performance risks, prevent governor limit issues, and optimize Flow design. Verified the enhancement of the rule **sfmeta:DmlInFlowLoop** via the following scenarios: * Validated that the rule correctly detects DML operations (Create/Update/Delete) executed inside Flow loops. * Validated that the rule reports a clear **Data Flow Trace** from the loop through intermediate elements (e.g., Decision) to the DML element.
**5. Added New Parameters for rule “Flow DML Should Not Be Called In Loops”** **{Rule ID: sfmeta:DmlInFlowLoop}** **Description** Rule is enhanced to flag DML operations inside Salesforce Flows as violations across all flow types. However, some flow types (e.g., Scheduled Flows, Record-Triggered Flows configured for specific contexts) may legitimately require DML operations and should not be treated as violations.\ To provide flexibility and prevent unnecessary noise, we have introduced a series of configurable parameters that allow admins to **enable or disable specific Flow Types** for which DML-in-Flow should **not** generate a violation. This configuration is part of rule settings, which allows users to choose which flow types are exempt (e.g., Screen Flow, Record-Triggered Flow, Subflow, Scheduled Flow). **Hypothesis** If users can configure flow types to be excluded from DML-in-Flow violations, then: * False positives will be reduced. * Teams will have better control over enforcing governance rules based on their architecture. * Developers will get cleaner, more relevant issue reports. **Value / Purpose** * Reduces unnecessary violations for legitimate flow designs. * Provides team-level customization aligned with their Salesforce practices **Acceptance Criteria** **Parameter Name: IgnoreRecordTriggeredFlow** **Description**: The violation for DML operations inside the flow will be skipped for *Record-Triggered Flows* if marked as false. Default is false.\ **Default Value**:\ false *** **Parameter Name: IgnoreScreenFlow** **Description**: The violation for DML operations inside the flow will be skipped for *Screen Flows* if marked as false. Default is false.\ **Default Value:**\ false *** **Parameter Name: IgnoreAutolaunchedFlow** **Description**: The violation for DML operations inside the flow will be skipped for *Autolaunched Flows* if marked as false. Default is false.\ **Default Value**:\ false *** **Parameter Name: IgnoreScheduleTriggered Flow** **Description**: The violation for DML operations inside the flow will be skipped for *Schedule Triggered Flows* if marked as false. Default is false.\ **Default Value**:\ false *** **Parameter Name: IgnorePlatformEventTriggeredFlow** **Description**: The violation for DML operations inside the flow will be skipped for *Platform Event–Triggered Flows* if marked as false. Default is false.\ **Default Value**:\ false Verified the new, configurable **Ignore parameters** for the **sfmeta:DmlInFlowLoop** rule, allowing selective exclusion of specific Salesforce Flow types from DML-in-loop violations via the following scenarios: * All the parameters that are mentioned are added and are default to **false** supporting the correct behavior. * The rule was tested using Flow metadata containing DML operations executed inside loops across different Flow types * When an **Ignore** parameter is set to **false** (default), the rule correctly reports DML-in-loop violations. * When the corresponding **Ignore** parameter is set to **true**, violations are correctly skipped for that Flow type. * Flow types are correctly identified by the rule. * Violations are conditional based on rule configuration.
*** ## CodeScan Release 26.0.1 **Release Date: 18 January 2026** ### Summary CodeScan 26.0.1. is comprised of the following 4 components: * 1 New Feature * 1 Application Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### New Features 1\. CodeScan extension for Cursor With this release, CodeScan introduces first-class support for Cursor, a rapidly adopted AI-focused IDE used heavily by both our customers and internal teams. By bringing CodeScan capabilities directly into Cursor, we strengthen our AI value proposition and ensure we’re present where modern development workflows are shifting. Since Cursor is built on top of VS Code, this integration can leverage existing extension architecture—making it a natural, efficient expansion of our current IDE support. The goal is to deliver seamless scanning, issue insights, and AI-driven assistance within Cursor, enabling a smooth, intelligent coding experience for our users. **Feature Description** For developers who are using Cursor as their primary IDE, they can now run CodeScan What Problem Are We Solving? Guardrails for AI coding Less security reviews and less rework Faster time to market with business requirements **User Benefits** * Improves release management productivity * Integrated seamlessly with CICD workflows * Delivers on the Cursor promise of “making developers extraordinarily productive”
### Application Enhancements **1. Include Issue Comments in CSV Issues Export** **Description** When exporting Issues to CSV, the file should include an additional column that captures all comments associated with each issue. Each entry in this column must list every comment along with the commenter’s user name, the date/time the comment was made, and the comment text, formatted in a readable, consistent manner. **Hypothesis**\ If issue comments are included in the CSV export with clear attribution & timestamps, then users will be able to review, audit, and share issue context offline without needing to revisit the application UI. *The image below illustrates the new format for comments added into CSV exports:*
**Value / Purpose** * Enables complete issue context in offline analysis and reporting. * Reduces dependency on the UI for reviews, audits, and stakeholder sharing. * Improves collaboration by preserving discussion history in exported data. Verified Issue Comments column in CSV export via the following Scenarios:\ \ Member Comment Export * Added a comment as an existing project member. * Exported the Issues CSV and verified that the comment is correctly displayed in the *Issue Comments* column along with user name and timestamp. * Invited Organization Member Comment * Invited a new member to the organization and added a comment from that user. * Exported the CSV and confirmed the comment appears correctly. * Multiple Comments from Different Members * Added multiple comments from different organization members on the same issue. * Verified that all comments are present in the CSV export and are displayed in a readable, consistent format. * Deleted User Comment Handling (Expected Behavior) * Invited a user, added a comment from that user, and then deleted the user. * Verified that the comment remains in the CSV export with a “Deleted” tag. * Confirmed that no additional user information is shown for the deleted user, which matches the expected behavior. ### Fixes **1. Fixed three issue with CodeScan User Licenses** Several customers reported that they were not able to activate all their team members, even though they had proper licensing. It appears that CodeScan was consuming 1 license spot. Upon detailed research, we identified 3 issues that needed to be fixed: 1. There were some “hanging*”* user entries in organization\_members table, where there were entries for users present in organization\_members table, which did not have a mapped corresponding user in users table. 2. Member count query was not taking into account inactive users. 3. When AutoRABIT SRO creates a new org, the root admin user used to create the org was being automatically added to that organization as a member. Thus, the root user was taking up a standard user slot in customer’s license limit (unless explicitly removed). We have addressed all of these issue in this release. We have verified all the fixes related to user license counting and orphan member cleanup via the following scenarios 1. Inactive SonarQube Users Excluded from License Count 1. Created SonarQube users and added them to CodeScan organizations. 2. Upon deactivating users in Administration page verified: 1. User is excluded from member/license count. 2. Corresponding license is freed immediately. 3. A new user can be added without encountering license limit errors. 3. Verified for both Standard users and Platform Integration users. 2. Immediate License Release on User Removal/Deactivation 1. Removed/deactivated active users from the organization. 2. Confirmed license count updates instantly on: 1. Organization → Members page 2. Administration → Billing page 3. Orphan (Hanging) organization\_members Entries Cleanup 1. Identified orphan entries in organization\_members table (no corresponding users users\_table entry). 2. Executed dev-provided cleanup SQL query. 3. Confirmed Orphan entries were successfully deleted.
**2. Fixed an issue with “Issues” assignment and status update, where filters are not working (as "Bulkchange and Bulkassign" API returns 500 Internal error)** Several customers reported issue with “Bulk Issue Assignments.” We identified 2 main causes: * Issue 1: Main Branch – Unable to Roll Back Issue Status to Open * Issue 2: PR Branch – Unable to Assign Issues We fully remediated these issues in this release by adding a logic fix for the bulk api (for pr analysis) by correctly fetching the projectuuid. Verified the following issues have been remediated and are now working as expected. * Regarding Issue 1: Main Branch * Users able to revert the issue status back to Open (on the main branch). * API able to assign/unassign multiple issues to org user * Regarding Issue 2: PR Branch * Issues in PR branches should be assignable to users through Bulk Issues, similar to main branch behavior. # Cloud Release Notes 25.1 CodeScan Cloud Release Notes {% @mailchimp/mailchimpSubscribe cta="CodeScan Release Notes Mailing List:" listId="a085e26e7e" %} ## Integration Requirements for CodeScan v25.1.0+ Please note that there are updated requirements for customers who are using one or more of the following to integrate with CodeScan: * SFDX * SonarScanner * ADO * VS Code * IntelliJ [**Please refer to our integration requirements page for further details.**](https://knowledgebase.autorabit.com/product-guides/codescan/codescan-integration/integration-requirements) *** ## CodeScan Release 25.1.17 **Release Date: 04 January 2026** ### Summary CodeScan 25.1.17 is comprised of the following 5 components: * 2 New Features * 3 Rule Enhancements * 1 Fix Component details are listed in their corresponding sections within this document. ### New Features **1. Data Flow Analysis** CodeScan has implanted new logic in some of our rules that detect vulnerabilities. This advanced logic provides precise visibility into where unsafe data originates and how it propagates, helping developers fix vulnerabilities at their source rather than applying superficial patches at the output stage. In this first release, we have added this advanced “source to sink” logic in 3 rules: * Unescaped Error Message XSS {Rule ID: sf:UnescapedOutput} * URL Parameters should be Escaped/Sanitized {Rule ID: sf:UnescapedSource} * Avoid Calling SOQL and DML Inside Loops {Rule ID: sf:AvoidSoqlInLoops} You can find specific details about each of these rules in the “Rule Enhancements” section of these release notes. **2. COMING SOON: New GitLeaks Rules in CodeScan** CodeScan has implanted new logic within the Rules Engine that can detect GitLeaks vulnerabilities. GitLeaks is a tool for detecting secrets like passwords, API keys, and tokens. We have extended this logic to cover Salesforce specific languages and components including: * GitLeaks Secret Detection in Apex source files * GitLeaks Secret Detection in Salesforce Metadata Files * GitLeaks Secret Detection in Visualforce & Lightning Files Please note that these rules are not yet available for your scans (but will be available soon). However, these rules are now visible within your CodeScan orgs so that you can begin planning and reviewing for incorporation within your analyses once fully available. We will provide detailed rule descriptions with the NEW RULES section of the corresponding release notes once they become generally available for use. **Description** Implement a GitLeaks rule that triggers scans specifically on Salesforce files, so that all standard and custom GitLeaks rules (e.g., AWS keys, OAuth tokens, passwords, PEM files) are applied to these files, and any detected issues are surfaced directly in CodeScan>Issues. Implementing GitLeaks rules within CodeScan provides tremendous value to our customers, enabling them to automatically scan Salesforce files and ensure: * Any secrets or sensitive credentials hardcoded in Apex classes or triggers(\*.cls, \*.trigger), Visualforce pages, Lightning components, etc. will be detected early. * Developers will see security issues integrated into their existing CodeScan reports without needing to run GitLeaks separately. **Value / Purpose** * Security Guardrail: Prevents exposure of secrets in Salesforce code (API tokens, passwords, OAuth client secrets). * Compliance & Governance: Helps organizations enforce security best practices and avoid regulatory violations due to hardcoded secrets. **Summary** These rules run GitLeaks on Salesforce source files to detect hardcoded secrets such as API keys, passwords, OAuth tokens, and private keys. All standard and custom GitLeaks rules are applied, and detected issues are surfaced in CodeScan. ### Rule Enhancements **1. Updated the Apex rule “Unescaped Error Message XSS” to include data flow analysis logic {Rule ID: sf:UnescapedOutput}** () **Description** 1\. Reimplement the sf:UnescapedOutput rule to include data flow tracing for variables passed to addError() (e.g., addError(html, false)). This will determine whether variables originate from unsanitized sources by tracing them across methods and assignments. Use UrlSanitizationRule logic as reference for tracking unescaped values. 2\. Update the issue description to include the exact source variable and its data path before being rendered. **Hypothesis**\ If we trace the data flow from unescaped or unsanitized sources to the point of output in addError, developers can clearly see how unsafe data reaches the output layer, making the issue more actionable. **Value/Purpose**\ Provides precise visibility into where unsafe data originates and how it propagates, helping developers fix vulnerabilities at their source rather than applying superficial patches at the output stage.
Verified the data flow tracking logic for unescaped output in Apex is working and the updated description has been applied.
**2. Updated the Apex rule “URL Parameters should be Escaped/Sanitized” to include data flow analysis logic {Rule ID: sf:UnescapedSource}** () **Description** 1\. Extend the sf:UnescapedSource rule to track the flow of URL parameters retrieved from ApexPages.currentPage().getParameters().get(...).\ The data flow analysis will identify whether these variables are properly sanitized or escaped before reaching any sensitive sink or being rendered. 2\. Update issue descriptions to show both the untrusted source and its usage path. **Hypothesis**\ If the system highlights the full journey of parameters from getParameters() to their usage points, developers will better understand how unescaped data can lead to vulnerabilities and where sanitization is missing. **Value/Purpose**\ Enables developers to pinpoint missing sanitization in their Apex controllers by visualizing data flow paths, thus improving the security posture of Visualforce and Lightning pages. **Acceptance Criteria** ```java public class ClassAbc { public Foo() { String unescapedstring = ApexPages.currentPage().getParameters().get('url_param'); someOtherFunction(unescapedstring); //Bad: this string is used elsewhere and may lead to an XSS vulnerability someOtherFunction(integer.valueof(unescapedstring)); //Good: the string is safely checked as an integer } } ``` **Existing Message**: URL parameters should be escaped/sanitized XSS **Updated Message**: URL parameters should be escaped/sanitized XSS. Data Flow Trace - DECLARATION (ClassAbc.Foo line: 3) The rule behavior was validated by testing multiple scenarios involving URL parameters retrieved using ApexPages.currentPage().getParameters().get(...). on Preview Instance. Verified scenarios: * Usage after type validation with Integer.valueOf() — no violation raised (expected behavior). * Direct usage of URL parameters without sanitization — violation raised. * Propagation of URL parameters through variable assignment without sanitization — violation raised. * Passing URL parameters through multiple methods without sanitization — violation raised with correct data flow trace. * Usage of URL parameters in dynamic SOQL without sanitization — violation raised. For all violating cases, the rule correctly reported the issue with an appropriate data flow trace (e.g., declaration point and usage path). The observed results match the expected behavior.
**3. Updated the Apex rule “Avoid Calling SOQL and DML Inside Loops” message to include detailed data flow analysis logic {Rule ID: sf:AvoidSoqlInLoops}** () **Description** Refine the issue message for sf:AvoidSoqlInLoops to clearly identify the loop structure and the query being executed inside it.\ Include variable references and contextual flow details showing how data or parameters within the loop lead to repeated queries. **Hypothesis**\ Providing contextual information about where and how SOQL queries are invoked within loops will improve developer understanding and reduce rework in optimizing code performance. **Value/Purpose**\ Enhances readability and educational value of performance warnings by showing contextual flow, helping developers refactor code more efficiently. **Acceptance Criteria** ```csharp public class CaseProcessor { public void processAllCases(List caseList) { // LOOP for (Case c : caseList) { processCase(c); // hop 1 } } void processCase(Case c) { fetchOwnerDetails(c.OwnerId); // hop 2 } List fetchOwnerDetails(Id ownerId) { return [ SELECT Id, Name FROM User WHERE Id = :ownerId // SINK (SOQL) ]; } } ``` **Existing Message:** Avoid running SOQL and DML inside loops. Loop Trace : CaseProcessor.fetchOwnerDetails: line 16 --> CaseProcessor.processCase: line 11 --> CaseProcessor.processAllCases: line 6 **Updated Message:** Avoid Running Soql and DML inside loops. Data Flow Trace - SOQL (CaseProcessor.fetchOwnerDetails: line 16) --> CALL (CaseProcessor.processCase: line 11) --> LOOP (CaseProcessor.processAllCases: line 6) Executed the following scenarios and validated that the advanced logic is working as expected. * Verified the updated behavior of the sf:AvoidSoqlInLoops rule. * Multi-hop scenarios (loop → method → method → SOQL) correctly show the full Data Flow Trace with SOQL → CALL → LOOP. * Direct SOQL-in-loop scenarios correctly show the simplified message, which is the expected behavior.
*** ### Fixes 1. **Improved License Limit Enforcement**: When a customer exceeds their licensed limits, CodeScan will no longer block access to the platform or restrict any previously licensed features. Customers can continue to use all features they are entitled to without interruption, ensuring uninterrupted workflows while they address licensing limits. ## CodeScan Release 25.1.16 **Release Date: 14 December 2025** ### **Summary** CodeScan 25.1.16 is comprised of the following 4 components: * 2 Rule Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### Rule Enhancements **1. Updated the description in the CodeScan APEX rule “Server Side Request Forgery (SSRF)”** {Rule ID: sf: ServerSideRequestForgery} **Description**: Update the issue description for the sf:ServerSideRequestForgery rule to include data flow information once tracking is implemented. Highlight how untrusted user input influences outbound requests or endpoint URLs used in HttpRequest.setEndpoint() or similar methods. **Hypothesis**:\ Providing a traceable flow from input source to request endpoint will help developers clearly identify unsafe URL usage leading to SSRF vulnerabilities. **Value/Purpose**:\ Improves clarity and helps prioritize high-risk SSRF issues by showing the complete journey of untrusted data to outbound request logic. Code Example: ```java public class Negative { public void otherMethod() { String oneMore = 'somethingHere'; init(oneMore); } public PageReference init(String Lastname){ String FirstName = getName(); try { HttpRequest req = new HttpRequest(); req.setEndpoint('callout:Third_Party_Authorization/v1'+Lastname); request.setMethod ('POST'); } } } ``` **Existing Message**: Sanitize input to avoid possible SSRF. Data Flow Trace: Negative.otherMethod: line 4 **Updated Message**: Sanitize input to avoid possible SSRF. Data Flow Trace - CALL (Negative.otherMethod: line 4) Make sure to check for internal methods also (E.g. FirstName variable on line 8 if used in the set endpoint call on line 11)
**2. Updated the description in the CodeScan APEX rule “Resource Injection” to account detection with Source-to-Sink Tracing {Rule ID: sf: ResourceInjection}** **Description**: Update the issue description for sf:ResourceInjection to display how untrusted input propagates to resource-loading statements, such as dynamic resource identifiers or file references.\ The new description should include the identified source and sink with a trace of intermediate transformations. **Hypothesis**:\ If developers can visualize which variable or parameter is used to form a resource path without sanitization, they will better understand the exploit path and fix it faster. **Value/Purpose**:\ Increases the usability and accuracy of Resource Injection findings by offering transparent, contextual information about the data flow chain. **Acceptance Criteria** Sanitize input to avoid possible resource injection. Data Flow Trace : {Class.method}: line {line number} --> {Class.method}: line {line number} Example: Sanitize input to avoid possible resource injection. Data Flow Trace : APIVersionsRetiredTrigger.processOldAPIVersionReferences: line 88 --> APIVersionsRetiredTrigger.processOldAPIVersionReferences: line 92 Code Example: ```java public class Negative { public void otherMethod() { String oneMore = 'somethingHere'; init(oneMore); } public PageReference init(String Lastname){ String FirstName = getName(); try { HttpRequest req = new HttpRequest(); req.setEndpoint('/Third_Party_Authorization/v1'+Lastname); request.setMethod ('POST'); } } } ``` **Existing Message**: Sanitize input to avoid possible resource injection. Data Flow Trace: Negative.otherMethod: line 4 **Updated Message**: Sanitize input to avoid possible resource injection. Data Flow Trace - CALL (Negative.otherMethod: line 4) Make sure to check for internal methods also (e.g., FirstName variable on line 8 if used in the set endpoint call on line 11)
### Rule Deprecations There are no Rule Deprecations in this release. ### Fixes **1. Fixed an issue in the APEX rule “Field Level Security Vulnerabilities**” {Rule ID: sf:FieldLevelSecurity} Several customers reported that they were receiving the error message “Permissions should be checked before accessing resource SObject” even though they were providing suitable permissions using DML and/or SOQL statements. It was determined that CodeScan was not recognizing both DML and SOQL statements. As such, we overhauled the rule logic to address this issue and have ensured that CodeScan is now recognizing the AccessLevel.\* commands in DML calls. We have validated this new logic and verified that no vulnerabilities were raised (which is the expected and correct behavior for this updated rule logic).
**2. Fixed an issue in the APEX rule “Resource Injection”** {Rule ID: sf: ResourceInjection} Resource injections occur when user-controllable data is used to specify a resource identifier without proper validation. This rule identifies potential resource injection vulnerabilities by detecting unsafe URL construction for internal network requests. Input can be cleansed by using Id.valueOf, Date.valueOf, etc. Or escaped using String.escapeSingleQuotes(). However, several customers reported that this rule was firing improperly, even when the recommended methods have been applied. After reviewing, we confirmed cases of false positives and determined that the rule required a minor update to the rule logic. We verified the new logic and validated that the rule is now working as originally designed.
*** ## CodeScan Release 25.1.15 **Release Date: 30 November 2025** ### Summary CodeScan 25.1.15 is comprised of the following 4 components: * 1 Rule Enhancement * 3 Fixes Component details are listed in their corresponding sections within this document. ### Rule Enhancements **1. Enhanced the logic in the CodeScan rule “Unnecessary Boolean Assertion”** {Rule ID: sf:UnnecessaryBooleanAssertion} Several customers have reported that the current rule detects unnecessary Boolean assertions only when using the System.assert() method. However, it does **not** flag similar patterns when assertions are made through the Assert class methods such as Assert.isTrue(true) or Assert.isFalse(false). To improve coverage, we enhanced the rule logic to include these Assert class scenarios, ensuring consistency across both assertion types. **Fix Summary** * Extended the rule logic to detect unnecessary boolean assertions in the following cases: * Assert.isTrue(true) * Assert.isFalse(false) * Updated the rule message and description to clearly explain why these patterns are redundant. **Updated Rule Description**: A Unit test assertion with a Boolean literal is unnecessary since it always will evaluate to the same thing. Consider using flow control (in case of assertTrue(false) or similar) or simply removing statements like System.assert(true) and Assert.isFalse(false).\ \ If you just want a test to halt after finding an error, use the System.assert(false, 'message') or Assert.isFalse(false, 'message') methods and provide an indication message of why it did.
Verified the following scenarios are working as expected: * Noncompliant scenarios using System.assert(true), Assert.isTrue(true), and Assert.isFalse(false). All were correctly flagged as expected. * Compliant scenarios have been tested. (by using only string values).
### Fixes **1. Fixed an issue in the rule “Require CSRF Protection On GET Requests”** {Rule ID: vf:RequireConfirmationToken} During our routine, internal rule evaluation process, we discovered that this rule wasn’t firing as expected. As such, we overhauled the rule logic to address this issue. **Summary**: The current xpath for this rule is: //Document//Element\[@Name='confirmationtokenrequired']\[Text\[@Image='false']] We recognize that this will not work as expected, as the confirmation token is actually in the metadata of the page and the tag is in camel-case (confirmationTokenRequired). The logic was updated to: //Document//Element\[lower-case(@Name)='confirmationtokenrequired']\[Text\[@Image='false']] With this enhancement, the rule will: * find the correct tag * look in the page-meta.xml metadata file (not the page itself) Verified the following scenarios and confirmed that the updated rule logic is working as expected. *“vf:RequireConfirmationToken” getting triggered only* when the corresponding meta.xml has false for ConfirmationToken tag . * Verified the rule behavior using by uploading only page file and then with corresponding meta.xml file with true and meta.xml file with false.
**2. Fixed an issue in the rule “Switch statements should not have too many case clauses”** {Rule ID: sf:MaximumNumberOfCase } Some customers have reported that this rule throws out of bounds exceptions. Upon investigation, we determined that this is caused by an empty switch statement, which manifests as a parser error when this class is added in Salesforce. The aim of fix is to make sure that the CodeScan parser sees empty switch statements as syntax errors. Verified that the below scenarios are working as expected. * Verified that the rule does not throw out of bounds exceptions in the analysis logs (it should not throw this and, as such, has been validated as working as expected). * Verified “sf:MaximumNumberOfCase” rule is triggered only when the maximum limit is exceeded.
**3. Fixed an issue in the CodeScan UI on the “Quality Gate Changelog” page, where the “author name” field overlaps with the “action taken” field.** Some customers reported an issue in the CodeScan UI on the “Quality Gate Changelog” page, where the “author name” field overlaps with the “action taken” field.
This fix remediates that issue in full. Verified the below scenarios and validated that the fix is working as expected. * Verified that the “author name” filed does not overlap with the “action taken” field. * Verified with different actions (Updated, Activated, Deactivated).
*** ## CodeScan Release 25.1.14 **Release Date: 16 November 2025** ### Summary CodeScan 25.1.14 is comprised of the following 10 components: * 1 New Feature * 3 Rule Enhancements * 2 Rule Deprecations * 4 Fixes Component details are listed in their corresponding sections within this document. ### New Features **1. New rules to Identify Potential Sensitive Data /PII Fields** **Description** These rules identify potential sensitive data and Personally Identifiable Information (PII) fields within the Salesforce Apex code. This helps organizations ensure these fields are handled securely and comply with data privacy regulations. **Hypothesis:** By implementing these rules to identify potential sensitive PII fields, CodeScan can identify and address security risks associated with handling sensitive PII data in Salesforce. CodeScan Sensitive Data Scanning uses regular expression patterns to search for potential sensitive PII field names. It looks for common identifiers listed below and some custom objects/fields such as "name," "social\_security\_number," "credit\_card," or "passport" and determines if they are being assigned string literals or used in an insecure way (exposed in debug).
ObjectFields Likely to Contain PII
ContactBirthdate, Department, Email, Fax, FirstName, HomePhone, LastName, MailingAddress, MiddleName, MobilePhone, Name, OtherAddress, OtherPhone, Phone, PhotoUrl, Title
LeadAddress, Company, Email, Fax, FirstName, Industry, LastName, MiddleName, MobilePhone, Name, Phone, PhotoUrl, Title, Website
UserAddress, CompanyName, Department, Email, Fax, FederationIdentifier, FirstName, FullPhotoUrl, LastName, MiddleName, MobilePhone, Name, Phone, Title, Username
Account (Business)BillingAddress, Fax, Name, Phone, PhotoUrl, ShippingAddress
Account (Person Account Fields)FirstName, LastName, MiddleName, PersonBirthDate, PersonEmail, PersonHomePhone, PersonMailingAddress, PersonMobilePhone, PersonOtherPhone, PersonTitle
*NOTE: We implemented advanced logic to Ignore Violations on Dummy/Masked data as shown below:*
Data TypeOriginal/Real PII (Violation)Dummy/Masked Data (Compliant)
Emailjohn.doe@company.comtest.user@example.test
Phone98765432105551234567 or 0000000000
SSN123-45-6789000-00-0000 or null
Credit Card41111111111112344111111111111111 (Visa test number)
Address123 Main Street, New York123 Test Street, Test City
LogsSystem.debug('Email: jane@corp.com')System.debug('Email: [REDACTED]')
**Value/Purpose:** The purpose of this user story is to enhance data privacy and security within our Salesforce organization. By identifying potential sensitive PII fields, we can Improve data governance and minimize the chances of data breaches. **Acceptance Criteria** **Name**: Identify Potential Sensitive PII Fields\ **Key**: SecurePIIFields\ **Description**: Certain standard Salesforce objects (such as Contact, Lead, User, Account, Person Account, and Opportunity) contain fields that may hold PII, including names, addresses, phone numbers, emails, birthdates, and other identifiers. These fields must be treated as sensitive data and protected in compliance with privacy and security regulations (e.g., GDPR, CCPA, HIPAA). {% hint style="info" %} NOTE: To fully maximize the value of these rules, you can also configure them to include custom fields as parameters (e.g., SSN, Social\_Security\_Number, Credit\_Card, Passport). {% endhint %} Ensure these fields are handled securely through encryption, masking, and strict access controls to minimize the risk of data exposure or breaches.\ **Type**: Vulnerability\ **Severity**: Major\ **Message**: Potential sensitive PII field detected. Ensure that this field is handled securely.\ **Tags**: Security\ **Parameters**:\ **Name**: sensitiveFields\ **Description**: A comma-separated list of sensitive custom fields. Add any custom fields you would like to monitor with this rule. Verified that **sf:SecurePIIFields** rules are being triggered in following scenarios: * Verified the **sf:SecurePIIFields** rules by activating these rules in a specified Quality Profile. The Project analysis should trigger the violation (Security Hotspot). * Verified by giving custom parameters (ssn, credit\_card, passport) and validated that they are working as expected. * Verified by sending both string and integer value for credit\_card.
### Rule Enhancements **1. Enhanced God Class Rule by adding parameters {Rule ID: sf:GodClass}** The sf:GodClass rule currently uses fixed threshold values to identify “God Class” design flaws: * WMC (Weighted Methods Count): > 47 * ATFD (Access to Foreign Data): > 5 * TCC (Tight Class Cohesion): < 1/3 (33%) These thresholds are hard-coded and not configurable. We decided to introduce parameters to allow users to customize these values based on their project requirements. By making these thresholds configurable, users can fine-tune the rule according to their project’s code complexity and quality standards, reducing false positives and improving detection accuracy. Value / Purpose: * Enables users to adjust thresholds to better match their codebase. * Improves usability and flexibility of the rule. * Increases adoption by making the rule adaptable to various team standards.Bottom of Form
Verified the sf:GodClass by validating that users are able to see the violations as expected for the below scenarios When users provide the below Threshold values: * wmc=47, atfd=5, tcc=0.33 Result: Violation * wmc=10, atfd=5, tcc=0.50 Result: Violation * wmc=60, atfd=10, tcc=0.90 Result: Violation * wmc=30, atfd=2, tcc=0.8 Result: Violation * wmc=100, atfd=10, tcc=0.2 Result: No violation * wmc=9999, atfd=9999, tcc=0 Result: No violation * wmc=0, atfd=0, tcc=0 Result: No violation * wmc=0, atfd=0, tcc=1 Result: Everything violates
**2. Updated the Rule Description and Example for rule “Check for Lightning Migration Issues for Salesforce.com and Force.com Links” {Rule ID: vf:LightningAvoidHardcodedSalesforceDomain}** This rule was updated with this new description and example: “URL references may not work as expected in Lightning Experience or if you decide to swap to My Domain. If you decide to use My Domain, you have to replace hard-coded references to your original URL with references to your new domain. Using something like {!Site.BaseUrl} will avoid this hassle. See: [Considerations Before Transitioning to Lightning Experience](https://resources.docs.salesforce.com/198/latest/en-us/sfdc/pdf/lex_considerations.pdf)” Example:
Verified these rule updated by confirming that users are able to see the updated description and the example.
**3. Updated the Rule Description for rule "em" Tags Should Be Used Instead of "i" {Rule ID: vf:ItalicTagsCheck}** We recognized that this description was out of date and determined it needed to change to: \ “The \/\ and \/\ tags have exactly the same effect in most web browsers, but there is a fundamental difference between them: \ and \ have a semantic meaning, whereas \ and \ only convey styling information like CSS. When \ can have simply no effect on a device with limited display or when a screen reader software is used by a visually impaired person, \ will: * Underline the characters on a phone or tablet * Speak with lower tone when using a screen reader * Display the text as bold in normal browsers Consequently: * In order to convey semantics, the \ and \ tags shall never be used, * In order to convey styling information, the \ and \ should be avoided and CSS should be used instead. Verified the rule description and confirmed that the updated description which is displayed as expected.
### Rule Deprecations **1. Deprecation of 2 rules for “disallow irregular whitespace outside of strings and comments” (one for Visualforce and one for JavaScript) {Rule ID: cs-vf:no-irregular-whitespace and Rule ID: cs-js:no-irregular-whitespace}** The reason these rules are being deprecated is because they do not fire before the parser catches the issue. These types of irregular white space are no longer even seen as parsing JavaScript. Further, we have updated the descriptions for these rules to include: \ “This rule has been deprecated due to these types of white space being caught by the JavaScript parser before a rule can be fired. Please make sure you have the cs-js:exception rule in your javascript Quality Profile to be made aware of these errors.” Verified the Rule Deprecations of cs-vf:no-irregular-whitespace and cs-js:no-irregular-whitespace and confirmed users are able to see the updated status as Deprecated and the updated description for these rules.
**2. Deprecation of 2 rules for “disallow octal escape sequences in string literals” (one for Visualforce and one for JavaScript) {Rule ID: cs-vf:no-octal-escape and Rule ID: cs-js:no-octal-escape}** The reason these rules are being deprecated is because they do not fire before the parser catches the issue. These types of octal escapes are no longer even seen as parsing JavaScript. Further, we have updated the descriptions for these rules to include: “This rule has been deprecated due to these types of octal escapes being caught by the JavaScript parser before a rule can be fired. Please make sure you have the cs-js:exception rule in your javascript Quality Profile to be made aware of these errors.” Verified the Rule Deprecation for cs-vf:no-octal-escape and cs-js:no-octal-escape and confirmed users are able to see the updated status as Deprecated and the updated description for these rules.
### Fixes **1. Fixed project deletion issues occurring on WEBHOOK type projects with SFDX/Sonar-Scanner** Several customers have reported unexpected issue under the specific circumstance of: 1\. Create a WEBHOOK type empty project. 2\. Run the analysis for the created empty type project using SFDX/Sonar-Scanner 3\. The Analysis will be successful (as expected). 4\. Then create a branch analysis for the same project type. 5\. Switch the branch analysis to main branch analysis. 6\. Then delete the project from Project settings. **Outcome:** Users are able to see that the project has been deleted successfully (expected behavior). However, if users then search for projects, these users are able to see the project which was deleted previously. This is not expected behavior. We have identified that the root cause of this issue is that the Project is not actually getting deleted when the default branch for a project is changed. This issue has been fully remediated with this fix. Verified the fix via the following scenarios * Ran sonar-scanner analysis twice (one with branch) >> switch to other branch >> try deleting project >> user able to view successful message for deletion >> project deleted. * Verified with empty webhook project analysis as well. Verified the below scenarios via the CodeScan APIs: * Verified Single project deletion and bulk project deletion * Verified Postman response - by giving security token and without security token * Verified deleting projects without having access * Verified deleting old projects. **2. Fixed issue where the bulk deletion of analyzed projects fails, while single project deletion works successfully** We have detected this issue under the following circumstance: From the Project Management page, deleting a single project after a completed analysis works correctly. However, when multiple analyzed projects are selected and deleted in bulk, the deletion operation fails and throws error as "error": "org.hibernate.TransientPropertyValueException: object references an unsaved transient instance." This issue has been remediated fully, so that all selected projects (analyzed) are deleted successfully (and the system shows proper confirmation messages (if required). Verified the Bulk delete option for all project integrations, including comparison branches and regular branches. Confirmed via the following scenarios that users are now able to successfully delete multiple projects at once.
**3. Fixed an issue in the rule “Immutable Field,” which was causing false positives {Rule ID: sf:ImmutableField}** Several customers have reported that the current rule logic incorrectly flags propertyVal as a candidate for final, even though its value can be modified indirectly through a property getter/setter. In the following example, the field propertyVal is updated within the getter of anotherPropertyVal via this.propertyVal = 'test' and subsequently returned: Example code:
**Expected Behavior:**\ The rule should **not** raise a violation when the private field’s value can be modified through class property accessors (get/set methods) or other internal logic. Such fields are **not immutable** and marking them as final would cause compilation errors. Verified that the “sf:ImmutableField” is getting triggered only when the private field’s value cannot be modified. Further, we verified the rule behavior using both mutable and immutable field patterns.
**4. Fixed an issue in the rule “Type Reflection Is Security Sensitive” {Rule ID: sf:HotspotTypeReflection}** During our routine, internal rule evaluation process, we discovered that this rule wasn’t firing as expected. As such, we overhauled the rule logic to address this issue. Verified the sf:HotspotTypeReflection rule by activating the rule in a specified Quality Profile. Then, in a subsequent project analysis, validated that the rule is now working as expected.
*** ## CodeScan Release 25.1.13 **Release Date: 02 November 2025** ### Summary CodeScan 25.1.13 is comprised of the following 5 components: * 4 Rule Enhancements * 1 Fix Component details are listed in their corresponding sections within this document. ### Rule Enhancements **1. Enhanced rule “Field Level Security” {Rule ID: sf:FieldLevelSecurity}** Previously, CodeScan did not raise violations if a method matched the condition:\ ![](/files/pVz3rBfkqvpHLViMRh34) This exception was originally introduced to reduce noise and was added to our rule logic before Salesforce introduced USER\_MODE. However, with Salesforce’s updated guidance requiring all database operations to consistently enforce permissions, the exemption is no longer valid. Getters can still expose data through bindings, so excluding them would not align with best practices. Now, DML operations in getter methods that do not enforce permissions (e.g., without USER\_MODE) will correctly raise violations. {% hint style="info" %} Note: The update has been refined to cover all scenarios—we’ve implemented logic to trigger violations for all getter method cases where there is no permission check, SOQL, or DML operation and removed the previous conditional checks. As a result, violations will now be raised for every return type except void (since it doesn’t return any value). Please note that, due to these rule changes, there may be a slight increase/decrease in reported issues for the FLS rule. {% endhint %} We have verified the rule logic and validated that users are able to see the violations for the getter methods on SOQL, DML operations.
**2. Enhanced rule “Aura Controller Naming Convention” {Rule ID: sf:AuraControllerNaming}** Previously, CodeScan Controller Suffix in the rule Aura Controller Naming Convention was incorrectly case-sensitive. This meant that a violation was not triggered (expected behavior) when the suffix to controller (lowercase). However, if the class name instead included "Controller" (uppercase), a violation was being thrown (i.e., when we set ControllerSuffix = Controller). Verified the below scenarios and validated that both are working as expected: * ControllerSuffix = "Controller" * ControllerSuffix = "controller" Further verified the sf:AuraControllerNaming rule by setting ControllerSuffix = “Controller” in first run of Project and then changed ControllerSuffix to “controller.” Both projects triggered the same number of violations based on the provided data. **3. Updated the rule description for “God Class Rule” {Rule ID: sf:GodClass}** Description: The God Class rule detects the God Class design flaw using metrics. God classes do too many things and are very big and overly complex. They should be split apart to be more object-oriented.\ The rule uses the detection strategy described in "Object-Oriented Metrics in Practice". The God Class rule evaluates classes using the following three key metrics to determine size, dependency, and cohesion: 1. WMC (Weighted Methods Count): Measures the number and complexity of methods in a class. A high WMC indicates that a class has too many methods or overly complex behavior. 2. ATFD (Access to Foreign Data): Counts how many times a class accesses data from other classes. A high ATFD means the class is overly dependent on external data, reducing modularity. 3. TCC (Tight Class Cohesion): Represents how closely the methods of a class are related to each other. A low TCC suggests poor internal cohesion, meaning the class handles unrelated responsibilities. Every violation will include three metrics: (configurable): * WMC: default > 47 * ATFD: default > 5 * TCC: default < 1/3 (33%) The violations are reported against the entire class. {% hint style="info" %} Note: For more information, please refer to Michele Lanza and Radu Marinescu. *Object-Oriented Metrics in Practice: Using Software Metrics to Characterize, Evaluate, and Improve the Design*\ *of Object-Oriented Systems* {Springer, Berlin, 1 edition, October 2006. Page 80}. {% endhint %} Verified the Update God Class Rule Description and confirmed that users are able to see the updated description for the rule.
**4. Updated the rule descriptions for “CodeScan Other Rules” {Rule ID: cs-vf:unknown and Rule ID: cs-js:unknown}** We have updated the rule description for the rule "CodeScan Other Rules" rule key. Updated Description: This rule detects ESLint rule references written in code comments that are not currently recognized by the plugin. It helps identify placeholder or upcoming rules that may be added in future updates. We have verified the Rule Description Updates on “CodeScan Other Rules (cs-vf:unknown and cs-js:unknown) and confirmed that users are able to see the updated descriptions.
### Fixes **1. Fixed issue where issue page was not properly loading (under specific condition)** Several customers have reported that under the specific circumstance of: Pull request > select any branch/pr > code > open any file and click on any issue message Users are presented with a blank page instead of being redirected to the issue page. This issue has been fully remediated with this fix. Verified that users are now able to navigate to the Rule description page. Also verified that the “Why is this an issue link” (as well as other associated pages) are all working as expected.
*** ## CodeScan Release 25.1.12 **Release Date: 19 October 2025** ### Summary CodeScan 25.1.12 is comprised of the following 3 components: * 1 New Feature * 2 Fixes Component details are listed in their corresponding sections within this document. ### New Features **1. Better Management of CodeScan Orgs via Soft Deletion** **Description** With this release, when an Admin performs an organization deletion, the org is maintained for an additional 30 days to allow for restoration (if needed). However, please note that the org will immediately become inaccessible to all members, owners, and IDE users, and any tokens associated with it become expired. The deleted organization will remain in a disabled state for 30 days and can only be restored by an Instance-level Admin during this period. {% hint style="info" %} Note: This soft deletion is triggered (and subsequently put into this disabled state) whether deleted by an org Admin OR platform-level Admin. {% endhint %} We recognize that we can improve organization lifecycle management and data governance for our customers, while also reducing accidental data loss, by allowing Admins to restore orgs within 30 days. Once an organization is deleted: * It will become immediately inaccessible to all non-admin users (members, owners, IDE users). * All API tokens and access credentials associated with the organization will be expired. * The deleted organization will be listed under a new "Deleted Orgs" section visible only to Instance-level Admins. * The deleted org is in a disabled state and cannot be accessed, modified, or used in any IDE integrations. * Instance-level Admins can restore the organization within 30 days of deletion. * After 30 days, the organization is permanently deleted unless restored. * Customers can notify us in writing to forgo the 30 days and have the instance deleted immediately, which we will perform at their request **Value / Purpose** * Ensures security and compliance by revoking access and expiring tokens immediately upon deletion. * Provides control and flexibility to Instance-level Admins with a grace period for restoration. * Prevents data loss from accidental deletions. * Improves auditability and accountability in organization management. * Aligns with standard enterprise-grade administrative controls. {% hint style="info" %} Note: Instance-level Admins and Org Admins (customers) are able to manage deleted organizations in a dedicated “Deleted Orgs” section, so they can view and restore them within a 30-day grace period. {% endhint %} ### Fixes **1. Fixed issue where the IDE usage was not being captured properly** Several customers have reported that Admins are not able to see any details in the IDE Usage screen in their Org, while others reported that while they see the records, they do not see the records in Order. We have determined the root cause to be a JDBC exception and have fully remediated both of these issues with this fix. We have verified the fix via the following scenarios and confirm that Admins are able to see the correct records without any errors. 1. Admins can view all relevant details on the IDE Usage page after selecting the Individual tab.
2. Admins can also view the records displayed in the correct order under the All tab.
3. When the user selects "All" and filters the data for 120 days in the IDE Usage screen, the "Show More" option appears, allowing them to scroll down and view additional records from the last 120 days.
**2. Fix to AvoidAbsoluteURL Rule** We have witnessed that, periodically, this rule does not seem to pick up new Salesforce URLs. As such, we updated the rule logic to detect and violate URLs matching the following patterns: {{\*.salesforce.com}} {{\*.force.com}} {{\*.site.com}} {{\*.documentforce.com}} {{\*.marketingcloudapis.com}}. We have verified the fix of the AvoidAbsoluteURL rule via the following: 1. Updated the rule to detect and flag violations for URLs matching the following patterns: * \*.salesforce.com * \*.force.com * \*.site.com * \*.documentforce.com * \*.marketingcloudapis.com 2. We also verified that usage of any of the below URLs in the code now triggers a violation after activating the AvoidAbsoluteURL rule.

*** ## CodeScan Release 25.1.11 **Release Date: 5 October 2025** ### Summary CodeScan 25.1.11 is comprised of the following 5 components: * 2 Application Enhancements * 2 Rule Enhancements * 1 Fix Component details are listed in their corresponding sections within this document. ### Application Enhancements 1. **Update Project Analysis Subtitle Dynamically** Several customers have reported that, regardless of project analysis, each time a user attaches ANY analysis project to CodeScan, there’s a message that says, “Connects to your Salesforce instance.” We recognize that when using \*Project > Project Analysis\*, the subtitle should dynamically update to display the text: * When the user selects \*Salesforce\* as ALM, the label updates to show: \_“Connects to your Salesforce instance to execute a CodeScan analysis.” * When the user selects \*Repository (GitHub, Bitbucket, GitLab)\* as ALM for Project Analysis, the label updates to show: “Connects to your \[ALM name] Repository to execute a CodeScan analysis.” * Further, the label must update in real time upon ALM selection, without requiring a page refresh. This ensures the user clearly understands the connection purpose based on the selected ALM. {% hint style="info" %} NOTE: If we cannot update dynamically, CodeScan will use the following generic text: “Connects to your Salesforce instance or Repository to execute a CodeScan analysis.” {% endhint %} Verified the **Update Project Analysis Subtitle Dynamically** via the following scenarios: Verified for the existing projects and newly created projects (all project integrations). The user is able to see the updated static description on the project analysis page as expected: **“Connects to your Salesforce instance or repository to execute a CodeScan analysis.”**
2. **New Version of CodeScan VS Code Extension (v 2.1.2)** **Description** In the previous version of VS Code (2.1.1 and earlier), we had a reported bug: Issues that have been resolved in the UI are still showing in VS Code. In the past, these issues have been ignored and would be updated with a refresh of the connection. In this updated extension, we have implemented improved synchronization of resolved issues from the CodeScan server, which addresses the reported issue. * Verified the VS Code plugin for the following file types: .cls, .page, .java, .js, .trigger, .css, .ts, .cmp. * Violations are appearing as expected in both the CodeScan environment and the VS Code plugin. * The resolution actions—Accept, False Positive, Confirm, and Fixed—are functioning correctly. * Verified the same functionality in the US PROD environment, which is working as expected and consistent with the TEST environments. * Verified the VS Code plugin on the self-hosted environment. After the user refreshes the connection, the resolutions are displaying as expected. * Also verified on the **Self-Hosted** environments (SQ versions 25.1 and 25.2): * When the user sets an issue as False Positive or chooses to Accept the issue, the issue count is reduced on the UI as expected.
### Rule Enhancements 1. **Enhancement to “sf:AvoidLogicInTrigger” Rule** Historically, this rule finds any blocks of code in a trigger and throws a violation. In this enhancement, we added a parameter to the rule allowing users to add a comma separated list of trigger frameworks that are allowed. The new parameter is “allowedTriggerFrameworks.” Description: A comma separated list of Trigger frameworks to allow. Violations will still be reported if complex logic is present within the allowed parameters. For more information, please review an overview of triggerframeworks: Details of the new parameter: * Allow: * Trigger.is\* checks * Direct calls to whitelisted methods/properties (including inside conditions or assignments). * Flag: * Any iteration (for, while, do) in a trigger is a violation, regardless of whitelist. * Any non-whitelisted method calls. * Any direct DML, SOQL, or field logic. * Variables assigned from whitelisted methods used later in invalid contexts (like while(var)). Verified the new parameter on the sf:AvoidLogicInTrigger rule to ensure compatibility with trigger frameworks via the following scenarios: 1. Any control statement with {} (e.g., if, for, switch) in trigger body → Violation. 2. Exception: if that uses Trigger.is… → No Violation.\ However, if Trigger.is… appears inside a for loop, it’s still a Violation. 3. If a method is added to the rule parameter (allow-list) (e.g., checkPermission), then an if using it → No Violation. **But**: for, while, do-while, SOQL, DML → always Violation (allow-list does not suppress these).
2. **Enhancement to “Use Annotation on Test Class” Rule** During our routine testing of our rules, we noted that this rule is outdated, as it only detects the testMethod keyword. It does not work with the newer @IsTest annotation, causing missed violations in modern Apex test classes. **Fix**\ Updated the rule logic to support detection of @IsTest annotation on test classes, ensuring compliance with current Apex best practices. Verified the enhanced rule logic in “Use Annotation on Test Class” in the following scenarios: 1. A non-test class or Utility class without test methods → Verified: No violation raised. 2. @IsTest annotated class with test methods (@IsTest and/or testMethod) → Verified: No violation raised. 3. Class containing only testMethod methods without @IsTest → Verified: Violation raised. 4. Class containing only @IsTest methods without class-level @IsTest → Verified: Violation raised.
### Fixes 1. Fixed Application Issue where the “Issues Filter” was not working as expected with CWE tags. Several customers have reported that the Issues Filter does not work with CWE tags. Although individual issues correctly display their associated CWE ID, searching or filtering by a specific CWE ID in the Issues view will sometimes return no results. We have identified that the root cause of the issue was that the CWE filter for Issues and Rules was limited to display and filter through only 10 items in the filter dropdown. Therefore, we expanded the filter limit to display up to 100 items and enabled input-based search across all options for enhanced usability and consistency. **After extensive research, we concluded:** ***Rules page – CWE search*** * In the Rules page, only the first \~10 CWE entries show up under the search. Beyond those, no additional rules appear when searching by CWE. ***Issues page – CWE filter*** * Issues do show up for certain CWEs, but not consistently.\ Example: an issue mapped to CWE-470 appears, yet the same issue also mapped to CWE-80 does not appear when searching for 80. * When a rule/issue has multiple CWE values, the CWE filter on the Issues page sometimes returns results for only one of those CWE values, not all. ***Filter/search behavior*** * The CWE filter search bar does not call an API while you type. It only searches within the already-fetched list from the backend. * An API request is made only after you click/select a specific CWE from that list to load rules/issues for that CWE. ***Technical details (implementation)*** * standardfacet.tsx renders the CWE filter component; handleSearch manages the in-filter search behavior. * Standards.json lists CWE values and descriptions. Even after adding additional CWE entries into this file, those new values still don’t appear in the filter list. * Conclusion: The filter list is not driven solely by Standards.json, or it’s being constrained elsewhere. **Data/API status** * Database: Contains all rules with their full set of CWE values. * API: Works as expected when calling with cwe=\; results return correctly.\ The inconsistency happens only in the filter UI, so we should inspect the UI-side response and check for any server or client-imposed limits on the number of CWE results returned. We have remediated these issues with this fix. Verified the fix for “Issues Filter is not working with CWE tags” via the following scenarios. 1. Searching or filtering by a specific CWE ID in the Issues page under Security Category is working as expected.
2. Verified that the Show More button under the CWE filter works correctly, with the default filter count set to 15.
3. Even when the CWE filter is limited to the default 15 entries, searching for an ID like CWE-16 still returns the correct result for the user. *** ## CodeScan Release 25.1.10 **Release Date: 21 September 2025** ### Summary CodeScan 25.1.10 is comprised of the following 9 components: * 1 New Feature * 8 Rule Enhancements Component details are listed in their corresponding sections within this document. ### New Features 1. CodeScan now imposes verification logic on email signup to enhance security. Previously, users were able to register and log in without verifying their email. We recognize that this could potentially lead to the creation of fake or fraudulent accounts. In this release, we have implemented an email verification via unique links to a one-time verification link. Additionally, we have added logic that restricts access to functionalities for unverified accounts.\ \ Verified the Migrate email verification Rule to Action in Auth0 via the following scenarios:\ After signing up, the user receives a verification email. Only after successfully verifying the account, the user is able to log in to the instance as expected.
### Rule Enhancements 1. **Enhancement to sf:ServerSideRequestForgery Rule**\ As part of the CodeScan 25.1.2 release (June 2025), we added this new rule (Server Side Request Forgery). We have had several customers request an enhancement to this rule, as they reported that this rule was not catching all of the SSRF issues.\ \ As such, we have enhanced this rule to find all the sinks for these issues with concatenated URLs to all methods that take an HttpRequest as an input.\ \ This is the list of methods we have added as sinks (these are in addition to the issues that this rule is currently finding): * Http.send(HttpRequest) * HttpRequest.setEndpoint(String) * Continuation.addHttpRequest(HttpRequest) * PageReference.getContent()\ \ Verified that the rule ServerSideRequestForgery is throwing violations when the following methods are used in the code: * HttpRequest.setEndpoint(String) * PageReference.getContent()
2. **Enhancement to Resource Injection Rule**\ As part of the CodeScan 25.1.2 release (June 2025), we added this new rule (Resource Injection). We have had several customers request an enhancement to this rule, as they reported that this rule was not catching all of the issues.\ \ As such, we have enhanced this rule to find all the sinks for these issues with concatenated URLs to all methods that take an HttpRequest as an input.\ \ This is the list of methods we have added as sinks (these are in addition to the issues that this rule is currently finding): * Http.send(HttpRequest) * HttpRequest.setEndpoint(String) * Continuation.addHttpRequest(HttpRequest) * PageReference.getContent()\ \ Verified that the rule Resource Injection is throwing violations when the following methods are used in the code: * HttpRequest.setEndpoint(String) * PageReference.getContent()
3. **Enhancement to “Switch Statements Should Have a When Else Case” Rule**\ Currently, the rule is not working as expected, as it does not raise violations when a switch statement lacks a when-else block. We have modified that logic to correctly identify switch statements that are missing a when-else case so that users can ensure the code is more robust, future-proof, and does not miss handling unexpected cases.\ \ Example:
Verified that the updated rule now correctly flags switch statements without a when-else block, ensuring violations are raised consistently for missing default cases.
4. **Enhancement to “Avoid Reversed Operators” Rule**\ Modified the rule logic to correctly detect and report improper usage of reversed operators (=-, =+) in Apex code, so that users can avoid mistakes where variables are unexpectedly reassigned rather than incremented/decremented.\ \ **Current Behavior:** * Violations are not raised when using reversed operators like target =- num; or target =+ num;.\ \ **Expected Behavior:** * The rule should detect and flag cases of reversed operators (=-, =+) and provide a clear violation message. * The violation message should explain the confusion: * x =- y; assigns -y instead of subtracting. * x =+ y; assigns +y instead of adding. This new logic will prevent developers from introducing subtle logic bugs caused by operator misuse. Further, we updated the rule example with the following:
Verified the new logic via the following scenarios:\ 1\. Rule sf:AvoidReversedOperators raises violations for reversed operator cases (=-, =+). 2\. Rule does not raise false positives on valid operator usage (+=, -=).
5. **Enhancement to “CouplingBetweenObjects” Rule**\ Modified the rule logic to correctly detect and report violations so that users can identify classes with excessive dependencies and reduce code complexity for better maintainability and testability.\ \ Verified that the violation is triggered when the number of classes used exceeds the defined threshold value in the rule parameter (for example, if the threshold is set to 4 and 5 classes are used, a violation will be raised).
6. **Enhancement to “Avoid Insecure Digest Algorithms” Rule**\ Enhanced the current rule logic to correctly raise violations when MD5 or SHA-1 algorithms are used. Since these algorithms are cryptographically broken and vulnerable to hash collision attacks, their continued use poses a security risk.\ \ The rule should: * Detect any instance or usage of MD5 or SHA-1 for hashing/digesting. * Report violations with clear remediation guidance. * Suggest secure alternatives such as SHA-256 or SHA-512. \ \ Verified the new logic via the following scenario:\ Validated that users are able to see a violation for the rule *AvoidInsecureMessageDigests*. This violation indicates the use of insecure message digest algorithms such as MD5 or SHA-1.
7. **Enhancement to “Add Empty String” Rule**\ Updated the rule logic to identify and flag expressions where literals are concatenated with an empty string (e.g., "" + 123 or 123 + ""). Also ensured that violations are reported with a clear message and that valid concatenations and type-specific toString() methods are not falsely flagged.\ \ Verified the below scenarios all are working as expected.\ 1\. Empty string with numeric or Boolean literals\ Examples:\ '' + 123, 123 + '', '' + -42, '' + 3.14, false + '', '' + true\ \ 2\. Empty string with string/char literals or inside chains\ Examples:\ '' + 'abc', 'abc' + '', 'A' + '' + 'B', 1 + '' + 2\ \ 3\. Empty string literals inside parentheses\ Examples:\ ('' + 1) + 2, 1 + ('' + 2)\ \ 4\. Empty string at start of long chain with literals and variables\ Example:\ '' + 123 + 987 + var1 + var2\ \ 5\. Empty string used with - operator and literals\ Examples:\ '' - 123, 123 - '', '' - -42
8. **Enhancement to “Avoid Hard-Coded Resource References” Rule**\ Enhanced the rule logic to identify hard-coded file path references and raise violations with a clear issue message.\ \ Validated the logic by verifying that users are able to see the violations for the use of the attribute value that starts with '/resource/'.
*** ## CodeScan Release 25.1.9 **Release Date: 07 September 2025** ### Summary CodeScan 25.1.9 is comprised of the following 4 components: * 2 Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### Enhancements 1. Enhancement to Suppress Warnings Rule Our rule TrackSuppressWarnings had logic to find @SuppressWarnings, but the logic didn’t include find @suppresswarnings. This suppression tag works in any case and we recognized that our TrackSuppressWarnings rule needs to do the same (meaning the rule needs to be case insensitive.) This logic was added to this rule in this enhancement. Verified the SuppressWarnings Rule enhancement and validated that the suppression tag is working in all case-insensitive instances and our TrackSuppressWarnings rule is throwing violation for all cases.
2. Rule Enhancement for sf:UnusedFormalParameter In this rule enhancement, we introduce a configuration flag (ignoreUnusedParametersInInterfaceOverrides) in the sf:UnusedFormalParameter rule so that unused parameters in valid interface implementations and method overrides can be conditionally suppressed. By default, violations will continue to be reported unless this flag is explicitly set to true. **How to Identify These Parameters for Suppression** When designing your rule improvement, the logic should: 1\. Check if the method is implementing a known Salesforce interface method: * Use method signature matching (name, parameters, visibility). * Confirm the containing class uses implements keyword for one of the known Salesforce interfaces. * Ensure parameter types match exactly, e.g., SchedulableContext, Database.BatchableContext.
2. Visibility Enforcement * Only suppress violations if the method visibility is public or global, as required by the platform. * Private or protected methods should never be eligible for suppression under this rule. * This ensures that suppression only applies to methods actually callable by the platform or conforming to Apex interface rules. 3\. Override Detection * If a method in a class overrides a method from a superclass or an abstract class: * Signature match is mandatory (same name, return type, and parameters). * Use of the override keyword confirms the intent, but even without it, structural matching should be enough. * In such cases, the parameter should not be flagged if unused, since it’s required by the parent contract. Value / Purpose * Prevent misleading or incorrect violations in valid interface and override implementations (e.g., execute \[SchedulableContext]). * Preserve backward compatibility by keeping the rule strict by default. * Additionally, we updated the Rule Description to “Avoid passing parameters to methods or constructors without actually referencing them in the method body. Use the ignoreUnusedParametersInInterfaceOverrides parameter to suppress violations for unused parameters in valid interface implementations and method overrides.” Verified the rule sf:UnusedFormalParameter and validated the following conditions: * The method implements a known Salesforce interface method. * Method signature matches exactly in terms of: * Name * Parameters * Visibility * The containing class uses the implements keyword with one of the known Salesforce interfaces (e.g., Schedulable, Database.Batchable). * Parameter types match exactly, including types such as: * SchedulableContext * Database.BatchableContext
### Fixes 1. Fixed issue with CodeScan rule detecting SOQL Injections, which was causing analyses to break. Previously, while analyzing for SOQL Injection, if a local variable is declared using a class-level variable of same name, then CodeScan analyses were erroring with StackOverflowError as it was stuck in a loop while resolving the reference. Example: class Foo { private static String QUERY = 'Select '; public static List\ getData(String stage) { String query = QUERY + 'Id FROM Opportunity WHERE StageName = :stage'; return Database.query(query); } } With this fix, we added validation to detect and prevent such recursive reference resolution. Verified the SOQL injection rule fix (which was causing stack overflow error) by validating that now users are not encountering the error, and their project analyses are working as expected.
2. Fixed an Error that was occurring when Deleting CodeScan Projects Some customers have reported that when attempting to do a project deletion, the task sometimes fails. We have determined that the root cause is that the system is trying to fetch project details after the project has already been removed, which leads to missing information and, subsequently, unexpected errors. This fix includes logic to delete projects properly. We have verified the fix for Error When Deleting CodeScan Projects and validated that users are able to delete their projects without any errors.
*** ## CodeScan Release 25.1.8 **Release Date: 31 August 2025** ### Summary: CodeScan 25.1.8 is comprised of the following 1 component: * 1 Fix Component details are listed in their corresponding sections within this document. ### Fixes 1. Fixed issue where CodeScan Project Analysis jobs getting stuck at "finalizing" stage. Previously, CodeScan project analysis jobs were getting stuck at "finalizing" stage, and not returning the result to GitHub PR, thus blocking all PRs. The root cause of the issue was that db-pool-limit-reached was occurring. This fix remediates this issue. After applying the fix, we validated the fix by creating jobs with alternating pass/fail quality gate statuses. Once the fix had been applied, we observed all jobs completing successfully (without getting stuck)\ \ We also verified the below Audit log cases: Verified the category "PROJECT\_ANALYSIS" and checked the below details that are stored in the logs all are appearing as expected. * Project Names * Project Keys * Lines of code count - split by ncloc languages * Created date * First analysis date Also, Verified the category Quality Gates and checked the below details which are stored in the logs all are appearing as expected. * operation": "UPDATE", * propertyValue": "Failed/Passed” * createdAt": “\*\*\*\*\*” * componentKey * componentName\ componentUuid
*** ## CodeScan Release 25.1.7 #### Release Date: 24 August 2025 ### Summary CodeScan 25.1.7 is comprised of the following 5 components: * 1 New Feature * 4 Fixes Component details are listed in their corresponding sections within this document. ### New Features 1. Enable/Disable feature of Mapping to multiple orgs from one SAML Connection at instance level. {% hint style="info" %} *NOTE: This feature is only available to customers who have a dedicated instance. It is not available for customers who are deployed on our SaaS multi-tenant instances.* {% endhint %} This new feature enables customers to map to multiple orgs from one SAML Connection at their instance level. Verified the following scenarios for SAML users, and all scenarios are working as expected. 1. Verified the User when CodeScan idp-group-mapping is disabled, user is able to log in through SSO when the Group synchronization and IDP mapping is not used. 2. Verified the User when CodeScan idp-group-mapping is disabled, user is able to log in through SSO when the Group synchronization and IDP mapping are used. 3. Verified the User when CodeScan idp-group-mapping is enabled, user is able to log in through SSO when the Group synchronization and IDP mapping are used. 4. Verified the User when CodeScan idp-group-mapping is enabled, user is able to log in through SSO when the Group synchronization and IDP mapping are not used. 5. Validated the SAML connection creation and login through SSO in the created Org. 6. Validated the SAML connection creation and login through SSO with the other Org. 7. Created a new user and checked the login through SSO with the same above SAML config. 8. Verified the IDP group mapping where the user is mapped to the organization where SAML connection is created. {% hint style="info" %} *NOTE: This feature needs to be enabled in customers’ organizations. It is NOT available by default* {% endhint %} {% hint style="info" %} *NOTE: This feature is only available to customers who have a dedicated Instance. It is not available for customers who are deployed on our SaaS multi-tenant instances.* {% endhint %} ### Fixes 1. **Fixed Broken Documentation Link in Status Module** It has been reported that the "Status" module in all CodeScan application contains a broken documentation link: \ This link provides users with detailed information on the lifecycle of issue statuses but currently leads to a nonexistent page. The correct, working link should be: \ This fix remediates this issue in full. Verified the fix by confirming that the documentation link under the "Status" tab in the Issues module has been updated and now redirects to the correct Knowledge Base page. \ The link is updated to [About Issue Status | AutoRABIT Knowledge Base](https://knowledgebase.autorabit.com/product-guides/codescan/issues/about-issue-status)
2. **URIs are not Valid in decorated SARIF output** It has been reported that the URLs are not valid in the SARIF file due to spaces. To remediate, we added logic to make certain that they are escaped. Verified that users are now able to see valid URLs in the SARIF report even when the file names include underscores, numbers, hyphens, special characters, with spaces.
3. **Fixed issue where scheduled analyses are not running for SF projects and its comparison branches** Several customers have reported that their daily scheduled analyses were not running for Salesforce integration projects and their corresponding comparison branches within the same project. We determined that the Scheduled Jobs were getting stuck, even though they were consuming memory and CPU. Further, we identified that the root cause of the issue stemmed from changes made in the previous release (25.1.6), and that scheduled jobs on our AWS infrastructure were running into “out-of-memory” issues. This fix remediates this issue in full. Verified the fix and validated that the scheduled jobs are now running without issue (as expected).
4. **Fixed issue with deleting branches in projects using Salesforce Integration** We uncovered that if the following steps were performed… 1\. Launch and log in to the CodeScan application and be on any org.\ 2\. Create Salesforce project.\ 3\. Create comparison and standard branch analysis.\ 4\. Try deleting comparison branch. …then users receive an error message indicating that an “unknown error occurred.”
This issue has been fully remediated in this release. We have verified the fix and have validated that the following scenarios are all working as expected:\ \ 1\. Verified salesforce comparison branch deletion.\ 2\. Verified creation of project with user having (create and analyze project permissions).\ 3\. Renaming of project branch.\ 4\. ALM project tags working as expected. *** ## CodeScan Release 25.1.6 **Release Date: 3 August 2025** ### Summary CodeScan 25.1.6 is comprised of the following 6 components: * 1 New Feature * 3 Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### New Features 1. **Categories for Project Types** Often, customers will have a lot of projects in CodeScan. Several customers have requested the ability to filter their projects by the type of integration including: GitHub: github\ Bitbucket: bitbucket\ GitLab: gitlab\ Git: git\ Salesforce: salesforce To deliver this feature, we created custom tags with the ability to add these tags when new projects are created. Unlike most tags, we designed integration type tags to remain once assigned. If the user tries to remove it the following error will occur: “Integration type tags cannot be removed from projects.” NOTE: Due to the change in permissions needed in the API for these tags to be added, we also adjusted the text in the API doc as well. For the endpoint api/project\_tags/set the text now states: “Requires the ‘Administer’ or ‘Create Project’ permissions on the specified project.” Here are the tag API references: [CodeScanCloud](https://app.codescan.io/web_api/api/project_tags) Verified Categories for Project Types in the following scenarios, and have verified that all are working as expected: 1. **Verify that the user is able to see the correct tag for the project on the Project Information page after completing the analysis.**\ *Example: For a Salesforce integration, the tag should display as “Salesforce.”*
2. **Verify that the user is able to see the correct tag for each project integration under the "Tags" column in the Projects tab of the organization.**\ *Example: For a Salesforce integration, the tag should display as “Salesforce.”*
3. **Verify that the user is able to see the correct tag for each project integration under the "Tags" column in the My Projects tab.**\ *Example: For a Salesforce integration, the tag should display as “Salesforce.”*
4. **Verify that the user is not able to remove an existing tag or add a tag of a different integration tag to the project.**
5. **Verified that clicking on a tag correctly displays the associated projects, with accurate project count and correct project listings.**
### Enhancements **1. Users getting error when trying to restore quality profiles.** Currently, when a Quality Profile import fails, CodeScan displays the following error: *"An error occurred. Please contact your admin."* We recognize that it would be a better experience (and more helpful) to make this error more verbose to allow the customer to remediate the issue themselves. Mostly these errors are thrown because of a rule present in their Quality Profile which is not present in their organization. In these cases, the error message is now “An error occurred. A rule in your Quality Profile is not available in this organization.” The second most common error occurs when the QP is corrupted or malformed. In these cases, the error message now states “An error occurred. The Quality Profile backup is malformed. Please export your Quality Profile again.” We believe that these more verbose error messages will help our customers remediate their issue much more easily. However, if they require assistance, they can create a support ticket. Verified this enhancement via validating the below scenarios 1. If a malformed QP (with no profile name/language) is imported, an error message is shown.
2. When importing a QP with custom rules from another instance, those custom rules are also created during import. 3. If the imported QP has no profile language, the error message says: "Profile language should be set."
4. If the QP has no profile name, the error message says: "Profile name should be set."
5. If no file is selected during import, an error occurs.
6. If the repository key is missing, an import error is triggered. 7. If a QP with profile name CodeScan way/CodeScan strict way/CodeScan nCino way name is imported, an error is thrown.
**2. Pagination in Projects and Previous Analysis** To provide a better experience, we have added separate pagination controls, allowing users to navigate Projects Analysis and Previous Analysis sections more easily. This enhancement includes Projects Analysis displaying 10 entries per page and Previous Analysis displaying 15 entries per page. This allows the user interface to remain responsive and readable even when there are many entries. Verified the Pagination enhancement via validating the following scenarios: 1. The *Projects Analysis* section displays a maximum of 10 entries per page.
2. The *Previous Analysis* section displays a maximum of 15 entries per page.
3. Pagination controls (e.g., next, previous, specific result numbers) are present and functional in both sections independently. **3. Email Limit & Validation for Multi-User Invites** To improve the user experience for admins inviting users to their CodeScan org, we have implemented the ability to invite multiple users at once (up to 50) using the same user type (Standard User or Platform Integration User). Additionally, this enhancement ensures that only valid email addresses are accepted in the batch. This ensures that the invite experience remains consistent and controlled; additionally, user onboarding will be faster and more efficient. Further, Admins are still able to maintain control over user type classification, email validation, and system performance. The main components of this enhancement are: 1. Added each email on a new line. * Text was added in UI beside Email option for multiple users invite option. 2. Add the following error during limit exceeded scenario: “Invite limit exceeded. Max 50 emails allowed.” Value / Purpose: * Streamlines onboarding by allowing multiple users to be invited in one action. * Maintains role clarity by restricting each batch to a single user type (Standard or Platform Integration). * Improves system integrity and reliability by validating email format and capping batch size. * Prevents errors and abuse by limiting the invite size to a maximum of 50 and checking for valid emails only. We have verified the enhancement for Email Limit & Validation for Multi-User Invites by validating the following scenarios: 1. Verified that if invite is sent to more than 50 members, then the following is thrown:
2. Invite sent successfully if invite is sent to less than or equal to 50 users.
3. Verified, if mail address is more than 100 characters, then an error is thrown; if it is less than 100 characters, then the invite is sent successfully.
4. If invite sent to non-corporate domains, the following error is thrown:
### Fixes 1\. Align CSV Export filter status with Latest SQ Issue status This enhancement implements issue status values in the CSV export filters to reflect the latest status terminology introduced after CodeScan 25.1.0 release (which occurred in April 2025). Prior to this enhancement, the filters in CSV Issue Export were showing outdated statuses such as Opened, Confirmed, ReOpened, Resolved, and Closed. This was in contrast to the updated statuses including Open, Accepted, False Positive, Confirmed, and Fixed. This inconsistency was reported by several users who cited confusion and data integrity issues when analyzing or reporting exported results. Value / Purpose: * Ensures consistency between issues UI and CSV exported data. * Improves user trust and understanding of exported scan results. Acceptance Criteria * Status Values in Export: * Legacy Status Replacement: * Filter Cleanup: * UI-CSV Consistency: * Backward Compatibility: * * Existing historical issues should reflect the new status names in the export, even if their status was stored using legacy labels. Verified this enhancement by validating the following scenarios:
1. Status Values in Export: The issue statuses in the exported CSV must match the latest values of Open, Accepted, Confirmed, False Positive, and Fixed\ Legacy Status Replacement: * Legacy status values such as Opened, Confirmed, ReOpened, Resolved, and Closed must no longer appear in the exported CSV. * These must be correctly mapped to the corresponding updated status where applicable.
2. Filter Cleanup: The Resolutions filter should be completely removed from the CSV Export page. The Is Resolved filter should be completely removed from the CSV Export page. Only the Status filter should be visible and functional.
3. UI-CSV Consistency: The status shown in the exported CSV for each issue must exactly match what is shown for the same issue in the UI. 4. The type, statuses and severity shown in the exported CSV is exactly matching what is shown in the issues page and CSV export page.
2. Fixed an unclear error message displayed when invite is sent only to non-corporate email addresses This fix addresses an unclear message that occurs when: * Admin clicks on "Invite user" * Admin enters only non-corporate email addresses (e.g., Gmail, Yahoo) * Admin clicks "Send Invitation" After these steps, Admin receives the following unclear error message:
However, this issue does not occur when multiple users are invited, including at least one corporate email:
This issue has been fully remediated. We have verified the fix via the following scenario:\ \ Validated that the proper error message is displayed when invite is sent only to non-corporate email addresses.
*** ## CodeScan Release 25.1.5 **Release Date: July 20, 2025** ### Summary CodeScan 25.1.5 is comprised of the following 17 components: · 4 New Features · 2 Enhancements · 4 Fixes · 1 Revenue Org Improvement · 6 Architecture Improvements Component details are listed in their corresponding sections within this document. ### New Features 1. **Support Intelligent Prompts for A.I. LLMs** CodeScan can now generate prompts for LLMs including Agentforce, Copilot, ChatGPT, and Claude AI. This feature is a component of the CodeScan extension for VS Code. Requirements: Your CodeScan environment must be running version 25.1.5 (or higher). In addition, you need to be running the latest version of the CodeScan VS Code extension (v 2.1.1), which can be downloaded here: What Problem Are We Solving? Adoption of AI can be challenging for companies for several reasons. CodeScan can help catalyze your AI initiatives. User Benefits • Generate prompt in the IDE • Directly update existing code with generated code • Ensures security issues are addressed Verified Intelligent Prompts for cls, page, component, trigger, and cmp files, all working as expected by validating the below scenarios: 1\. Able to click generate prompt and copy it
2. Able to paste the generated prompt in the Agentforce search box
3. Able to receive the message prompt copied to clipboard after generating prompt.
4. Able to receive a message stating that the file is too long; please select the impacted lines of code and click "Generate Prompt" if the selected file has more than 1,000 characters.
5. Able to copy the code generated by Agentforce as expected
{% hint style="info" %} Notes: If the file content isn’t too long (less than 1000 characters) the \ placeholder gets the contents of the entire file. Else, only selected items will be passed (needs to be selected manually by the user). This is intentional because although Salesforce maintains that Agentforce’s input limit is 27k, we have discovered that when we do pass large code in the prompt the response generation is only for the first few lines (around 1000 chars) then stops (causing the response to be incomplete). {% endhint %}
2. **CVSS Implementation for Security Vulnerabilities** The Common Vulnerability Scoring System is a technical standard for assessing the severity of vulnerabilities in computing systems. Scores are calculated based on a formula with several metrics that approximate ease and impact of an exploit. Scores range from 0 to 10, with 10 being the most severe. In this release, CodeScan has applied this quantitative scoring to all security vulnerabilities, allowing organizations to more systematically prioritize the security remediations. *The following metrics were used to generate our CVSS scores:* Base Score Metrics * Attack Vector (AV) (specify) * Attack Complexity (AC) (specify) * Privileges Required (PR) (specify) * User Interaction (UI) (specify) * Scope (S) (specify) * Confidentiality Impact (C) (specify) * Integrity Impact (I) (specify) * Availability Impact (A) (specify) Temporal Score Metrics * Exploit Code Maturity (E) (specify) * Remediation Level (RL) (specify) * Report Confidence (RC) (specify) Environmental Score Metrics * Modified Attack Vector (MAV) (specify) * Modified Attack Complexity (MAC) (specify) * Modified Privileges Required (MPR) (specify) * Modified User Interaction (MUI) (specify) * Modified Scope (MS) (specify) * Modified Confidentiality Impact (MC) (specify) * Modified Integrity Impact (MI) (specify) * Modified Availability Impact (MA) (specify) * Confidentiality Requirement (CR) (specify) * Integrity Requirement (IR) (specify) * Availability Requirement (AR) (specify) *Verified the CVSS range from 0 to 10, where users are able to see the CVSS violations for the below rules as expected.* 1. OpenRedirect 2. CustomFieldSecurityInStandardObject 3. SOQL Injection 4. FieldLevelSecurity
Verified the CVSS Category on RULES page, ISSUES page and also verified the CVSS issues for the specific analysis.
**3. When encountering an Incorrect Custom XPath rule, CodeScan Analysis continues** Currently, if a customer’s Xpath Rule has incorrect XPath syntax, an error is shown in the analysis log and no further checks are run on the file that the custom rule was being applied to. We decided to make this more visible to users, as there was no further explanation of skipping the file outside of reviewing the associated logs. Instead, users would see the issues disappearing from their files. In this release, the following improvements were added: * one incorrectly formatted custom rule shouldn’t stop the processing of all rules on a file * created a project level rule that triggers a violation when this issue occurs * implemented the logic for a project level violation that appears when this issue occurs * created an associated message: “The custom XPath rule {rule key} failed to parse. Your {language} files were not able to display this issue. Please check your custom rule in the rule designer before your next analysis” 4. **Define User Type While Inviting or Adding Member** CodeScan now allows admins to define the user type when inviting or adding a member (either "Standard User" or "Platform Integration User"). This ensures that each user is onboarded with the appropriate role, purpose, and permissions. \ Since the system now allows for the designation of users as either Standard Users or Platform Integration Users during the invitation or member addition process, admins are now able to manage users more effectively (and thereby Ensuring Standard Users have the appropriate access (All the features of CodeScan), and Platform Integration Users are recognized distinctly for integration IDE purposes (or similar integration purposes). Value / Purpose: * Improves access control by ensuring correct user roles at the point of entry. * Differentiates Standard Users from Platform Integration Users for better tracking and reporting. * Enhances audit logs, billing accuracy, and license management. * Reduces post-invite administrative tasks by setting the correct user type up front. * Supports security and compliance needs by maintaining a clear separation between user types. Verified the ability to define User Type While Inviting or Adding Member by validating the below scenarios: 1. Admin must be able to select the user type ("Standard User" or "Platform Integration User") when inviting or adding a member. 2. The user type selection must be a required field.
3. "Standard User" should be the default selection.
4. Selected user type must determine the role and permissions automatically: * Standard Users get full access to all CodeScan features.
* Platform Integration Users get limited access scoped to integration IDE tasks.
5. User type must be clearly labeled in the member management.
6. “Platform user cannot be added to the Owner group.” — should be displayed when the Owners group is selected for a Platform user. Additionally, the Send Invite button should be disabled in this case.
7. For multi-user invites, the flow should be the same as for a single invite. Invites can be sent in batches, but only for one user type at a time.
8. Able to see the standard and platform user type while adding a member to the organization
### Enhancements 1. Add ESLint rules from @lwc/eslint-plugin-lwc CodeScan has traditionally provided ESLint rules within our rules library. Separately, Salesforce has an official ESLint plugin to analyze LWC code:. The rules in this plugin are different to our current set and expand on it; expanding the rules in our LWC set is vital to support the needs of our customers using Lightning Web Components. Our aim was to include all rules from the GitHub - salesforce/eslint-plugin-lwc: Official ESLint rules for LWC repository added to our current list. However, there are a few rules from this plugin that were not included. Rules that weren’t added as part of LWC set: * Disallow duplicate class members (no-dupe-class-members). This wasn’t added because it’s a Deprecated Rule Additionally, we did not include these 3 rules because of the Complex Parameter Type: * Enforce wire adapters to be used with wire decorator (no-unexpected-wire-adapter-usages) * Disallow usage of unknown wire adapters (no-unknown-wire-adapters) * Disallow access to global browser APIs during SSR (no-restricted-browser-globals-during-ssr) Note that all of these LWC rules were added to our Salesforce Lightning Quality Profile. Verified the Add Eslint rules from @lwc/eslint-plugin-lwc for the below scenarios:\ \ 1\. Verified the 21 rules from the [GitHub - salesforce/eslint-plugin-lwc: Official ESLint rules for LWC](https://github.com/salesforce/eslint-plugin-lwc) repository added to our Salesforce Lightning Quality Profile of javascript language.\ \ 2\. Verified the Description, Rule Details, Type of issue, Remediation function, Severity for all the rules.\ 3\. Verified that new rules is not included in the default Quality Profile.\ 4\. Verified that violation is thrown for all the 21 rules.
2. Enhancement to Apex rule “Unused Formal Parameter” {sf:UnusedFormalParameter} CodeScan has offered this rule since Dec 2017. Recently a customer reported that Unused Formal parameter doesn’t find when variables used in SOQL. We replicated this issue where CodeScan flagged a variable as an unused variable even though it is used in the SOQL string. We have enhanced this rule to detect additional cases where string parameters are part of SOQL. The rule now detects cases where string params are used as part of building soql query. Verified the enhanced logic of rule “UnusedFormalParameter” via the following scenarios.\ \ 1\. Previously, a parameter (e.g., encounterIds) used in a SOQL string (e.g., WHERE Id IN :encounterIds) was wrongly reported as unused.\ Now, this is correctly detected as usage — no violation.
2. Also verified below cases all are working as expected Verified: Parameter used in SOQL with bind variable (:encounterIds) — no violation Verified: Parameter used via clause string assembly — no violation Verified: Parameter incorrectly concatenated into SOQL string — violation Verified: Parameter declared but not used anywhere — violation
### Fixes 1. **Fixed issue ARM users recieving an error: “Component can't be null” while running a CodeScan analysis from ARM.** The issue is occurring in the SFDX retrieval. From ARM, when the user commits only the fields (or, for example, lookup fields), the .object-meta.xml is not retrieved. As a result, the retrieved file structure differs from what was expected. After analysing the rule’s implementation, it was found that the rule does not check if the .object-meta.xml file exists first and forcibly tries to throw the violation on the file. Hence, the "component can't be null" error is thrown. This required an engineering fix in the rule. Note: The issue lies in one of the common methods many rules use, so this error is not confined to these two rules. Other rules that use this method include:
With this fix, users are now able to see the violations for all 7 rules when running a CodeScan analysis from the ARM side using the CodeScan plugin: #### Rules: sfmeta:CrossObjectFormulaOveruse sfmeta:ObjectLookupsOveruse sfmeta:RelationShipOveruse sfmeta:ExternalIdOveruse sfmeta:RollUpOveruse sfmeta:LimitCustomFields sfmeta:nCinoFieldHistoryTracking Verified by committing only specific fields and triggering SCA analysis — violations appeared as expected. **Ran analysis for the entire Salesforce org, including objects — violations were also detected."**
2. **Fixed issue where after a user is deactivated, the user is still displayed on Members page** Some users were reporting that after a user is deactivated, the user is still displayed on the Members page. **Detailed Solution** 1. Made changes in the codebase to remove the user from members table when the user is deactivated. 2. Enusresd that using “search” on the Members page only active users are retrieved. 3. The user is no longer able to login via SAML Verified the below scenarios regarding users being displayed in Members page, and all scenarios are working as expected. 1. Create and Activate New User- User appears under the Members list of the active organization 2. Add User to Inactive Organization- User is visible under the Members list of the inactive organization 3. Deactivate User from Instance- User no longer appears in the Members list. Behavior confirms that deactivated users are excluded from the UI display 4. Verify SAML Login for New User- Authentication via SAML was successful 5. Billing Page User Count Verification- User count reflects the new user addition appropriately. Billing data is updated as per user assignments 3. **Fixed issue with rule “Avoid running Soql and DML inside loops” {sf:AvoidSoqlInLoops}** Recently, some customers reported unexpected behavior in this rule, producing false positives. The root cause of the false positives is that when a method of an object is invoked within another method, and both methods share the same name, the current rule implementation incorrectly interprets this as a recursive call and subsequently triggers a violation. Further, the Stack Loop trace is indefinite. This had been remediated in a previous release (25.1.2 release in June 2025). The updated rule logic now handles these edge cases by checking for method image to be exactly the same (method != diffObj.method). However, there’s more to this issue and fix! A scenario which was earlier covered stopped working as expected as a result of the fix made above. This new issue was reported to us, and has been fully remediated in this release by adding additional logic to the rule implementation was made to accommodate both scenarios (the pre-existing condition but also indefinite stack loop trace). Verified the Fix for rule sf:AvoidSoqlInLoops via several scenarios, including: Verified – SOQL inside a method (not directly in a loop) — no violation as expected Violations Expected for the below scenarios 1. Verified SOQL directly inside a for loop — got violation as expected
2. Verified SOQL inside nested if blocks within a loop — got violation as expected
3. Verified SOQL inside a try/catch block within a loop — got violation as expected
4. Verified SOQL in a method (or recursive call) invoked from a loop — got violation as expected
5. Verified SOQL in static helper method called from a loop — got violation as expected
6. Verified SOQL inside a while loop — got violation as expected
7. Verified SOQL inside a do-while loop — got violation as expected 8. Verified SOQL directly inside System.debug() within a loop — got violation as expected
**No Violations Expected for the below scenarios** 9. Verified Bulkified SOQL outside the loop (e.g., IN :ids) — no violation as expected 10. Verified SOQL in deep conditional logic but not inside a loop — no violation as expected 11. Verified SOQL inside try/catch block, not inside a loop — no violation as expected 12. Verified SOQL in method not called from a loop — no violation as expected 13. Verified SOQL inside interface/abstract method (called via polymorphism from loop) — no violation as expected 14\. Verified SOQL inside constructor called from a loop — no violation (as expected for shallow analyzers) 4. **Fixed issue regarding restricted access for CodeScan Platform Integration Users** Some users were reporting that their platform integration users has the same accessibility to CodeScan as their standard users. This issue is remediated in this release. As a PIU (Platform Integration User) with restricted access in the CodeScan platform, PIU should only be able to view the Account section after logging in. All other features like Project Analysis, Project View, Issues View, and Search etc. (All except Account Section) should be inaccessible. Within the Account section, PIU should see the following tabs: * Profile * Security * Notifications * Projects * Organization
Additionally, the Help and Profile sections in the header should remain accessible. When clicking on the Profile icon, a pop-up should appear displaying (As shown in attached images): * Username, Email * My Account * Logout Option
Verified Restricted Access for CodeScan Platform Integration User by validating the following scenarios: 1. Verified all integration project analysis and PR analysis as a Standard user. 2. Verified all IDEs as a Platform user. 3. Verified IntelliJ, VS Code, GitHub Actions, SFDX, Sonar Scanner, and Azure as a Standard user. 4. Platform users should have access only to the My Account page.
5. Platform users should only be able to view the Projects and Organizations tabs—no actions should be permitted.
6. Both Standard and Platform users should have: * The Help section is accessible in the header.
* The Profile section is accessible in the header.
7. On clicking the Profile icon, the Platform user should be able to see: * Username * Email * My Account * Logout option 8\. Verified Billing & Revenue Compliance for both Standard and Platform users. 9. Users who are Standard users in some organizations and Platform Integration users in other organizations should be shown the homepage of the organizations where they are Standard users upon login. 10. If Standard users do not have any homepage, they should be shown the My Projects page (All Projects), which should only display projects from the organizations where they are Standard users.
11. User type and UI should be organization-specific. If a user switches between organizations, the UI corresponding to their user type in the selected organization should be displayed.
12. If Standard users do not have any homepage, they should be shown the My Issues page (All Issues), which should only display issues from the organizations where they are Standard users.
*** ## CodeScan Release 25.1.4 **Release Date: 6 July 2025** ### Summary CodeScan 25.1.4 is comprised of the following 6 components: * 1 New Features * 3 Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### New Features 1\. Support for Enterprise Git Connections / Configuring & Managing ALM Integrations In CodeScan, Enterprise Git Connections enable organizations to securely integrate with self-hosted or enterprise instances of GitHub, GitLab, and Bitbucket. Admins can configure these connections at the organization level using OAuth credentials and define allowed IP ranges for secure access. Once connected, these integrations streamline project onboarding by allowing users to directly link Git repositories during project setup for automated analysis and CI/CD workflows.

ALM Connections

More detailed info can be found in our Knowledge Base here: ### Enhancements 1\. Enhancement to CodeScan Rule “URL Redirection to Untrusted Site” {sf:OpenRedirect} CodeScan has traditionally used this rule to check against redirects to user-controlled locations. This is important because untrusted input could cause an attacker to redirect the user to a malicious site, thereby allowing the attacker to launch a phishing scam and steal user credentials.
However, our existing rule did not specifically check for the use of Network.forwardToAuthPage.
This rule has now been enhanced with this logic, and we have verified that users are now able to see the violation for the use of both Network.forwardToAuthPage and PageReference.
More details regarding the Network class can be found here: [Salesforce Developers](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_classes_network.htm#apex_System_Network_forwardToAuthPage). 1\. Enhancement to CodeScan decorations of SARIF Reports Since the 24.0.6 release (June 2024), CodeScan was enhanced to decorate standard SARIF output. While CodeScan had been able to generate SARIF output before the 24.0.6 release, it’s noteworthy to mention that the SARIF output in GitHub does not contain the severity. As such, we added severity to our SARIF output, thereby allowing CodeScan to provide a more verbose presentation of the issues in GitHub. This change has been providing a better experience for our customers working in GitHub Actions. The way this feature was originally designed was: * When generateSarifFile: true, the generated SARIF file includes all issues, both open and resolved. Additionally, the report contains detailed metadata such as Type and Severity for each issue. * When generateSarifFile: false, the generated SARIF file includes only open issues, and it does not include the Type and Severity information for the issues. This means that when generateSarifFile is set to false, the generated SARIF file includes only open issues, but omits important metadata such as Type and Severity for each issue. However, to maintain consistency and support downstream analysis tools, the SARIF file should always include detailed metadata for each issue, regardless of the generateSarifFile setting. Thus, this enhancement expands upon the existing capability and introduces much more robust functionality. With this release, when generateSarifFile: false or generateReportFile: true, the SARIF file: * Contains only open issues respective to the branch and PR * Includes full metadata for each issue, including Type and Severity for rules and results More detailed information can be found here: Verified the below types of analyses with SARIF report all are working as expected: * Commit request analysis * PR analysis * Merge analysis * SARIF reports Verified the SARIF report with the parameter generateSarifFile: false/true in the YML file user is able to see the open issues of the specific branch or pr and also able to see the issue TYPE and SEVERITY in the SARIF report. 2\. On the Billing Page, a banner was added that details the level of access users have within the CodeScan UI based on user license type Customers who are using a user-based license model will now have a banner on their Billing Page that provides additional clarity regarding the CodeScan features available to users based upon their license type. Standard users will have access to all CodeScan features (although access can be restricted by admin based on user privileges). Platform Integration Users will only have access to their Profile, along with access to the Security Tab and the Notifications Tab. Additionally, both types of users can fully use the CodeScan extension for VS Code and IntelliJ.
### Fixes 1\. Fixed issue where after a user is deactivated, the user is still displayed on Members page Some users were reporting that after a user is deactivated, the user is still displayed on the Members page. Detailed Solution 1. Made changes in the codebase to remove the user from members table when the user is deactivated. 2. Ensured that using “search” on the Members page, only active users are retrieved. 3. The user is no longer able to login via SAML Verified the below scenarios regarding users being displayed in Members page, and all scenarios are working as expected. 1. Create and Activate New User: User appears under the Members list of the active organization 2. Add User to Inactive Organization: User is visible under the Members list of the inactive organization 3. Deactivate User from Instance: User no longer appears in the Members list. Behavior confirms that deactivated users are excluded from the UI display 4. Verify SAML Login for New User: Authentication via SAML was successful 5. Billing Page User Count Verification: User count reflects the new user addition appropriately. Billing data is updated as per user assignments 2\. Fixed issue with codescan-scanner-action (occurring after CodeScan upgrade) Some users were reporting that when their CodeScan project was upgraded to CodeScan 24.12.0.100206, it was incompatible with our codescan-io/codescan-scanner-action (and thus breaks customers’ GitHub Actions pipelines for pull request scanning). This issue is remediated with this fix. Validated that all below scenarios are working as expected. 1. Verified the GitHub Actions runner when using runs-on: ubuntu-latest 2. Verified the GitHub Actions runner when using runs-on: macos-latest 3. Verified the GitHub Actions runner when using runs-on: windows-latest 4. Verified the GitHub Actions if JRE and Sonar Scanner is not present in cache and also Verified the logs if JRE and Sonar Scanner are present in the cache. 5. Verified the below type of analysis (with SARIF report) are all working as expected. * Commit request analysis. * PR analysis. * Merge analysis. * SARIF reports. 6. Verified the SFDX analysis (with SARIF report) the analysis is successful and able to generate the SARIF file locally where user is able to see the tags, rule text, results, type of the Bug and type of the Severity. 7. Verified the S3 integration the analysis is successful. 8. Verified the CodeScan extension in the Azure DEVOPS plugin on the TEST instance working as expected. * Verified the main/default analysis which is successful. * Verified the branch analysis which is successful. 9. Verified the below sonar scanner versions * sonar-scanner-5.0.1.3006 - Analysis is successful * sonar-scanner-6.0.0.4432 - Analysis is successful * sonar-scanner-6.2.1.4610 - Analysis is successful * sonar-scanner-7.1.0.4889 - Analysis is not successful (threw exception; nested exception is org.bouncycastle.crypto.fips.FipsOperationError: org.bouncycastle.crypto.fips.FipsOperationError: Module checksum failed: expected) *** ## CodeScan Release 25.1.3 **Release Date: 22 June 2025** Summary: CodeScan 25.1.3 is comprised of the following 5 components: * 3 Enhancements * 2 Fixes Component details are listed in their corresponding sections within this document. ### Enhancements **1. New Banner in billing when license entitlements exceeded** In this release, we created a new banner to inform admins when their licenses entitlements have been exceeded. It advises the admins to contact their account team to get their entitlements amended. Separately, the AutoRABIT account team will be notified directly as well.
In the example shown, Customer X is licensed for 2 Platform Users, but currently have 4 Platform Users activated in their Org. As such, the banner appears to advise the admins of this discrepancy. Additionally, this new banner is coupled with additional billing logic (detailed in the next note) aimed to ensure that user operations are not disrupted when license entitlements are exceeded, providing a better user experience for our customers. **2. New logic in billing allows users continued operations** In this release, we made an update so that users are not blocked when an organization exceeds their license entitlements. Instead, a new banner will appear on the billing page advising the admins that their license entitlements have been exceeded (see previous note above). This feature also ensures that user operations are not disrupted when license entitlements are exceeded, providing a better user experience for our customers. **3. Project Report Status update in UI** Several customers had previously reported that on the Project Report page, the UI displays the Project Report as “stuck” in the queue. This status persists even after users receive the corresponding email notification in Outlook. We have remediated this issue with this release by updating the status in the UI to "Your project report is currently being processed. You will receive it via email shortly." *Verified that the 4 scenarios below are working as expected* 3.1 - "Verified: The updated message after enabling project reports and enabling the received scheduled reports in the CodeScan UI."
3.2 - "Verified: The updated message after enabling project reports and disabling the received scheduled reports in the CodeScan UI."
3.3 - "Verified: The updated message after disabling project reports in the CodeScan UI."
3.4 - Able to receive the project reports via email for all the above three case
### Fixes **1. Fixed issue with certain menus where users were unable to easily scroll down and choose a value from the menu** Some users were reporting that they were unable to scroll down in the quality profiles section in project settings.
This issue has been remediated in this release. The dialog box was resized. We have verified that with this fix, users are able to scroll down in the Quality Profiles section within the Project Settings. We also verified that the dialog box is resized.
**2. Fixed Deprecation Warning associated with sonar.login** Some customers were reporting that they were receiving deprecation warnings in their scans indicating that the use of sonar.login is deprecated, and that instead, going forward, authentication should be done using sonar.token. This issue has been remediated in this release. CodeScan now supports both sonar.login and sonar.token for authentication during Codescan analyses. Verified the below plugins by using sonar.token and sonar.login parameters in the sonar command and sfdx; both scenarios are working as expected. SFDX -\@salesforce/cli/2.61.8 Sonar-scanner - 5.0.1.3006V 1. Validate Project analysis through above plugins 2. Validate branch analysis. *** ## CodeScan Release 25.1.2 **Release Date: June 11, 2025** ### Summary CodeScan 25.1.2 is comprised of the following 19 components: · 3 New Features · 3 Enhancements · 2 New Rules · 11 Fixes Component details are listed in their corresponding sections within this document. ### New Features #### 1. CWE Numbers Added to Vulnerability Rule “Unescaped Value Could Cause XSS” We have added CWE Number [MITRE CWE-80](http://cwe.mitre.org/data/definitions/80.html) and additional CWE numbers (95 and 470) to the rule “Unescaped Value Could Cause XSS” Verified the CWE number on the rule Unescaped Value Could Cause XSS by confirming that user is able to see the added CWE Number [MITRE CWE-80](http://cwe.mitre.org/data/definitions/80.html) (along with additional CWE numbers 95 and 470)
Please note, these rules are only available for projects created with CodeScan's direct Salesforce integration due to being based on a direct query to a Salesforce Org. **2. Disable “Invite Members" option** Invite members is a feature in CodeScan designed for organizations using Auth0 for authentication. In contrast, it is not applicable for SSO enabled environments. To date, SSO customers would have access to this feature, even though the functionality would not be enabled for them. We recognize that this can cause confusion and lessen the user experience. As such, we have added a new option in CodeScan allowing any organization to disable the “Invite Members” functionality in CodeScan. **Description** The "Disable Invite Members" option in Administration > Organization Settings of CodeScan allows Organization Admins to control the visibility of the "Invite Member" button. By default, the option is active or visible. When enabled, the "Invite Member" button is hidden for users, while disabling it keeps the button visible and functional. Verified below scenarios, all are working as expected\ \ 1\. An option/toggle called "Disable Invite Members" should be available in Administration > Organization Settings of CodeScan.
2. The default behavior of the invite member option should be active or visible.
3. When the toggle is enabled, the "Invite Member" button is hidden in administration module and members page
4. When the toggle is disabled, the "Invite Member" button remains visible and functional as usual in administration module and members page
5. Other functionalities related to member management (e.g., viewing members, editing permissions) should remain unaffected.
6. Able to invite users to the codescan organization
3. **Restricting Platform Integration User Access for Standard Users** This feature ensures that standard users who manage user access cannot switch their role to a Platform Integration User, so that user permissions are maintained correctly. Preventing Standard users with System Admin Permission from switching to a Platform Integration User role will reduce potential misconfigurations and ensure compliance with user access policies. To enforce this, we have implemented an alert and disabled the option in the UI. This will give administrators better control over role assignments and prevent unintended access changes. On the Members page, the following alert "You are a System Admin. You are required to have a Standard User License.“ is displayed. Verified the Restricting Platform Integration User Access for Standard Users via the following:\ \ 1\. Verified admins are able to see the alert “You are a System Admin. You are required to have a Standard User License.“ if Standard users with System Admin Permission try switching to a Platform Integration User.
2. Verified admins are able to change users from standard to platform if standard user is without System Admin Permission
3. Verified admins are able to see the alert “You are a System Admin. You are required to have a Standard User License.“ if user is owner and trying to switch from standard to platform user
### Enhancements 1\. Enhanced rule “vf:AvoidJavaScriptScriptlets” by adding a new parameter to the rule Historically, CodeScan has offered our “Avoid JavaScript Scriptlets” rule to inspect customer’s code and flag where there JavaScript Scriplets. With this release, a new parameter was introduced to allow users to choose whether to include or ignore violations related to code supporting the Lightning functions within script. * Parameter Name: ignoreSupportingCode * Type: Boolean (true or false) * Default: false * Description: This option allows users to ignore violations related to code supporting the Lightning functions within script. By default, it is set to false. Verified the below scenarios for rule vf:AvoidJavaScriptScriptlets and report that all scenarios are working as expected. 1. Validated the rule with LightningFunctions and set the default value false then user is able to see the violations. 2. Validated the rule with LightningFunctions and set the value true then user is not able to see the violations which is expected. 3. Validated the rule without LightningFunctions then user is able to see the violation which is expected. 4. Validated the rule by setting the parameter ignoreSupportingCode as false/true working as expected.
1\. Enhanced rule “Controller Naming Convention” for Apex and Visualforce Some customers are reporting that CodeScan is flagging violations on components that should not be flagged (i.e., SandboxRefreshAdminController) This issue is remediated in this release. We validated the fix by: * Creating a class file in salesforce org using UI and name the controller like in example. * Creating a vf page in salesforce org with the controller attribute like shown in the example. * Setting parameters for controller naming in CS, try the parameters with different cased letters ex: ConTroLLer etc. * After scanning false positives should not be visible 2\. Updated description for Deprecated rules Historically, CodeScan has deprecated rules over time. However, we recognize that we can be clearer about why the rule is being deprecated. In this release, we have initiated this practice (and plan to adhere to this practice in the future). **1.Update the description of deprecated Apex Rule “Use System.assertEquals instead of System.assert“ and key”sf:UseAssertEqualsInsteadOfAssertEquality” with the following:** This rule detects unit test assertions in object references equality. Instead of using System.assert combined with "==" as an equality operator, these assertions should be made by more specific methods, like assertEquals. This rule has been deprecated, as Salesforce recommends using the Assert class for unit tests. Please remove this deprecated rule from your custom Quality Profile and instead add the rule sf:UseAreEqualInsteadOfAssertBoolean. **2.Update the description of deprecated Apex Rule “Use System.assertEquals instead of System.assert“ and key”sf:UseAssertEqualsInsteadOfAssert” with the following:** This rule detects Unit test assertions in object references equality. Instead of using System.assert combined with ".equals()" as an equality check, these assertions should be made by more specific methods, like assertEquals. This rule has been deprecated, as Salesforce recommends using the Assert class for unit tests. Please remove this deprecated rule from your custom Quality Profile and instead add the rule sf:UseAreEqualInsteadOfIsTrue **3.Update the description of deprecated Apex Rule “Use System.Assert instead of System.assertEquals“ and key”sf:UseAssertInsteadOfAssertEquals” with the following:** When asserting a value is the same as a boolean literal, use System.assert, instead of System.assertEquals. *This rule has been deprecated, as Salesforce recommends using the Assert class for unit tests. Please remove this deprecated rule from your custom Quality Profile and instead add the rule sf:UseIsTrueInsteadOfAreEqual* **4.Update the description of deprecated Apex Rule “Unnecessary Parentheses“ and key”sf:UnnecessaryParentheses” with the following:** Sometimes expressions are wrapped in unnecessary parentheses, making them look like function calls. This rule has been deprecated. Please remove it from your custom Quality Profile and instead add the rule sf:UselessParentheses as a best practice for code styling. ### New Rules **1. Server Side Request Forgery** This is a rule that checks for any changeable inputs to a url string in a method that returns a PageReference. **Type:** Vulnerability\ **Severity:** Critical\ **Name:** Server Side Request Forgery (SSRF)\ **Key:** ServerSideRequestForgery\ **Message:** Sanitize input to avoid possible SSRF\ **Description:** This rule identifies potential Server-Side Request Forgery (SSRF) vulnerabilities by detecting unsafe URL construction and external network requests that could allow an attacker to manipulate server-side network calls. Server-Side Request Forgery (SSRF) occurs when an attacker can influence the server to make arbitrary network requests, potentially accessing internal resources, sensitive endpoints, or bypassing security controls. Input can be cleansed by using Id.valueOf, Date.valueOf, etc. Or escaped using String.escapeSingleQuotes(). **Parameters**\ **Name:** sanitizationMethod\ **Description:** A comma separated list of custom methods that provide input sanitization. CWE: 918 **Test Cases with Violations**\ \ **1.Validated direct embedding of user input into a URL without sanitization, resulting in a violation (SSRF) as expected**
2.Validated unescaped dynamic input into URL, resulting in a violation (SSRF) as expected.
3.Validated that one parameter is sanitised but the other is not sanitised, still resulting in a violation (SSRF) as expected
4.Validated concatenated unsafe dynamic parameters in a URL, resulting in a violation (SSRF) as expected.
5.Validated the presence of a malicious SSRF-style payload embedded in the URL, resulting in a violation (SSRF) as expected.
6.Validated the attempt at "sanitization" using regex, which is not an approved method, resulting in a violation (Improper sanitization) as expected
Test Cases with No Violations 1\. Validated input sanitized using Id.valueOf, resulting in no violation as expected.
2. Validated input escaped using String.escapeSingleQuotes, resulting in no violation as expected.
3. Validated that the URL starts with "/" ensuring an internal redirect, resulting in no violation as expected.
4. Validated date validated using Date.valueOf, resulting in no violation as expected.
5. Validated a static URL with no dynamic input, resulting in no violation as expected.
6. Validated fully escaped input and use of safe methods, resulting in no violation as expected.
*NOTE: The implementation currently addresses the most common scenarios related to resource injection and SSRF vulnerabilities. However, due to the dynamic and context-dependent nature of these issues—especially when influenced by external inputs, indirect references, or complex backend behaviors—there may be edge cases that are not readily identifiable or testable. These may only surface under specific configurations or data conditions.* 2. **Resource Injection** Prior to this new rule, CodeScan did not catch resource injection in Apex. This is very similar to [our new rule “Server Side Request Forgery”](https://autorabit.atlassian.net/browse/CD-6437) (also included in this release) However, there are some basic things that make it resource injection and not SSRF. `In this example:` `public PageReference init(){` `AccListString = 'INIT';` `BaseObjId = system.label.MY_Label;` `return null;` `}` `public PageReference prepareAccs(){` `String newUrl = '/apex/maps__Maps?baseOjectId='+BaseObjId+'&recordIds='+AccListString;` `PageReference p = new PageReference(newUrl);` `p.setRedirect(true);` `return p;` `}` Here, we are looking at resource injection because the URL is internal (starts with / ) This rule should find any external variables that are used to create dynamic internal URLs.
**Acceptance Criteria** **Type:** Vulnerability\ **Severity:** Critical\ **Name:** Resource Injection\ **Key:** ResourceInjection\ **Message:** Sanitize input to avoid possible resource injection\ **Description:** This rule identifies potential resource injection vulnerabilities by detecting unsafe URL construction for internal network requests. Resource injection occurs when user-controllable data is used to specify a resource identifier without proper validation. Input can be cleansed by using Id.valueOf, Date.valueOf, etc. Or escaped using String.escapeSingleQuotes(). See: [MITRE, CWE-99](https://cwe.mitre.org/data/definitions/99.html) - Improper Control of Resource Identifiers ('Resource Injection') Tags: cwe Remediation Time: 10 minutes Parameters:\ Name: sanitizationMethod\ Description: A comma separated list of custom methods that provide input sanitization. CWE: 99 Verified the below scenarios are all working as expected 1. **Verified that sanitizing both BaseObjId and AccListString before URL building prevents violations.**
2. **Verified that validating BaseObjId using Id.valueOf() ensures the ID is valid and safe to use in URLs.**
3. **Verified that input AccListString validated with regex and sanitized prevents violation.**
4. **Verified that using AccListString directly in URL without any sanitization or validation causes violations.**
5. **Verified that sanitizing only BaseObjId but not AccListString leads to a violation.**
6. **Verified that sanitizing the URL string after using variables has no effect, resulting in a violation.**
7. **Verified that URL encoding AccListString without further format validation leads to violation**
8. **Verified that replacing characters rather than proper sanitization leads to security violations.**
*NOTE: This implementation currently addresses the most common scenarios related to resource injection and SSRF vulnerabilities. However, due to the dynamic and context-dependent nature of these issues, specially when influenced by external inputs, indirect references, or complex backend behaviors—there may be edge cases that are not readily identifiable or testable. These may only surface under specific configurations or data conditions.* ### Fixes **1. Fixed issue with the CSV Export not functioning properly with all nCino projects** We detected that some nCino projects are unable to export to CSV. The issue occurs after 500 records are returned (where the request does not contain the necessary data). This issue is remediated in this release. We verified the fix and are now able to export the issues exceeding 500 records for all ncino projects (as expected) **2. Fixed 2 issues with our SOQL Injection rule** We have discovered that the issues flagged disappear on different lines; we have also discovered that CodeScan doesn’t find the fflib method escape. These 2 issues are remediated in this release. **3. Fixed issue with the rule “Page layout name contains special characters” (sfmeta:PageLayoutNaming)** Some customers were reporting that CodeScan was flagging that their Page layout name contains special character even though they didn't add any special characters. This issue has been remediated in this release. **4. Fixed issue with the rule “vf:UnescapedAttributes vulnerability” {where false positive violations were being flagged}** CodeScan suggests the remediation for this issue is to use JSENCODE() to escape values. However, some customers reported that when this is added to their code, the issue was still being flagged as a violation. We validated the fix by: * Verified the updated description and example under rule: vf:UnescapedAttributes vulnerability
• Verified that Rule is throwing violation as expected
This CodeScan rule was updated with the following changes: **1. Changed the description to the following:** Reflected Cross-site Scripting (XSS) occurs when an attacker injects browser executable code within a single HTTP response. Using unescaped parameters can be a security risk. c:\* and apex:\* attributes are not checked unless they are known to cause problems. You can check other attributes by adding them to the configuration for this rule. In Visualforce, escape methods such as JSENCODE can be used to sanitize variables as shown below. For Aura components, sepcifically aura:unescapedHtml, make sure to sanitize variables in controllers before using them. This component is intended to output properly sanitized HTML from a trusted source. If properly handled, mark the issue as Resolved: False Positive/Won't Fix. **2. Added the following Aura Example Bad Scenario:** Example : `` `. //Bad: not recommended.` `` **5. Fixed issue with the rule “Open Redirect” (sfmeta:PageLayoutNaming) {where false positive violations were being flagged}** Some customers reported that our current rule does not handle the use of “Network.forwardToAuthPage”
We remediated this issue and validated that CodeScan now throws a violation in both of these cases. Verified the rule “Open Redirect” by validating: * Users are able to see the violation for the use of both Network.forwardToAuthPage and PageReference
More info regarding “Network class” can be found here: [Network Class | Apex Reference Guide | Salesforce Developers](https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_classes_network.htm#apex_System_Network_forwardToAuthPage) 6. **Fixed issue with the rule “Field Level Security Vulnerabilities” (sfmeta:PageLayoutNaming) for classes using “Without Sharing” {where false positive violations were being flagged}** Some customers have reported an issue with CodeScan's reporting of "Permissions should be checked before accessing resource" vulnerabilities in our Apex codebase, specifically within classes that are declared without sharing. The without sharing keyword in Apex classes causes the code to execute in system context, bypassing standard Salesforce sharing and field-level security checks. This is intentional for certain system-level operations and utility classes within our application. However, CodeScan is flagging fields within these without sharing classes as vulnerabilities, stating "Permissions should be checked before accessing resource." This is creating an inflated number of false positives and incorrectly portraying our code's security posture. CodeScan is designed to identify potential security issues; however, in the context of without sharing classes, these field-level security checks are redundant and misleading. As such, the rule update in this release enables CodeScan to recognize that when a class is declared without sharing, field-level security checks are irrelevant, and the "Permissions should be checked before accessing resource" rule is suppressed for fields within without sharing classes.
Note that a new parameter has been added to this rule to Ignore Without Sharing Name: ignoreWithoutSharing\ Message: When this parameter is true, this rule ignores Field Level Security issues in all without sharing classes.\ Default: false
Appropriately, CodeScan is flagging violations properly when “with sharing” is used.
7. **Fixed issue with CodeScan’s APEX parser** Some customers reported that the CodeScan parser was incorrectly flagging valid Apex code using the UPDATE AS SYSTEM syntax as a parsing error. This was occurring because the parser doesn't recognize the AS SYSTEM portion of the UPDATE statement, leading to a ParseException and preventing accurate code analysis. This issue has been remediated with this release. We had previously verified the Parsing error in APEX Code for DML queries if user using UPDATE AS SYSTEM syntax would throw the parser exception. With this fix, users are now able to see the violations as expected for the file. Verified the below queries in Apex code that users do not get any Parser errors; instead the updated CodeScan parser is working as expected. * INSERT AS SYSTEM * DELETE AS SYSTEM * UNDELETE AS SYSTEM * UPDATE AS SYSTEM
8. Fixed issue with rule “Avoid running Soql and DML inside loops” {sf:AvoidSoqlInLoops} Some customers reported unexpected behavior in this rule, producing false positives. The root cause of the false positives is that when a method of an object is invoked within another method, and both methods share the same name, the current rule implementation incorrectly interprets this as a recursive call and subsequently triggers a violation. Further, the Stack Loop trace is indefinite. This has been remediated in this release. The updated rule logic now handles these edge cases by checking for method image to be exactly the same (method != diffObj.method). We have verified the fix across related and existing test cases and edge conditions by confirming that if a method of an object is invoked within another method, and both methods share the same name, the user will not see the violation (as it is false positive). 9. **Fixed issue with rule “RequireDescriptionComponent”** Some customers reported that the CodeScan rule “RequireDescriptionComponent” rule was not working for custom fields on standard objects. This issue has been remediated in this release. Previously, CodeScan offered a rule “*sfmeta:RequireDescriptionField*” which had been deprecated for this updated rule. But the updated rule was not designed for standard objects. When we tested the logic of the deprecated rule, we found that it could be used for reference for this update to the new rule “RequireDescriptionComponent” The rule enhancement was verified via the below scenarios\ \ 1\. Verified Custom Field on Standard Object – Missing Description
2. Verified Custom Field on Custom Object – Missing Description
3. Verified Standard Fields on Standard Object – Missing Description
4. Verified Custom Field on Standard Object – With Description
5. Verified Custom Field( With Description) on Custom Object (Without description)
**10. Fixed issue with rule “sf: FieldLevelSecurityRule”** During maintenance testing, we discovered that this rule was triggering the null pointer exception when parsed through the trigger files. In the rule logic it was searching for relevant ASTClassOrInterfaceBody to get all the constructors in that class. Since triggers don't have constructors, control flow proceeds further if we get a non-null node for ASTClassOrInterfaceBody.\ \ We updated this rule to parse the trigger files by adding extra logic to find the Trigger specific nodes (TriggerBodyDeclaration etc). We tested the fix to the Null pointer Exception with sf: FieldLevelSecurityRule and verified we are now no longer able to see the Null pointer exception for the trigger files in the logs (as expected).
**11. Fixed issue with Organization images displaying as large icons in the org list** CodeScan has historically allowed images to be added under Organization settings by our customers. These images are then displayed on the organization home page and in the Org list. After we released CodeScan 25.1.0 (April 2025), customers org icon images could appear as large icons. This issue was remediated in this release by restricting the size of the image on the Org page to the size of a usual non-image icon (around 30px). We have verified the Organization image is now restricted in size, and users are able to see the image as expected.
*** ## CodeScan Release 25.1.1 **Release Date: May 11, 2025** ### Summary **CodeScan 25.1.1 is comprised of the following 3 components:** * 3 Fixes Component details are listed in their corresponding sections within this document. ### **New Features** There are no New Features associated with this release ### **Enhancements** There are no Enhancements associated with this release ### **New Rules** There are no New Rules associated with this release ### **Fixes** 1. **Fixed an issue with rule tags blocking analyses** Several customers reported that, after the recent CodeScan upgrade to 25.1.0, some of their analyses were not properly executing. We uncovered that this was due to new logic added to a database table. This fix corrects this issue and will allow all blocked analyses to run properly. We have verified the below scenarios and report that all are working as expected. * Tags which are system default * Tags which are not system default * Custom tags 1. Verified the vf:exception and sf:exception rule by adding tags in one organization and seeing the analysis working without any issue in that org or any other org. 2. Verified the analysis for the rule sf:exception by assigning the tags. Confirmed analysis was successful and that users are able to see the assigned tags in the issues page. 3. Verified the analysis when the tags are not assigned. If there are any new violations the user is unable to see any tags for the violations (which is expected). 2. **Fixed Error: \[CS] API GET status code: 404 when users try to generate Sarif File on their environment** Several customers reported the following error “Error: \[CS] API GET status code: 404 “when users try to generate Sarif File on their environment. This fix corrects this issue and will allow users to generate Sarif files on their environment. We have verified the below scenarios for GitHub Actions SARIF report on TEST environment and are able to generate SARIF reports successfully. 1. Analysis is getting “success” and able to get the SARIF report where the results are same in the report and on CodeScan UI 2. Validated the Pull request analysis in GitHub actions we are able see that the PR analysis is happening for the changed files. * Validated the Commit request analysis. * Validated the PR analysis. * Validated Merge analysis. 3. **Fixed Error: \[CS] API GET status code: 404 when users try to generate Sarif File on their environment** **After the upgrade to 25.1.0, we uncovered 2 minor issues:** 1. The IDP group mapping feature flag was not working as expected. 2. If an ID user is member of org 1 and owner of org 2, then from org2 SAML connection she was able to make anyone an owner of org1. This update remediates these 2 issues. Verified the IDP Group Mapping flag by Enabling and Disabling the instance is now working as expected.
*** ## Release Notes 25.1.0 **Release Date: 20 April 2025** ### Summary CodeScan 25.1.0 is comprised of three main components / features: * [New User Interface ](#new-user-interface) * [Technical Architecture Improvements ](#technical-architecture-improvements) * [Fixes](#fixes-1) Component details are listed in their corresponding sections within this document. ### New User Interface In this release, we have updated the CodeScan User Interface order to provide four key benefits: * Easier navigation, which provides both an improved, intuitive experience for more advanced users, while reducing the learning curve for new users * Consistency in screen layout, providing a more cohesive experience throughout the application * Enhanced performance and responsiveness within CodeScan * Brand modernization alignment with other AutoRABIT solutions

UI Upgrades

{% hint style="info" %} Please note: CodeScan documentation pages will have new images to reflect the latest UI changes over the coming weeks. This should not affect the effectiveness of instruction steps in the meantime. {% endhint %} ### Technical Architecture Improvements * The CodeScan 25.1.0 contains various technical architecture improvements and upgrades to various libraries. We have also included several enhancements to CodeScan’s security architecture. ### **Fixes** * Fixed a false positive in the 'sf:AvoidGlobalModifier' rule. The violation is now ignored for global classes used as return types in any global static method. # Cloud Release Notes 25.0 Newest CodeScan Releases ## CodeScan Cloud ## Release Notes 25.0.3 **Release Date: 5 March 2025** ### Summary CodeScan 25.0.3 is comprised of the following 1 component: * [1 Enhancement](#enhancements) Component details are listed in their corresponding sections within this document. ### Enhancements 1. Enhanced rule “Use System.runAs to test user permissions” to ensure that a violation should not be thrown if the variable used is within the class scope.\ \ Historically, the CodeScan rule “Use System.runAs to test user permissions” checks for the presence of System.runAs in the test methods and that a local User variable is passed.\ \ This enhancement provides an alternative for the rule by adding a parameter to ignore checks for the variable passed to the RunAs method.\ \ The implantation of this enhancement is via a parameter which defines an execution: * \*Parameter name\*: checkRunAsOnly * \*Parameter desc\*: When true, this parameter tests only if RunAs is used in the method, not the arguments passed to it.\\ Note that the parameter default is false. We have verified that users are now able to see the violation for the following scenarios. ```apex public void noRunAs(){ // No RunAs will always violate } ``` ```apex public void standardRunAs(){ User newUser = new User(); System.runAs(newUser){ // RunAs User will never violate } } ``` ```apex public void otherRunAs(){ System.runAs(userFactory.createTestUser()){ // RunAs given a method will violate when checkRunAsOnly parameter is false } } ``` ## Release Notes 25.0.2 **Release Date: 5 February 2025** ### Summary CodeScan 25.0.2 is comprised of the following 4 components: * [1 New Feature](#new-feature) * [1 Enhancement](#enhancement) * [2 Fixes](#fixes) Component details are listed in their corresponding sections within this document. ### New Feature 1. **Added “Security Hotspots” in CSV Export**\ \ We have had a long-standing capability to export issues directly from the CodeScan user interface. However, there was not the ability to export Hotspots.\ \ With this new feature, we have added a new page in the CodeScan UI that allows users to directly export Hotspots. And, similar to exporting issues, this can be done at the branch or PR level.

Hotspots Export

{% hint style="info" %} Please note that if the Status selected is **Reviewed**, then the Resolution field is also added as a selectable input. {% endhint %}

Export Dropdown

Further, to make navigation clearer and easier for users, we have renamed the existing CSV export page to “CSV Issues Export”, which is separate from the new “CSV Security Hotspots Export” page. Both pages can be opened under the “More” tab (as long as the user has the proper permissions).

More Dropdown

Finally, we verified the following scenarios: * Verified that we are able to export security hotspot issues of a selected project. * Verified that all the required fields were included in the exported CSV with correct data. * Verified that the resolutions are visible only when the status **Reviewed** is selected. ### Enhancement 1. **Enhanced rule “Avoid Classes Without Explicit Sharing" to account for interfaces**\ \ Previously, CodeScan did not consider interfaces when flagging violations. As such, the rule "sf:ClassExplicitSharing" was generating a false positive when applied to interfaces, as the Sharing keyword is not allowed on interfaces in Salesforce.\ \ This issue has been remediated. We have updated the rule to exclude interfaces from its check for the Sharing keyword, ensuring accurate validation and preventing incorrect flags.\ \ We have verified the rule: "sf:ClassExplicitSharing" for the following scenarios: * Violation is not thrown if we use with/without sharing for classes. * Violation is thrown if we don’t use with/without sharing for classes. * Violation is not thrown for an interface class, not even when used with/without sharing. * Violation is thrown if we only use sharing for classes. ### New Rules There are no new rules associated with this release. ### Fixes 1. **Fixed issue with “Project Search” in CSV Export (within the CodeScan UI)**\ \ Recently, we added a search function to the dropdown on the CSV export page to allow users to search for the name of the project they wish to export.

CSV Export

Several customers reported an issue when selecting a project in the new Project Search Window. This updated fully remediates this reported issue. Further, we have validated the CodeScan export issue is resolved via the following scenario: * Users are able to select the projects in the Project Search Window (on the CSV export page) as expected. 2. **Fixed an issue with some users being unable to be converted to SAML when not assigned to a SAML org.**\ \ Some users were receiving the following error:

Error Msg

This was occurring when a user who had previously been either an Auth0 user or an SQ native user was attempting to log in via SAML, but the user is not part of the SAML org. This was occurring because CodeScan had been operating under the assumption that the user had previously logged in to CodeScan at least one time previously. This assumption, which triggered the issue, has been fully corrected with this fix. ## Release Notes 25.0.1 **Release Date: 29 January 2025** ### **Summary** CodeScan 25.0.1 is comprised of the following 11 components: * [3 New Features](#new-features-1) * [4 Enhancements](#enhancements-1) * [1 New Rule](#new-rules-1) * [3 Fixes](#fixes-1) Component details are listed in their corresponding sections within this document. ### New Features 1. **Added nCino module**\ \ The new nCino module contains rules that scan your metadata and directly query your Salesforce org to find issues and inconsistencies with your nCino configuration.\ \ Please note, a portion of these rules are only available for projects created with CodeScan's direct Salesforce integration due to being based on a direct query to a Salesforce Org. 2. **nCino Rules Activation**\ \ Create a project analysis with the Salesforce Org that includes nCino objects. Select the nCino-specific built-in profile and run the project analysis.\ \ Users can choose the built-in nCino Quality Profile consisting of nCino-specific and nCino-goldstandard rules in Apex/Salesforce metadata, or Users can add nCino rules to the CodeScan Quality Profile. Users can extend existing profiles and activate more rules from Apex and Salesforce Metadata using the "nCino-specific" tag.\ \ Alternatively, they can add the rules directly to newly created Quality Profiles by selecting the "nCino-specific" tag from the Rules filter, then apply Bulk Change > Activate in > Choose a quality profile.\ \ To learn how to create a custom Quality Profile, [see this article.](https://knowledgebase.autorabit.com/product-guides/codescan/quality-profiles/customizing-quality-profiles) 3. **New nCino Specific Rules**:\ \ The following nCino-related rules have been added to the existing Apex/Salesforce Metadata rule sets and are tagged as "nCino-specific." * **Avoid Duplicates in Custom Labels**: Maintaining unique labels ensures data accuracy and consistency within the nCino platform. By avoiding the creation of multiple labels with the same value, users can rely on the uniqueness of each label for categorization and analysis purposes. * **Collateral Configuration Is Null**: The Collateral Configuration Field on the Collateral Type object should not be null. This will reduce the likelihood of missing or incomplete Collateral information. * **Duplicate LookupKeys**: In the nCino Record-Based Configuration, no two records in the configuration should have duplicate LookupKeys. The LookupKey is a critical identifier for these records, and duplicates could lead to data inconsistency and errors in the system. * **Fee Template Record Screen Section**: Ensure that every Fee Template record includes a Screen Section data value. This will reduce the likelihood of missing or incomplete Fee information. * **Field History Tracking Check**: Field History Tracking is limited according to the features in your Salesforce org. By default, Field History Tracking can be used to track a maximum of 20 fields per object. * **Null LookupKeys**: In the nCino Record-Based Configuration, object records without LookupKeys will cause challenges in data management and processing. * **Product Feature Record Does Not Exist**: Ensure that for each nCino Product Object, there is a corresponding Product Feature record. Product Object records existing without an associated Product Feature record can lead to potential data inconsistencies. * **Product Feature Sharing**: Ensure each nCino Product Object record is associated with unique Product Feature records. Shared Product Feature records may lead to data inconsistencies and operational challenges. * **nCino Custom Components with Duplicate Names**: Avoid naming conflicts with existing Managed Package Components to minimize the risk of errors and conflicts within the system, ultimately enhancing system stability and reliability. * **nCino Custom Fields with Duplicate Names**: Avoid naming conflicts with existing Managed Package Fields to minimize the risk of errors and conflicts within the system, ultimately enhancing system stability and reliability. * **nCino Data Integration User Configuration**: The Data Integration user is authenticated for background jobs such as nightly batched updates of records. Configure this user’s Permission Sets correctly to ensure updates by the Data Integration User don't execute additional tasks. * **nCino Deprecated Fields**: Deprecated fields in an nCino environment are labeled with a '-D' to make the deprecation visible when configuring the environment. This rule is to identify the location when deprecated fields are used and should be addressed. * **nCino Trigger Handler Framework**: The Trigger Handler Framework removes logic from Triggers and enforces consistency across the platform. There are many ways to create a Trigger Framework/Factory; however, the nCino Managed Package can save users time and effort. By levering the nCino Trigger Framework, users can control the execution of triggers at runtime to simplify existing customizations and logic. * **System Bypass Logic – Flows**: System bypass logic is required for custom Flows. Checking for the Exclude Flows Permission Set allows the system to cease further processing of the Flow if it is found at the outset. This improves the efficiency of flow execution and reduces unnecessary processing steps. * **System Bypass Logic – Triggers**: System bypass logic is required for custom triggers. Checks for the Exclude Trigger Permission Set allow the system to cease further processing of the Trigger if it is found at the outset. This improves the efficiency of Trigger execution and reduces unnecessary processing steps. * **System Bypass Logic - Validation Rules**: System bypass logic is required for Validation Rules. Checks for the Exclude Validation Permission Set allow the system to cease further processing of the rule if it is found at the outset. This improves the efficiency of Validation Rule execution and reduces unnecessary processing steps. ### Enhancements 1. **Enhanced rule “Avoid Untrusted/Unescaped Variables in DML Query" to account for potential SOQL injections when “queryWithBinds” is used.**\ \ Historically, CodeScan has offered our “Avoid Untrusted/Unescaped Variables in DML Query” rule to inspect customer’s code and flag where there are SOQL injection possibilities. Recently, one of our customers performed a test and expected this rule to flag an issue in their code, but it did not. We determined that the rule should be enhanced for when “queryWithBinds” is used.\ \ Our engineering team utilized specifications within Salesforce documentation (specifically, [Help and Training Community](https://help.salesforce.com/s/articleView?id=release-notes.rn_apex_bind_var_soql.htm\&release=242\&type=5)) to consider only the query for executed with queryWithBinds() for vulnerability check and violation, avoiding the other parameters such as: (Map, accessLevel) and Database.queryWithBinds (query, bindVariablesMap, accessLevel).\ \ Example:

List Accounts

Verified after the rule enhancement was engineered that users are able to see the violation for rule “Avoid Untrusted/Unescaped Variables in DML Query” as expected.

Query Results

2. **Enhanced IDE to accept email IDs that have up to 255 characters**\ \ We discovered that certain users could not use the IDE as expected. The root cause was that the CodeScan plug-in was not able to fetch their valid licenses from CodeScan because these users have an email id with more than 40 chars. This enhancement now allows the CodeScan IDE plug-in to accept email IDs with up to 255 characters. 3. **Fixed rule “Require CSRF protection on GET requests” to distinguish Visualforce page settings from Aura components**\ \ Previously, this rule was flagging violations on .cmp files that are aura:component files. The guidance in the rule suggested to change the Visualforce page setting, but this is not possible on Aura components because they are not Visualforce components. This fix for the rule “Require CSRF protection on GET requests” now enables CodeScan to distinguish Visualforce page settings from Aura components. ### New Rule 1. **Remote Site Settings Description**\ \ Remote Site Settings should have a description of their functionality to make it easy for others to understand the purpose and functionality of the component, as it may not always be understandable from the name. ### Fixes 1. **Fixed issue with CodeScan plug-ins for VS Code and IntelliJ not working after the 24.0.15 release**\ \ Recently, we added a search function to the dropdown on the CSV export page to allow users to search for the name of the project they wish to export. 2. **Fixed issue with rule “Flow DML Should Not Be Called In Loops"**\ \ Recently, we observed that the rule “Flow DML Should Not Be Called In Loops" throws a null pointer exception because of access of parent node without a null check. This fix corrects the issue. We verified the fix by testing and confirming that the rule now throws a violation as expected, and, additionally, we are no longer getting the null pointer exception. 3. **Fixed issue with tracking IDE usage in CodeScan UI**\ \ Over the last few months, we have made several enhancements that allow admins to track IDE adoption and usage. However, we recently learned that the tokens associated with AutoRABIT ARM users were also being logged in the same report. This fix removes ARM users from the IDE user reports. # Cloud Release Notes 24.0 ## CodeScan Cloud ## Release Notes 24.0.14 **Release Date: 04 December 2024** ### Summary CodeScan 24.0.14 is comprised of the following eight components: * [2 Enhancements](#enhancements) * [2 New Rules](#new-rules) * [4 Fixes](#fixes) Component details are listed in their corresponding sections within this document. ### New Features There are no new features associated with this release. ### Enhancements 1. **Added “Project Search” in CSV Export**\ Customers with a large number of projects were experiencing a UI issue with the export feature: users who wanted to export issues in CSV format were only able to see the first 100 projects on the list.\ \ In this release, we have addressed this issue by adding a search function in the drop-down list to allow users to search for the name of the project they wish to export. \ We verified the added “Project Search” on CSV Export page for multiple scenarios including: 1. Verified search option functionality with the drop-down list of projects:
2. Verified the drop-down list shows 20 of the most recently scanned projects by default.
2. **Updated the message for Security Hotspot Status “Exception”**\ We recently added a new status type for Hotspots (status = “Exception”). Its intent is to serve as a more accurate status than 'Acknowledged' or 'Open' for issues being treated as exceptions. \ \ When we first delivered an “Exception” status, the associated message was: “The code has been reviewed and does not pose a risk currently. Further review is needed at a later date.” Based upon numerous client suggestions, we have enhanced the message to read: "The issue has an approved exception and will be re-reviewed until mitigated or upon exception expiry.”
### New Rules 1. **New Rule for LWCs: “API Version Is Too Old”**\ This is a new rule to ensure that all Lightning Web Components (LWCs) are using an acceptable API version (including the most current API version).\ \ Using outdated API versions can lead to compatibility issues, missed opportunities to leverage new features, and potential security vulnerabilities. This rule aims to streamline the process of identifying and updating LWCs to the latest API version. We recognize that by identifying and updating LWCs to the latest API version, developers are able to maintain higher code quality, reduce the risk of deprecated features, and improve the overall performance and security of the application.\ \ Verified the new LWC rule (API Version Is Too Old) for these scenarios: * Verified the description, issue type, severity, message, tags, remediation, and parameters of the rule:
* Verified that a violation is thrown if the API version used is lower than the minimum version allowed:
* Verified that a violation is thrown if the API version used is higher than the maximum version allowed:
* Verified that no violation is thrown when the API version is between the minimum and maximum versions allowed. 2. **New Rule for APEX: “OuterClassExplicitSharing”**\ Enforces security best practices on classes by ensuring that sharing settings ('with sharing', 'without sharing', or 'inherited sharing') are explicitly declared. This prevents accidental data exposure and enhances code maintainability and compliance with security policies. * **Name**: Outer Class Explicit Sharing * **Key**: OuterClassExplicitSharing * **Type**: Vulnerability * **Severity**: Major * **Message**: Class '{className}' does not have an explicit sharing rule * **Tags**: Convention * **Remediation**: 5 minutes Verified the rule: OuterClassExplicitSharing for the following scenarios: * Verified the rule’s description, type, severity, message, tag, remediation, key, and name:
* Verified the rule is not throwing a violation if used with sharing, without sharing, or inherited sharing:
* Verified that a violation is thrown if not used with sharing, without sharing, or inherited sharing.
{% hint style="info" %} **NOTE**: This rule overlaps with the **ClassExplicitSharing** rule and will always overlap with violations for outer classes. This rule has been created to: * Allow for the reporting of this issue as a vulnerability instead of a code smell * Only flag if sharing settings are missing for outer classes (inner classes that are missing sharing settings will not be flagged—which is opposite of how the ClassExplicitSharing rule works) If both rules are active, check the violations that were reported and disable one of the rules as necessary. {% endhint %} ### Fixes 1. **Fixed an issue in the CodeScan application in which flagged violations were not being displayed when using the "issues in new code" filter**\ \ **NOTE**: This issue only relates to a separate fix stemming from our last release (24.0.13), when we fixed an issue with reference branch analyses. After that fix, however, users were experiencing a new issue, in which flagged violations were not being displayed when using the "issues in new code" filter. The other parts of the CodeScan application were NOT impacted by the reference branch analyses fix in release 24.0.13. As such, all other parts of CodeScan continued to show the accurate new issue count.\ \ Regarding this issue, users were unable to navigate to the issues page after running the project analysis. Further, users were not able to see the issues if the user selected any of the issue types (e.g., vulnerability) after running the project analysis.\ \ This fix corrects this issue. Users are now able to navigate to the issues page after running the project analysis. Further, users are now able to see the issues if they select any of the issue types (e.g., vulnerability) after running the project analysis.
2. **Fixed issue in rule for APEX “sf: {{FieldLevelSecurity}}” {Permissions should be checked before accessing resource}.**\ Previously, this rule was throwing violations that were false positives. This was occurring when a SOSL query having an inner query calls the related Object. The Object needs to be checked by using isAccessible() before accessing its data.\ \ *NOTE: We addressed a similar issue related to SOQL queries in a previous release. That update has been extended in this release to also include SOSL queries.*\ \ As per Salesforce documentation, when checking the Access for the inner query object, it allows to check by using \_\_c, but while making inner query on related Objects, it must be in plural and end with \_\_r.\ \ *This fix corrects this issue.* In this enhancement, the Object is checked by using isAccessible() before accessing its data.\ \ Verified the rule “Field Level Security Vulnerabilities” for the following scenarios: 1. Rule is throwing a violation if isAccessible is not checked for the objects used in the inner query:
2. Rule is not throwing the violation if isAccessible is checked for the objects used in the inner query.
**REMINDER**: In the previous release, we added support for SYSTEM\_MODE in this rule. A new parameter has been added, allowing users to choose true or false to include or ignore violations related to SYSTEM\_MODE.\ \ We have verified the rule: FieldLevelSecurity for the following scenarios: * Rule is throwing the violation if the object is NOT checked via isAccessible for the methods used in the inner query. * Rule is not throwing the violation if the system mode value is set = “true” (and the object IS NOT checked via isAccessible for methods). * Rule is not throwing the violation if the system mode value is set = “false” (and the object IS checked via isAccessible for the methods).
3. **Fixed issue with Retention Period settings**\ The retention period for project branches in CodeScan was not functioning properly. The UI is able to be set, but it does not affect the cleanup of branches within the project.\ \ This setting can be found in Project Settings > General Settings > Housekeeping > Delete inactive branches and PRs after.\ \ Also, the text in the “Branches” menu did not reflect the branch retention length change:
Verified the Retention Period fix for the following scenarios: 1. In the UI, users are able to set **Delete inactive branches and PRs after** value:
2. Users are able to see the same branch retention length value on the **Branches & Pull Requests** page.
4. **Fixed issue with Group Synchronization for SAML connections**\ We uncovered an issue with Group Synchronization during a recent customer implementation. We identified the root cause and a code change delivered in this release fixes the issue. Group synchronization is now working as designed. Further, we verified the Group synchronization option in SAML connection on a customer environment and have reported that this capability is working as expected. ## Release Notes 24.0.13 **Release Date: 30 October 2024** ### Summary CodeScan 24.0.13 is comprised of the following 4 components: * [1 Enhancement](#enhancement) * [3 Fixes](#fixes) Component details are listed in their corresponding sections within this document. ### New Features There are no new features associated with this release. ### Enhancement 1. **Enhancement to Rule for VF: “"vf:AvoidJavaScriptScriptlets”** \ \ We recognize that using direct \