(Updated on 1/18/2019)

When searching for loans or using filters to display specific loans on the Pipeline, an issue occurred where loans indicated as subordinate loans were not displaying correctly on the Pipeline. On the Pipeline, the Lien Position column should display a blank value, First, or Subordinate to indicate the loan’s lien position. The value displayed here is based on the Lien Position indicator (field ID 420) that is selected on the 1003 Page 1 input form. However, when loans were indicated as Subordinate on the 1003 Page 1, the Lien Position column on the Pipeline displayed a blank value instead of Subordinate. This issue has been resolved so that Subordinate is displayed in this Pipeline column for applicable loans. In addition, if you select Subordinate from the Lien Position column’s dropdown list to filter your Pipeline to show only subordinate loans, the subordinate loans are listed in the Pipeline accordingly.

As part of the fix for this issue, the field description and field size for field 420 (Lien Position) were updated in the Reporting Database. In order for this fix to be applied and resolve this issue with your Pipeline, you must manually remove field 420 from the Reporting Database, and then add field 420 back to the Reporting Database. Once you have re-added the field and updated the Reporting Database, the issue will be resolved in your Pipeline. Refer to the Admin Tools: Reporting Database help topic for instructions to remove and add the field.

The following updates have been made to the calculations for the Estimated Construction Interest (field ID 4088):

• The calculation has been updated to support construction-only and construction-to-permanent ARM loans with the A (Half loan) option selected for Est. Interest On (field ID SYS.X6) when the Require Interest Reserves (Compound Interest) and Creditor Prohibits Borrower from Making Interest Payments checkboxes (field IDs 4086 and 4087) are selected.

• The calculation has been updated to support construction-only and construction-to-permanent ARM loans with the B (Full loan) option selected for Est. Interest On (field ID SYS.X6) when the Number of Days (field ID 1962) is 365/365 or 365/360.

• The calculation has been updated to resolve an issue that occurred with construction-only ARM loans with either the A (Half loan) or B (Full loan) option selected for Est. Interest On (field ID SYS.X6) when the fully indexed rate is through the life of the construction loan. When this occurred, the calculation was removing one month of interest from the Estimated Construction Interest (field 4088), which also impacted the APR calculation. This issue has been resolved and the correct number of month of interest are now being included in the Estimated Construction Interest.

To preserve the data integrity of existing loans, a Lock icon has been added to the Estimated Construction Interest field (field ID 4088). When upgrading to Encompass 19.1, the field is locked for previously disclosed Construction or Construction-to-Permanent loans with the A (Half loan) or B (Full Loan) option selected for Est. Interest On (field ID SYS.X6). Click the Lock icon to apply the new calculations.

Updates have been made to the Amortization Schedule for construction-only ARM loans when the interest Number of Days (field ID 1962) is 365/365 or 365/360. Previously the interest payments in the schedule were displaying amounts that were off by one month. For example, the February interest amount would display in the row for April instead of March.

This update also affects the Projected Payments tables on the Loan Estimate Page 1 and Closing Disclosure Page 1.

An issue occurred where certain loan officers were not being automatically assigned to loan files imported into Encompass from Encompass WebCenter sites even though they were assigned as the loan application recipient (LAR) in Encompass WebCenter when applicants submitted loan applications. If the loan officer’s name in their user profile in Encompass included a middle name or a suffix (for example, Jr., Sr., etc.) then they were not being assigned to loan files received the Encompass WebCenter even if they were the LAR. This issue has been resolved so that these loan officers are now assigned to these loan files as expected when they are the assigned LAR.

(Added on 12/20/2018)

An issue occurred where if a user changed the borrower name in the Name field (field ID 1868) on the Borrower Information – Vesting input form so that it was different from the data in the borrower’s or co-borrower’s First Name (field ID 4000, 4004) or Last Name (field ID 4002, 4006) on the Borrower Summary – Origination input form, then the fields in the Disclosure Details’ eDisclosure Tracking tab would display as blank for all eDisclosures sent on the loan file.

