Fixed Issues for Version 19.2
Why we fixed these issues: These issues were fixed to improve usability and to help ensure Encompass is operating as expected. The issues that are chosen to be fixed are based on the severity of their impact to clients and client feedback.
Encompass Forms and Tools
An issue occurred where the Good Faith Fee Variance Violated alert was being triggered after the initial Loan Estimate (LE) was disclosed any time any transfer tax fees in the 1200 section (1203, 1204, and 1205) of the 2015 Itemization was increased, even if the aggregate total was not over the tolerance amount, yet the alert was not being triggered after disclosing the Closing Disclosure (CD) unless the aggregate total was was above the tolerance amount. (If the aggregate total did go above the tolerance amount when the initial CD was sent, the alert was not triggered.) This issue has been resolved so that transfer tax fees in the 1200 section that are changed after the LE or CD are disclosed will not trigger the alert unless the aggregate total reaches above the tolerance amount. The alert will only trigger after the initial LE and CD are disclosed when the aggregate amount of the fees in the 1200 section increase.
An issue occurred where values entered into the Impounds Waived (field ID 2961) and Impound Type (field ID 2962) fields on the Lock Request Form were being cleared from the fields whenever a user utilized the Piggyback Loans tool to link the loan to another loan. Specifically, the user opened the Piggyback Loans tool, clicked the Link to Loan button, selected the loan to link to, and then saved the original loan file. After saving the file, the two Impound fields were cleared. This issue has been resolved and these values now remain in the Impound fields when loans are linked to other loans.
An issue occurred where once the Key Pricing Fields alert was triggered and cleared, the alert was not triggered again when key pricing field values were modified. This issue has been resolved and the Key Pricing Fields alert is now triggered any time a key pricing field value differs from the original lock value.
An issue occurred where the Base Price was not mapped correctly from the Correspondent loan to the Correspondent Loan Status Tool. This issue has been resolved and the Base Price mapping is now correct.
An issue occurred where the ECOA Name field (field ID ECOA_NAME) on the Statement of Denial input form was being populated with the first and last name (i.e., the Personal Name) of the person associated with the Business Contact instead of the Company Name (i.e., the name of the Federal agency that administers the Equal Credit Opportunity Act (ECOA) as it applies to credit decisions) when the user clicked the field’s Address Book icon and selected the contact information to add to this ECOA Notice section of the input form. This issue has been resolved so that the agency name entered in the Business Contact’s Company field for the selected contact is populated to the ECOA_NAME field.
An issue occurred where preceding zeros were being removed from certain loan numbers in NMLS Mortgage Call Exception reports. In the generated Exception report, loan numbers that start with a zero or multiple zeros and contain at least one letter (i.e., an alpha character) were being displayed without the preceding zero or zeros in the loan number. If there were any letters within the loan number, then the preceding zeros were not being removed.
Example:
-
0011000014 - The preceding zeros were removed from the Exception report.
-
001M000044 - The preceding zeros were not removed from the Exception report
This issue has been resolved.
The Exception report can be generated when you generate an NMLS Call Report and the system prompts you that the report may contain incomplete data due to missing or invalid data. Click Yes on the prompt to generate the Exception report in Microsoft Excel.
(Added on 4/2/2019)
The By field in the CAIVRS Number section of the Tracking tab on the VA Management input form is now being populated with the name of the individual who obtained the CAIVRs number (field ID 3068). Previously the By field was populated with the name of the individual who conducted the LDP/GSDA search (field ID 3070). This issue did not affect the By field for the CAIVRS number on any other input forms in Encompass.
CBIZ-2978
(Added on 4/2/2019)
On the Fee Details windows on the 2015 Itemization input form, the Last Disclosed fields for the Loan Estimate no longer clears for all previously disclosed fees when a Closing Costs template is applied to the loan file. While the cumulative amounts for the disclosed fees were still being tracked on the Fee Variance Worksheet, the individual fees were no longer visible on the Fee Details windows. This issue has been resolved and the Last Disclosed amount for the Loan Estimate is now being retained in the Fee Details windows when a Closing Costs template is applied.
Workaround Information
The following workaround was provided for this production issue and is no longer required for Encompass version 19.2 and later:
-
In the Default Template Setting (Encompass > Settings > Loan Templates > Default Template Setting) select the Closing Cost Template checkbox to apply only fields in a Closing Costs Template that contain a value.
CBIZ-19283
(Added on 4/2/2019)
The QM Status (field ID HMDA.X26) on the NMLS Report Information pop-up window (accessed by clicking the NMLS button on the HMDA Information input form) is now updated when a change occurs in the Ability-to-Repay Loan Type (field ID QM.X23) on the ATR/QM Eligibility tab on the ATR/QM Management input form.
CBIZ-21129
(Added on 4/2/2019)
An issue was resolved that caused the Loan Originator Information from the 1003 Page 3 to not copy to the 3. Creditor Contact Information section on the Statement of Denial input form when a Data Template or Loan Template Set were used to select the Copy to Lender in File Contacts checkbox (field ID 1969) and to populate the Channel option (field ID 2626) in a loan file. This issue has been resolved and the Loan Originator Information is populating correctly to the Statement of Denial input form when templates are used to apply the options described above.
Workaround Information
The following workarounds were provided for this production issue and are no longer required for Encompass version 19.2 and later:
-
Do not select a Channel option or the Copy to Lender in File Contacts checkbox in your Data Templates.
-
If a Data Template has already been used to apply the Channel option and to select the Copy to Lender in File Contacts checkbox, select another Channel option and then switch back to the correct option to retrigger the calculation for Box 3 on the Statement of Denial input form.
CBIZ-20818
(Added on 4/2/2019)
All 11 options now display in the Purpose of Refinance dropdown (field ID 299) on the RegZ-LE and RegZ-CD input forms and in the dropdown lists for these forms in the Data Templates setting in Encompass. Previously all 11 of the Purpose of Refinance options were previously displaying for the dropdown list on other Encompass forms, but only 9 of the options displayed for the RegZ-LE and only 6 displayed for the RegZ-CD on the input forms and in the data templates.
Workaround Information
The following workaround was provided for this production issue and is no longer required for Encompass version 19.2 and later:
-
Manually type a value for the Purpose of Refinance (field ID 299).
CBIZ-20764
Calculation Updates
(Added on 4/2/2019)
The payment used in the Total Debt Ratio (field ID QM.X376) is now calculated correctly for fixed-rate loans with interest-only payments on a primary residence property. Previously the payment was not correctly including the present housing expenses for the non-occupant co-mortgagors (field ID 1379), resulting in the Total Debt Ratio being higher than the Housing Ratio (QM.X375).
Migration
To preserve the data integrity of existing loans, updating to the Encompass 19.2 release will migrate the existing Total Debt Ratio (field ID QM.X376) without triggering a recalculation if the Primary checkbox is selected for Property Will Be (field ID 1811), the Fixed Rate checkbox is selected for Amortization Type (field ID 608), and the Interest Only months (field ID 1177) are greater than 0 (zero). A gold Lock icon will display for this fields to ensure that the automatic calculation function for this field in existing loans is disabled after migrating to Encompass 19.2. An Encompass user can manually update the amount if needed or can trigger a recalculation to the field by clicking the gold Lock icon next to the field.
CBIZ-14758
(Added on 4/2/2019)
An adjustment has been made to ensure that the PMI Midpoint Cancellation Date (field ID 3548) matches the midpoint of the amortization schedule for the loan. The midpoint of the amortization period is halfway through the period from the first day of the amortization period (established by the initial amortization schedule for a fixed rate loan and the amortization schedule in effect for an adjustable rate loan) and ending when the mortgage is scheduled to be amortized. The cancellation now occurs at the next payment after the midpoint. Previously, Encompass was off by one month when calculating the PMI cancellation date.
Migration
When updating to Encompass 19.2 release, the PMI Cancellation Date will be recalculated for previously existing loans.
CBIZ-20217
HELOC Loans
(Updated on 5/7/2019)
An issue was resolved that resulted in the Maturity Date (field ID 78) not updating for HELOC loans when the Term (field ID 4) or 1st Payment Date (field ID 682) is changed. This issue has been resolved and the Maturity Date is now updating as expected.
Migration
To preserve the data integrity of existing loans, updating to the Encompass 19.2 release will migrate the Maturity Date (field ID 78) without triggering a recalculation if the Document Date (field ID L770) is populated. A gold Lock icon will display for the Maturity Date when the field is not blank to ensure that the automatic calculation function for this field in existing loans is disabled after migrating to Encompass 19.2. An Encompass user can manually update the date value if needed or can trigger a recalculation to the field by clicking the gold Lock icon next to the field.
CBIZ-2347
An issue occurred where the HELOC Initial Draw (field ID 4510) field on the Lock Request Form was editable for non-HELOC loans. This issue has been resolved and the HELOC Initial Draw field can now only be edited when the Loan Type is “HELOC”.
HELOC Initial Draw Field Disabled for Non-HELOC Loan
HELOC Initial Draw Field Enabled for HELOC Loan
Construction Loans
(Added on 4/2/2019)
An issue was resolved with the value being populated for the Estimated Construction Interest (field ID 4088) for fixed-rate construction-only or construction-to-permanent loans. The Estimated Construction Interest for these loans was populated with the same value regardless of whether 365/360 or 365/365 was selected for the Number of Days (field ID 1962). This discrepancy was also reflected in the APR value (field ID 799). This issue has been resolved and the correct values are now being populated based on the option selected for the Number of Days.
Workaround Information
The following workaround was provided for this production issue and is no longer required for Encompass version 19.2 and later:
- Click the Lock icon for the APR (field ID 799) and enter the correct value.
CBIZ-14161
Encompass Dashboard
In previous versions of Encompass, when field Log.MS.DateTime.xxxx was added to a Loan Table Snapshot in the Dashboard it was not sorting correctly. (This field captures the date and time that an action was taken on a milestone. For example, Log.MS.DateTime.Started captures when a milestone was started.) The Log.MS.DateTime.xxxx field data was sorting correctly by MM/DD/YYYY HH:MM:SS, however, the AM and PM indicators were not. PM times were being sorted ahead of times AM times.
For example, 11/26/2018 6:02:00 PM was being listed before 11/26/2018 9:34:00 AM when the column was to be sorted in ascending (earliest to latest) order. This issue has been resolved and the Log.MS.DateTime.xxxx log entry is now sorted correctly in the Dashboard’s Loan Table Snapshots.
Encompass Home Page
The Encompass Tip of the Day module on the Encompass Home Page has been updated with new tips and links to updated topics in the Encompass Help site. This module is a configurable module that you can add or remove from your Home Page as you want. When included on your Home Page, a new Encompass tip is provided each day. Refer to the Home Page help topic for information about adding and configuring this module on your Home Page.
Encompass Pipeline
(Added on 4/2/2019)
On the Encompass Pipeline, authorized users can click to select multiple loan files, and then click the Delete icon (or right-click a selected loan, and then select Delete Loans) to delete all of the selected loans at once. A pop-up prompt is provided, and you can select Apply to all items, and then click Yes to complete the deletion. However, an issue occurred where only one loan file was being deleted even when the user had selected the Apply to all items option here. This issue has been resolved so that all of the selected loan files are now deleted as expected in this scenario.
(Added on 4/2/2019)
An issue occurred where expired locks with pending extension requests incorrectly displayed an unlocked lock icon with a label of “Expired” on the banner. This issue has been resolved and the correct icon/label of red lock with purple envelope and label of “Expired, Extension Requested” is now displayed on the loan banner and the pipeline.
Encompass Settings
An issue occurred for clients who use custom versions of the Borrower Summary input form (or forms). If the administrator had created a custom input form named Borrower Summary, and then included that custom form in an Input Form Set, this custom form was replaced by the standard Borrower Summary – Origination and Borrower Summary – Processing input forms in the Input Form Set every time they upgraded from one version of Encompass to another. This could result in the wrong Borrower Summary input forms being used for loans if a loan template including this Input Form Set was applied.
This issue has been resolved and the custom Borrower Summary input form is no longer being replaced.
The field UWC.ALLPTCPTFCOUNT provided in the Encompass Reporting Database is intended to reflect the number of Underwriting Conditions Prior to Close (PTC) and Prior to Funding (PTF). However, it was discovered that this value was incorrect and contained only the number of Underwriting Conditions PTF. This issue has been resolved and this value now reflects the number of Underwriting Conditions Prior to Close (PTC) and Prior to Funding (PTF). With this update, customers can now report on the number of these conditions accurately and get an indication on the number of conditions remaining PTC and PTF.
(Added on 4/2/2019)
An issue occurred with User Groups when creating a new user. Here is the scenario where the issue occurred:
- Create a new User Group. (For example, a group named Sample User Group.)
-
Settings > Company/User Setup > User Groups.
-
On the Members tab, click the New icon, select the Administration organization folder, and then click the green checkmark. These steps ensure that the users in this User Group are part of the Administration organization only (and not any levels below it) and their access to loans and data are adjusted accordingly.
-
Save this User Group.
- Next, go to the Organization/Users setting, expand the Administrator folder hierarchy, and then select an organization folder under the Administration organization.
- In the Enabled Users section, click the New icon to create and add new user in this organization.
This is where the issue occurs. In the User Details window, the new user group that you created (Sample User Group) and was intended to include only users in the Administration organization is automatically listed in the Group Membership section. However, unless the user is being created in an organization that is a member of the user group, the user group should not be listed in the Group Membership section.
This issue has been resolved so that User Groups are only listed in the Group Membership section for a new user profile if the user is being created in an organization that is a member of the User Group.
(Added on 4/2/2019)
An issue occurred where an administrator could use the Loan Reassignment tool in Encompass Settings to assign a loan file to a different loan officer, but the newly assigned loan officer’s name was not reflected on applicable disclosures or on the 1003 Page 3 (Loan Originator’s Name (field ID 1612)). This issue could result in disclosures being sent with the incorrect loan officer information and they will not be assigned to the correct loan officer. This issue has been resolved so that the newly assigned loan officer is reflected in all applicable loan fields.
NICE-15949
(Added on 4/2/2019)
An issue occurred with the “Company controls extension days and price adjustments by extension occurrence” Control Option in the Lock Extension Price Adjustment section of the Product and Pricing setting. When a new entry was added to the Adjustment per Lock Extension grid with a duplicate Days to Extend value to an existing entry, an error message “There already exists a price adjustment with the same Days to Extend.” was displayed and the duplicate value was not accepted. This issue has been addressed and multiple extensions with the same Days to Extend value can now be entered in the grid.
Business Rules
(Added on 4/2/2019)
An issue was resolved that enabled Encompass users to bypass Persona Access to Fields business rules that restricted access to the Link to Loan, Add New Closed End, and Add New HELOC buttons on the Subordinate Mortgage Loan Amount pop-up window. The window is access by clicking the Sub. Financing button on forms such as the Borrower Summary – Origination, Borrower Summary – Processing, 1003 Page 1, RegZ-LE, and RegZ-CD. Users were able to enable the buttons by clicking one of the following fields and then tabbing out of the field:
-
New Closed End Primary Mortgage (field ID 4487)
-
New Closed End Subordinate Mortgage (field ID 4488)
-
New HELOC Draw / Credit Limit (field IDs 4489 and 4490)
This issue has been resolved and Personas who have been denied access to the buttons can no longer bypass the buttons by clicking and tabbing out of the fields listed above.
CBIZ-21214
An issue occurred with Field Data Entry business rules. When one of these rules had been set up with an advanced condition that specified that an action should occur when a user selected one or more specific values from an input form dropdown field, the rule was being triggered regardless of the option the user selected from the specified dropdown field. For example, if a rule had been set up to trigger a pop-up window if the user selected Gift Funds from the Source of Down Payment dropdown field (field ID 34), the pop-up window was still being triggered by the rule if the user selected Cash on Hand or any other option from this dropdown field. This issue has been resolved.
In earlier versions of Encompass, if a Field Triggers business rule was created and an action was set to trigger when field HC0101 (the checkbox for the first agency listed on the Home Counseling Providers input form list) was updated, the system was automatically clearing field HC0101 in the Home Counseling Providers List if the user clicked the Get Agencies button on the Home Counseling Providers input form, selected the first service under Multiple Services, clicked Get Agencies, and then clicked Save.
This issue has been resolved so that this checkbox (field HC0101) is selected as expected when a Field Triggers business rule is set up to trigger when field HC0101 is updated.
Dynamic Data Management (DDM)
It was discovered that Dynamic Data Management (DDM) Fee and Field rules were not taking calendar-based calculations into account. Specifically, if the rule was set up to populate a specific field with a value that was based on a calendar-based calculation, the calculation was not being executed and the field was not updated.
This issue has been resolved and the Calculation Value Type now supports the following calendar-based operations and will be executed in applicable DDM rules:
- Calendar.AddBusinessDays(date, count, moveToNext)
- Calendar.AddPostalDays(date, count, moveToNext)
- Calendar.AddRegZBusinessDays(date, count, moveToNext)
(Added on 4/2/2019)
An issue occurred in FHA loans where the value in field 232 (Proposed/Estimated Monthly Mortgage Insurance) on the 1003 Page 2 was not being updated when a DDM fee rule had been set up calculate mortgage insurance (MI) applicable scenarios. In these FHA loans, users could open the MIP/PMI/Guarantee Fee Calculation window and click the Get MI button to calculate the MI and field 232 was updated as expected. However, the DDM rule, which also should have resulted in the MI calculation populating field 232, was not operating correctly. This issue has been resolved and field 232 is now updated accordingly when an applicable DDM fee rule is run.
NICE-15221
(Added on 4/2/2019)
An issue occurred for Encompass users who set up and activated DDM field or fee rules. When the Effective Date Criteria was set to Blank / On or After, the rule was not running when the effective Date field was left blank. Since the rule was not running, loan data could be incorrect and loan team members could be unaware of this issue since they would expect the rule to run. This issue has been resolved and the field and fee rules will run as expected when the effective Date field (highlighted below) is left blank.
NICE-16219
(Added on 4/2/2019)
When an active fee or field rule is exported, it is automatically deactivated. An issue occurred where a fee or field rule that had been exported, and was then imported, was indicated as Active on the Field Rules or Fee Rules screen. However, after opening the newly imported rule, the rule was correctly indicated as Inactive in the Add/Edit Field [or Fee] Scenario pop-up window. After closing the pop-up window, the rule was then correctly indicated as Inactive on the Field Rules or Fee Rules screen. This issue has been resolved so that a field or fee rule is indicated as Inactive on the Field Rules or Fee Rules screen after it is imported.
NICE-15619
(Added on 4/2/2019)
An issue occurred where the DDM Data Tables were not operating correctly with field and fee rules. When a Data Table included field ID 16 (Subject Property # of Units) and List of Values was selected as the Value type, the data from the Data Table was not being populated to field 16 even though the field or fee rule associated with the Data Table was set up correctly to populate data to the field. When Range was selected as the Value type in the Data Table, field 16 was updated as expected. This issue with the Data Table has been resolved and field 16 is now populated as expected in this scenario.
NICE-22028
Loan Templates
(Added on 4/2/2019)
The 2010 Itemization input form is now used in Encompass for HELOC loans created in Encompass Consumer Connect under the scenario described below:
-
The HELOC loan was created using an Encompass Consumer Connect Loan Template Rule.
-
The Encompass Consumer Connect Loan Template Rule was based on an Encompass Loan Template Set configured to use the 2010 Itemization input form.
Previously HELOC loans created under the scenario described above would have the 2015 Itemization applied to the loan in Encompass, regardless of the version of the Itemization form specified in the template. This issue has been resolved and the 2010 Itemization is now being used on loans that match the scenario described above.
When different versions of the RESPA-TILA forms are specified in the Data Template and Closing Costs Template in an Encompass Loan Template Set, the Closing Costs Template takes precedent.
CBIZ-20820
Electronic Document Management
An issue was resolved that caused a “Your web browser is out of date” message to display when a loan officer was directed to electronically sign a document from within Encompass. The warning message did not interfere with the eSigning process, and loan officers were still able to close the warning message and electronically sign the document. This issue has been resolved and the warning message no longer displays.
EDM-20788
Encompass Input Form Builder
When trying to open the standard Encompass version of the Settlement Service Provider List in previous versions of the Encompass Input Form Builder, the following error was triggered and the form would not open.
This issue has been resolved and you can now successfully open this form and not receive the error.
Encompass Software Development Kit (SDK)
If an Encompass SDK user utilized the SDK to create a new user and set the user up so they were forced to change their password the first time they logged into Encompass, the user received a “Password Synchronization Failed” error when they attempted to log into Encompass and set up their new password as instructed. This cause of this issue was identified. The relevant code has been updated to ensure that this error is no longer triggered and the new user can successfully change their password and proceed to log into Encompass in this scenario.
Additional Fixed Issues
(Added on 4/2/2019)
An issue was resolved that caused an error message to display and the Encompass application to stop working when an Encompass user running Windows 10 typed an entry in the Action Date field (field ID 749) on the HMDA Information input form and then attempted to open another input form without first tabbing out of the Action Date field. This issue has been resolved and Encompass continues to run as expected under the scenario described above.
Workaround Information
The following workarounds were provided for this production issue and are no longer required for Encompass version 19.2 and later:
-
Type a date in Action Date field and then tab out of the field before opening another input form
-
Or select an Action Date by clicking the Calendar icon.
-
Or enter the Action Date on another input form such as the Borrowers Summary – Origination or Borrowers Summary – Processing.
CBIZ-20766
Fixed Issues for Version 19.2.0.1 Server Patch 1
(Updated on 5/20/2019)
This update contains updates to users' Encompass client machines (19.2.0.1) and a Server Patch (server patch 1) that is applied to the Encompass Server.The fixed issues listed below are included in this update and were first released on April 25, 2019.
This client-side update (19.2.0.1) and the Server Patch (server patch 1) will be applied to your users' computers automatically and cannot be controlled manually via the Encompass Version Manager tool. Users will receive the update upon their initial log in of Encompass following the release.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.2.0.1 Server Patch 1 release. Although it is not required, it is strongly recommended that you upgrade to this latest SDK delivered with this update to ensure the same functionality that is in this latest version of Encompass is also available in your SDK. If your SDK application utilizes the Encompass SmartClient, you can automate this process so the SDK is upgraded automatically every time you apply an Encompass release. If your SDK application is installed on a computer at your location, you must manually upgrade the SDK for every release. For instructions for automating the upgrade process or manually upgrading the SDK, refer to the Upgrading the Encompass SDK page or view the SDK Programmer’s Guide.
Again, upgrading to this latest SDK package is strongly recommended, but not required, for this 19.2.0.1 Server Patch 1 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once you upgrade, your new version number will be 19.2.0.1 Server Patch 1.
Updates to the Encompass Server (i.e., Server Patch 1)
(Added on 5/20/2019)
Below is the update in the Server Patch that is applied to the Encompass Server. The Server Patch contains the relevant Encompass code that applies to the following fixed issue. The Server Patch included with this release will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
In Encompass 19.2, on the Home Counseling Providers input form the following field updates were made:
- Agency Name field ID has been changed to field ID URLA.X232 (from HOC.X2).
- Home Counseling Completion Date field ID has been changed to field ID URLA.X233 (from HOC.X17).
- A new Agency ID field (field ID URLA.X155) has been added to the form.
To make these fields available to be included in Encompass reports, the Encompass Reporting Database was updated accordingly with these fields.
CBIZ-23751
Updates to the Encompass Client Machines
The Encompass 19.2.0.1 update includes the following items, which are client-side updates that are applied to users' Encompass client machines.
Dynamic Data Management (DDM)
An issue occurred that resulted in Dynamic Data Management (DDM) field rules and fee rules failing to run if the rule included a stop condition that referenced a date field and the date field was blank in the loan file. For example, a stop condition like this one could be set up for the Application Date field so that the DDM field rule does not run and automatically populates fields when the Application Date is earlier than January 1, 2019:
[@3142] < #1/1/2019#
In this example, if the Application Date field was blank, the stop condition would erroneously evaluate as true and the DDM field rule would not run.
This issue occurred with the rule level stop condition, as well as with the global stop condition in DDM. This issue has been resolved so that DDM field and fee rules run as expected when there is a stop condition that references a date field and if the referenced date field is blank in the loan file.
Fixed Issues for Version 19.2.0.2
(Updated on 5/10/2019)
This update contains updates to users' Encompass client machines (19.2.0.2). The fixed issues listed below are included in this update and were first released on May 9, 2019.
This client-side update (19.2.0.2) can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.2.0.2. Although it is not required, it is strongly recommended that you upgrade to this latest SDK delivered with this update to ensure the same functionality that is in this latest version of Encompass is also available in your SDK. If your SDK application utilizes the Encompass SmartClient, you can automate this process so the SDK is upgraded automatically every time you apply an Encompass release. If your SDK application is installed on a computer at your location, you must manually upgrade the SDK for every release. For instructions for automating the upgrade process or manually upgrading the SDK, refer to the Upgrading the Encompass SDK page or view the SDK Programmer’s Guide.
Again, upgrading to this latest SDK package is strongly recommended, but not required, for this 19.2.0.2 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once you upgrade, your new version number will be 19.2.0.2.
Updates to the Encompass Client Machines
The Encompass 19.2.0.2 update includes the following items, which are client-side updates that are applied to users' Encompass client machines.
Fixed Issues
To preserve the data integrity of existing HELOC loans originated prior to Encompass 19.2, the intended approach is that upgrading to Encompass 19.2 or 19.2.0.1 Server Patch 1 from an earlier version will migrate the Maturity Date (field ID 78) without triggering a recalculation if Closing documents have been generated (i.e., the Document Date (field ID L770) is populated). However, an issue occurred where field 78 was being recalculated after migrating to Encompass 19.2 or 19.2.0.1 Server Patch 1 (if the field was not blank). This issue has been resolved in Encompass 19.2.0.2. A gold Lock icon will display for the Maturity Date when the field is not blank to ensure that the automatic calculation function for this field in existing loans is disabled after migrating to Encompass 19.2.0.2. Authorized users can then manually update the date value if needed or can trigger a recalculation to the field by clicking the gold Lock icon next to the field.
CBIZ-24460
Issues impacting Field Data Entry and Field Triggers business rules were introduced in Encompass 19.2. As a result, Field Data Entry business rules that were intended to restrict users from entering or changing data in specific fields were not being enforced and users could enter or change field data despite the business rules being activated and triggering for the user as expected.
The relevant code introduced in Encompass 19.2 that caused these issues was identified and removed from this new Encompass 19.2.0.2 release. As a result, these issues have been resolved.
NICE-24362, NICE-25140, NICE-25141, NICE-25093
Documents are now displaying correctly when they are added to the eFolder using the Scan and Attach icon on the Document Details window. Beginning with the Encompass 19.2 release, "ImageMan Twain.Net Version 1.0 Trial" watermarks began displaying on document files added to the eFolder via the Scan and Attach feature.
This issue has been resolved and scanned images are now displaying as expected without a watermark.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass version 19.2.0.2 and later:
- Scan a document into your computer using an external scanner and then use the Browse and Attach icon in the Document Details window to add the file to the eFolder.
DOCP-4460
Fixed Issues for Version 19.2.0.3 Server Patch 2
(Updated on 5/20/2019)
This update contains updates to users' Encompass client machines (19.2.0.3) and a Server Patch (server patch 2) that is applied to the Encompass Server. The fixed issues listed below are included in this update.
This client-side update (19.2.0.3) can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
Please note that the Server Patch (server patch 2) included with this release will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
The Encompass SDK (Encompass Software Development Kit) has been repackaged with this 19.2.0.3 Server Patch 2 release. Although it is not required, it is recommended that you upgrade to this latest SDK delivered with this update to ensure the same functionality that is in this latest version of Encompass is also available in your SDK. If your SDK application utilizes the Encompass SmartClient, you can automate this process so the SDK is upgraded automatically every time you apply an Encompass release. If your SDK application is installed on a computer at your location, you must manually upgrade the SDK for every release. For instructions for automating the upgrade process or manually upgrading the SDK, refer to the Upgrading the Encompass SDK page or view the SDK Programmer’s Guide.
Again, upgrading to this latest SDK package is recommended, but not required, for this 19.2.0.3 Server Patch 2 update.
Visit the Encompass SDK Install Files page to access the SDK install files for this release.
In Encompass, go to Help > About Encompass in the menu bar to view your Encompass version. Once you upgrade, your new version number will be 19.2.0.3 Server Patch 2.
Updates to the Encompass Server (i.e., Server Patch 2)
Below is the update in the Server Patch that is applied to the Encompass Server. The Server Patch contains the relevant Encompass code that applies to the following fixed issues. The Server Patch included with this release will be applied to the Encompass Server automatically and cannot be controlled manually via the Encompass Version Manager tool.
Fixed Issues
High memory usage was observed for the ConcurrentDictionary object in the Elli.MessageQueues.Rmq.RmqTunnel class. The relevant code on the Encompass Server has been updated to prevent potential “memory leaks” that could occur due to these system calls. The reduction of these memory leaks results in improved Encompass system performance.
Updates to the Encompass Client Machines
The Encompass 19.2.0.3 update includes the following items, which are client-side updates that are applied to users' Encompass client machines. This client update can be controlled manually via the Encompass Version Manager tool. If the tool has been configured to always apply new releases to users’ computers automatically, users will receive this update upon their initial log in of Encompass following the release.
Fixed Issues
In Encompass versions 19.2, 19.2.0.1 Server Patch 1, and 19.2.0.2, an issue occurred for non-administrator users (i.e., users not assigned with an Administrator or Super Administrator persona) in certain user groups where they were unable to generate 1003 forms in disclosure packages. Even when the eFolder Setup administrative settings were configured to include the 1003 forms in specific eDisclosure packages when specific criteria was met, when users were in the process of ordering disclosures, the 1003 forms were not listed in the Select Documents window that lists the forms to include in the disclosure package. As a result, users could not indicate that the 1003 forms should be included in the disclosure package.
Please note that this issue with the 1003 forms only occurred in one specific scenario: When an administrator in Encompass 19.2, 19.2.0.1 Server Patch 1, or 19.2.0.2 accessed the User Groups setting and then selected a user group there to update, if they added or removed any forms in the Standard Print Forms list for the user group, this resulted in the error occurring for the users. When users in the impacted user group attempted to order disclosures, the 1003 forms were not listed in the Select Documents window.
This issue with generating the 1003 disclosures has been resolved.
NICE-25254