The Knowledge Base is your 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:

• — Structured CI/CD pipelines for Salesforce. Aligns governance with acceleration.

• — Industry leading static analysis to enforce quality and secure code before it ships.

• — Resilient, compliant backup and recovery tailored for complex Salesforce data models.

• — Real-time permission intelligence and compliance automation. Prevents access risk before it becomes exposure.

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

• Precision answers, fast. Use our embedded AI assistant to extract exact steps, explanations, and insights from our full documentation library.

• Stay informed. Track feature updates, patch releases, and roadmap-aligned improvements—built for enterprise-readiness.

• From initial configuration to advanced workflows—our user guides provide structured clarity for every role and function.

• Self-serve solutions to unblock your team and reduce downtime.

Can’t Find What You’re Looking For?

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

Quick Access

Stay informed — this page is your go-to destination for all organization-wide announcements.

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, Vault, and nCino Integration.

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.

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.

CodeScan Self-Hosted

Release 24.0.8

19 July 2024

1. Rule enhancement for Misuse of Assert Class Included the ability to configure parameters for the "Misuse of Assert Class" rule, specifically for the Assert methods Assert.isFalse, Assert.isNotNull, hard-coded values, and Assert.areEqual, so that user can customize the rule to better fit the coding standards and practices of their project.

2. Rule Enhancement for “Avoid Using Test.isRunningTest()” {APEX Rule}: Previously, this rule was flagging violations when finding methods written as Test.isRunningTest(). This rule has been enhanced to also flag violations when finding methods written as System.Test.isRunningTest().

3. Decrease False Positives reported for Rule “sf:FixDuplicateMethods” Summary: CodeScan recognizes that methods should not share the same implementations. As such, the scope of the rule will be limited to methods with actual implementations, rather than including interface method declarations. This means the rule will now focus solely on detecting and addressing duplicate implementations within concrete classes, ensuring that only methods containing executable code are evaluated. Violations reported by this rule will now include details of all duplicate methods affected. This means each violation will list every instance of a method that shares the same implementation, making it easier to identify and resolve duplicated code. These updates will make the rule more precise, and its violation reports more comprehensive, enhancing its effectiveness.

4. Enhancement to Rule "Field-Level Security" (FLS): CodeScan’s FLS rule did not detect DML methods called when syntax is insert (record), update (record), etc. Instead, FLS was only detecting when “insert record;” syntax was used. We made a parser update within CodeScan and an enhancement to the rule was applied, which corrected the syntax detection.

5. Enhancement to Rule "Cyclomatic Complexity" Summary: Several enhancements were applied to the rule cyclomatic complexity, including adding the decision points '?', '&&', '||', and 'catch'.

6. New Rules: CodeScan Polyfill Protection We are excited to announce that CodeScan has been updated with crucial enhancements to address recent security concerns related to polyfills. Recent advisories have highlighted significant threats stemming from polyfills, particularly those distributed via the CDN polyfill.io, which are linked to malware. This update introduces advanced protection mechanisms to ensure your Salesforce environment remains secure.

Here’s how CodeScan is advancing your security:

1. Configuration Scanning: Our enhanced system now scans the configuration settings of Salesforce components, including Salesforce Sites, Salesforce CORS (Cross-Origin Resource Sharing), and Salesforce CSP (Content Security Policy), to detect any unauthorized calls to polyfill.io domains.

2. Component Scanning: We are scanning the core Salesforce components that enable developers to build sophisticated, custom user interfaces including Visualforce, Aura, Lightning, and other web components

3. Package Scanning: Our updated scanning mechanism checks downloaded packages from Salesforce AppExchange to ensure they do not contain insecure calls to polyfill.io domains

Activate the Polyfill rules, Avoid Script References to Polyfill.io, and Avoid Configuration References to to your custom quality profile to begin using them.

Rule Updates

1. The 'Hard-Coded Credentials' rule name has been changed to 'Use Named Credentials' for clarity.

2. 'Use Named Credentials' and 'Field-Level Security' rules have updated descriptions highlighting Salesforce best practices and better paths to resolution.

Bug Fixes

Fixed a false positive in the rule 'Avoid using methods getDescribe and getMap inside Loops' when using custom methods with similar names.

Major Updates

23 April 2023 Release Date

(CodeScan v 23.1.0)

1. New policy rules added for Salesforce Metadata

The complete CodeScan rules list can be accessed .

Improvements

UI/UX Improvements

• New interactive and appearance have been introduced to the CodeScan Welcome screen. Two new options, Application Security Testing and Policy Management are offered when you first log in to CodeScan. If you select Application Security Testing, you will be directed to the Projects page, which is now your default homepage. As a result, when you log in to CodeScan the next time, you will be immediately redirected to the Projects page. Similarly, if you choose Policy Management, you will be navigated to the Policy Results screen, now set as your default homepage.

Other improvements

• This release includes minor stability fixes and improvements for the CodeScan platform.

Minor Releases / Changelogs

7 November 2023

(CodeScan v.23.1.6)

This update included minor improvements.

1 November 2023

(CodeScan v.23.1.5)

The following was updated:

October 2023

(CodeScan v23.1.4)

The following rules were updated for release 23.1:

September 2023

(CodeScan v23.1.3)

What's New:

CodeScan Self-Hosted version 23.1.3 (now compatible with SonarQube™ version 10).

31 May 2023

(CodeScan v23.1.2)

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

• Starting from version 23.1.2, CodeScan supports integration to GIT with SSH Keys and supports ssh:// protocol. Connecting to GIT repository using the Secure Shell Protocol (SSH) provides a secure channel over an unsecured network. )

• Salesforce Spring '23 (API version 57.0) Support: To keep our product up to current with the most recent Salesforce upgrades, CodeScan supports the most recent API 57.0 version in this release.

• This release also includes insecure dependent libraries upgrade and other significant security improvements.

12 May 2023

(CodeScan v23.1.1)

• CodeScan self-hosted has been upgraded from 22.8 to 23.1.1 version.

• This release includes Apex-pmd dependency upgrade and significant security improvements. Updating is strongly recommended.

Guard 25.2.9 Release Notes

Release Date: 3 December 2025

New Features

Embedded Virtual Assistant

A new in-product chatbot that provides real-time guidance on product features, navigation, troubleshooting, and best practices.

Includes:

• Floating in-app widget

• Natural language Q&A

• Documentation-backed responses

• Smart fallback and escalation to Support

Enhancements

Permissions Explorer Enhancements

Permission History

A new Permission History feature allows users to select one or multiple permissions and view history of all modification events across profiles, permission sets, and permission set groups. Results are auto sorted by permission name for streamlined review.

Alternative View by Profile/Permission Set

A new view selector supports switching between:

• Matching Users (default)

• Matching Profiles

• Matching Permission Sets

• Matching Permission Set Groups

Available in both Permissions Explorer and Explore Object Access.

Session-Wide Org Preselection

Selecting a Salesforce org in any feature now auto-selects it across all features for the duration of the session. Logging out clears the selection.

Salesforce Orgs Accessible from Main Menu

Salesforce orgs are now directly accessible from the main navigation menu, improving discoverability and reducing navigation steps.

Tenant Name Displayed in UI

Users can now see their tenant's name next to the Release version in the bottom-left corner of the interface, providing better environment awareness.

Spring Boot Upgrade

The platform has been upgraded to Spring Boot 4.0 for enhanced performance, security, and framework stability.

Bug Fixes

Missing Salesforce Field

User Activity Monitoring now works even in orgs missing the User.LastPasswordChangeDate field, preventing GQL errors.

Risk Assessment

Multiple issues have been fixed, including:

• Incomplete Risk Assessment results

• Failure to refresh after Permission Explorer errors

• Errors parsing Salesforce API usage statistics

Guard 25.2.8 Release Notes

Release Date: 26 November 2025

Improvements

Salesforce Org Dashboard Enhancements

• Added Change Monitoring and Data Classification widgets to the Salesforce Org Dashboard.

• Widgets link directly to their respective feature pages.

• Updated the Executive Report to include Change Monitoring and Data Classification insights.

Password Hints

• Added clear password requirement hints to the New Password screen.

• Helps users understand the strict password criteria and successfully set up their account.

Bug Fixes

Risk Assessment: Certificate Values

• Fixed the formatting of certificate details.

• Shows “No certificate created” when no certificates are available.

“Sync to Salesforce” button

• Fixed an issue with the Sync to Salesforce button appearing multiple times in Data Classification.

Placeholder in Permission Explorer

• Improved placeholder text shown in the Permission Explorer.

• The placeholder now displays the intended guidance.

Guard 25.2.7 Release Notes

Release Date: 29 October 2025

New Features & Enhancements

API Security Dashboard

Gain deeper insight into your connected apps and organizational exposure with the enhanced API Security Dashboard.

View key risk metrics, filter results by org, explore detailed app information, and export data for further analysis — all from a responsive, easy-to-use interface.

Permissions Explorer – Support All Permissions

The Permissions Explorer now automatically supports all available Salesforce permissions, giving you a complete view of your org’s access setup.

A new “Other” category dynamically lists uncategorized permissions, ensuring nothing is missed and reducing manual effort.

Permissions Explorer – Object Permissions Saved Queries