It is important to note that this issue only occurred in loan files in Encompass that were originated from an Encompass Consumer Connect website. This issue occurred because Encompass was not considering the borrower name entered in the loan file when the initial loan disclosures were sent. Therefore, when the borrower name was changed after the initial disclosure, Encompass could not update the borrower name on the eDisclosure Tracking tab accordingly.

This issue has been resolved so that changing the borrower’s name on the Borrower Information – Vesting input form does not result in the eDisclosure Tracking details being blanked out. Encompass now considers the borrower and co-borrower names in fields 4000 – 4007 to ensure the borrower name and the eDisclosure Tracking details are populated correctly if the borrower or co-borrower names are changed after the initial disclosure.

(Added on 12/20/2018)

An issue was introduced in Encompass 18.3.0.4 where once a disclosure package was sent electronically and a disclosure tracking record was generated in the Disclosure Tracking Tool, the Presumed Received Date in the Fulfillment section of the record’s eDisclosure Tracking tab was not populating when the user printed documents and manually fulfilled the disclosure package (by clicking the Print Documents and Manually Fulfill button on the eDisclosure Tracking tab). The Presumed Received Date field itself was missing from the Fulfillment section. This issue has been resolved so that the date is populated to this Presumed Received Date field when the user clicks the Print Documents and Manually Fulfill button.

The Interest Only dropdown list (field ID 2982) on the Qualification tab on the ATR/QM Management input form is now being populated correctly for loan files that have been imported into Encompass, for example from the Encompass WebCenter, Encompass TPO Connect, or a Fannie Mae 3.2 file. Previously the dropdown list was blank when an imported loan did not have Interest Only information entered. Now No is populated in the dropdown list if the interest-only information in the imported loan file is either blank or No.

(Added on 12/20/2018)

An issue related to Dynamic Data Management (DDM) field rules and fee rules and the following fields on the 2015 Itemization input form occurred in Encompass 18.4 (and later):

• Line 1202 Recording Fees (field ID 1636)
• Line 1204 City/County/Stamps (field ID 1637)
• Line 1205 State Tax/Stamps (field ID 1638)

In Encompass systems where no DDM fee rules or DDM field rules were currently activated, if the user clicked the Edit icon for one of these fields and manually entered and saved a new value in the field, the value in the field reverted back to the previous value that was in the field before it was edited when a DDM fee rule or field rule that was not related to these fields was then activated and the same loan file was then re-opened and saved. Once a DDM rule was activated and the loan was re-opened and saved, the fee (or fees) that were updated manually reverted back to its previous value.

This issue has been resolved and these fee values are retained after they are manually updated and saved in this scenario.

An issue has been resolved that caused the This is the first use of the VA loan program dropdown list (field ID VASUMM.X49) on the Basic Information tab on the VA Management input form to clear under the following conditions:

• The No option was selected for the This is the first use of the VA loan program dropdown list.

• An Encompass user then opened the MIP/PMI/Guarantee Fee Calculation pop-up window and then clicked the OK button. The pop-up window is accessed by clicking the Edit icon next to fields such as the VA Funding Fee Amount (field ID 1826) or the borrower-paid Mtg Ins. Premium (field ID 337) on the 2015 Itemization input form.

This issue has been resolved and the No option is no longer cleared after clicking the OK button on the MIP/PMI/Guarantee Fee Calculation pop-up window.

When the Loan Type (field ID 1172) is changed from USDA-RHS to another option, the text entry field (field ID 1063) for the Other option is now updating as expected. When the USDA-RHS option is selected for the Loan Type (field ID 1172), the text entry field is populated by default with RHS.

Previously, the text entry field was not being cleared if the loan type was then changed from USDA-RHS to another option. This issue has been resolved and the text entry field is now cleared when the Loan Type is changed from USDA-RHS to another option.

(Added on 12/7/2018)

