Platform under the package
A Salesforce change reaches nCino screens the package release never touched.
Two release calendars, one decision examiners can follow
The Qventis Engine reads nCino's Lightning screens and the core banking desktop and terminal screens behind them in plain English, so one test follows a loan end to end. Release Intelligence watches both the Salesforce and nCino calendars and traces each change to your lending steps.
- Salesforce and nCino releases
- Through to core banking
- Evidence examiners can follow
How an nCino release moves through Qventis One
- Release rhythm
- Two calendars: Salesforce three times a year, plus nCino releases
- What we read
- Salesforce release notes and release updates, nCino release notes
- Process chains covered
- Loan origination, credit approval, account opening, R2R
- Sign-off
- Go or no-go per sandbox, then production
Both calendars, read on publish
Release Intelligence reads Salesforce release content and nCino release notes as each is published, so you see changes from either side in one Release Feed.
See Release Intelligence- Salesforce release updates that reach nCino screens
- nCino features and configuration changes per release
- API versions scheduled for retirement
- Changes to Flow and permission behavior
Traced to the lending step
The App Model maps every change to your lending processes, steps and tests, then scores it low, medium, high or critical by transparent rules.
See the App Model- Application, spreading and pricing steps in origination
- Authority limits and approver routing in credit approval
- Identity checks and funding in deposit account opening
- Booking and general ledger postings in R2R
Only the tests each release needs
The Qventis Engine builds the test delta and runs it from nCino screens into core banking in plain English, with zero AI tokens at run time.
See the Qventis Engine- One test delta, whichever calendar the change came from
- End-to-end chains into core banking screens
- Smoke the rest before production
A decision examiners can follow
Quality View rolls results up to readiness per sandbox and production, with evidence for each check and a named person who signs.
See Quality View- Release acceptance: accept, accept with actions or hold
- Steps, results and screenshots for every check
- Every number labeled observed, derived or estimated
- A named signer from lending operations
What nCino updates usually break
Custom fields and Flows
Customization exposure flags custom fields, Flows and permission sets on nCino objects that a release changes.
Documents and checklists
Required documents and checklist items fail to appear at the right stage of the loan.
Core and bureau integrations
Core banking, credit bureau and pricing connections return different data after either side moves.
Questions
Do we test for Salesforce or nCino releases?
Both. Run the same suite in the Salesforce preview sandbox and again before each nCino release.
Is the evidence enough for an exam?
It gives examiners a clear record of steps, results, screenshots and sign-off. Your compliance team decides what an exam needs.
See one loan traced from release to core banking
Bring one lending process. We trace the next release across nCino and core banking with you.