You can now save custom Object Permission queries with names and descriptions, making it easy to revisit important configurations without rebuilding them each time.

Help Section Improvements

Access to support resources is now simpler. The Help menu has been redesigned to include quick links to the Support Portal, Guard Product Guide, and Support Login Access.

Guard Home Page Update

The Guard home page now features interactive cards that highlight recently added features. Each card links directly to its feature page for quick navigation, and the updated Change Monitoring card reflects the latest functionality for easier discovery.

Bug Fixes

Permissions Explorer Field Error

Fixed an issue where the “Approve Uninstalled Connected Apps” permission caused an error indicating that the field PermissionsCanApproveUninstalledApps did not exist in the PermissionSet entity.

Permissions Explorer Not Displaying Permissions

Resolved an issue where some permissions were not displaying correctly in the Custom Explorer view for some environments. Permissions now load correctly under their respective categories.

Guard 25.2.6 Release Notes

Release Date: 15 October 2025

New Features

Sync Data Classification Results to Salesforce

We’re thrilled to announce that users can now sync Data Classification results directly back to their Salesforce org. This closes the loop between AutoRABIT Guard and Salesforce, keeping compliance data consistent and up to date.

Highlights:

• Push Data Classification results (compliance categorizations and relevant regulations) back to Salesforce.

• New table view with field selectors, compliance and regulation columns, and sync status.

• “Sync to Salesforce” button for bulk or individual field syncs.

• Field detail view enhanced with Compliance and Sync options.

Impact: Automates alignment between Guard and Salesforce for compliance data — reducing manual effort, errors, and audit risk.

Salesforce Org Summary Dashboard

A brand-new Org Summary Dashboard provides a unified overview of an org’s health, compliance, and risk posture.

Highlights:

• Aggregates data from multiple modules:

  • Risk Assessment

  • API Security

  • Permissions Explorer

Impact: Gives customers an executive-level view of org performance and compliance in one place.

Support Login Access for Secure, Audited Troubleshooting

We’re introducing Support Login Access—a secure, auditable way for AutoRABIT Support Engineers to access Guard instances with customer approval and full transparency.

Highlights:

• Dedicated “Grant temporary Support access” screen.

• Customers approve access by providing case details, support representative email, and preferred access duration (7, 15, or 30 days).

• Support users are created as read-only accounts; activity is fully logged and auditable.

• Customers can revoke access at any time.

Impact: Faster issue resolution with complete transparency, security, and customer control.

Enhancements

Re-authentication for Salesforce Orgs

We’ve added a “Reauthenticate” button to simplify reconnecting Salesforce orgs without deleting them.

Impact: No more data loss when tokens expire—orgs, access controls, and rules stay intact.

Display Risk Level of Changes in Change Monitoring

Module: Change Monitoring Risk levels (Low, Medium, High) are now visually displayed for each change.

Impact: Greater visibility into risky activities and faster prioritization of security review.

Capture Detailed Profile Permission Changes in Change Monitoring

Change Monitoring now records granular details when user permissions change on Profiles, aligning with existing tracking for Permission Sets.

Impact: Improved traceability and audit accuracy, enabling downstream features.

Tabular View in Risk Assessment

Introduced an alternative table view for displaying risks, complete with sorting and filtering by name or properties.

Impact: Simplifies navigation and analysis, especially for large number of orgs.

Separated Status and Severity in Risk Assessment

The previous single “Status” field was split into two:

• Status: Unresolved, Resolved

• Severity: Warning, Critical

Impact: Improves clarity, ensuring severity and progress are tracked distinctly.

Org Selection from Main Detail Page in Permissions Explorer

Added the ability to change the org directly from the main detail page, streamlining workflows.

Impact: Saves time for admins managing multiple orgs.

Show/Hide Frozen Users in Permissions Explorer

Added a new “Show Frozen Users” checkbox in Custom Explorer.

• Unchecked (default): frozen users excluded.

• Checked: frozen users included.

Impact: Provides clarity and control in results interpretation.

Bug Fixes

Notification Rules in Delete Org Confirmation Modal

Fixed an issue where the Delete Org confirmation modal displayed unrelated notification rules.

Impact: Now shows only items tied to the org being deleted, eliminating confusion.

Guard 25.2.5 Release Notes

Release Date: 24 September 2025

User Activity Monitoring

A new User Activity Monitoring section is now available under Compliance, giving admins real-time visibility into Salesforce users' activity.

Highlights

• Real-time monitoring

• Accessible via the standard org switcher

• Data sourced from Salesforce

Why it matters: Strengthens compliance visibility and enables proactive security monitoring of user behavior.

Change Monitoring Notifications

We’ve introduced a dedicated Real-time Change Notifications section with pre-built notification templates, making it easier to detect and respond to critical security-related changes.

Highlights

• Pre-built templates for key events, including:

  • Profile created

  • Password policy modified

  • User assigned to new profile

Why it matters: Helps enforce Compliance requirements and ensures visibility into high-impact configuration changes.

Tenant Data Expiration & Deletion

Tenant data now has a mandatory expiration time to enforce lifecycle management.

Highlights

• Mandatory expiration is set at tenant creation.

• Automated tenant deletion is triggered on the expiration date.

• Advance notice: Tenant managers receive an email 5 days before deletion.

Why it matters: Ensures consistent data lifecycle management and enforces retention limits.

Event Logging & Audit Records

The platform now provides comprehensive event logging to strengthen accountability and monitoring.

Highlights

• Audit records for key events.

• Logs safeguarded against unauthorized modification or deletion.

• Supports audit reduction, correlation, and reporting for easier compliance review.

Why it matters: Provides robust traceability and supports effective security investigations.

Bug Fixes

• Salesforce Org Registration OAuth Error: Fixed an issue preventing new Salesforce Orgs from being registered due to OAuth flow failures.

• Password Reset Flow: Password policy error messages now clearly display complete requirements

• Permission Explorer – User Metadata: “User Created By” displays details properly

• Permission Explorer – Custom Objects: Object access results are displayed correctly for custom objects.

Guard 25.2.4.3 Release Notes

Release Date: 15 September 2025

Enhanced Export Capabilities

• Change Monitoring Export

  • Users can now export the Change Monitoring Changes table into CSV file.

  • Export includes all columns available in the UI, as well as detail and modifiedProperty fields for improved auditing and analysis.

Other Enhancements

• Copy as JSON

  • A new “Copy as JSON” button has been added to the Permissions Explorer.

This feature allows users to copy the entire JSON response, which simplifies troubleshooting, data sharing, and downstream analysis.

Bug Fixes

• Implemented additional APIs and added extended logs for deeper insights during troubleshooting, improving visibility into system operations.

Guard 25.2.4 Release Notes

Release Date: 10 September 2025

API Security

We’re launching API Security in Guard to help customers identify and mitigate risks from third-party apps connected to Salesforce. As attacks on Salesforce orgs increase, including from unverified or over-permissive apps, this feature gives teams visibility into which apps are connected, how they’re being used, and whether they pose a risk.

AutoRABIT Guard introduces a new API Security tab under the Risk section. From here, users can inspect API activity for a specific Salesforce org in real time.

Value to Users:

• Increased security visibility: Spot risky or shadow apps that might otherwise go unnoticed.

• Proactive defense: Prevent over-permissive apps from giving unauthorized users access to critical data.

• Multi-org management: Quickly assess and compare API risks across all Salesforce orgs.

Permission Explorer Enhancements

User Details at a Glance Admins can now view detailed user information directly within Permissions Explorer, including:

• Full name, active/inactive status, and last login.

• Creator details and their current status.

This makes it faster to investigate suspicious permissions and strengthens overall security posture.

Object-Level Access Insights A New Object Access Mode makes it easy to see who can perform actions (Read, Create, Edit, Delete) on both standard and custom Salesforce objects. With filtering by Profile, Role, or Email, compliance audits and security reviews are now faster and more accurate.

New Filters in Permissions Explorer Permissions Explorer now offers additional Super Admin permission filters, including:

• Setup & Configuration access.

• AppExchange package downloads.

• Approval of uninstalled connected apps.

These updates give admins greater visibility into high-risk privileges.

Risk Assessment Improvements

• Business-Oriented Risk Labels: Risks are now described in simple, more understandable terms. Once resolved, risks display positive compliance outcomes to reinforce progress.

• Navigation Enhancements: Users can browse between risks with new “Previous” and “Next” buttons, cycling through seamlessly.

• Dedicated Risk Detail Page: Clicking on a specific risk now opens a full detail page, providing richer context and better usability.

• Certificate Settings Clarity: Updated UI labels make certificate key sizes and expiration values easier to understand and configure correctly.

These changes make Risk Assessment more accessible for both technical and non-technical stakeholders, while streamlining the review process.

Usability & UI Enhancements

• Information Hierarchy: Organizations are now grouped into clear priority categories (Critical, Quick Wins, Compliant), making it easier to focus remediation efforts.

• Improved Icon Visibility: Table header icons are now larger and easier to read, improving accessibility and UI consistency.

• Data Classification Transparency: A new “Non-Started” state prevents confusion and allows users to trigger analysis manually when needed.

Bug Fixes

• Data Classification Export: Email notifications correctly include attached exports.

• Permissions Explorer: Accurate Access visibility ensured.

