nCino UI Performance Gotchas
Is your Financial Institution (FI) support team bogged down with tickets from your line complaining about the nCino UI performance, or experiencing Apex CPU timeouts when performing a credit action or recalculating credit risk exposure? Know that you are not alone! It’s often one of the first conversations that we have with our nCino clients. Luckily, there are some common gotchas that can be very easy to fix! As part of this blog post we will be focusing on performance as it relates to the nCino UI.
nCino UI Performance
The nCino UI is a super slick and powerful user interface that helps your institution know all the required fields and steps to progress a loan through its lifecycle, assist with managing a relationship, and maintain your product package. Given that Salesforce and the nCino UI is highly configurable, many FI’s think they should configure the UI to cover every scenario so that their line never has the opportunity to make a mistake. We often say at Lucro, “just because you can configure something doesn’t mean you should.” Never giving your line an opportunity to make a mistake might sound like a perfect solution, but the result is a UI that is very hard to maintain, slow to load, and prone to timeouts. These performance issues may cause your line to lose trust in the platform and want to revert to old habits. Below are our top 3 main culprits for UI performance issues and what you can do to remedy them.
1. Too Many Validation Rules
Limit the number of validation rules to those that are absolutely necessary. Having too many validation rules will frustrate users as they attempt to progress through a loan especially if required fields reside on many different routes. The 80/20 rule is best here.
2. Limiting the amount of Conditional Rendering (Route and Field)
Attempting to make the nCino UI display and hide fields for every loan type/stage is very helpful for your line, but doing so comes at a large performance cost. The reason being is that when the nCino UI is loaded all permutations are queried and then whittled down to exactly what needs to be displayed to the user. If most of the data being collected is the same, leveraging an all-encompassing validation rule or updated job aides will be more beneficial from a system performance standpoint.
3. Upgrade, Upgrade, Upgrade
nCino has two major releases a year and with each of those they come out with awesome new functionality as well as major performance enhancements. The nCino UI has been a hot topic for years and they have invested heavily into ensuring that the load times and functionality is top notch. The thing that many FI’s forget is that you have to actually upgrade your UI or routes to get the full benefits of what has been released. To start you will want to ensure that every route being displayed within your UI has been upgraded from the older KO routes to the latest NC routes. Second, if your institution leverages Salesforce lightning you will want to leverage nCino’s UI Lightening Web Component (LWC). The nCino UI LWC leverages the latest lightning framework along with caching to provide the best performance for your institution.
There are many other potential factors for sluggish nCino UI performance and we at Lucro offer an nCino org health check to examine your current nCino org to help your Financial Institution identify these problem areas. Reach out to find out how we can partner together and profit together.