An issue was resolved that caused the Estimated Cash to Close (field LE2.X25) on the Loan Estimate Page 2 to not recalculate after updating the POC amount on line K6 (field ID CD3.X228) on the Adjustments and other Details pop-up window. This window is accessed by clicking the Edit icon for Adjustments and Other Credits on the line above the Estimated Cash to Close field.

This issue has been resolved and the Estimated Cash to Close amount is updating as expected when the POC amount is updated on line K06.

On the Quick Entry - Custom Escrow #3 pop-up window (accessible by clicking the Edit icon on the third free-entry line) on the Aggregate Escrow Account input form, the field descriptions that display when an Encompass user places the mouse pointer over the Agent field (field ID VEND.X364) and Policy Number field (field ID VEND.X473) now display properly. Previously, the descriptions for the fields were reversed. This issue has been resolved and the field descriptions now display properly.

This update takes effect on the official Encompass 19.1 release currently scheduled for February 2019.

For loans with multiple borrower pairs, an issue was resolved that caused the first name of one of the borrowers to display incorrectly after navigating between borrower pairs on the Manage Borrowers pop-up window under specific conditions. This scenario would occur when an Encompass user switched between borrower pairs in the Manage Borrowers window and then closed the window by clicking the red X on the upper-right corner of the window.

The Manage Borrowers pop-up window is accessible by clicking the Edit icon next to the Borrowers dropdown list in the loan header or by clicking the Manage Borrowers option on the Loan menu in Encompass.

In this scenario, when an Encompass user opened the Manage Borrowers pop-up window, selected a different borrower pair in the window, and then clicked the red X to close the window, the first name of the Borrower in the last borrower pair selected would replace the first name of the Borrower in the borrower pair originally selected when the window was opened.

For example, in the scenario shown below, the window was opened with John Smith and Mary Smith selected as the first borrower pair.

The Encompass user then selected the Tammy Jones and Jake Jones borrower pair, and then closed the Manage Borrower window using the red X. The next time the window was opened, Smith, John was replaced with Smith, Tammy.

This issue has been resolved, and the borrower pair names now display as expected.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Close the Manage Borrowers window by clicking the Close button. Do not click the red X in the upper-right corner of the window.

(Added on 12/20/2018)

An issue occurred in the Piggyback Loans tool where the Encompass system would freeze when users clicked the Link to Loan button in the tool when the loan file they were working in was located in a loan folder that contained 35,000 or more loan files. This issue has been resolved and this issue no longer occurs in loan files located within a loan folder with 35,000+ loans in it.

The Estimated Cash to Close (field ID LE2.X25) in the Calculating Cash to Close section on the Loan Estimate Page 2 now updates automatically when you close the Adjustments and Other Details pop-up window after entering adjustments or other credits in sections K or L in the window.

The Adjustments and Other Details window is accessed by clicking the Edit icon for the Adjustments and Other Credits (field ID LE2.X4) in the Calculating Cash to Close section on the Loan Estimate Page 2.

Previously, the calculation for Estimated Cash to Close updated only after leaving the Loan Estimate Page 2 input form, editing the Deposit field (field ID L128), or using the Print feature to preview the Loan Estimate output form.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• From the Loan Estimate Page 2:

• Open another input form in Encompass.

• Or edit the Deposit field (field ID L128).

• Or click the Print icon on the upper-right of the Loan Estimate Page 2, click Loan Estimate in the Selected Forms panel on the right, and then click the Preview button.

An issue was resolved that caused the mortgage insurance amount to be incorrectly doubled in the calculation for the Total of Payments (field ID CD5.X1) on the Closing Disclosure Page 5 for loans with mortgage insurance. Additionally, the prepaid amount of MI (field ID 3971) was not included in the total.

To resolve this issue, the borrower-paid portion of the Mtg Ins. Premium (field ID NEWHUD2.X2191) has been removed from the calculation and replaced with the Prepaid Amount (field ID 3971) from the MIP/PMI Guarantee Fee Calculation pop-up window (accessible by clicking the Edit icon on line 902 on the 2015 Itemization).

