- Getting Started
- Demo apps
- How To
- Notifications
- Using VB Expressions
- Designing your App
- Designing your App with Autopilot
- Events and Rules
- Rule: If-Then-Else
- Rule: Open a Page
- Rule: Open URL
- Rule: Close Pop-Over/Bottom Sheet
- Rule: Show Message
- Rule: Show/Hide Spinner
- Rule: Set Value
- Rule: Start Process
- Rule: Reset Values
- Rule: Upload File to Storage Bucket
- Rule: Download File From Storage Bucket
- Rule: Create Entity Record
- Rule: Update Entity Record
- Rule: Delete Entity Record
- Rule: Add to Queue
- Rule: Trigger workflow
- Rule: Submit Action
- Leveraging RPA in your App
- Leveraging Entities in Your App
- Leveraging Queues in Your App
- Leveraging Media in your app
- Leveraging Actions in your app
- Leveraging Connections in your apps
- Web apps in Studio Web
- Application Lifecycle Management (ALM)
- UiPath® First-Party Apps
- Basic Troubleshooting Guide
Performance best practices
The following maximum values are recommended for an optimal app performance. Exceeding these values may lead to performance degradation, but Apps does not impose any limit.
-
Use maximum 200 controls on a page.
-
Include maximum five complex controls on a page, such as tables or grids.
-
Use page containers in maximum 10 tabs per Tab control.
-
Nest maximum five containers.
-
Nest maximum ten rules in an event.
-
Use Table controls to display maximum 200 read-only records.
-
Use the same page container and variables to load individual pages.
Say you have a multi-step form, where steps are sequential and the content of every step resides in an individual page. On the starting page, instead of having containers for each step, reuse the same page container and load a different page into it by using a variable or the If-Then-Else rule.
-
Use less Tab and Page containers on a page, to improve the initial loading of the page.
-
Use Edit grid control to display and edit tabular records or large datasets. This control offers sorting, pagination, and server-side capabilities, enabling it to display more than 1,000 entity records.
-
For read-only Edit grid controls, disable the editing capabilities in the app designer to speed up rendering and to remove editing icons for a cleaner layout.
-
Enhance the rendering speed of the Edit grid control by adjusting the height to a maximum of 1200px. This modification concurrently optimizes the number of rows visible.
-
If you are using the same formatting style across multiple lines in a Rich Text Editor control, apply the style at once rather than for each individual line. Doing so saves the time spent to render the style for each line.
-
For Image controls, we recommend keeping image sizes above 50% of the original size. Use a lower resolution for small logos, and avoid using high-definition images to ensure optimal performance.
-
To ensure successful video playbacks in IFrame controls, use the embed links provided by the hosting site.
-
To improve readibility and app user experience, we recommend using seven options or less for Radio Button controls, and stacking them vertically when the width is restricted. To use more than seven options, use Dropdown controls.
-
Do not set the width of Table controls to
auto, to prevent unexpected shifts in column widths due to varying content lengths, or to prevent tables from becoming too narrow on smaller screens. This also enable virtual scrolling in the table. -
Use pixels to set the width and height of Table controls, to render tables more quickly, or to prevent table cells from overflowing or wrapping when the content is too large. This also enable virtual scrolling in the table.
-
To reuse the output of a
Fetch()or aGetChoiceSet()function, assign the output to a variable of typeListSourceusing the Set Value rule.
-
Each page should contain a single use case.
For example, in an organization management scenario, you can have an overview page and then a separate page for each department, such as IT, HR, Finance. For a typical add/edit scenario, consider using an Edit grid control instead of additional edit / add forms.
Split complex pages into modular pages, then use page containers to display them.
-
In some cases, you may need to display contextual content on a page, where different sections on the page are mutually exclusive and become visible based on specific conditions, such as the value of an app variable. We recommend to implement this scenario as follows:
-
Create separate pages for each section that needs to be displayed conditionally.
-
On the main page where these sections should be displayed, add a page container.
-
Use the Open page rule to display the relevant section in the page container by selecting the page container as the target.
-
Add an If-Then-Else rule to determine which page should be rendered, based on the variable value. This ensures that only the appropriate page is displayed, resulting in a more efficient and streamlined user experience.
-
