Read/Write Custom Fields via Extension Mapping

Extension enables partner integration to read and write lender instance specific custom fields in a uniform and pre-defined manner. To enable this the lender administrators would need to specify mapping between their instance specific custom field ids and integration published extension field ids. The steps to define mapping are as below:


Encompass LO Connect: Field Mapping setting

Field Mapping tab can found within the Encompass LO Connect Service Management screen when logged in as administrator.


Extensions field for read/transaction request

For Read/Transaction Request, mapping for both - standard and custom fields - to extensions are supported.


Max number of fields supported for a partner

From Encompass to Provider

When a lender is reading data from EPC, if EPC identifies the Encompass Field ID (Standard or Custom) in the customer's instance, data from the field will be sent to the partner's Provider Field Name JSON path.


From Encompass to Partner/Provider

From Provider to Encompass

When a partner sends their response to Encompass Field ID (Standard or Custom), the data is written to the Provider Field Name.


Write back via Extensions is limited to custom fields only

Via the extension the integration can only write back to custom fields. Writing to standard fields via extension is not supported


From Provider to Encompass


Maximum Number of Extensions

Partners cannot send unlimited number of extensions to Encompass LO Connect. The number of extensions a partner integration can send is predefined in the extensionLimit in EPC Configuration, and displayed in the Encompass LO Connect Services Management setting.