Fixed Issues for Version 18.1.0.4 Server Patch 3
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.
The Encompass 18.1 February Service Pack includes updates to users' Encompass client machines and a Server Patch that is applied to the Encompass Server.
Updates to the Encompass Server (i.e., Server Patch 3)
The Encompass 18.1 February Service Pack includes updates to users' Encompass client machines and a 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.
The Encompass 18.1 February Service Pack includes updates to users' Encompass client machines and a 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.
The relevant code in the Server Patch 3 portion of this release applies to features in Encompass Banker Edition only. This code in Server Patch 3 does not impact Encompass Broker Edition.
Encompass Forms and Tools
An issue occurred where the Net Sell Price (field ID 2274) was not calculated correctly for loans with a lock extension after they are assigned to a trade.
This issue has been resolved and the Net Sell Price now calculates any extension fees into Price Adjustments.
SEC-10537
An issue occurred where the Escrow Details tab of the Correspondent Purchase Advice Form only captured the borrower paid escrows entered on the 2015 Itemization form. For example, on the 2015 Itemization form, four months of Property Taxes were entered on line 1004 at $234.33/month, for a total of $937.32. If the borrower paid $437.32 and the seller paid $500.00, the Correspondent Purchase Advice Form only captured the borrower paid amount of $437.32 instead of the whole $937.32.
This issue has been resolved and the Correspondent Purchase Advice Form now captures both the borrower and seller paid escrows entered on the 2015 Itemization form.
SEC-12657
Updates to the Encompass Client Machines
The following items are all client-side updates that are applied to users' Encompass client machines. These client updates 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.
Encompass Forms and Tools
An issue occurred where Log entries that were being generated and provided in loans using 2010 forms (Forms > RESPA-TILA Form Version > RESPA 2010 GFE and HUD-1) were not being generated and provided in loan files using 2015 forms (Forms > RESPA-TILA Form Version > RESPA-TILA 2015 LE and CD). This issue with loans using 2015 forms has been resolved as follows:
- Disclosures sent electronically - When an eDisclosure is sent to a borrower (or other recipient) or when a pre-closing Closing Disclosure is disclosed electronically, a Disclosures sent electronically entry is now added to the Loan Log in the loan file. When you click to select the Disclosures sent electronically entry in the Log, the Disclosure Tracking Tool will display to the right of the Log, with the applicable entry pre-selected in the Disclosure History section of the tool.
The eDisclosures Ordered entry that is added to the Log when eDisclosures are ordered through the eFolder will continue to be used accordingly as in previous versions of Encompass.
- Closing Disclosures sent electronically - A Closing Disclosures sent electronically entry is now added to the Log when closing documents are generated and then sent. When you click to select the Closing Disclosures sent electronically entry, the Disclosure Tracking tool will display to the right of the Log, with the applicable entry pre-selected in the Disclosure History section of the tool.
- Disclosures mailed - A Disclosures mailed entry is now added to the Log when disclosures are printed when generating an eDisclosure package (using the eDisclosures button) from the eFolder. Specifically, if you click the Print button (and then click Print Selected Documents to print the disclosures) on the Select Documents window, a Disclosures mailed entry is now added to the Log. In addition, if you use the Disclosure Tracking tool to manually add a new entry to the Disclosure History table to indicate disclosures have been generated and sent, a Disclosures mailed entry is now added to the Log. When you click to select the Disclosures mailed entry in the Log, the Disclosure Tracking tool will display to the right of the Log, with the applicable entry pre-selected in the Disclosure History section of the tool.
A Disclosures printed entry will continue to be added to the Log each time a user clicks the Print icon anywhere in Encompass and then prints or previews disclosures from the Print window. This is the same functionality as in previous versions of Encompass.
NICE-4696, NICE-5584, NICE-5424
An issue was resolved that caused several No Co-applicant checkboxes to be cleared inappropriately on the 2018 DI version of the HMDA Information input form. This issue would occur when the Information Not Provided checkbox (field ID 4244) was selected in the Race category for the borrower. Selecting the checkbox would clear the No Co-applicant checkbox at the top of the co-borrower section (field ID 3840) and the No Co-applicant checkbox in the co-borrower Race section (field ID 3174). This issue has been resolved and the checkboxes are no longer clearing under the circumstances described above.
CBIZ-14901
The following updates were made in the logic used to populate the Total Points and Fees (field ID HMDA.X78) on the HMDA Information input form:
-
NA is populated when the 6. Purchased loan option is selected for the Action Taken (field ID 1393).
-
NA is populated when RESPA-TILA Form Version > RESPA-TILA 2015 LE and CD forms are not used for the loan.
-
NA is populated when the Transaction is exempt from Reg. Z Ability-to-Repay requirements based on checkbox (field ID QM.X103) is selected.
-
When none of the preceding conditions are true, the value from the Total Section 32 points and fees in this loan (field ID S32DISC.X48) is populated in the Total Points and Fees field (field ID HMDA.X78). If the Total Section 32 points and fees in this loan is blank, 0 is populated in the Total Points and Fees field.
CBIZ-14964
An issue has been resolved that caused the Purchase Price (field ID 136) for Conventional loans to round up to the nearest dollar after using the Secondary Registration tool to lock and confirm the loan rate. The issue has been addressed and the Purchase Price now retains the cent amounts in the two decimal values.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Adjust the purchase price back to the original amount after locking and confirming the rate.
CBIZ-2803
An issue was resolved that caused POC (Paid Outside Closing) fees entered on the 2015 Itemization in lines 802e, 802f, 802g, and 802h to be populated on two different lines in the Details of Transaction section on input forms such as the 1003 Page 3. These fees were included in line f. Estimated closing costs (field ID 137) and line h. Discount (if Borrower will pay) (field ID 1093). This double entry resulted in an incorrect reduction in the line p. Cash to Borrower (field ID 142) amount in the Details of Transaction.
The duplication of fees was not transferring to the Loan Estimate or Closing Disclosure.
This issue has been resolved and the POC fees for lines 802e–802h are now included only in line h. Discount (if Borrower will pay) (field ID 1093).
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
- Click the Lock icon for line f. Estimated closing costs (field ID 137) on the 1003 Page 3 and subtracting the total POC fee amounts from lines 802e–802h on the 2015 Itemization.
CBIZ-4115
A Lock icon has been added next to the Maximum percentage of total loan amount for points and fees allowed (field ID S32DISC.X100) and the following updates have been made to the field:
-
When the Application Date (field ID 745) is earlier than 01/01/2018, the Maximum percentage of total loan amount for points and fees allowed field (field ID S32DISC.X100) is a free entry field.
-
When the Application Date (field ID 745) is 01/01/2018 or later, the Maximum percentage of total loan amount for points and fees allowed field (field ID S32DISC.X100) is a read-only field. Click the Lock icon to recalculate this field if needed.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Make a note of the dates for Application Date (field ID 745), Est. Closing Date (field ID 763), Closing Date (field ID 748) and Doc Signing Date (field ID 1887). Change the Application Date, Est. Closing Date, Closing Date, and Doc Signing Date to reflect a date of 12/31/2017 or earlier. Update the Maximum percentage of total loan amount for points and fees allowed (field ID S32DISC.X100). Change Application Date, Est. Closing Date, Closing Date, and Doc Signing Date back to the previous values. The Maximum percentage of total loan amount for points and fees allowed will retain the value entered manually.
CBIZ-14710
An issue was resolved that caused broker fees to double in the Section 32 points and fees that display on the ATRM/QM Management input form. This occurred when broker fees were entered in the line 801 section on the 2015 Itemization and the Broker Compensation when rate was set checkbox (field ID QM.X372) was also selected on the Qualification tab on the ATR/QM Management input form. Under these conditions, the Broker Fees were copied to the Section 32 Points and Fees (field ID NEWHUD2.X489) in the Fee Details window for Broker Compensation in the line 801 section. This in turn caused the amounts and percentages for Total points and fees applicable under section 32 (field IDs S32DISC.X48 and QM.X123) to double on the Qualification tab on the ATR/QM Management input form. This issue has been resolved and the broker fees are no longer included twice in the Section 32 points and fees.
CBIZ-2981
An issue occurred with the Disclosure Tracking Tool for loans where an active Field Data Entry business rule was active and being enforced. When a user in a loan file ordered and sent eDisclosures to a borrower, the applicable entry was added to the Disclosure Tracking Tool’s Disclosure History section as expected. Then, if the user attempted to save the loan file without entering data in a field that was required to satisfy the Field Data Entry business rule, the user received a pop-up message alerting them they could not save the loan due to the required field not being completed. This is expected behavior since the business rule was active and being enforced. However, the issue occurred when the user chose not to enter the required data and close the loan file without saving their latest changes. Closing the file without saving their changes resulted in the tracking entry being cleared from Disclosure History section of the tool. Conversely, if the Field Data Entry business rule was not active in this scenario, the user could close the loan without saving their changes and the tracking entry would remain listed in the Disclosure History section of the tool as expected. This issue has been resolved so that the tracking entry remains in the Disclosure History section even if a Field Data Entry business rule is active and being enforced.
NICE-5406
An issue was resolved that caused the Flood Ins. Reserve (field ID 235) for a VA loan to be added twice to the Total Proposed Monthly Payment (field ID VASUMM.X99) on the Qualification tab on the VA Management input form. This issue has been resolved and the flood insurance reserve is now only added once to the total Proposed Monthly Payment.
CBIZ-2801
The Payoff and Payments table for the alternate version of the Closing Disclosure Page 3 now displays the text entered in the Adjustment Description field for the entry, instead of Other (the adjustment type). To access the Payoff and Payments table, click the Payoff & Payments button on the version of the Closing Disclosure Page 3 that displays when using alternate disclosures. The description on the table now matches the verbiage used on the Closing Disclosure Alternate Adjustment printed output form. The Adjustment Description is also now populated to the Disclosure Tracking tool snapshot.
CBIZ-13167
An issue was resolved that caused the Property will be checkboxes (field ID 1811) to be set only for the first co-mortgagor when importing a FNMA 3.2 file into Encompass. The FNMA 3.2 file format supports a Property will be value for the whole loan, and not per co-mortgagor. This issue has been resolved and Encompass now applies the Property will be value to all borrower pairs when importing a FNMA 3.2 loan file.
CBIZ-3425
An issue was resolved for VA loans that caused the co-borrower Other income amounts (field IDs 116 and 117) on forms such as the 1003 Page 2 to not be included in the Spouse’s Income (field ID 1008) in box 55 on the VA 26-0286 Loan Summary input form. This issue has been resolved and the co-borrower Other amounts are now included in the calculation for the Spouse’s Income field.
Additionally, a Lock icon has been added to the Spouse’s Income field on the VA 26-0286 Loan Summary input form. When upgrading to Encompass 18.1.0.4, any existing value in the field is retained and is not recalculated. Encompass users need to click the Lock icon if they want to recalculate the amount.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Manually enter an amount in the Spouse’s Income field (field ID 1008) on the VA 26-0286 Loan Summary.
CBIZ-6884
An issue was resolved that cause Seller Obligated Fees to be included in the Borrower FHA Closing Cost amount (field ID 1132) on the Freddie Mac Additional Data input form. The issue has been addressed and the seller obligate fees are no longer included in the Borrower FHA Closing Cost.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Click the Lock icon next to the Borrowers FHA Closing Costs field on the on the Freddie Mac Additional Data form, and enter the correct value manually.
CBIZ-6934
An issue was resolved that caused the LTV field (field ID 353) to display the MIP LTV ratio (field ID MAX23K.X104) instead of the Case LTV ratio (field ID MAX23K.X120). This resulted in inaccurate information being added to the Transmittal Summary and transmitted to DU/LP. When a user clicked the Lock icon to manually edit the LTV (field ID 353), the MIP was then calculated incorrectly and had to be manually adjusted. This issue has been resolved and the LTV (field ID 353) loans now correctly displays the Case LTV ratio.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Manually adjust the LTV in the Transmittal Summary to the Case LTV.
-
Option 1: Manually adjust the MIP amount and term as needed to fit the MIP LTV amounts.
-
Option 2: Create an FHA MI table in the Encompass Settings (Encompass > Settings > Tables and Fees > MI Tables) to address the various scenarios for the MIP for loans to be applied to FHA 203(k) Loans. When an Encompass user clicks the Get MI button, a pop-up Window provides both available MIP scenarios.
-
CBIZ-12019
The following three corrections have been made to the wording used in the Request for Transcript of Tax and Request for Transcript of Tax (Classic) input forms:
-
In the last sentence in section 6b, 30 calendar days has been replaced with 10 business days.
-
In the last sentence in section 6c, 30 calendar days has been replaced with 10 business days.
-
In the last sentence in section 8, 45 days has been replaced with 10 business days.
CBIZ-13229
An issue was resolved that caused the checkbox indicating that the interest rate is subject to change prior to the expiration of the commitment agreement (field ID DISCLOSURE.X477) on the Illinois State Specific Information input form to be selected when disclosing the loan, even though the checkbox was cleared prior to disclosing the loan. This caused the Illinois Commitment Letter to erroneously state that the interest rate was subject to change prior to the expiration of the commitment. This issue was introduced with Encompass version 16.3.1.0. It would occur when the rate was locked, but was due to expire prior to the expiration date of the commitment letter. The issue has been resolved, and the checkbox is no longer automatically selected after having been cleared.
CBIZ-10350
An issue has been resolved that caused Encompass to not recognize the name for 22 counties when they were automatically populated after entering the ZIP Code for an address. The following error message would display:
-
No valid county limit can be found based on the provided county name and number of units information.
The user was required to update the county name manually. Additionally, when the county name was automatically populated or was selected in the Select a City pop-up window, and the loan amount, purchase price, or PMI was then adjusted, the loan file was not updating accordingly. This issue has been resolved. The counties are now populating correctly and the loan amount, purchase price, and PMI are now updating as expected for those counties.
CBIZ-15342
An issue was addressed that caused data entry for the Universal Loan ID (field ID HMDA.X28) to be limited to 14 characters when the 6. Purchased Loan option was selected for the Action Taken (field ID 1393). This issue has been resolved and data entry limit is now set at 45 alphanumeric characters.
CBIZ-15406
An issue occurred on the Correspondent Purchase Advice form where the Number of Payments was calculated incorrectly when the 1st Payment Due from Borrower was in one year while the 1st Payment Due Investor was in the next year. For example, if the 1st Payment Due from Borrower was in December (month 12) and the 1st Payment Due Investor was in January (month 1), the calculated Number of Payments was -11 instead of 1.
This issue has been resolved and the calculation now takes into account payments made in different years.
SEC-12532
In Encompass version 15.1.4.6, the High Cost Mortgage Disclosure form was migrated to the Encompass Docs Solution. (For more information on this migration, visit the Encompass Docs Solution Help site.) At that time this form was only made available to print in loans using 2015 forms (RESPA-TILA Form Version > RESPA-TILA 2015 LE and CD). Starting in Encompass 18.1.0.4, this form is available to print in loans using 2010 forms (RESPA-TILA Form Version > RESPA 2010 GFE and HUD-1) as well.
NDE-9658
An issue was resolved that caused the Escrow (T&I) checkbox (field ID 1550) and the Sync with Prepaid Interest Date checkbox (field ID 2852) on the Transmittal Summary input form to clear after importing an Encompass WebCenter loan via the Encompass Loan Mailbox and then applying a data template in which the two checkboxes were selected. This issue has been resolved and the checkboxes now remain selected after applying the template.
CBIZ-9950
Electronic Document Management (EDM)
An issue was resolved that sporadically caused an “Encompass has stopped working” error message to display when users performed tasks with certain versions of Adobe Acrobat, for example, previewing or printing output forms, generating disclosures, working with PDF file attachments in the eFolder, and uploading attachments. This issue has been resolved and Encompass is now functioning properly when performing tasks that involve Adobe Acrobat.
EDM-18521
An issue was resolved that caused an error message to display when using the Print feature to preview a custom form that has been added to the list of custom forms that are recorded in the Disclosure Tracking tool when printing or previewing forms from the Print menu. An error message would display stating that the file could not be found. The file opened after the error message was closed, but a Disclosure Tracking entry was not created in the tool's Disclosure History section. The issue occurred when all the following conditions were met:
- The following set of options were configured in the Disclosure Tracking Settings (Encompass > Settings > Loan Setup > Disclosure Tracking Settings):
-
In the Select the disclosures that will be recorded in Disclosure Tracking section, the custom form was added to the list of forms.
-
In the Select the events that will trigger recording of disclosures section, all four options were selected for creating a record.
-
In the Copy of disclosures section, the Save copy of disclosures when disclosing from the Print Menu option was selected.
- An Encompass user clicked the Print icon in the loan file, select the custom form added in the first bulleted point in step 1, and then clicked the Preview button on the Print window.
This issue has been resolved and the custom form is now captured in the Disclosure Tracking entry in the Disclosure History section of the tool.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
-
Clear the Save copy of disclosures when disclosing from Print Menu checkbox in the Disclosure Tracking Setting or remove the custom form from the Selected Forms column on the print window before clicking the Preview button.
EDM-18688
An issue was resolved that caused an eSign points are missing error message to display when using the Request button in the eFolder to send a file attachment to a third party (for example, a service provider) for a loan originated on an Encompass Consumer Connect website. The error message would display when the Notify me when borrower does not access by checkbox was selected on the Send window.
This issue has been resolved and the error message no longer displays when using the Send button to send a document to a third party for an Encompass Consumer Connect loan file.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
- Clear the Notify me when borrower does not access by checkbox on the Send Request window.
EDM-18752
An issue was resolved that caused eConsent requests to not be delivered properly for some borrowers for loans originated on an Encompass Consumer Connect website. This issue occurred when there was no email entered in Encompass for the borrower’s Home Email (field ID 1240) and an Encompass user then manually entered the email address on the Send Consent window in the eFolder. When the Encompass user sent the request, the email address was not saved back to the loan file in Encompass. When the borrower tried to open the eConsent request on the Encompass Consumer Connect website, the borrower was not able to access the request and the following message would display:
- Your loan is currently being processed. You will be notified when electronic consent is ready for your review.
This issue has been resolved. When an Encompass user manually enters an email address on the Send Request window, the email address is now saved back to the Encompass loan file. Encompass Consumer Connect borrowers can now access eConsent requests when the borrower email address was entered manually on the Send Request window.
Workaround Information:
The following workaround was provided for this production issue and is no longer required for Encompass 18.1.0.4 and later.
- Populate the borrower email address (field ID 1240) in Encompass before sending the eConsent request.
EDM-18753
An issue was resolved that caused an error message to display when a document request was sent to both co-borrowers for a loan originated from an Encompass Consumer Connect website, but only one of the co-borrowers was being sent a Request for Transcript of Tax (4506-T) or Request for Copy of Tax Return (4506) form. When these requests were sent, the email address was populated for both co-borrowers on the Send Request window. If an Encompass user clicked the Send button without removing the co-borrower who was not associated with the 4506 or 4506-T request, an Esigning points are missing error message would display.
This issue has been resolved. A new, more detailed error message now displays, informing the Encompass user that there are no eSignable documents for one of the borrowers and instructing the Encompass user to clear the checkbox for that borrower before sending the request.
EDM-18764
An issue was resolved that caused an Esigning points are missing error message to display when requests for Request for Transcript of Tax (4506-T) or Request for Copy of Tax Return (4506) were sent to both co-borrowers as part of an eDisclosure package for a loan originated on an Encompass Consumer Connect website. The issue has been resolved. The error message no longer displays, and the 4506 or 4506-T is included in the eDisclosure package.
EDM-18765
Encompass Settings
In previous versions of the Encompass Admin Tools when administrators opened the Reporting Database, pop-up messages like this one below would be presented to the administrator that prompted them to add specific fields to the database for reporting purposes. These pop-up messages were provided for HMDA-related fields, NMLS Mortgage Call Report-related fields, and North Carolina Mortgage Loan Data reports-related fields. Administrators could select Do not ask again to prevent the pop-up message from displaying in future sessions.
The issue that occurred is that once administrators selected this option, they had no way to add these required fields to the Reporting Database in the future. As a result they would need to contact Ellie Mae’s Customer Support team and work with them to add the fields to their database.
To resolve this issue, a new Preferences button is now provided at the bottom of the Reporting Database screen administrators use to add and remove fields from the database. They can now click this button and then select the pop-up messages they want to re-enable. Once they make their selections and click Save, the pop-up messages for the selected options immediately display and the administrator can proceed with adding the fields to the database. When they log into the Reporting Database in the future, these same pop-up messages will be provided again. At that point, if they want to prevent these pop-up messages, they can select Do no ask again or they can return to the Preferences screen and update their preferences again.
CFUN-10664
When managing individual user profiles and settings (in the User Details window in Encompass Settings) administrators can click the View/Edit Rights button to view the user’s assigned persona settings and then select the Modify this user’s rights checkbox to make changes to these settings and grant or revoke access rights. An issue occurred where administrators were not able to grant individual users the right to duplicate loans in this scenario. Administrators could select the Modify this user’s rights checkbox, click the Pipeline tab, and then select the Duplicate Loans option, but they were then unable to select any loan duplication templates which are required to grant this right to the user. This issue has been resolved and administrators can now select the loan duplication templates and successfully grant this right to the user.
Please note, the administrator will only be able to select the loan duplication templates if the user has only one persona assigned to them. If the user has multiple personas assigned to them the administrator can see the list of loan duplication templates, but they will not be able to select any of them. This is by design. To modify the user’s access rights when they have more than one assigned persona, use the Personas setting to modify the access rights within the specific persona or personas.
CFUN-5328
An issue occurred where users who were not assigned with Persona access rights to the Lock Desk Setup setting could still access this setting if they were assigned with any other access rights within the Secondary Setup section of Personas > Company Settings .
This issue has been resolved and the Lock Desk Setup option provided on the Personas > Company Settings tab must be selected before users can access the Secondary Setup > Lock Desk Setup setting.
SEC-10315
The prorated fees listed below have been removed from the options available in the UCD Fees section of the Itemization Fee Management setting in Encompass to prevent users from mapping these fees as UCD fees.
These fees can still be selected as items paid in advance to the seller on the Adjustments and Other Details pop-up window, which can be accessed by clicking the Edit icon for Adjustments and Other Credits on the Closing Disclosure Page 3.
-
BoroughPropertyTax
-
CityPropertyTax
-
CondominiumAssociationDues
-
CondominiumAssociationSpecialAssessment
-
CooperativeAssociationDues
-
CooperativeAssociationSpecialAssessment
-
CountyPropertyTax
-
DistrictPropertyTax
-
EarthquakeInsurance
-
EarthquakeInsurancePremium
-
FloodInsurance
-
FloodInsurancePremium
-
GroundRent
-
HailInsurancePremium
-
HazardInsurance
-
HazardInsurancePremium
-
HomeownersAssociationDues
-
HomeownersAssociationSpecialAssessment
-
HomeownersInsurance
-
HomeownersInsurancePremium
-
InterestOnLoanAssumption
-
MortgageInsurance
-
MortgageInsurancePremium
-
PastDuePropertyTax
-
RentFromSubjectProperty
-
StatePropertyTax
-
TownPropertyTax
-
TownshipPropertyTax
-
Utilities
-
VolcanoInsurance
-
VolcanoInsurancePremium
-
WindAndStormInsurancePremium
-
WindstormInsurance
CBIZ-12972
Administrators use the User Details window in the Organization/Users setting to set up a user’s profile, assign personas, set up their access to loans, and more. An issue occurred with the Comments field in this User Details window where data entered in this field was not wrapping properly. Instead of wrapping to the next line once the data reached the right edge of the field, the data was overflowing past the field by 13 characters and then wrapping to the next line, leaving those 13 characters of data hidden from the field. This issue has been resolved so that all the data entered in the Comments field is now visible in the field.
NICE-6359
Business Rules
By default, users assigned with the Administrator [Local] persona are not granted with access rights to the business rules in Encompass Settings. However, an issue occurred in Encompass 17.3 (and later) where these Local Administrators were able to view and modify the Loan Action Completion and Persona Access to Loan Actions business rules, as well as the Collateral Tracking tool nested within the Business Rules settings. This issue has been resolved and Local Administrators can no longer access any of the Business Rules settings by default.
In addition, users assigned with the Administrator (Local) persona were able to modify business rules even though their persona settings were not configured to grant them edit rights to business rules. By using the Analysis Tools in Encompass Settings, these users could search for a field ID being used in a business rule, click the link to the rule in the search results, modify the rule, and then save their changes. This issue has been resolved. These users can still use the Analysis Tools to search for field IDs and view related business rules, but the editing tools and the Save button in the business rules have been disabled for these users.
Users assigned with the Administrator persona that are not at the top of the user hierarchy are considered Local Administrators. Local Administrators have different access rights than those users assigned with the Administrator persona who are at the top of the user hierarchy. These users are considered Global Administrators and by default they will continue to be able to access, and modify, business rules and the Collateral Tracking tool. For more information about the different types of Administrator Personas, view theview the Persona Access to Encompass Settings and Add-On Products document.
CFUN-11175, CFUN-10302
An issue was resolved that caused incorrect fields from the 2015 Itemization input form to be selected when configuring a Persona Access to Fields business rule (Encompass > Settings > Business Rules > Persona Access to Fields). The incorrect fields were selected when an Encompass user defined the field access by clicking the Find button, selecting the 2015 Itemization input form, and then clicking the Select All button. This issue has been resolved and the correct fields from the 2015 Itemization form are now being added to the business rule after clicking the Select All button.
CBIZ-14117
An issue occurred for some clients when syncing Field Triggers business rules between different instances or environments using the Settings Sync Tool. These clients started with a Field Triggers business rule in one instance that was designed to trigger an action when a custom milestone was completed. However after syncing the rule from this instance to a new instance using the Settings Sync Tool, the name of the custom milestone in the rule was indicated as Unknown Milestone in the new instance instead of the milestone’s actual name that was assigned in the original instance. This issue has been resolved so that the custom milestone’s actual name is indicated in the rule after it has been synced from one instance to another.
CFUN-11056, CFUN-11076, NICE-6489
Reports
An issue occurred when generating reports that included milestone tasks. In the generated reports, the Date Task Added date and the Date Task Completed date were identical. Specifically, both dates reflected the date the task was completed. This issue has been resolved so that the Date Task Added date in the report is the date the task was added to the milestone and the Date Task Completed date in the report is the date when the task was completed.
CFUN-8454, NICE-7047
Encompass SDK
An issue occurred for clients using the Encompass SDK to import a Fannie Mae 3.2 file into an Encompass loan then apply a loan template. Specifically, the SDK program imported a Fannie Mae 3.2 file into a loan and then applied a template to the loan, and upon save, or commit, of the loan the following Exception Error was triggered:
System.NullReferenceException: Object reference not set to an instance of an object...
This issue has been resolved and Fannie Mae 3.2 files can now be imported via the SDK and attached to existing loans in Encompass, and then applying a loan template to the loan does not result in the Exception Error being triggered upon save, or commit, of the loan.
CFUN-10728
Encompass SDK users experienced an issue where running the AuditTrail.GetMostRecentEntries method to retrieve the most recent audit trail entries for a loan resulted in receiving the following server-side Exception Error:
(LoanManager): EllieMae.EMLite.ClientServer.Exceptions.ServerException: Unexpected server error: Input string was not in a correct format. ---> System.FormatException: Input string was not in a correct format…
This issue has been resolved and running the AuditTrail.GetMostRecentEntries SDK method now results in the most recent audit trail entries for the loan being written to the console as expected.
NICE-6654
Additional Fixed Issues
An issue was introduced in Encompass 18.1 (and later) for those clients logging into Encompass using a command line interface (instead of using the Encompass Log In window). After sending the log in parameters to their Encompass instance via the command line, the following Exception Error was triggered when the Encompass Home page started to load and the user was forced to close Encompass:
An unhandled exception occurred: Arithmetic operation resulted in an overflow…
This issue has been resolved and clients can once again log into Encompass 18.1.0.4 via a command line interface.
NICE-7009