Performance Guide

This page offers solutions for improving the speed of the Avonni Components package in Salesforce.

Overview

Avonni Components for Flows are designed to enhance your Flow screens and provide a rich user experience within the Flow Builder environment. While engineered for efficiency, their performance operates within the context of the Salesforce Flow runtime.

IMPORTANT NOTE: For Optimal Performance on Lightning Pages

While Avonni Components for Flows excel at enhancing Flow screens, for building custom, high-performance UI directly on Salesforce App, Record, or Home Pages (outside Flows), use our separate package: Avonni Dynamic Components.

These are native LWCs optimized for fast loading, responsiveness, and reactivity in the Lightning App Builder. If page speed and direct customization—like related lists, dashboards, or record layouts—are priorities, Avonni Dynamic Components deliver the best solution

Boost Avonni Component Performance: Enable Lightning Web Security

Enable Lightning Web Security (LWS) in your org's Session Settings to prevent performance issues with Avonni Components in Salesforce Screen Flows. This boosts LWC security, improves Avonni speed and reliability, and is Salesforce-recommended for optimal performance and user experience

Performance Considerations within Flows

Several factors influence the speed and responsiveness of Avonni Components inside your Flows:

• Flow Complexity: The overall design of your Flow significantly impacts performance. Flows with numerous elements, complex branching logic, multiple loops, or frequent data operations (such as Get, Create, and Update Records) will naturally take longer to execute, which can affect screen load times.

• Salesforce Flow Runtime: Components run within Salesforce's Flow execution environment. The overall performance of the Salesforce org and the current load can influence performance.

• Avonni Query Data Source (QDS) Advantage: For Avonni data components (like Data Table, List) used within a Flow screen, leveraging the Avonni Query Data Source can often provide more efficient data retrieval compared to using multiple standard Flow "Get Records" elements followed by assignments to populate the component.

• Sandbox vs. Production: As with many Salesforce features, components may render, and Flows may execute slightly slower in Sandbox environments than Production orgs due to differences in resource allocation. Always perform final performance testing in Production or a Production-like Sandbox.

Tips for Optimizing Performance in Flows

Streamline Your Flow Design

• Minimize the number of elements on each screen.

• Optimize loops and decision logic.

• Perform data operations efficiently (e.g., update records in bulk after collection instead of inside a loop).

Leverage Avonni Query Data Source (Where Applicable)

For components such as Data Tables or Lists within your Flow screens, use the integrated Avonni Query Data Source to fetch and filter data efficiently, thereby reducing the need for multiple separate Flow data elements.

Test in Realistic Environments

While building in any Sandbox is fine, conduct performance testing in an environment that closely mirrors Production.

General Salesforce Settings Affecting Performance

These Salesforce settings can impact the performance of all Lightning Web Components, including Avonni's:

• Lightning Web Security (LWS): Salesforce generally recommends enabling LWS in your Salesforce org's Session Settings, which can improve the performance and security of LWCs.

• Caching: Initial load times for any LWC, including Avonni components (especially in the Flow Builder itself), might occasionally be longer due to Salesforce's internal caching mechanisms being populated. Subsequent loads are typically much faster.

Learn more about the Avonni Dynamic Components

Product Tour

We're Committed to Performance

Avonni continually evaluates and enhances components to ensure optimal performance. If you have specific performance questions or concerns regarding Avonni Components for Flows, please contact our support team.