Note: Nintex Apps data centers are located in West US and Australia (AUS). In-region processing of Nintex Apps data is only available in these regions.

Best Practices

Quick Ways to Make Your Nintex Apps Pages Blazing Fast

It's true: Nintex Apps pages already load quickly, but you can make them load even faster--just follow these tips to optimize your pages for speed.

Uncheck "Query on page load"

image0

Now, with the actions framework, and especially tab actions, you can trigger models to load precisely when the end user needs to see the information, and not a moment before. This will make the overall page load faster.

Use Nintex Apps themes and static resources for extended styling

The page level CSS resources are for one-off snippets, not your stylesheets.

Optimize Conditions: Sort on first level fields

image4

In conditions and filters, use first level fields instead of second or third level fields (e.g. use lookup relationships rather than fields from related objects). For example, even though Account__c and Account__r.Id both return the same value, (Account Id), use Account_c NOT Account_r.Id (the second level field).

Only add fields to your model that you need

image5

The less fields you add, the faster your page loads. This is one of the things that makes Nintex Apps so much faster than standard Salesforce and Visualforce - we are only calling the specific fields we want.

Always include model row limits

image6

What do we mean by "model row limits?" Selecting the maximum number of records to load (say, 10 instead of the default 100). And not selecting "Order by" when your model contains lots of records (for example, over 100,000).

Here's how to set row limits:

  1. Click on your model.
  2. Click on the Advanced properties tab.
  3. Set a smaller Max # of records limit. For lists limit the records to the number you want to view on one page of the list. Filters and search still query all of the records, but end users can always click "load more." Even on detail pages, including max # of records = 1 on the primary model will make the page load faster.
  4. Don't include a Fields to order records by when your Model contains lots of records (i.e. 100,000+). If you have sortable columns and table filters, your users will be able to easily order according to their own preferences.

Add Nintex Apps content as Nintex Apps Page Includes wherever possible

image7

Yup. Just do it!