Updates and Enhancements

We have implemented a new mechanism to identify borrower pair changes and properly update the Account with the primary borrower. This enhancement adds a borrower pair index feature to our mapping, ensuring that whenever the primary borrower changes, the Account is accurately updated, eliminating the need for assumptions and improving data integrity.

This improvement resolves a common issue in implementation projects, providing a reliable way to update the primary borrower on the Account associated with the Opportunity.

A feature flag has been added to delay the inbound update to Salesforce when a loan is created within the last 30 seconds (configurable). This enhancement serves as a workaround to prevent race conditions, particularly in the USDA scenario.

When using the Encompass Connector, you can now configure a delay for the inbound sync to avoid creating duplicate records in Salesforce. This feature ensures that the Encompass Loan GUID is written back to the Salesforce record before any updates occur, preventing duplicates and maintaining data integrity.

Support has been added for upsert matching on a client-defined External ID, in addition to the existing Encompass Loan GUID, within the Encompass Connector.

When configuring the inbound sync from Encompass, you can now use a unique client-defined External ID to update existing records in Salesforce. This enhancement prevents the creation of duplicate records, ensuring that mapped data is updated on the existing record.

Key Features

• Configure an external ID field in Salesforce that corresponds to an Encompass field, allowing for identification and updates of existing records.

• If the Encompass record and Salesforce record share a match on the custom external ID field, the Connector will update the existing record instead of creating a duplicate, even if the Encompass Loan GUID does not exist on the Salesforce record.

An additional mapping field has been added to the Data_Model__c to support the synchronization of more fields between Encompass and Salesforce. This update addresses the need for syncing extensive data beyond the current limit of two long text fields.

As an Encompass Connector admin, you can now map more fields than previously allowed, enabling the sync of a larger dataset between Encompass and Salesforce.

Key Features:

• No longer limited to two long text fields for storing the entire JSON dataset.
• Supports up to approximately 250 fields, depending on the JSON length of mapped fields.
• Dynamically grows the available space for JSON as fields are added, accommodating extensive data synchronization needs.

Use Cases:

• Syncing custom fields extensively used by clients.
• Using Salesforce as the point of sale with comprehensive data synchronization.
• Syncing extensive borrower demographic data for marketing purposes.

You can now send loans from Salesforce to Encompass and assign the Loan Officer (LO) to someone other than the user triggering the send.

You can use a chosen field from the primary object to define the Encompass User ID that will be used as the assigned LO when sending a loan to Encompass. This field can be mapped on the primary object in the Configure Object Models page. This functionality enables non-Encompass users, such as loan officer assistants or front office teams, to initiate loan creation and assign the LO in Encompass.

Use Cases:

• A loan officer assistant sends a loan to Encompass on behalf of their Loan Officer, ensuring it is assigned to the correct LO.
• A front office team without Encompass licenses converts leads to opportunities, which are then automatically sent to Encompass with the appropriate LO assigned.

The interest rate field (Opportunity.Interest_Rate__c) in the Salesforce package has been updated to display three decimal points by default, aligning with the standard in Encompass. The previous version displayed the interest rate with only two decimal points, creating a discrepancy with the three decimal points used in Encompass.