• User Management: Enforced validation for mandatory fields and added clear toast messages for success/error feedback.

Backend & Infrastructure

• Database Cleanup: Removed legacy tables for improved performance and maintainability.

• Tenant Deletion API: A new API introduced to enable safe and auditable tenant removal.

Guard 25.2.3 Release Notes

Release Date: 20 August 2025

New User Creation Simplified

Creating new users is now faster and more flexible. Admins can set up accounts with just an email address and role. Other details (username, first name, and last name) are optional and hidden by default but can be filled out as needed.

• The system now automatically handles username conflicts by suggesting available alternatives.

• The user list view and user icons have been updated to reflect these enhancements.

Improved Account Protection

To enhance security and prevent accidental or malicious account removals:

• Admins can no longer delete or deactivate their own accounts but still can manage Standard User accounts.

• Standard Users cannot delete or deactivate their own or any other accounts.

This change helps maintain system stability and protects privileged accounts.

Stronger Role Management Controls

We’ve introduced new safeguards to reduce the risk of privilege loss or escalation:

• Admins can no longer downgrade themselves to Standard User.

• Admins can still promote Standard Users to Admin.

• Standard Users cannot change anyone’s role.

• All role changes are now logged for better auditing and compliance.

Single Sign-On (SSO) with Enhanced Security

Guard now supports Single Sign-On (SSO) using encrypted SAML assertions. This ensures:

• Sensitive authentication data is securely transmitted.

• Reduced risk of data interception or tampering.

• Compliance with federal security standards.

Bug Fixes

• User Unlocking: Resolved an issue with locked accounts that couldn’t be unlocked from the Settings page. Admins can now restore users' access without any errors.

Other Enhancements

• Security & Compliance: We have strengthened our platform’s security by implementing targeted improvements that meet stringent federal standards. These updates reduce potential attack surfaces and further enhance data protection.

• Implemented a few back-end optimizations to enhance system stability and ensure long-term maintainability, supporting a smoother and more reliable user experience.

Guard 25.2.2 Release Notes

Release Date: 23 July 2025

1. Risk Assessment is goal-oriented now!

We have grouped risks under four key Security Goals:

Goal 1: Establish Secure Access & Identity

Ensuring only authorized users access Salesforce, their identities are verified, and highly privileged access is governed.

Goal 2: Harden Application & Session Security

Protecting the Salesforce application from common web vulnerabilities, ensuring secure communication, and maintaining user session integrity.

Goal 3: Safeguard Data & Control Exposure

Protecting data confidentiality and integrity by managing sharing settings, controlling access to sensitive information, and limiting guest user access.

Goal 4: Ensure Foundational Platform Integrity

Maintaining the core security of the Salesforce platform via valid configurations for certificates, encryption, and secure external connections.

Users can see their progress towards achieving each Goal and remediate the associated risks accordingly.

1. Custom Permission Explorer queries can be saved

Just give your query a name and definitive description, and it will be saved for your future revisits:

1. New home page

To help navigate and get instant value, we are happy to introduce a brand-new home page:

1. Instance version details are available now in the bottom left corner of the expanded page:

1. New menu

To improve application navigation, in this release we have added a new menu:

1. While we enhance its performance and functionality, we have temporarily removed the Field usage (data) tab from Data Classification UI:

Bug Fixes

1. Zoho desk link now works as expected.

2. User menu is no longer cut off by browser window.

Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information for FAQs on AutoRABIT ARM.

CodeScan 21.5

Released Date: 30 Oct 2021

Keeping with our commitment to continuous improvement, our October 21 release of CodeScan offers new features and improvements that will make it more powerful and effective.

nCino Release Notes 24.1

Release Date: 16 June 2024

Overview

nCino 24.1 is a major release that encompasses the following release items:

• nCino Compare Functionality

• Enhanced Data Loader Pro Job Configuration

• Exclude the OwnerID from Automapping in nCino CI jobs

• Data Loader Pro Job Run Options in Configuration

New Features

1. nCino Compare Functionality

   Overview: This provides users with enhanced control and insight into the deployment of nCino Record-Based Configurations (RBC). Application: The nCino RBC Comparison Tool allows users to effortlessly compare RBC configurations between those ready for deployment and those already existing in the target environment. This comparison ensures that users can identify discrepancies, confirm consistency, and make informed decisions before finalizing deployments. Benefit: This tool addresses the need for a reliable method to ensure consistency and accuracy in RBC deployments, reducing the risk of configuration errors and streamlining the configuration management process. Further documentation: For more detailed information, please refer to our

2. Enhanced Data Loader Pro Job Configuration Overview: To provide users with greater flexibility and control over the data loading process by allowing the users to enable and disable the validation rules, workflow rules, and triggers.

Enhancements

1. Exclude the OwnerID from Automapping in nCino CI jobs

   Overview: Users can now disable the auto-mapping of ownerIDs between environments within the application.

   Application: This new option allows users to prevent the automatic mapping of ownerIDs during record-based configuration migration. This is particularly useful in scenarios where developers in lower environments, such as a development sandbox, have the necessary privileges to own configuration records but lack similar access in higher environments like QA or production. By disabling auto-mapping, users can manually set appropriate ownerIDs, ensuring a smoother and more controlled migration process.

   Benefit: Helps avoid issues encountered during record-based configuration migration due to limited access to record owners in higher environments. This enhancement ensures that migrations do not fail or cause access-related issues, improving the reliability and consistency of deployments across different environments.

   Further documentation: For more detailed information, please refer to our .

Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information here for FAQs on Vault.

We are thrilled to announce that you can easily change your Super Admin with our new 23.1 release.

With the new 23.1 release, we’ve consolidated the roles of Super Admin and Registered Admin into a single empowered Admin role. But also with the new 23.1 release, we have added a new feature so you can assign the ex-Super Admin from your login.

Please follow the simple steps below, making sure you are on the latest 23.1 build.

1. Log in with your Admin credentials. Go to the Users section in the Admin panel.
2. From the User tab, you will see the * symbol next to the current Super Admin name. Click on the Edit icon.
3. Edit the previous Super Admin user, remove the Admin access by pressing the 'Deactivate' button on the right.
4. Once the deactivation is completed, you will see the other Admin being promoted to Super Admin.
5. Once you're finished, save the changes. You will get a confirmation pop-up window about the new Super Admin on the next page. Log out and log in again.

CodeScan 4.3

New Features

New Apex Security Hotspots

• Deserializing JSON Is Security-Sensitive: Deserializing an object from an untrusted source is security-sensitive. An attacker could modify the content of the data.

• Encrypting Data Is Security-Sensitive: Encrypting data is security-sensitive. Although most encryption problems are solved or managed by Salesforce, care must be taken when relying on encryption.

• Type Reflection Is Security Sensitive: Dynamically executing code is security-sensitive. If the code comes from an untrusted source, the untrusted source may be able to choose which code to run.

• Using Cookies Is Security-Sensitive: Attackers can use widely available tools to view the cookie and read the sensitive information. Even if the information is encoded in a way that is not human-readable, certain techniques could determine which encoding is being used, then decode the information.

• Using UserInfo.GetSessionId() Is Security-Sensitive: The use of UserInfo.GetSessionId() is security-sensitive. Ensure that you need to do this.

New Visualforce Security Hotspots

• Using GETSESSIONID() and $API.Session_Id is security-sensitive: The use of GETSESSIONID() and $API.Session_Id is security-sensitive. Ensure that you need to do this.

Quality Profiles

• Removed Unescaped Source rule from default Apex profile (v4.3.12).

• Removed deprecated rule javascript: S2228 from Salesforce Lightning Quality Profile (v4.3.9).

Enhancements

• SonarQube™ Ant task has been updated to 2.6.0.1

• SOQL Injection Rule updated and improved.(v4.3.11)

• Open Redirect Rule updated and improved. (v4.3.11, v4.3.12)

Bug Fixes

• Bug fixed in RightLineBracesPositions rule.

• Bug fixed in Field Level Security Vulnerabilities rule. (v4.3.10)

• Bug fixed in Preserve Stack Trace Rule (v4.3.12)