For loans created prior to upgrading to Encompass 19.1, the Total of Payments (field ID CD5.X1) is locked for loans with mortgage insurance to preserve the disclosed value and is not recalculated by default when there is an amount enter for the borrower-paid portion (field ID 337) on line 902. Click the Lock icon to recalculate the amount, which might be required for loans that are still being processed.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Click the Lock icon for the Total of Payments (field ID CD5.X1) and the In 5 years Total you will have paid amount (field ID LE3.X17) and adjust the amount.

The Owner Occupied option is now selected by default on the Occupancy dropdown list (field ID 3335) on the Quick Entry - NMLS Report Information pop-up window when the Secondary option is selected for the Property Will Be (field ID 1811). The Quick Entry - NMLS Report Information pop-up window is accessed by clicking the NMLS button in the Property Information section of the HMDA Information input form.

(Added on 12/20/2018)

When viewing the Good Faith Fee Variance Violated alert details in a loan file, the Comments field in the Fee Details section was not displaying correctly. The field’s right side was cut off, making it difficult to read comments in the field in their entirety. This issue has been resolved and the Comments field is now displayed correctly and no longer cut off.

After using the Reports tool in Encompass to generate a report that displays data in a bar chart, you can hover your mouse pointer over each bar in the graph and the value of the bar is displayed below the bar. However, an issue occurred in charts with short bars. When hovering the mouse pointer over a shorter bar, the hover text that displays the bar’s value was not visible. This issue has been resolved so that the hover text is now visible for all bars in the graph.

Updates have been made to resolve an issue that resulted in Non-Borrowing Owner file contacts not being deleted properly under the following circumstances.

• When a Non-Borrowing Owner file contact was created and then deleted without clicking the Save icon for the loan file. If the loan file was then closed and saved by clicking the red X on the upper-right corner of the loan file, the contact was not being removed from the File Contacts tool or the Borrower Information – Vesting input form.

• Additionally, under the conditions described above, if an Encompass user attempted to delete the Non-Borrowing Owner file contact before removing the contact from the Borrower Information – Vesting input form, the Non-Borrower Owner contact would remain on the Borrower Information – Vesting input form permanently and could not be removed.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Save the loan file using the Save icon at any time after the Non-Borrowing Owner contact is created, but prior to exiting the loan.

• When removing a Non-Borrowing Owner contact, delete the contact from the Borrower Information - Vesting input form BEFORE removing it from the File Contacts tool.

This issue has been resolved and the non-borrowing Owner files contact is now being deleted successfully under the conditions described above.

An issue was resolved that caused the Buyer’s Agent information to not copy from the File Contacts tool to the Real Estate Broker (B) section of the Closing Disclosure Page 5 input form under the following conditions:

1. The Add to CD Contact Info checkbox (VEND.X93) was selected for the Buyer’s Agent entry in the File Contacts tool.

   

2. The information for the Buyer’s Agent in the File Contacts tool was then updated by clicking the Address Book icon to add contact information from an existing business contact.

This issue has been resolved and the Buyer’s Agent information is now populating properly to the Closing Disclosure Page 5 after the Buyer’s Agent entry is updated in the File Contacts tool via the Address Book icon.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Clear the Add to CD Contact Info checkbox for the Buyer’s Agent after the agent's information is selected via the Address Book icon and then select the checkbox again.

When sorting business contacts by Company Name in the Address Book feature, the sorting feature now functions correctly for companies with more than 100 business contacts. Previously, the sorting order functioned correctly when displaying the first 100 users, but the sorting order would stop functioning properly as users began viewing different groups of contacts on the tool (for example, by moving between the 1-100, 101-200, or 201-300 groups). The entries would no longer be arranged alphabetically, as shown in the image below.

This issue has been resolved and the sorting feature now functions as expected.

An issue occurred where users who navigated to the Contacts tab in Encompass and attempted to import business contacts (i.e., a comma-separated values (CSV) file) received the following error:

