Overview
Due to ICE’s (Intercontinental Exchange) data center migration, the workaround method that allowed a specific nCino Mortgage region or user to route traffic to your Encompass UAT environment is no longer supported. This page explains what changed, who is affected, and what your options are.
Contents
- What Changed?
- Am I Affected?
- Common Questions
1. What Changed
ICE migrated its data centers. As part of that migration, the ability to connect a nCino Mortgage user or region to route traffic to a client’s Encompass UAT environment has been removed from the new infrastructure.
Previously, clients could configure a user or region within their nCino Mortgage production environment to point at their Encompass UAT instance. That routing mechanism no longer exists post-migration.
2. Am I Affected?
You are impacted if all three of the following were true before the migration:
| Condition | Detail |
| Uses nCino Mortgage POS + Encompass UAT | Connected to an Encompass UAT environment |
| Has a separate Encompass UAT environment | A non-production Encompass instance exists separately |
| Was using region/user routing as a workaround | Configured a nCino user or region to Encompass UAT instead of using a dedicated nCino UAT environment |
Note: If you already have a dedicated nCino Mortgage UAT environment, you are not impacted. Your existing UAT-to-UAT connection remains intact.
3. Common Questions
“My UAT API key stopped working — can you fix it?”
This is a known impact of the ICE data center migration. The API key configuration in place relied on a routing method that no longer exists at the infrastructure level. This is not a fixable configuration error, and regenerating or correcting the UAT API key will not resolve it.
“Is this a bug? Will it be fixed?”
No. This is a permanent infrastructure change driven by ICE’s data center architecture. There is no roadmap item to restore the legacy UAT routing behavior.
“We still need to test before pushing to production — what are our options?”
There are two supported paths:
Option 1 — Test region or branch (recommended starting point)
You can create a dedicated test region or branch within your existing nCino Mortgage production environment. This is the most common approach used by clients today.
- No additional cost
- Configurable within your current nCino environment
- Supports test loan applications, workflow simulation, and configuration validation
- Access can be restricted to internal testers
Limitation: This approach still uses the production Encompass connection. If your primary need is validating Encompass-side changes in isolation, this may not be sufficient.
Option 2 — Dedicated nCino Mortgage UAT environment
If you require a fully isolated environment connected directly to your Encompass UAT, you can request a scoping call to discuss provisioning a dedicated nCino Mortgage UAT instance.
- Requires a formal scoping call through Professional Services
- Involves additional licensing and services cost
- Best suited for clients with complex testing requirements, heavy release validation, or regulatory obligations
To explore Option 2, reach out to your Customer Success Manager or Account Manager to initiate a scoping conversation.
“How does a test region or branch work?”
A test region or branch in nCino Mortgage lets you segment test activity within your production environment using an area not used for live lending. You can:
- Create test loan applications and simulate workflows
- Validate form changes, configuration updates, and process changes
- Restrict access to a defined group of internal testers
Key limitation: this still uses the production Encompass connection. If your primary testing goal is validating Encompass-side changes independently, Option 2 is the better fit.
Questions? Contact your Customer Success Manager or reach out to nCino Support.
Published: mm/dd/yyyy Last Update: mm/dd/yyyy