Encompass Data Connect Replication - Frequently Asked Questions (FAQs)

The following table describes the differences between Encompass Data Connect Standard and Encompass Data Connect Lite.

To host your Encompass instance on an Encompass Data Connect instance, contact your account representative to initiate a provisioning request.

The provisioning process takes up to a week to complete and is as follows:

• Provisioning Request - Two to four days after your account representative initiates a provisioning request, ICE Mortgage Technology will send a welcome email to the address you provided during initiation. This welcome email contains your instance ID and a link to the Encompass Data Connect website.

• Log into Encompass Data Connect - Click the link in your welcome email to log in to Encompass Data Connect. From the log in screen, enter the instance ID (provided in the welcome email), your Encompass user ID, and your Encompass password.

  In order to access Encompass Data Connect, you must have permission to log in to Encompass with the admin user ID, or be assigned the Super Administrator or Administrator persona.

• Provisioning Request Form - Upon logging in, if you haven't yet been provisioned, you will be shown the Provisioning Request form to fill out and submit.

  In the Provisioning Request Form, enter the following:

  • Email – Use commas to separate multiple email addresses.

  • Database User Name - Your desired Encompass Data Connect user name.

  • Database Password - Your desired Encompass Data Connect password.

  • IP Address Range - The IP address range allowed to access the Encompass Data Connect instance. Use commas to separate multiple IP addresses. Use the subnet mask of "/32" for an individual IP address.

  • Public Key – For how to manage keys, view Encompass Data Connect Replication - Best Practices.

    This feature is available in Encompass Data Connect Standard only.

• Connection Details - After receiving your completed Provisioning Request Form, ICE Mortgage Technology will create an Encompass Data Connect instance. It can take up to seven days to complete creation. Once complete, ICE Mortgage Technology will email you the connection details for your Encompass Data Connect instance.

For more information, view Getting Started with Encompass Data Connect Replication.

To generate a PGP key using one of the verified methods for Mac/Linux or Windows, visit https://help.github.com/articles/generating-a-new-gpg-key/.

​A guide detailing the best practices to use Encompass Data Connect Schema can be downloaded from the following knowledge base article in the Resource Center: Encompass Data Connect - Schema Best Practices.

​A file explaining the schema relationships can be downloaded from the following knowledge base article in the Resource Center: Encompass Data Connect - Schema Relationships.

After receiving the Provisioning Request Form, ICE Mortgage Technology will create an Encompass Data Connect instance. It can take up to seven days for the creation to complete. Once complete, ICE Mortgage Technology will email you the following connection details for your Encompass Data Connect instance:

• Server

• User

• Password

• Port

Using the provided information, you can use SQL Workbench to connect to your Postgres or MS SQL Server database and view their records.

For details, view Connecting to Encompass Data Connect Replication.

Yes. You can use the following queries:

• To explore loan data (replace xxxxxxx with your loan number):

  select loan_id,loan_number ,modified_utc from elliedb.loan where loan_number='xxxxxxx';

• To see how many total loans you have in the database:

  select count(*) from elliedb.loan;

Once provisioned, Encompass Data Connect adds three years of historical data. If you would like to access to additional historical data, contact ICE Mortgage Technology Technical Support with the exact dates.

During the processing of historical data, the system may run slower than usual. It can still be accessed, replicated, or queried.

Custom fields are stored in the table "customfields". Each field is stored as values in a row. To query values in "customfield", the table must be filtered by that custom field and loan_number.

Example: "California_id" is a custom field of type "String".

To get value of this custom field, the query can be:

select string_value from customfield where custom_field_id = ‘California_id' where loan_number="SMPLLOAN123";

Ensure the following is true:

• Your IP address matches one of the IP addresses listed on the IP Management screen provided on the Administration Settings tab.

• The provided Port number is not blocked in your network.

If you are still encountering access issues, contact ICE Mortgage Technology Technical Support.

Typically, it takes a few seconds for data to update in Encompass Data Connect. At times, due to high volumes or optimization, delays can occur.

If after 30 minutes the data still hasn't updated, or if you experience frequent delays, contact ICE Mortgage Technology Technical Support.

There are multiple reasons for this but it does not necessarily mean that your data is not getting synced in near real-time:

• Loan folder: Since Loan Folder is the metadata and is not part of the Loan file, Data Connect gets the updates for Loan Folder using a parallel process that is not related to the Loan File. This is like moving a file to a different folder on your computer, which does not update the timestamp on the file but only moves the file. Similarly, when a loan is moved there is no update to the ModifiedUTC but DC_Modified is updated since it is an update in the database, Example: user makes changes to the loan on 11/11/2019, now ModifiedUTC and DC_Modified are same but when user moves it to a new folder on 11/13/2019 the ModifiedUTC remains old value of 11/11/2019 but DC_Modified.

• Miscellaneous: At times Encompass will treat certain tasks after a loan has been opened but closed without any changes or save. These could include printing out forms for example. In this case, Data Connect DC_Modified is updated but since the loan hasn’t changed, the Modifiedutc is not updated so you can see a gap of days or weeks or even longer.

• Latency: In some cases the system may be running slowly and have issues. This is usually identified when the latency is considerably long but it usually catches up and impacts all loans, not selectively. If your loans are taking more than an hour, then please check Status Center and if there is no existing issue then contact Technical Support to open a case.

Data Connect holds data for all Encompass customers in a common infrastructure. When a loan is created in any time zone, it will be converted into UTC.

• Data Connect does not store customer-specific time zones. The same customer may have branches across 50 states and Data Connect does not store a separate time zone for each one.
• Data Connect cannot assign a time zone based on the parent company location.

Data Connect uses PST and UTC only. Customers can convert to the target time zone as needed.

• CreatedUTC is the loan created time in Encompass.
• DCModifiedUTC is every time when this is updated in Data Connect.

You can contact ICE Mortgage Technology Technical Support through the Resource Center.

In order to access Technical Support features, you must be a named Support contact.

In order to keep your Data Connect instance running with seamless replication, minimum latency and no data loss, we highly suggest you follow the below best practices.

• Do not run join queries on Data Connect database
• Do not run aggregate queries on Data Connect database.
• On SQL Server, use the WITH NOLOCK construct to avoid deadlock issues on database tables.

Query Table like the following.

1. Postgres:

Create table public.lookup_encompassid as ( select encompassid from elliedb.loan (NOLOCK) where DcModifiedutc >= (FLOOR(EXTRACT(epoch FROM NOW())*1000) - 8640000000)

2. SQL Server:

SELECT encompassid INTO dbo.lookup_encompassid FROM elliedb.loan (NOLOCK) where DcModifiedutc >= <TimeStamp1> and DcModifiedutc <= <TimeStamp2>

select * from elliedb.Asset (NOLOCK) where encompassid in (select encompassid from dbo.lookup_encompassid (NOLOCK))

Query all the other tables like described above.