An error has occurred while importing contacts: Error executing query: The INSERT statement conflicted with the FOREIGN KEY constraint "FK_BizPartner_BizCategory". The conflict occurred in database "[name of database]", table "[user’s client ID].BizCategory", column 'CategoryID'.

The statement has been terminated.

This issue has been resolved. Users can now successfully import a CSV file to add business contacts to the Contacts tab in Encompass.

When a borrower’s legal name includes a hyphen, the eSigning process now inserts the hyphen in the electronic signatures that are applied to loan documents. Previously the hyphen was not displaying in the electronic signature. Example: Ramos-Estevez would display as RamosEstevez on the applied eSignature.

(Added on 12/20/2018)

An issue was resolved that caused some logo images to not display correctly in file attachments for certain credit service documents, for example The Work Number verification from Equifax, when the files were imported into the eFolder while the Document Conversion setting was enabled. This issue has been resolved and logo images now display as expected.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

1. In the eFolder, double-click the document, select the file attachment in the Files section of the Document Details window, and then click the View in Original Format button.

2. Click the Print icon, select Encompass eFolder from the Printer dropdown list, and then click the Advanced button.

3. Select the Print as Image checkbox, click OK, and then click Print to print the file to the eFolder.

(Added on 12/20/2018)

An issue was resolved that resulted in Encompass users receiving intermittent Cross-thread operation not valid error messages when clicking the Send or Cancel button on the Send eDisclosure window in the eFolder. This issue has been resolved and the error message no longer displays.

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Close and reopen Encompass and then retry the eDisclosure process.

(Added on 12/20/2018)

When sending an eConsent request for an Encompass Consumer Connect loan to a co-borrower with no email address entered in the loan file, a pop-up message now prompts the Encompass user to enter the email address for the co-borrower. Previously the eConsent request was sent to the borrower’s email address if the co-borrower did not have an email address in the loan file.

(Added on 12/20/2018)

When managing files in the Documents setting (Encompass Settings > eFolder Setup > Documents), administrators can select the Queue Documents for Upload/Conversion checkbox to enable users to continue working in Encompass while files are uploaded and converted (when document conversion is enabled) into the eFolder in the background. However, an issue occurred where the background processing was not being performed even if this option was enabled and the Background Processing icon was displayed near the date and time displayed in the lower-right section of the system tray. This issue has been resolved so that the background processing is now operating successfully. The Background Processing icon will continue to display near the date and time as expected. Click this icon to view the status of the file processing.

In addition, to help reduce the time it takes for the user log in process to complete in Encompass, the system will no longer check to determine if the background processing is running and if the icon should be displayed in the system tray. Previously, the system checked for this during the log in process. This check in is now performed outside of the log in process.

(Added on 12/20/2018)

