Important Notes Regarding the Upgrade to 15.02

The following table outlines important notes that need to be considered during an upgrade to release 15.02:

Core/Connector

Functionality

Note

All

CUNA Loan Calculator

The CALCULATOR_APPLICATION_PREMIUM_ADD_TO_LOAN_BALANCE solution parameter has been removed from the Calculator tab on the Solution.Origination System Management page and replaced with the IsChargeInterestOnPremium field available for application screens, views, reports, and set through rules. The upgrade to Lifecycle Management Suite release 15.02 now automatically sets the IsChargeInterestOnPremium field on existing applications that are not disbursed, auto withdrawn, or withdrawn to the value that was defined in the CALCULATOR_APPLICATION_PREMIUM_ADD_TO_LOAN_BALANCE solution parameter prior to the upgrade. Additionally, the CUNA loan calculator logic that sets the MAPRLoan and PREMADDTOLOANBAL tags has been updated to set the tags based on the CalculateMAPR and IsChargeInterestOnPremium fields, respectively.

For institutions using the KeyStone core: The CALCULATOR_APPLICATION_PREMIUM_ADD_TO_LOAN_BALANCE solution parameter was used during the Create Loan process. Since that parameter has been removed, the Create Loan process has been updated to now use the Application.IsDebtProtectionFinanced field instead. When IsDebtProtectionFinanced is true, as set by the system-defined CalculateDebtProtectionFinancedFlag rule, the SINGLE_PREMIUM_DISABILITY and/or SINGLE_PREMIUM_LIFE fields are sent to Keystone during the Create Loan process.

All

Custom Applicant Types

For institutions with custom applicant types: During an upgrade to 15.02, all custom applicant types that were previously configured for an institution are imported into the Lending.ApplicantType table in the database, displayed in the grid that appears in the new Applicant Types page in System Management and are available to assign to an application type and/or account product. The Solution Id’s for all custom applicant types are also automatically updated during the upgrade process to be within the required 2000000 range. Additionally, the TIN Required field is set to true for all applicant types during the upgrade; however, with the exception of the Primary applicant type, the value can be modified in the Applicant Types page after the upgrade. For more information on the Applicant Types functionality, please see the Applicant Types topic in this guide.

All

Exports

In 15.02, data in Export fields using the date/time format string (mm/dd/yyyy hh:mm) is now formatted correctly in the export file. In previous releases of the Lifecycle Management Suite, the time portion of the field would not always display within the export file. Following an upgrade to 15.02, all Exports that use fields with a date/time format string should be checked to ensure that adjustments do not need to be made to accommodate fixed-width files, as date/time fields could now be longer.

All

Is Disbursed Field

In 15.02, the Disbursement process has been enhanced to automatically identify that both the loan and application have been disbursed as well as capture the disbursement date for the overall application. During an upgrade to 15.02, the following occurs within applications that were disbursed prior to the upgrade:

Application Disbursed Date is set to the value of the Disbursed Transaction Date.
Is Loan Disbursed is set to true.

All

Review Indicators

In 15.02, the Review Indicators functionality has been enhanced to automatically classify review indicators as Loan during decisioning. To support this functionality, the following updates were made:

A new field titled Applies To was added at the Review Indicators level to determine whether a review indicator is for a Loan decision.
The existing Review Indicators panel was renamed to Loan Review Indicators and now lists all review indicators related to a Loan decision.

During an upgrade to 15.02, the value of the Applies To field is set to "Loan" for all review indicators that existed prior to the upgrade. After an upgrade to 15.02, any existing review indicators are listed in the Loan Review Indicators panel. If the existing Review Indicators panel appears in an Application screen prior to the upgrade, the label configured for the panel is not updated and continues to display in the screen after the upgrade.

For more information, please see the Enhancements to the Application Experience topic in this guide.

All

Upgrade Changes for Converting Fees to Cross-sells

The 15.02 upgrade removes $0 indirect GAP and MBD cross-sells from applications if they were created during the upgrade from Lifecycle Management Suite release 10 or 15.01 to release 15.02. The 15.02 upgrade utility reviews the upgrade history to determine if the upgrade to 15.02 is occurring on the same day as the upgrade from release 10 or 15.01. If the upgrade is occurring on the same day, $0 indirect GAP and MBD cross-sells are deleted from applications. If the upgrade is occurring more than one day after the upgrade from release 10 or 15.01, $0 indirect GAP and MBD cross-sells are not deleted from applications.

Prior to 15.02, GAP and MBD fee data imported from indirect providers was mapped to cross-sells in the Lifecycle Management Suite.

HMDA

Reporting Changes for 2017 and 2018

In support of the HMDA reporting regulation changes for 2017 and 2018, the IsHOEPA check box has been replaced with the HMDA HOEPA Status system lookup. While the upgrade to release 15.02 automatically updates the IsHOEPA field on screens and views, rules and reports that use the IsHOEPA field must be manually updated to use the HMDA HOEPA Status lookup prior to the 15.02 upgrade.

Additionally, the 15.02 upgrade automatically sets the HOEPA Status field to 1 HOEPA Loan on each application that had IsHOEPA set to true. HOEPA Status is set to 2 Not a HOEPA Loan on each application that had IsHOEPA set to false.

To ensure that the correct data is included in the export to HMDA, it is important to update the Activity Year on the HMDA connector page at the begining of each new calendar year. Failure to update the Activity Year could result in the collection of data that cannot be reported to HMDA per the new year's standards.