Encompass has the ability to differentiate between doublewide and singlewide property types, but when the Loan Officer launches to Optimal Blue, Encompass uses their ePass data push which does not differentiate between doublewide and singlewide. Because we are not able to determine which type of manufactured home is is, Optimal Blue defaults to Doublewide, as this is the most common.
Encompass customers cannot change the access of the Property Type field to Read/Write. On the Optimal blue search form, the Property Type field is read-only for customers using the Encompass Select integration. This is because Encompass does not update their property type fields with the data we push back to Encompass. As an example, if a LO changed the property type in Optimal Blue from Single Family to a Manufactured, Encompass does not get updated with this new value. To avoid Encompass and Optimal Blue being out of sync, we force the field to be read-only, so changes must be made in Encompass.
Other customers have added a custom dropdown field (ex: Singlewide Yes/No) to script rules.
Delete above and send to customer (edit as needed):
When a loan officer launches to Optimal Blue for pricing on a manufactured home, Encompass does not differentiate if the property type is singlewide or doublewide. Because we are not able to determine which type of manufactured home is is, Optimal Blue defaults to Doublewide, as this is the most common.
We are not able to unlock the Property Type field. The problem you would run into is that, if you change the property type in OB, it doesn’t get updated in Encompass. We do send the Property Type back, but Encompass doesn’t update from what was originally entered in before you use Product & Pricing.
What some customers have done is have us add a custom No/Yes dropdown so you can write rules around it to disqualify based on if it is Yes.