An issue was reported with the display settings of the FHA County Limits setting (Encompass Settings > Tables and Fees > FHA County Limits). By default, this setting defaulted to the 2017 version of the HUD web site’s FHA county limits table (http://hud.gov/pub/chums/cy2017-forward-limits.txt). After users selected the Jan 1 - Dec 31 2018 HUD Web Site option (http://hud.gov/pub/chums/cy2018-forward-limits.txt), and then clicked the Synchronize button, this option remained selected. But after closing the Encompass Settings window, or navigating to another setting, and then navigating back to the FHA County Limits setting, the 2017 option was once again selected. This caused confusion and lead Encompass administrators to think that the 2018 option was not synchronized nor saved, even though it was. The system was simply defaulting back to the 2017 option regardless.

To resolve this issue and alleviate confusion, the system now defaults to the last synchronized HUD Web Site on this setting after Encompass Settings is closed and the administrator returns to this FHA County Limits setting at a later time.

An issue occurred in Encompass where the User Details screen was not being displayed in its entirety for users utilizing monitors with certain screen resolutions, such as 1366 x 768 and 1024 x 768. Specifically, when users navigated to the Encompass Settings > Company/User Setup > Organization/Users, and then opened the User Details screen to create a new user or edit an existing user, the bottom section of the screen, including the Save and Cancel buttons, were not visible on the screen due to the screen resolution. This issue has been resolved so that the entire User Details screen now displays on the screen when users are utilizing monitors with any screen resolution up to 1024 x 768 or greater. As documented in the Encompass System Requirements and Compatibility Matrix, Encompass supports all monitor resolutions up to 1024 x 768 or greater.

(Added on 12/20/2018)

An issue was introduced in Encompass 17.3, where the Address Book icon was no longer available for the Address field in the Organization Information section of the Organization Details screen. Without this icon, administrator could not access their Business Contacts list and select the desired organization. Starting in Encompass 19.1, the Address Book icon is once again available for use with the Address field on the Organization Details screen.

(Added on 12/20/2018)

Using the Loan Custom Field Editor, administrators can set up custom fields to be audit fields, by setting the field’s format to Audit and indicating the field [ID] to be audited. When a field is indicated as an audit field, the indicated field in the loan file will be populated with the audit data selected by the administrator (the log in ID of the user who changed the indicated field, the name of the user who changed the indicated field, or the date and time the indicated field was changed).

However, an issue occurred. If a custom field was changed from the Audit format to a different format (such as the Date format) and then saved in the Loan Custom Field setting, the custom field was still acting as an audit field in the loan file. This issue has been resolved so that the custom field in the loan file functions according to the field format indicated in the Loan Custom Field Editor as expected.

(Added on 12/20/2018)

An issue occurred for users assigned with the Super Administrator persona attempting to unlock loan files. After navigating to Encompass Settings > System Administration > Unlock Loan File, selecting a locked loan in the list, and then clicking the Unlock button, the following error was triggered and the loan was not unlocked:

ERROR {4159} (DbAccessManager): <a142c03c-d6e6-4c7f-99d0-8fe4becca3df>Error executing query: [select L.*, S.SessionID, S.ServerUri, U.first_name, U.last_name from LoanLock L left join Sessions S on L.loginSessionID = S.SessionID

left join users U on L.lockedby = U.userid

where (lockedfor <> 0)

and (Guid in (select Loan.Guid from LoanSummary Loan

inner join @loanFolders _vid_fol on _vid_fol.Name = Loan.LoanFolder))

]

Must declare the table variable "@loanFolders".

…

This issue has been resolved.

(Added on 12/20/2018)

An issue with the naming of the Processing milestone has been resolved. Previously, if an administrator or authorized user renamed the Processing milestone using all uppercase letters (PROCESSING), or just some uppercase letters (besides the first letter, such as, ProCESSing), it would result in the following error being triggered when a user then tried to create a new loan file.

This issue only occurred with the Processing milestone. This issue has been resolved and you can now include upper-case letters in the name for the Processing milestone and it will not prevent users from creating new loan files.

(Added on 12/20/2018)

An issue occurred where the persona-based reports generated using the Settings Reports tool displayed blank information in portions of the Tools Access tab in the downloaded report (i.e., Excel spreadsheet). This issue has been resolved so that the report information is provided on this tab in its entirety.

(Added on 12/20/2018)

An issue occurred in Encompass 18.3 for users when attempting to access the Performance Meter (perfmeter.exe). Some users reported receiving the following error when attempting to access the Performance Meter to troubleshoot Encompass system connection issues:

The specified server has an invalid format.

This issue has been resolved and users can once again run the Performance Meter without triggering this error message.

The Encompass Reporting Database is recording the correct value of FullDocumentation when the (F) Full Documentation option is selected for the Loan Documentation Type Code dropdown list (field ID MORNET.X67) in a loan file. Previously a value of (F) Full Documentation was populated in the Encompass Reporting Database when an Encompass user pressed the CTRL+G keys on the keyboard, searched for MORNET.X67, and then selected the (F) Full Documentation option from the Loan Documentation Type Code dropdown list. This resulted in the incorrect (F) Full Documentation value being populated to Encompass reports .

Workaround Information

The following workaround was provided for this production issue and is no longer required for Encompass 19.1 and later.

• Do not press the CTRL+G keys to locate and adjust the Loan Documentation Type Code dropdown list (field ID MORNET.X67). Instead, open an Encompass input form that includes the Loan Documentation Type Code dropdown list (for example, the Borrower Summary - Processing or FNMA Streamlined 1003), and then select the (F) Full Documentation option from the dropdown list.

CBIZ-13489

An update has been made to correct the description that displays in the Encompass Reporting Database for the Was the Sex of the co-borrower collected on the basis of visual observation or surname? checkbox (field ID 4134) that displays on the HMDA Information input form. Previously the Encompass Reporting Database incorrectly listed the field as Borr Was the Sex of the Borrower collected on the basis of visual observation or surname?

This issue has been corrected and the description in the Encompass Reporting Database now displays as Co-Borr Was the Sex of the Co-borrower collected on the basis of visual observation or surname?

If the field has already been added to your reporting database, your administrator must remove field 4134 and add it again in order to populate the updated description. Alternatively, the description can be manually modified by the administrator. For clients with large databases, the second option takes significantly less time and is the recommended best practice.

CBIZ-14139

An issue was discovered in the System Audit Trail where the Loan File Sequence Number was not changing/incrementing correctly when an applicable loan file was edited and saved. In order for a field to be included in the System Audit Trail, it must be added to the Encompass Reporting Database and the Include in Audit Trail option must be selected for the field. To resolve this issue with the field not reflecting the correct data in the System Audit Trail, this field is no longer eligible to be included in the System Audit Trail. The Encompass Reporting Database has been updated so that this option is disabled for the Loan File Sequence Number field (field ID LOANFILESEQUENCENUMBER).

For clients who had indicated that the Loan File Sequence Number field should be included System Audit Trail in earlier versions of Encompass, this indication will be automatically removed upon upgrading to Encompass 19.1 and the field will no longer be included in the System Audit Trail.

When installing a new Encompass SmartClient instance on a user’s client machine, various programs and components required for Encompass to operate successfully are installed. An issue occurred for some users where the Microsoft Visual C++ 2015 environment product installation was failing during the initial Encompass SmartClient installation. However, once the Encompass SmartClient installation process was successfully completed and Encompass was started for the first time, the VC++ 2015 installation is re-started and it is successfully installed. This issue has been resolved so that the VC++ 2015 product is successfully installed during the initial installation of Encompass SmartClient.

(Added on 2/8/2019)

The Server Settings Manager in Encompass Admin Tools has been updated to remove an IP restriction policy. This policy was intended for internal use only and not intended for use by customers. With this update, this policy will no longer be displayed on the Server Settings Manager screen.

The following two options have been restored to the Offering Identifier dropdown list (field ID CASASRN.X163) on the Freddie Mac Additional Data Input Form:

• 250: Home Possible Advantage

• 251: Home Possible Advantage for HFAs

These options were removed from the dropdown list with the initial release of Encompass 19.1 along with a number of other options that were no longer supported by Freddie Mac. After the initial release, Freddie Mac decided to continue support for these two options, which have now been added back to the dropdown list.

(Added on 1/23/2019)

In the Ellie Mae knowledge base article How to Disable Plugins at the Workstation Level (article # 5911), Ellie Mae provides the relevant file locations and instructions for Encompass administrators and/or developers to quickly disable one or more Encompass SDK plugins in a systematic fashion from a single workstation. This proves especially useful when they receive reports of problematic behavior after a plugin has been deployed and it may not be known if the problem directly relates to the plugin or to something else. By disabling the relevant plugins they can quickly determine if the issue is directly related to the plugin or not. An issue occurred in Encompass 19.1 where the procedure provided in the knowledge base article was no longer working correctly and customers were unable to disable the SDK plugins. The source of this issue was identified and the relevant code was updated to resolve this issue. Customers can once again follow the steps in the knowledge base article and successfully disable the desired SDK plugins.