Back to All

Nov '20 Release 🎉

over 3 years ago by Rishabh Prakash

The EPC 2.0 November 2020 release is now live in production! With this release, we've made a number of new features and improvements available:


Support for Response Resource Classification

We now support the ability for integrators to assign a specific resource type classification to the file attachments delivered as part of a transaction response. Classifying response file attachments into a deterministic set of types enables lenders to define rules for importing these attachments into appropriate locations in the subject loans eFolder. For example, a home appraisal integration may deliver both an appraisal report for the subject property, along with an invoice for the appraisal. If the integration appropriately classifies these documents, lenders will be able to define which specific eFolder documents these files should get attached to upon import into Encompass. If lenders do not choose to specify any import rules, the file attachments will get imported into a default document in the loans eFolder corresponding to the service category the integration is listed under.

Check out our updated developer guides to learn more about what an integration needs to do to:

  1. Register the specific set of file types it intends to deliver as attachments to a transaction response
  2. Classify a response resource (file attachment) as a registered type when delivering a transaction response

Support for Accessing Production Products in Lender Test Environments

We now support the ability for lenders to access both sandbox as well as production products from their test Encompass environments. Previously - lenders could only access sandbox products from their test environments. Giving lenders access to production products in their test environments enables them to test and validate the exact same product configuration that they will have access to in their production Encompass environment.

Keep in mind, transactions originated from an Encompass test environment for a production product will still be considered billable, production transactions. Alternatively, integrators can register a product instance that has the exact same routing configuration (interface/webhook URLs) as their production product, but keep this instance in sandbox mode - enabling lenders to test a production mirror configuration without bearing the cost of production transactions.


If you have any questions or comments, you can send them to us at [email protected]. You can also post your questions and look for answers on our discussion board - which is actively tracked by a community of experts available to help as needed.