New Features in 21.1 Major Release
A new IP Management screen is now provided on the Administration Settings tab in the Encompass Data Connect portal. Here you can enter a list of IP addresses to whitelist for your Encompass Data Connect instance. A maximum of 50 IP addresses can be added here. List the IP addresses of the computers running Encompass database instances that Encompass Data Connect is allowed to access when replicating the data.
This new option enables you to manage (add or delete) the IP addresses for your company, rather than having to submit an Ellie Mae Technical Support Case to request that they perform these IP management actions on your behalf.
To Access the IP Management Tool:
- Visit the Encompass Data Connect log in page, and then enter the following credentials:
- Instance ID - The ID of your Encompass instance
- User ID - Your Encompass user name
- Password – Your Encompass password
- On the Encompass Data Connect tool, click the Administration Settings tab.
You must be an Encompass administrator to have access to the Administration Settings tab. This includes the user assigned with the admin user ID, as well as users assigned with the Super Administrator or Administrator personas in Encompass.
- Click the IP Management tab.
To Add IP Addresses:
- On the IP Management screen, click the New IP Address button.
- Enter the IP address range (including /32) for the Encompass database instances that Encompass Data Connect will have access to.
- The IP Address must be a public IP address.
- When finished, click Save. The new IP address is added to the bottom of the list. All IP addresses within the range are now whitelisted and are accessible to Encompass Data Connect.
To Delete IP Addresses:
- On the IP Management screen, hover your mouse pointer over the hamburger menu next to the IP address you want to delete.
- Click the Delete icon (trash can). Once clicked, the IP address is removed from the list.
At least one IP address must be listed here. If you attempt to delete the last remaining IP address range, you will receive an error message and the IP address range will not be deleted.
DPL-5641, DPL-9969
Loan Schema Updates
To minimize any downtime and disruption experienced when upgrading the schema and data in your current production instance, the schema upgrade process for Encompass Data Connect is as follows:
- The Encompass Data Connect schema upgrade process for 21.1 will start at 10:00 PM on the day you receive and upgrade to Encompass 21.1. (Encompass 21.1 is currently scheduled to be available to all customers on March 6, 2021.) This schema upgrade process will take approximately four (4) hours on this day.
All of these Data Connect Schema upgrades are scheduled based on when you receive Encompass 21.1.
The Encompass Data Connect Schema has been updated to include the new fields added, regulatory updates, and changes to existing fields, in the Encompass 21.1 Major Release.
Loan Schema Field Mapping Files
The 21.1 schema is available to download from the following knowledge articles in the Ellie Mae Resource Center:
Microsoft (MS) SQL
-
Loan Schema Field Mapping with PII (MS SQL) (KA # 37065) - For PII (with encryption) MS SQL users, a file detailing the mapping of Encompass Data Connect 21.1 fields to the corresponding fields in the Encompass Loan Schema.
-
Loan Schema Field Mapping, No-PII (MS SQL) (KA # 37066) - For no-PII (no encryption) MS SQL users, a file detailing the mapping of Encompass Data Connect 21.1 fields to the corresponding fields in the Encompass Loan Schema.
Postgres
-
Loan Schema Field Mapping with PII (Postgres) (KA # 37072) - For PII (with encryption) and Postgres users, a file detailing the mapping of Encompass Data Connect 21.1 fields to the corresponding fields in the Encompass Loan Schema.
-
Loan Schema Field Mapping, No-PII (Postgres) (KA # 37073) - For no-PII (no encryption) and Postgres users, a file detailing the mapping of Encompass Data Connect 21.1 fields to the corresponding fields in the Encompass Loan Schema.
Field Updates Comparison Files
To compare the field updates in 20.2 with the field updates in 21.1, the DIFF file is available to download from the following knowledge articles in the Ellie Mae Resource Center:
Tip: SQL scripts assume that schema name is elliedb.
MS SQL
-
Field Updates Comparison 20.2 vs 21.1 no-PII (MS SQL) (KA # 37067) - For no-PII (no encryption) and MS SQL users, a file to help existing customers to view the difference between 20.2 and 21.1 field updates.
-
Field Updates Comparison 20.2 vs 21.1 with PII (MS SQL) (KA # 37068) - For PII (with encryption) and MS SQL users, a file to help existing customers to view the difference between 20.2 and 21.1 field updates.
Postgres
-
Field Updates Comparison 20.2 vs 21.1, no-PII (Postgres) (KA # 37074) - For no-PII (no encryption) and Postgres users, a file to help existing customers to view the difference between 20.2 and 21.1 field updates.
-
Field Updates Comparison 20.2 vs 21.1 with PII (Postgres) (KA # 37075) - For PII (with encryption) and Postgres users, a file to help existing customers to view the difference between 20.2 and 21.1 field updates.
Data Model Files
The SQL files used to help create tables for Encompass Data Connect 21.1 are available to download from the following knowledge articles in the Ellie Mae Resource Center:
MS SQL
-
21.1 Data Model (MS SQL) with PII (KA # 37069) - For PII (with encryption) and MS SQL users, a file containing MS SQL files to be used to help create tables for Encompass Data Connect 21.1.
- 21.1 Data Model (MS SQL) with no-PII (KA # 37071) - For PII (with no encryption) and MS SQL users, a file containing MS SQL files to be used to help create tables for Encompass Data Connect 21.1.
Postgres
-
21.1 Data Model (Postgres) with PII (KA # 37076) - For PII (with encryption) and Postgres users, a file containing SQL files to be used to help create tables for Encompass Data Connect 21.1
- 21.1 Data Model (Postgres) with no-PII (KA # 37077) - For PII (with no encryption) and Postgres users, a file containing SQL files to be used to help create tables for Encompass Data Connect 21.1.
Previous Section: Introduction |