• Bug fixed in Unescaped Source Rule (

CodeScan 22.2

Released Date: 26 Jan 2022

New Features

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

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.

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.

This release incorporates new features, enhancements, and resolved issues from all previous significant releases. If you're upgrading from an earlier version of Vault, check the release notes for any interim versions or details about additional improvements in this release over your current release.

Vault 23.2.13 Release Notes

August 2023

What's New?

View Archived Data through Vault Connect (Beta)

The archival capabilities of Vault are now enhanced further to create a connection between Salesforce and the storage environment (AWS S3 bucket), leveraging Salesforce Connect with OData 4.0 adapter to display the archived records directly within Salesforce without having to perform complex data loading operations.

Prerequisites

1. Salesforce Connect OData 4.0 adapter license

2. Reach out to [email protected] to express your interest in participating in the beta program.

Pricing

Please reach out to your respective Customer Success Manager or Account Executive for more details on the pricing of this capability.

Highlights

1. OData protocol is an open and platform-independent protocol that can be integrated with the system of the user’s choice (along with Salesforce) as it exposes REST APIs for consuming and querying data from the underlying archives.

2. External objects support most of the capabilities that standard and custom objects have in Salesforce.

3. No need to install any managed packages or write custom scripts in Salesforce.

Limitations

1. Files and attachments are not supported for viewing through external objects in Salesforce. This will be supported in the upcoming version of Vault Connect scheduled for the end of Q4 ’23.

2. Salesforce OData 4.0 adapter has a limitation on the number of callouts per hour. This is going to be addressed with the support for the Salesforce OData 4.01 adapter in the subsequent versions of the capability.

3. Relationships between external objects and Salesforce objects need to be established manually (like if cases are archived and they are related to accounts that are not archived, the reference to accounts that are in the Salesforce object will be available in the external object but will not be reflected as a lookup relationship). The plan is to support the automated recreation of these references by the end of Q4 2023.

For details on how to configure Vault Connect, please click here to access our .

Vault 23.1.12 Release Notes

January 2023

What's New

Multi-Factor Authentication (MFA) support

Currently, Vault allows usernames and passwords or SSO-based authentication to grant users access to the Vault application; however, most of our customers requested the implementation of an additional layer of protection to prevent the misuse of their credentials if user credentials were compromised. With MFA now supported, it will allow our users to add Google, Salesforce, or other comparable authenticator apps to provide an authentication code at login.

Unique Identifiers for Object

With this update, we've added the capability to assign a unique identification to each object, preventing the generation of duplicate records. The mapping between source and destination records was not previously available with Vault when records were available in a sandbox, making it impossible to uniquely identify the records in the destination.

Thanks to this capability, every entity in the Salesforce org can now have a unique identifier configured. You can now restore or replicate data without recreating duplicate records.

Enhanced schema representation in restore/replicate

With the most recent Vault 23.1 release, we improved the schema representation by showing one level of the child/parent objects at a time. The tree can now be expanded based on your selection rather than the entire tree, which speeds up the download of the schema data and improves the UI.

The significant improvements are:

• Shows the user one level of the child/parent objects at a time.

• Expand the tree based on user selection instead of expanding the entire tree.

• The schema is easily searchable, and objects are easily selectable.

Ability to search records in backup with partially matching values

We have now made it possible to search backups for records selectively using a term that partially matches them. Users can now search backup records with partially matching values instead of using the whole value as the search keyword.

Description field for backup and archive configurations

Users need to understand the details of the config created, and it is helpful for any new member to understand the configs setup and why they were created. As a result, we included the Description box on the Configuration page so that you may describe why you created the backup and archiving configurations. This description field can also be seen on the Config Summary screen.

Improvements

• Improved pagination to reduce page load times across the modules.

• Minor performance, bug fixes, and security improvements can also be observed in the Vault portal.

Changelogs

3 Jan 2024

Vault v23.2.14

1. Backup Delay: The backup is taking longer because FeedItem and EmailMessages are processing for over an hour.

2. Suggested Workaround: A workaround was suggested to exclude Total Price and Unit Price to resolve the issue.

3. Policy Level Verification: Verification revealed issues with multiple policies when selecting policy-level changes.

7 June 2023

Vault v23.1.11

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

1. An issue was resolved where users were experiencing a problem replicating records from production to a developer sandbox with the backup with hierarchy option. In this issue, when attempting to replicate over 1100 records, no records were being populated in the developer sandbox.

2. An issue has been resolved that affected manual backups. Users were unable to obtain all the objects in the backup, even when using the correct configuration settings.

3. An issue has been addressed where users were archiving jobs with a configuration set to limit to 1 million records, but more than 1 million records were being archived. This issue has been fixed.

17 May 2023

Vault v23.1.10

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

1. Vault now supports Single Sign-On (SSO) capability through its auto-login function.

10 May 2023

Vault v23.1.9

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

1. Fixed an issue for the Restore/Replicate operation where the Person accounts restoration/replication failed when the backup got triggered with Person contacts.

03 May 2023

Vault v23.1.8

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

1. Fixed an issue where the Vault archival failed with "No Records Archived" status in the Vault UI.

2. Fixed an issue where replicating the Assest records from the source to the destination org ran for a few hours, but no records were picked up.

3. Fixed an issue where the scheduled backups failed for production orgs.

26 April 2023

Vault v23.1.7

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

1. Fixed an issue where the scheduled Archival jobs ran even after the Config was deleted.

2. Fixed a bug where users had issues downloading the Label Names report in the Replicate section.

19 April 2023

Vault v23.1.6

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

1. Fixed an issue when replicating records from the production to a developer sandbox (1100+ records); no records were populated in the developer sandbox.

2. Fixed an issue where the archive job kept running after data were processed.

3. Fixed an issue with the Vault's data storage and management where the archive process failed as it could not write a backup to the Amazon S3 bucket.

12 April 2023

Vault v23.1.5

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

1. Fixed an issue where the users could not archive the ContentDocument files ().

2. Fixed an issue where the users could not edit or delete masking rules in the Replicate module (internal ticket).

3. Fixed an issue where the Archival jobs did not show all children's details in the Archive config info section (internal ticket).

29 March 2023

Vault v23.1.4

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

1. Fixed an issue when the archive jobs got stuck, and the following error was thrown java.util.concurrent.ExecutionException: [UnexpectedErrorFault [ApiFault exceptionCode='TXN_SECURITY_RUNTIME_ERROR'. Additionally, when multiple archive jobs were initiated in the Salesforce environment, the count of the archive records fluctuated. Now that the issue has been rectified, everything works as it should.

2. Fixed an issue where the Salesforce API limit for the backup triggered using the Bulk API differed from the limit displayed inside the Vault application.

3. Fixed an issue that stopped the replication jobs from migrating the Case and related objects to the production environment, including the Content Document, ContentVersion, and ContentDocument link

21 March 2023

Vault v23.1.3

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

1. Fixed an issue where users were trying to map case records which were eventually restored but not properly mapped.

2. Fixed an issue where the users could not use the SSO feature to log in to their Vault account.

3. Fixed an issue where users, while changing the password, the users were unable to see the Save button.

15 March 2023

Vault v23.1.2

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

1. Fixed an issue where the restore operation was stuck for hours, and in the end, the status threw as failed.

2. Fixed an issue where the replicate job failed with no error in the log.

3. Fixed an issue where the replicate Job is not replicating ContentVersion and ContentDocumentLink objects.

08 March 2023

Vault v23.1.1

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

1. Handling Salesforce session timeout in restore/replicate improved and performance improvement in the updateOldIdsWithNewIds method.

Guard Release Notes 25.1.7

Release Date: 9 July 2025

This release includes a few bug fixes, including improvements to information displayed under Field Usage of unsupported types.

nCino + DataLoader - Release 25.3.12

Release Date: September 28, 2025

Multi-Bucket Support

Enhanced multi-bucket handling to ensure records are processed without creating duplicate entries.

Viewing Diff Count

Fixed an issue preventing users from viewing record differences when multiple templates were committed to the repository. Diff counts now display accurately.

Templates with Multi-Buckets

Resolved a deployment failure scenario where templates containing multiple buckets caused object deployment errors.

Build Failure Due to Null Entry

Fixed a defect where builds failed because of null entry objects. Builds now complete successfully.

Error Uploading to S3

Improved stability of data uploads to S3 to ensure seamless and reliable transfers.

Multi-Object Set Template

Implemented safeguards to prevent failures in multi-object set templates during execution.

nCino + DataLoader - Release 25.3.11

Release Date: September 21, 2025

Multi-bucket Rollback

Enhanced rollback functionality to ensure that inserted records are deleted and updated records are accurately reverted to their previous state.

Multi-bucket – Duplicate Objects

Resolved an issue where duplicate objects were displayed when working with multiple buckets..

Single DataLoader – Attachments Processing

Fixed an issue where optional fields were incorrectly considered during delete operations — now only record IDs are considered for deleting the records.

Feature Deployment – Object Duplication

Addressed duplication issues when using the same branch with the VC Revision Range option including both commits. Objects are no longer duplicated.

Multi-bucket Support

Introduced support for multi-bucket functionality in templates, enabling better CI/CD data migration deployments and commits..

nCino + DataLoader - Release 25.3.10

Release Date: September 14, 2025

Fix for Field Order in DataLoader Module Results

Resolved an issue where the ID and Status/Error fields were displayed in an incorrect order when viewing success or failure results in the Data Loader modules.

Optimized Log Display for Bulk Operations

Enhanced the log display for bulk operations to present users with optimized, clear, and relevant information for better troubleshooting and analysis.

nCino + DataLoader - Release 25.3.9.1

Release Date: September 10, 2025

AuditLog – Null Pointer Exception Fix

A fix has been provided to address a null pointer exception occurring in instances with AuditLog enabled, ensuring stable and consistent execution.

nCino + DataLoader - Release 25.3.8

Release Date: August 31, 2025

Data Migration Flow Fix

Resolved an issue caused by an unwanted forward slash that disrupted the complete data migration flow in both nCino and Data Loader. Customers must re-run the affected jobs to process data successfully.

nCino + DataLoader - Release 25.3.7

Release Date: August 24, 2025

Uber Jar Dependency

The dependency on the uber jar has been removed. Bulk data operations are now handled programmatically in the backend, improving efficiency, stability, and maintainability of the system.

Handling Source ID

A Salesforce discrepancy previously prevented source IDs from being fetched correctly. This issue has been resolved with a code fix, ensuring accurate retrieval and consistency of source IDs.

Org-Level Permissions

A code fix has been applied to enforce correct permission requirements:

• Source ORGs now only require read access.

• Destination ORGs require write access.

nCino + DataLoader - Release 25.3.6

Release Date: August 17, 2025

Handling Record Types

A fix has been implemented to ensure that Record Types are now correctly assigned to records during processing. This resolves issues where records were previously created or updated without the appropriate Record Type association.

DataLoader Pro

A fix has been rolled out to ensure that, during data deployment, the deployment status is fetched accurately, resulting in a more reliable and successful deployment process.

nCino + DataLoader - Release 25.3.5

Release Date: Aug 10, 2025

Logs Enhancements

Improved logging capabilities for enhanced tracking and traceability.

Cloning Data Loader Pro Jobs

Enhanced Data Loader Pro job cloning to ensure accurate replication with all settings retained.

Data Loader Clone Functionality

Improved cloning process for Data Loader jobs to maintain configuration integrity.

DL File Handling

Resolved issues to ensure reliable upload, insert, and delete operations for files.

nCino + DataLoader - Release 25.3.4

Release Date: August 03, 2025

Commit Jobs

The processing of the commit jobs through the commit workspace has been streamlined.

DataLoader Pro – Stability Improvement

An issue affecting the reliability of Data Loader Pro job execution has been resolved, ensuring smoother performance under high-load conditions.

DataLoader Pro – Clone Issue

An issue that is occurring during the clone operation is rectified

DataLoader Pro – Clone Operation Fix

Resolved an issue where the clone functionality did not behave as expected, ensuring cloned jobs retain original configurations accurately.

nCino + DataLoader - Release 25.3.3

Release Date: July 27, 2025

CI Job Execution

CI Job execution via the queue has been streamlined to ensure consistent and reliable processing.

nCino & DataLoader – Leading and Trailing Spaces

A fix has been implemented to ensure leading and trailing spaces are correctly handled during nCino and DataLoader job executions, improving data accuracy and consistency.

nCino + DataLoader - Release 25.3.2

Release Date: July 20, 2025

Feature Template

Resolved an issue impacting feature template functionality to ensure seamless loading, selection, and execution across workflows.

Data Deployment via Migration Template

Implemented a fix to ensure reliable data deployment using migration templates, addressing inconsistencies during dataset migration.

nCino + DataLoader - 25.3.1 Release Notes

Release Date: July 13, 2025

Pagination

A fix has been implemented to ensure that pagination functions reliably and transitions between pages occur seamlessly without disruptions.

October 2022 - New Features, Enhancements, Improvements, and Bugs Fixed

New Features

1. SAML-based SSO for login

You can easily log in to CodeScan Cloud by setting up a Single Sign-On (SSO) through SAML-based third-party identity providers such as Okta, PingOne, and Microsoft Azure.

For more information, see .

2. CSV Export tool for CodeScan Cloud

The ability to download a CSV file containing the issues has now been added. The CodeScan CSV issue export option can be found in the More menu. Prior to this release, this functionality was only accessible to CodeScan Self-Hosted users; however, we have now enabled support for Cloud users as well.

For more information, see

3. New CodeScan Rule

CodeScan now has a new rule added to their Quality Profile called Do not use vulnerable packages, which checks for deprecated and outdated dependencies in the project and highlights the vulnerabilities available.

Enhancements

Scheduled Reports available for Project Branches

Previously, project reports were available for download for the main branches. With this update, we now support generating reports manually or by scheduling them for every project branch.

For more information, see

UX Enhancement

1. The drop-down list for the entry of Rule Parameters has been introduced to the improved Activate in Quality Profiles page. You could only feed regular text into fields prior to this release.

Fig 1: Old Screen

Fig 2: New Screen

1. With this update, the Add Member button on the Members page for all CodeScan versions is deleted.

Improvements

• This release includes significant security improvements. Updating is strongly recommended.

• The existing metadata rules in CodeScan have been tweaked for SFDX compatibility.

• Significant improvements in the ways GitHub is triggered within CodeScan.

Bugs fixed

• Fixed a minor issue where the analysis would start for both branches when merging a feature branch into the master branch. This shouldn't happen as analysis should be initiated only on the master branch and not the feature branch.

• Fixed an issue where the target branch's newly added code was not being fetched when the analysis was running.

• Fixed an issue where users could view invalid grant type errors while running a pull request analysis.

New Features

1. Comparison branches for Salesforce projects

Added the ability to add comparison branches to a Salesforce project in this release.

Key characteristics to look for:

• The comparison of issues

• The transfer of issue resolutions to the main branch of the Salesforce project.

For more information, see .

2. New nCino rules

Below are the nCino related rules added to the existing Apex/Salesforce Metadata rule sets and are tagged as “ncino-goldstandard.”

• Process Builder Must Reference Product: For general automation and validation best practices, associate actions in the system to a product line, product type, or product feature. Depending on how widespread the automation is, this ensures that follow-on phases for new lines of business have limited rework

• Workflow Must Reference Product: For general automation and validation best practices, associate actions in the system to a product line, product type, or product feature

• Validation Rule Must Reference Product: For general automation and validation best practices, associate actions in the system to a product line, product type, or product feature

3. Compute Engine parallel processing

This April's CodeScan cloud release includes the Compute Engine parallel processing capability. The key benefit is that it allows multiple analysis jobs to run in parallel in a fluid manner, reducing analysis job duration during peak usage and thereby improving user experience.

SonarQube compatible

CodeScan self-hosted is now compatible with SonarQube™ 8.9 and SonarJS 6.2+. For more information, see

Enhancements

1. Enhanced log report

The log report is now better than before. View your project analysis job's detailed log report, which includes the reasons for failed jobs.

2. CodeScan integration with Github

In this release, the CodeScan integration with GitHub actions has been improved. When working on Github actions, the report generation feature has been included, which displays accurate findings based on analysis.

Improvements

Minor performance, bug fixes, and security improvement can also be observed in the CodeScan portal.

Bugs fixed

• Fixed a minor bug where the scheduled Salesforce jobs were not running in an instance because of several hardcoded values in the product sources.

• Fixed an issue where the project analysis job took a long time to accomplish and displayed the "Job took too long" error in some instances.

This release incorporates new features, enhancements, and resolved issues from all previous significant releases. If you're upgrading from an earlier version of Vault, check the release notes for any interim versions or details about additional improvements in this release over your current release.

nCino + DataLoader - 25.2.12 Release Notes

Release Date: 06 July, 2025

Job Comment Retention

An issue where the Job Label would overwrite the existing Job Comment during job edits has been resolved. The comment field will now retain its original value unless explicitly modified by the user.

RBC Deployment Templates Accuracy

The logic for handling RBC Deployment Templates has been refined. The system now correctly accounts for omitted templates and accurately calculates the count of selected templates, ensuring consistent and reliable template tracking.

CodeScan On-Premises

Release Notes 24.0.4

Release Date: April 2024

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

CodeScan Self-Hosted

Release Notes 24.0.1

This update introduces several new rules and bug fixes for current rules and the CodeScan analysis.

Flow Rules

CodeScan 22.1

Released Date: 29 Dec 2021

New Features

nCino Release Notes 24.3.2

Release Date: 22 September 2024

1. Default Sorting by ExternalID for CI Jobs The sorting structure for "CI Jobs" has been updated. From now on, the ExternalID will be selected by default for sorting, replacing the previous selection of LookupKey.

CodeScan Self-Hosted Editions: Latest Release Dates

• Eagle Edition v5 was released on 17 October 2025.

• Tiger Edition v3 was released on 26 February 2025.

Numerous configuration options are available to users when setting up their profile in ARM. The Profile section allows users to view and update their basic information, personal email settings, etc.

To access user preferences, click your user name in the upper right corner and select Profile.

Personal Details

The Personal Details section displays your full name, ARM user name, email address, phone number, etc. Your personal details will be populated, as the system administrator must enter this information when creating a new user account. In this section, you can update your name, phone number, address, etc., accordingly.

My Projects

The My Projects section will list all the projects that you have created or have permission to view. Users with admin-level permissions will have access to all projects.

My Roles

The My Roles displays the list of roles assigned to the user. If you have admin roles and permission, you can perform all the tasks an administrator can perform and access all modules within ARM.

About Skip Mappings

If users maintain an individual version control branch for every release, they must map every branch to Salesforce Org and Version Control branches to keep synchronizing with Salesforce Org. To overcome this daily routine, ARM provides the option to skip the Org Mappings part and directly perform commits.

My Salesforce Orgs

View the Salesforce Orgs assigned to you, or you have permission to view.

My Version Control Mappings

View the Version Control Repositories here based on the Salesforce Orgs selected in the My Salesforce Orgs section. Map the required repositories by choosing the correct Credential from the drop-down field. Click Test Connection to determine whether the connection has been authenticated or not.

My ALM Mappings

Under My ALM Mappings section, you can map your ALM using your credentials or Re-Authenticate Jira ALMs configured with OAuth access.

For ALM type IBMRTC (IBM Rational Team Concert) and JIRA, we have added the filter to fetch specific work items according to the filter applied.

According to the filter set, only specific work items will get fetched. When the developers progress (via EZ-Commit or merge operation in ARM) on updating the ALM status, they are reflected on the corresponding work items. If the user wishes to discard the filter selected, uncheck the Apply My Filter option, and all work items will get fetched.

My Default Page

My Default Page is the first page that appears when you log in to ARM. You can customize ARM to open any page as the default page.

Mapping Your Profile with Version Control and Salesforce Org

The next step is to map your profile with the Version Control system you will be working with and the associated Salesforce Org.

1. Go to the Profile section.

1. Scroll down to My Salesforce Orgs.

2. Select the Salesforce Org and assign the Salesforce Org User to them.

1. Next, Scroll down to My Version Control Mappings.

2. Select the Repository and assign the user.

1. Click Save.

2. Go to Admin > SF Org Mgmt, select your org, and scroll down to Salesforce Org - Mappings.

3. Select the mapping against the version control that you have set up.

1. Click on Save Mappings.

Uploading Multiple Profile Files

413: Status Error: Users may encounter a 413-status error in the browser console when trying to upload duplicate profile files that have been resolved after downloading from version control. This occurs when users try to download numerous files at one time. Download one profile file at a time to resolve the error.

Inviting colleagues to AutoRABIT (ARM) lets them run commits, deployments, and CI jobs under their own accounts—so actions are tracked to the right person, and permissions stay aligned with their role. Only Org Administrators can create or modify users.

Adding a New User

1. Log in to ARM.

2. Hover over Admin and click Users.

3. Click Add User.
4. Complete User Details and assign a Role Permission Set that matches the person’s responsibilities.

5. Choose one of the activation options:

   • Save & Activate – sends the invitation email immediately.

   • Save Now & Activate Later – save the profile and activate at a future time.
6. The new user receives an email to set their password and log in.

7. Newly created users appear in Admin › Users.

Editing a User Account

You can edit most profile fields and permissions after creation—except Username and Email (they are immutable).

1. Go to Admin › Users and locate the user.

2. Click the Edit icon.
3. Update fields as needed and click Save.

FAQ

Can an AutoRABIT login username be changed after it has been created?

No. Usernames and emails are locked once the account is created. To correct either field:

1. Delete the old account (Admins: remove the user from the list).

2. Create a new account with the correct username/email.

3. Reassign the same roles and permissions.

Why am I unable to add more users to my account?

You’ve reached your organization’s license limit. Contact your account manager or AutoRABIT support to purchase additional seats or review discrepancies.

nCino Release Notes 24.2

09 September 2024

1. Ability to Download CI Job Backup Snapshot Users can now seamlessly download the entire backup snapshot of CI Jobs, providing quick and easy access to crucial data. Please refer to the Knowledge Base for more information.

2. Support for Post Deployment ORGs in Rollback We’ve added support for including Post Deployment Orgs in rollback processes. This enhancement ensures seamless rollback operations, maintaining environment consistency and control during deployments. Please refer to the for more information.

3. Skip Records Functionality Enhancement The Skip Records functionality has been improved by replacing the icon with a checkbox. Please refer to the for reference

4. Depicting Fields Excluded from Compare and Identifying Record Differences Between Environments Fields excluded from the compare operation are now clearly depicted, helping users focus on relevant data. Differences between records across environments are highlighted for quicker, more accurate assessments.

5. Option to Delete CI Jobs in Queue Users can now delete CI jobs directly from the queue, giving them greater control over their CI pipelines. This feature optimizes resource usage by allowing the removal of unnecessary or outdated jobs.

Standard User

A Standard User is an individual authorized by the Customer to log in to and directly use AutoRABIT’s subscribed products.

Additional Notes

• Platform Owners/Admins are included in the Standard User class, allowing customers to manage admin rights without affecting licensing terms.

• The number of licensed users represents the total unique users of the products, calculated throughout the entire course of the Subscription Term.

Platform Integration User

A Platform Integration User is an individual authorized by the Customer to commit to a Source Code Management (SCM) system, where that external commit is then used in any ARM process. This is primarily intended to represent users who interact with ARM through Git and do not have a Standard User license.

Tracking Platform Integration Users in ARM

AutoRABIT tracks the usage of ARM as an orchestration engine through version control systems. The unique identifier used is the associated email address. Therefore, it is important that activity be linked to official customer email addresses to avoid double-counting users who may use personal email addresses.

Key Points:

• Code Commits and Licensing: Any person who commits code to an SCM system, where that commit is later used in an AutoRABIT function, requires a Platform Integration License (unless the person committing has a active AutoRABIT ARM License). This would include external commits to the SCM System.

• Service Accounts: If a service account triggers automation or integrates with AutoRABIT, the individual or team responsible for the actual code commit must still hold a Platform Integration License. This ensures that all contributors whose actions trigger AutoRABIT processes are appropriately licensed.

• Commit Count in SCM Systems: For SCM systems such as Git, multiple commits pushed simultaneously are counted separately toward the user license.

Determining the Count of Platform Integration Users

Platform Integration Users are sold in blocks of 10. This means any user meeting the criteria above who is not also a licensed Standard User will be counted. These are not “named” users; instead, users are defined by their activity within the quarter. The count is recalculated each quarter.

Calculation:

• The average high-water mark of the two highest quarters is used, rounded up to the nearest block of 10, to determine the total Platform Integration User count for the term.

• Counts reset each quarter and include both new and recurring users.

Example:

ACME Corp purchases 10 Platform Integration User licenses.

• Quarter 1: 15 users

• Quarter 2: 8 users

• Quarter 3: 17 users

• Quarter 4: 5 users

The average of the two highest quarters (15 and 17) is 16. Since licenses are sold in blocks of 10, ACME oversubscribed by 6 users and would need to purchase an additional 10 licenses.

Notes:

• The subscription model aligns with the contract start date, not the fiscal year. For example, if the contract starts in May 2025, the quarterly data points would include: Q1 (May, June, July 2025), Q2 (August, September, October 2025), Q3 (November and December 2025, January 2026) and Q4 (February, March, April 2026).

• Licenses are sold in blocks of 10 and always round up. If oversubscribed by 6 licenses, purchase an additional 10. If oversubscribed by 11, purchase an additional 20.

• Unique Email IDs: ARM counts users via unique email IDs retrieved from Git. If an individual uses multiple email addresses for commits, they will be counted as separate users. To prevent this, ensure best practices when using Git.

Vault 22.2 Release Notes

What's New

Support for Serial Backups

With this release, we have added the flexibility to enable your backup configs to run in serial mode. This prevents overlap of backups triggered under the same config and helps reduce redundant data storage caused due to overlapping backups.

Access restriction through SSO for non-registered users

We’ve added the capability to Vault administrator to prevent the auto-creation of new users in Vault from SSO ID providers like OKTA and Microsoft Azure AD.

Notifications for Restore/Replicate operations

With this release, we have enhanced the capability of how the users get notified once an operation is performed inside Vault. You will now have a field to add multiple recipients who should receive notifications whenever the action is performed. The currently logged-in recipient will automatically be enabled to receive the notifications.

CodeScan offers three primary deployment options: Cloud, Self-Hosted, and Government. Release notes and information are available for each deployment type.

Credential Manager: Overview

CodeScan for Government

CodeScan for Government is a secure, compliance-focused solution designed to meet the unique needs of public sector Salesforce environments. Built with enhanced security protocols and governance in mind, it empowers agencies to maintain code quality, enforce standards, and reduce risk across their DevOps pipelines.

Please note: Access to CodeScan for Government release notes is currently limited to government license holders only.

CodeScan 4.4

New Features

New Cloud Features

• Salesforce Project Branch Types: when adding a sandbox to your Salesforce project as a branch, you are now able to specify the type of branch you would like to add (Long or Short). Find out more here about branches here.

New Metadata Rules

• BETA metadata ruleset added: our beta metadata ruleset has been added to this release. Currently, you will find rules covering security settings, custom fields, permissions, and record type ID's. This edition also includes a setting to define the metadata types to be downloaded. Find out more here for CodeScan Cloud and here for a Self Hosted package.xml file.

New Apex Rules

• Aura Controller Naming: Aura Controllers should adhere to certain naming conventions. Only classes linked to a page as a controller or extension are considered.

• Track Usage of @SuppressWarnings: overuse of the @SupressWarnings annotation can mean issues in your code are not picked up. This rule flags each usage to make sure it is needed.

• Track Usage of //NOSONAR: overuse of the //NOSONAR rule suppression can mean issues in your code are not picked up. This rule flags each usage to make sure it is needed.

New Visualforce Rules

• Avoid using Tab Characters Check (v4.4.5): checks that there are no tab characters ('\t') in the source code.

Enhancements

• Field Level Security now specifies the field it is failing on.

• Old Page API Version now specifies the API version in the message (v4.4.4).

• Metadata parsing was improved to fix memory errors caused by larger types (v4.4.5).

Bug Fixes

• Excessive Method Length no longer counts comments as lines.

• Use Singleton now ignores Aura controllers.

• NPath Complexity now calculates correctly around ternary statements.

• False-positive fixed in Unnecessary Boolean Assertion.

December 2022 - New Updates, Improvements

Date of release: 18 December 2022 Article last updated: 24 April 2023

New Updates

Frequently Asked Questions (FAQs) have been integrated within the product documentation for easier reference. Please refer to the information for FAQs on CodeScan.

nCino + DataLoader Release 25.4.10

Release Date: 07 December 2025

nCino – Deployment History Action Button Fix

A fix has been implemented to restore the functionality of the action button next to the download icon in Deployment History. The button now correctly expands the object set view, as intended.

Dataloader Pro – UI Sync Issue After Bulk Delete

A fix has been implemented to ensure that all jobs are immediately removed from the list after a bulk delete operation. Previously, one job continued to appear until the page was manually refreshed. The job list now updates correctly without requiring a browser refresh.

Login Screen Loading Issue – Template Dependency Optimization

A fix has been applied to prevent heap-space and restart issues caused by processing objects with complex parent dependencies during initial template creation. The system now skips non-selected standard and non-nCino package objects, ensuring the login screen loads reliably.

nCino + DataLoader Release 25.4.9

Release Date: 30 November 2025

DataLoader Pro – Multi-Level Parent Hierarchy Fix

A fix was implemented to correctly handle multi-level parent relationships during DataLoader Pro migrations. An issue where ancestor object failures caused master and parent objects to fail has been resolved. The migration flow now isolates such failures and works reliably, including when Automatic Apply Filter is enabled.

DataLoader Module – DB Optimization

Redundant database calls across DataLoader Pro and Single DataLoader execution flows were removed, including unnecessary process, job, and object lookups. Job execution now fetches only relevant in-progress records, minimizing load. These enhancements significantly reduce DB usage and prevent connection pool shutdown issues.

DataLoader Pro – Child Object Selection Fix

A fix was implemented to ensure that, when editing a DL Pro job, the child object list correctly displays all available child objects rather than only the previously selected ones. This resolves inconsistencies in object visibility during job configuration.

DataLoader Pro – Incorrect Parent Object Identification

A fix was applied to ensure only the intended parent objects are included during job execution. The issue occurred when an object acted as both a parent and a child to the master object. The logic has been corrected to prevent additional, unintended parents from being identified and processed.

DataLoader Pro – Job Redirect Issue Resolved

A fix was implemented to ensure that, after running a DataLoader Pro job, the application correctly redirects back to the same job. Previously, it always loaded the first job in the list. The redirect logic on the DL Pro landing page has now been corrected.

Corrected Error Message Handling

Resolved an issue where an incorrect authentication error was shown for query-related failures. The system now displays the proper error message when a connection exception occurs.

nCino + DataLoader Release 25.4.8

Release Date: 23 November 2025

Proxy Connectivity Issue – nCino & Data Loader

A fix was implemented to resolve failures in nCino and Data Loader operations when Salesforce connectivity was routed through a proxy. Bulk API requests now establish connections reliably without timing out when the proxy is enabled.

Schema Synchronization for Feature Migration Templates

A new option has been added to synchronize schema metadata directly within the Feature Migration Template. Triggering a sync refreshes the latest objects, fields, and attribute changes from Salesforce, ensuring templates remain up-to-date and reducing deployment failures caused by outdated schema definitions.

nCino + DataLoader Release 25.4.7

Release Date: 16 November 2025

Handling User Data

A fix was rolled out to make sure the user data such as jobs are handled properly once the user account is deleted from the Super Admin.

Handling Object Relations

A fix is provided to make sure the circular relations of objects in the buckets with multiple objects will be handled properly.

nCino + DataLoader Release 25.4.6

Release Date: 09 November 2025

Delta Preparation Enhancement

Enhanced delta preparation logic to ensure only relevant changes from the selected revisions are included when the source is Version Control (VC). This fix resolves migration failures caused by missing .csv files during deployment.

CI Job – Validation Rules Handling

Resolved an issue where the “Disable Validation Rules” setting was not honored during nCino CI job execution. The fix ensures that destination org details are correctly passed from the Agent to Rabbit, allowing validation rules to be accurately identified and disabled during deployment.

Audit Fields Handling in Data Migration

Resolved an issue where audit fields were incorrectly included during data migration, causing deployment failures for specific templates. The fix ensures audit fields are now processed only for objects that support them, preventing similar errors during deployment.

RBC Feature Deployment – Authentication Error

Resolved an issue where nCino RBC feature deployments intermittently failed with authentication errors despite valid credentials. The fix ensures record type data is properly saved during deployment, and additional loggers have been added to help trace any future occurrences.

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 (JWT Bearer) authentication to ensure uninterrupted connectivity. The migration can be done through Connections → {{ConnectionName}} → Migrate to OAuth, followed by the on-screen steps to confirm the connection status as “OAuth (JWT)”.

nCino + DataLoader Release 25.4.5

Release Date: 2 November 2025

Parent–Child Object Reference Handling

Implemented code changes to ensure parent object references in child records are correctly migrated when both parent and child objects are selected as child objects in a Data Loader Pro job.

Lookup Key Sorting Fix in Feature Commit

A fix was implemented to ensure the sorting field defaults to the lookup key during feature commit creation. The sorting field now switches to “Name” only when a lookup key field does not exist, preventing duplicate lookup keys in pull request file changes.

Dataset Loading Issue with Special Characters

Resolved an issue where datasets failed to load and got stuck at “Retrieving Iterations...” when the deployment label contained a “#” character. The label handling logic was updated to prevent URL truncation during dataset retrieval.

RBC Deployment – Invalid Field Error with Attachment Names

A fix was implemented to handle attachment names containing commas (,). Previously, deployments failed with an “Invalid Field” error when processing attachments with commas in their filenames.

nCino + DataLoader Release 25.4.3

Release Date: 19 October 2025

Connection Pool Shutdown Issue

Optimized redundant database calls to prevent connection pool shutdown errors. This enhancement ensures stable and consistent connections during data processing, eliminating the “Connection Pool Issue” encountered by users.

nCino + DataLoader Release 25.4.2

Release Date: 15 October 2025

Person Account Org

A fix has been implemented to ensure records are processed correctly in environments with Person Account–enabled orgs, preventing migration failures.

Skipping Migration for Selected Parent Records

Resolved an issue where parent records were incorrectly migrated even when the Automatic Apply Filter option was selected. The system now skips parent records as intended.

Cloning Single DataLoader Job

Addressed an issue that prevented cloned DataLoader jobs from updating records properly. Cloned jobs now retain and update data accurately.

Feature Management Versioning

Implemented a UI enhancement to ensure versioning information displays correctly within the Feature Management section.

DataLoader Pro – Invalid Query Error

Fixed an issue that occurred during job execution when no mappings were provided. The system now handles empty or null mapping values gracefully during job editing and saving.

DataLoader Pro – Circular Reference Error

Introduced a safeguard to handle empty source and destination external ID conditions, preventing circular reference errors during data processing.

nCino + DataLoader Release 25.4.1

Release Date: 5 October 2025

Person Account Org Handling

Resolved an issue that caused record failures in environments with Person Account–enabled orgs. The process now supports these orgs seamlessly.

DataLoader Extraction – Custom Query Handling

Implemented a fix to ensure that custom queries in DataLoader extractions are parsed and executed correctly, preventing query-related failures.

Attachment Processing

Addressed an issue with attachment handling in form templates to ensure smooth and reliable processing during uploads and migrations.

DataLoader Status Auto-Update

Introduced an automatic refresh mechanism to keep job status updates in sync, ensuring that the latest execution status is always displayed in real time.

Welcome to ARM!!

You'll see this when you log in to your ARM account.

Let's get to know the main areas of the ARM application.

The Menu

You see a list of icons with the context in the top-right corner.

Let's examine each of these links in detail:

Create New

A Create New drop-down is available, which allows users to perform the primary and most used features in ARM, such as creating a CI job or a merge operation, etc., The users can also find the listed Create New operations within the ARM sub-module.

Hover your mouse over the Create New menu and click the drop-down icon. The drop-down field will allow the users to select a value from a predefined set of choices.

Quick Links

Here you can:

1. Find links to

2. Know about the ARM version on which you're logged in

3. ARM Feedback page

User Details

Here you can:

1. View your profile or update your basic information, personal email settings, etc.

2. Change your current password

3. Logout from your ARM account

Left Navigation Bar

On the left-hand side of the application, you see a list of icons with the context in it. These icons are nothing but the modules or features of ARM. The sub-modules which are part of it will be listed by hovering your mouse over each module.

Let's examine each of these links in detail:

The ARM Dashboards enable you to display multiple performance analytics, reporting, and other widgets on a single screen. ARM includes pre-defined widgets that can be customized and displayed on the Classic Dashboards page. These widgets are displayed as graphs, tables, and text. Each user can choose the widgets to populate their dashboard.

Version control helps you track changes you make in your code over time. Using a version control system, you can create snapshots of your code by creating branches or copies and isolating the codebase from the central repository. Every change made to the source is tracked, along with who made the change, why they made it, and references to problems fixed or enhancements introduced by the change. This makes it easier to make changes and enhances the overall quality of the code. A list of action items related to the Version Control system will get displayed, such as EZ-Commit, Merge, Manage Labels, etc.

ARM's Continuous Integration (CI) is designed to help customers rapidly release code confidently by automating the build, test, and deployment process to accomplish Continuous Delivery for Salesforce. CI encourages developers to share their code and unit tests by merging their changes into a shared version control repository upon completing every task. You can release code faster as it allows you to track application development and metadata modifications.

The Deployment process allows you to quickly and safely transfer new developments from your sandbox instance to a production instance. You can transfer validation rules, custom objects, new fields, apex codes, and many other components from your development environment to a live production environment using the deployment process.

ARM Data Loader allows you to configure your data loading operations in convenient and user-friendly GUI wizards and even allows importing and exporting Salesforce data without typing a line of code. Its powerful and easy-to-understand scheduling settings will enable you to specify almost any schedule quickly. You may schedule any data-loading operation for automatic execution.

Salesforce Developer Experience (DX) is a new set of tools that streamlines the entire development life cycle. It improves team development and collaboration, facilitates automated testing and continuous integration, and makes the release cycle more efficient and agile. It’s a new approach that supports team collaboration, focusing on predictability, quality, and standardized development life-cycle on Salesforce. Salesforce DX enables developers to build and release the latest features in a short period with minimal risk. ARM provides the best Salesforce Developer Experience with continuous integration and helps deliver software rapidly.

ARM allows its users to view all the deployment, merge, and data loader-related information carried out in the Salesforce Org in the form of reports. This information improves productivity, accountability, and insight into your business data in the form of reports.

Environment Provisioning is a unique interface ARM provides to quickly facilitate a Salesforce sandbox with metadata and data requirements that suit specific needs. These can be created as a template and stored in ARM. The same templates can be reused multiple times across various modules in ARM. For example, you can create an Environment Provisioning template to disable validation rules, enable history tracking, anonymous Apex, etc., of a particular object as a post-deployment setup.

Admin-related items are displayed here, such as registering a Salesforce Org, Version Control, adding team members, etc.

nCino-related operations will be displayed in this section, for example, creating a feature migration template, automating nCino deployments, etc.

The ARM signup and activation process has several steps — some on our end and others on yours.

1. Go to https://www.autorabit.com/ and log in or go directly to https://login.autorabit.com/.

2. Now, click on the Sign up for a Demo link. The AutoRABIT – New Registration screen appears.

1. Fill in the registration details, and then click Register.

1. Wait for an email from us. Next, we review your details to check if they comply with our policies and to set up the rest of your account. When we've completed this process and your account is activated, you will get a confirmation sent to your email address.

Logging In

The ARM login screen allows you to log in to your instance.

1. Go to your web browser to your instance's URL (for example, https://instance.autorabit.com).

2. The ARM login screen appears.

3. Enter your login credentials (username and password), and then click on Login.

Password Requirements

• MUST contain at least 10 characters (12+ recommended)

• MUST contain at least one uppercase letter (A-Z)

• MUST contain at least one lowercase letter (a-z)

• MUST contain at least one number (0-9)

Logging Out

When you are done working in ARM and wish to log out of the system, click your username in the upper right corner and click Logout. This will log you out completely from ARM, and you must log in again to access your account.

How to Prevent Credential Sharing

ARM only allows a username to be logged in under one session, and any additional user sessions started using the same username will be logged out of the previous session. This mechanism is for security, as ARM does not allow multiple sessions for the same username from different machines or browsers. To prevent situations like this, please do not share your login credentials (username and password) with users in your organization.

Another situation where users are automatically logged out is when the user does not perform any actions in ARM for a certain period. Configuration settings in the ARM UI control the security timeout period in ARM.

Users can have multiple tabs of ARM pages open within the same web browser (e.g., Chrome) without getting logged out of the system. For example, this is useful when working with multiple ARM pages or records without navigating away from previous pages.

FAQ

Why can't I log in to my ARM account?

If you're having trouble logging into your AutoRABIT account, here are some common causes and solutions.

1. The account is not created: Please check with your admin to create a new account.

2. The User ID and Password supplied to access the AutoRABIT account were incorrect or invalid: Try resetting the password by following the instructions .

3. Check if your account subscription has expired or your account is disabled: You'll see a message saying your account is disabled when you try to log in.

4. If you get the following error

Why did I not receive the email to reset my account password?

If you requested a new password but didn't receive your reset email:

1. Check the spam or junk email folder in your email linked to your AutoRABIT account.

2. Try to reset your password again.

How often do I have to change my password for ARM?

ARM requires you to change your password every 90 days.

How do I reset my password?

Follow the instructions to reset your ARM password.

CodeScan On-Premises

Release Notes 24.0.5

Release Date: 7 June 2024

New Rules

1. Rule Name: “Comment All Hardcoded Values” Category: New APEX rule in CodeScan Purpose: Ensure comments are included when using hardcoded values in Apex classes Detail: Ensures any hard-coded values or strings in the code are accompanied by descriptive comments or, alternatively, use constants. This practice enhances code readability, maintainability, and will make it easier for other developers to understand the purpose of these values.

2. Rule Name: “Use the null coalescing operator instead of the ternary operator” Category: New APEX rule in CodeScan Purpose: CodeScan recommendation to consider replacing ternary operators (? :) for explicit null checks with the Null Coalescing operator (??) where applicable to enhance code performance and clarity. Detail: In Salesforce's Spring '24 release, the null-coalescing operator has been introduced in Apex. This rule will identify where this operator could be used but isn’t being utilized. For further information, please refer to Salesforce Release Documentation - .

1. Rule Name: “Avoid JavaScript Scriptlets in Aura Components and Apex Pages” Category: New Aura / Lightning / Visualforce Rule in CodeScan Purpose/Detail: JavaScript scriptlets should not be directly embedded within the markup of Aura components or Apex pages. Instead, utilize Salesforce Static resources for including JavaScript code. Using direct <script> tags in components or pages can pose a security risk, increasing the likelihood of cross-site scripting (XSS) attacks. For further information, please refer to: - - Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

2. Rule Name: “Exposed Lightning Message Channel” Category: New LWC / Aura / Visualforce rule in CodeScan Purpose: It is recommended to verify instances where the 'isExposed' flag in Lightning Message Channels is set to true. Setting this flag can lead to unintended access to the Lightning Message Service (LMS) API, potentially resulting in unauthorized message publishing and subscribing across components within the Salesforce ecosystem. Detail: This term specifically refers to cases where you have not configured the 'isExposed' flag in Lightning Message Channel to false. Since this provides access to the Lightning Message Service (LMS) API, which lets you publish and subscribe to messages across the DOM and between Aura, Visualforce, and Lightning Web Components, it should be set to false. For further information, please refer to:

Fixes

1. Updated the rule “Avoid duplicate conditions in "if"/"else if" and "switch" statements to eliminate dead code." Detail: In the Initial implementation, the "if/else-if" statements and the nested "if/else-if" statements present within them were not allowed to have duplicate conditions. Now only the related "if/else-if" statements are checked for duplicate conditions, without considering the nested "if/else-if" statements present within them. Value: The same conditions can cause duplication and lead to dead code in statements such as "if"/"else if" and "switch." This issue often occurs due to a copy/paste error. In the best-case scenario, it results in dead code that serves no purpose, but in the worst-case scenario, it introduces bugs that may propagate as the code is maintained, potentially leading to unexpected behavior.

1. Updated the documentation and example on rule “API Version is Too Old” to: “This rule identifies visual force pages which are using older versions of the API. Change the API Version of this visual force page.” Reason for change: The description and example needed to be updated for the rule.

March 2023 - Version 22.3 (nCino)- Key Features and Enhancements

Date of release: 05 March 2023 Article last updated: 05 March 2023

Key Features

1. Specify baseline revision in continuous integration for version control

With this nCino release, we've added a new option called Version Control to facilitate deployment. The users will now be able to define a starting point from which commit needs to be picked for the range of revisions to be deployed via Continuous Integration (CI) jobs. The key features are:

• The user will be able to trigger builds for new revisions (delta deployments).

• The user will be able to select baseline revisions as a starting point for CI jobs.

• The user will be able to group all commit revisions together to run dataloader operations at once.

2. Reuse the package from the build and deploy in multiple Salesforce environments as post-deployment success activity

As a post-deployment success activity, we've provided the ability to reuse a package from a single build from a single CI job to deploy the same data in various Salesforce environments.

While using the current nCino implementation, the user must create multiple CI jobs, one for each destination org, in order to build data from the same repository and branch and deploy it to multiple salesforce environments. This results in repeated effort in building from the same source and defining the same job over and over again merely to choose a different destination, making it difficult to manage several CI jobs. With this new functionality, the user can build once and reuse it for deploying to multiple Salesforce orgs using a single build from a CI job.

The key features are:

• Reduced effort in redefining the CI jobs with the same source multiple times.

• Reduced time to deploy to multiple environments from the same source.

3. New 'Spreads Schedule Template' tile in Feature Creation screen

New objects, such as Schedules and Debt Schedules, were introduced with the latest nCino version release.

All of them are part of the Spreads Schedules group. To include all these objects under a single umbrella, we added a new tile called Spreads Schedules Template.

The Spreads Schedules Template template includes the following objects:

• LLC_BI__Underwriting_Bundle__c

• LLC_BI__Spread_Statement_Type__c

• LLC_BI__Spread_Statement_Record__c

• LLC_BI__Debt__c

Enhancements