Fixed Issues for Encompass - 25.1 Major Release
This section describes the issues that have been fixed in this release.
Why we made these updates: The following issues were fixed to improve usability and to help ensure the Encompass web interface and the Web Input Form Builder 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 User Experience
When using a custom panel on the Loan Summary bar, an issue occurred where the Loan Summary bar was retaining the loan team member information from the previous loan file viewed before the current file. For example, for a loan where the file starter had not been assigned to the loan yet, the Loan Summary bar displayed the name of the file starter from the previously viewed loan (as shown in the example below). This issue has been resolved and now the Loan Summary header indicates the correct loan team member currently assigned to the loan even when custom panels are being used with the Loan Summary bar.
ENCW-112282
An issue occurred for users utilizing a custom Loan Left Navigation menu where the Milestone Timeline was not displaying correctly. After navigating to the Correspondent Loan Status tool, and then selecting the Milestone Timeline icon (clock), the milestone timeline would display correctly for a moment, but then it would disappear. This issue has been resolved and now timeline remains displayed as expected.
ENCW-115481
Updates to Forms, Tools, and Calculations
An issue occurred where users manually typed a date in the date field on a verification input form (for example, the Date field (DD0198) on the Verification of Deposit (VOD) input form), but when they navigated to a different field the day in the date would change to three days earlier. For example, if 05/23/2024 was typed in the field, it would change to 05/20/2024. This issue has been fixed.
ENCW-108655
An issue was discovered where the Conditions page would sometimes not load a list of conditions when viewed by a user. This issue occurred when the Encompass instance had a large amount of persona access rights configured in the Encompass desktop interface. This issue has been fixed, and now the list of conditions loads as expected.
An issue was discovered where the "Cleared" checkbox on a condition incorrectly indicated that it was cleared by an Encompass user when the condition was actually cleared as a result of a workflow rule. This issue occurred when a condition status was set to Cleared by a workflow rule with the Update Enhanced Conditions Tracking Status resulting action. This issue has been fixed, and now the "Cleared" checkbox accurately indicates that the condition was cleared by "Automation" when the condition is cleared by a workflow rule with the Update Enhanced Conditions Tracking Status resulting action.
An issue was discovered where the Fee Description dropdown options were missing from the Calculate Other Housing Expenses window. When the user navigated to the Application View > Loan Information form and selected the Edit button next to the Other field in the Proposed Monthly Payment for Property section, the pop-up window only enabled users to manually enter a fee description. This issue has been fixed, and now the fee description fields enable users to select a fee description from a dropdown list.
An issue was discovered where users were unable to link a liability to a mortgage for both borrowers when the liability was only assigned to one borrower. When this issue occurred, the user received the following error:
Please review - selected liability is not associated with the current owner of the property.
After receiving this error and saving the loan, the VOM is for field would be blank. This issue has been fixed, and now users are able to link a liability for one borrower to a mortgage for both borrowers.
An issue was discovered where the Go To Field search would display field locations for forms that the user didn't have access to. This issue has been fixed, and now the Go To Field search only displays results for field locations that the user has access to.
An issue was discovered where users were unable to filter the workflow task templates list using a lowercase search term. This issue typically occurred when the search term returned results with a mixture of upper- and lower-case matches. This issue has been fixed, and now case sensitivity doesn't affect the search function.
An issue was discovered where task workspace content associated with a subtask would sometimes fail to load. This issue has been fixed, and now workspace content displays on subtasks as expected.
An issue was discovered where the advanced conditions field would sometimes be cleared when validating multiple advanced conditions fields. This issue has been fixed, and now users can validate multiple advanced conditions fields in succession without the field contents being cleared.
An issue occurred where the Commitment Type (field ID 4187) and Delivery Type (field ID 3965) values on the Lock Request Form were removed when a correspondent loan was locked with Auto-Lock enabled. This issue has been resolved, and the two values are no longer removed from the Lock Request Form.
After initially creating and submitting a new rate lock request (i.e., the Request Type (3841) on the Lock Request tool is set to New Lock) with price and rate adjustment values entered in the Total Rate Adjustment (2099), Total Price Adjustment (2142), Net Rate Expected (2100), and New Price Expected (2143) fields, and then getting that lock confirmed, an issue occurred when you navigated back to the Lock Request tool and began creating a new rate lock request for the loan. The price and rate values from the previous rate lock request were not cleared from fields 2099, 2142, 2100, or 2143. This issue has been resolved and when New Lock is selected for the Request Type, any values from the previous lock request are cleared from these fields.
An issue was discovered where Workflow Tasks that included a two-pane workspace template would sometimes not load properly. This issue occurred when the content for both workspace template panes was a document. This has been fixed, and now workspaces with a two-pane content layout load properly when both panes contain a document.
In previous versions of Encompass, when a user was accessing the business contacts by clicking the Rolodex icon on an input form so they could select the contact to add to the associated field, the Business Contacts pop-up window displayed as expected, but an issue occurred where the list of contacts did not display in the window. This prevented users from being able to select a business contact to add to the form field. This issue has been resolved and the list of business contacts now displays as expected.
ENCW-108881
When working with custom categories in the File Contacts tool, once you select a custom category group from the Category dropdown list, the contact details for the selected category group are now displayed in the applicable fields as expected. In previous versions of Encompass, once you selected custom category for the file contact, the details for the custom category (such as Company Name, Address, City, etc.) were not displayed on the File Contacts tool.
Custom Category is Selected from Category Dropdown List:
Company Name for Selected Custom Category is Displayed in Applicable Field in File Contacts
Once the selected custom category is saved, the name of the custom category is updated accordingly:
ENCW-118013, ENCW-119185
An issue occurred with the field search feature and the FRE Condominium Project Identifier field (CASASRN.X221). If a user who was not an administrator (based on their assigned persona) entered CASASRN.X221 into the field search bar, the search results returned: No items found even though the user had access to the Project Review tool where the field is located. When users who were administrators searched for the field, the search results returned the correct results, indicating that the field was located on Project Review tool. This issue has been resolved and now all users who have access to the Project Review tool receive the correct results when searching for field CASASRN.X221 in a loan.
ENCW-117143
An issue occurred with the field search feature and the Manner in Which Title is Held field (33). If a user entered 33 into the field search bar, the search results returned: Warning: Field ID is hidden even though the user had access to the Borrower Information - Vesting form where the field is located. This issue has been resolved and now users who have access to the Borrower Information - Vesting form receive the correct results when searching for field 33 in a loan.
In previous versions of Encompass, an error was returned when users attempted to create a new opportunity. Specifically, when the user navigated to the App Launcher > Prospects page, and then successfully created a new lead, an error was returned when the user started to then create a new opportunity, provide the required information, and then select Save to save and create the new opportunity. The error prevented the new opportunity from being created. This issue has been resolved, and now new opportunities can be successfully created even when the lead is created first.
An issue was discovered where searching for workflow rules by a column header only returned exact matches, resulting in partial matches not being displayed. For example, if you searched for Create Task in the Results column, you would only receive results for workflow rules where the resulting action was Create Task but would not see workflow rules where the resulting action was Create Tasks. This issue has been fixed, and now search results will include partial matches, ensuring that users can find relevant workflow rules.
An issue was discovered where the Tracking Owners option in the Encompass web interface did not always match the settings defined in the Enhanced Conditions settings in the Encompass desktop interface. This issue has been fixed, and now the View Tracking Owners option reflects the settings configuration defined in the Encompass desktop interface. For information on configuring condition types, click here.
An issue was discovered where the users were sometimes not able to select any templates from the "Select Request for Transcript of Tax Template" window. When a user removed a tax template and then added a new one in the Encompass desktop interface, the user was unable to select any templates when using the Encompass web interface. This issue has been fixed, and now users can select a Request for Transcript of Tax Template in the Encompass web interface as expected.
An issue was discovered where changes to the years requested for additional tax requests would sometimes update the first tax request. When an initial tax request was for exactly one year of tax transcripts and subsequent record(s) had a request for exactly three years of tax transcripts, any changes to the years requested on the subsequent record would update the initial request instead. This issue has been fixed, and changes to individual tax transcript requests are updated individually.
An issue was discovered where users were unable to delete a requested year from the Request for Transcript of Tax. When a user removed the dates from the Year or period requested field, the value was retained. This issue has been fixed, and now users can delete a requested year from the Request for Transcript of Tax form.
An issue was discovered where disclosures processed by a workflow rule with the Send Disclosures resulting action would populate the Received By field with the user name surrounded by additional automation text. For example: <Automation> User Name (<automation>). This issue has been fixed, and now only the user name displays in this field.
An issue was discovered where users were able to enter comments longer than 80 characters in the Underwriter Comments section of the Transmittal Summary. This issue has been fixed, and now the Underwriter Comment fields are restricted to 80 characters to match the Encompass desktop interface.
Updates to Encompass Document Management (EDM)/eFolder
In instances where two or more disclosure packages are being redisclosed due to a changed circumstance or other trigger, an issue occurred where all of the disclosure packages that should have been redisclosed were not being sent. This issue has been addressed and now all the intended disclosure packages are included in the redisclosure.
An issue with the way role access is indicated on the eFolder occurred in previous versions of Encompass. When a document folder was added to a loan in the Encompass web interface, and then the role access to the document was modified later in the Encompass desktop interface to remove roles from the Access list, the list of roles in the Encompass web interface indicating who had access to the document folder included commas in place of the removed role in the Role Access column. This issue has been resolved and now these extra commas are no longer displayed.
DOCP-68866
Business rules (for example, Persona Access to Fields business rules) designed to hide or display the Plan Code field in the eFolder based on the persona or other conditions are now being enforced correctly. Previously, the rules were not being enforced and the button was displaying for all users regardless of the business rule.
DOCP-66527
ICE PPE
An issue occurred where not all validation messages were displayed, when applicable, on the Search page in the Encompass web interface. This issue has been resolved and validation messages are now displayed when appropriate.
| Next Section: Change Log |
|
|
|
Previous Section: Web Input Form Builder |

