Spring 2022 Release Notes

1.   Preface

This is a living document, and its contents may be updated often. Any changes to the contents of this document are listed in the Change Record section. Make sure that you have the latest version for use.

The contents of this document are applicable to all the customers who have installed the latest version of Q2 OriginationSpring'22 release for the first time or have upgraded from an earlier version. You can access the release notes of the previous releases from the Q2 Customer Portalor Q2 Lending Help Center.

1.1 Purpose of this Document

This document provides information on the following for the Spring'22 release:

• Installation Information

• Technical Assistance

• Upgrade Considerations

• System Performance

• New Features and Enhancements

• Fixed Issues

• Known Issues

• New Objects

• Modified Objects

• New REST APIs

  Modified REST APIs

• New Global Methods

• Modified Global Methods

1.2 Intended Audience

The audience of this document includes business users, implementers, and system administrators.

1.3 Prerequisites for Use

This document assumes a basic knowledge of the product concepts, the product release, and the Salesforce platform.

2.   Introduction

These release notes may be updated after the first release. Any changes to the contents of these release notes are listed in the Change Record section.

3.   Installation Information

Contact your Q2 Professional Services team or the Customer Success team for information on the package dependency and installation order of the packages required to install and set up the latest version of Q2 Origination.

4.   Technical Assistance

For all customers and partners of Q2 Software, Inc., our technical support team provides technical assistance. Q2 Software, Inc. customers are served via a dedicated support desk. Contracted customers are provided a sign-on to communicate with Q2 Software, Inc. technical support staff.

5.   Upgrade Considerations

For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.

6.   System Performance

To view the batch jobs performance statistics for Q2 Origination without customizations under test conditions, see the Q2 Performance Benchmarking Guide.

7.   New Features and Enhancements

This section briefly describes the new features and enhancements added in the Spring'22 release of Q2 Origination.

7.1 New Enhanced UI

Feature Description

Q2 Origination UI has been redesigned for an enhanced user experience for back office users. This new UI is now available for all. Please refer to the upgrade guide to understand the steps for an

7.2 Party Deletion (Jira ID: GD-3790)

Feature Description

Earlier whenever a party on an application was deleted, the associated tasks, documents, policy conditions, etc. used to remain on the application. This led to a lot of process and workflow problems.

To address this issue, Q2 Origination is enhanced to support deletion of party and archiving/hiding (on UI) its associated records. As per the changes:

• When a party is deleted on an application, the party record gets inactivated.

• Associated functionalities linked to the inactive party are made inactive/archived.

• Whenever any rule is evaluated and calculations are done on party records, the inactive party is always ignored.

When a user deletes a party on the application, the following records associated with the inactive party are archived.

• Documents: All documents associated with the Account AND Application combination are archived

• Tasks: All tasks associated with the inactive party are archived

• Policy Conditions: All policy conditions associated with the inactive party are archived and no new policy conditions are generated for the inactive party

When a user deletes a party on the application, the following sections associated with the inactive party are not displayed on UI.

• Relationship Dashboard & Party Relationship Details

• Documents (Party lookup)

• Covenants

• Collaterals (Party lookup)

• Financial Spreads

• Party level DTI

• Scorecard

• Tasks

• Policy Conditions

7.3 Batch Job to Clear Execution Criteria Logs (Jira ID: GD-5506)

Feature Description

Execution Criteria result log records are meant for audit purposes and the Banks/FIs clear them on a regular basis. Earlier execution criteria result log records were used to fill up storage space in Salesforce Org as there was no mechanism, other than manual intervention, to delete such records in the system. Also, storage space was a concern for our customers in terms of the cost of space.

To resolve the issue, a new apex class ‘CleanupExecutionCriteriaResultsJob’ has been introduced in Q2 Origination. A batch job can be scheduled in the system using ‘Schedule Apex’ by selecting the Apex class and by defining the execution frequency. This batch deletes the execution criteria result log records based on age of the records.

7.4 Party Relationships within an Application (Jira ID: GD-5771)

Feature Description

In Q2 Origination, a Party object is used to associate an Account with an Application, and Party type describes the relationship of an Account with an Application. Party is also categorized based on the Role. A Party can play single or multiple roles. For Instance, a party can act as a co-borrower and a guarantor in the application.

At the same time, a party can be a Signer or Beneficial Owner to other accounts on the application. To achieve this, we already have a defined Party relationship that links a Party type to a related non-Individual or a related Individual. For instance, a Party (John Smith) can act as a Signer for Acme Bricks. BUT the same Party (John Smith) can also act as a Signer for Acme Constructions.

Earlier Origination system had a 1:1 relationship between a Party and a Related Entity, it was becoming restrictive to cater to such business needs.

As it is a common lending scenario wherein a Child Entity might be a Borrower with Parent Entity as a Co-Borrower and Beneficial Owner. And there might be multiple parties playing a common role towards all the Primary Parties. Hence, Q2 Origination has been enhanced to consider the 'Party-Related Entity' relationship from 1:1 to 1: many.

7.5 Approval with Conditions (JIRA ID: GD-4702)

Feature Description

It is a common industry practice to attach exceptions (policy condition) to an application. At times, even approvals are based on certain underlying conditions. For instance, approval would be granted on the requested loan amount provided the borrower adds collateral or a guarantor to the loan application.

Q2 Origination’s approval feature has been enhanced to support the provision of conditional approval and thereby, handling of exceptions and tasks.

Following is the nature of changes:

• A new button 'Add Conditions' has been added to Approval UI (Application > Approval > Approval Instance > Review Approval > Add Conditions).

• On Manual addition of exceptions (Policy Conditions), the exceptions are displayed on the Approval UI.

• Approval Instance remains in the 'Conditionally Approved' state till the attached exceptions are satisfied.

• Exceptions can also be associated to tasks so that the workflow can be restricted from going forward till all exceptions (of type Approval) are satisfied.

7.6 Manual Addition of Policy Conditions for Party and Collateral (Jira ID: GD-6114)

Feature Description

Earlier while adding a policy condition manually (under Approvals or under Exceptions) for any application in Q2 Origination, the system used to display only the policy condition defined for the Application Object and did not display the policy conditions defined for Party or Application Collateral objects.

Q2 Origination has been enhanced to remove such restrictions so that the user can attach policy conditions on the application that can be context-specific (Application/Party/Application Collateral).

7.7 Auto Spreading (JIRA ID: GD-6114)

Feature Description

Q2 Origination has be enhanced with the following changes as the first step towards Auto Spreading:

• OCR of Financial Statements (Form 1040 and Schedule C in the Phase 1).

• Extract Data from Form 1040 and Schedule C by invoking the ABBY OCR adapter.

• A configuration tool to map the fields from extracted data to financial statement template.

• Create Financial Statement records.

• A workflow is introduced to orchestrate the above one after another

OCR of Financial Statements:

As an end goal, we will be working towards OCR of different types of Financial Statements. In this release, we have started with the following 2 statements :

• 1040 Individual tax form (US Region Only)

• Schedule C - of 1040 (US Region Only)

We are leveraging the ABBYY partnership for OCR and extracting the financial statement data The 1040 Individual tax returns and Schedule C, which is the P&L statement of Individuals are configiured for data extraction.

Extract data from Form 1040 and Schedule C:

The data extracted from 1040 and Schedule C is now stored in the Financial Statements.

Configuration tool to map the extracted data to financial statement template:

A new configuration tool is introduced to map the extracted data to financial template. This configuration tool can be leveraged in the upcoming releases when we add new statements to the OCR functionality. This tool is a 1-1 mapping between the field in the extracted data to the template detail in the Financial Statement Template.

Creation of Financial Statements in Financial Spreads:

Q2 Origination has been enhanced to translate the extracted data into yearly financial statements for that Account in the Financial Spreads. In order to achieve this, the following enhancements have been done:

Seed 1040 + Schedule C Financial Statement Template: This Financial statement template is a pre-configured template and is available as part of the post-install.

• Create Financial Statement records from the extracted data: Income Statement for Individuals are created from data extracted from multiple documents ,for example a 1040 statement + schedule C statement for the Year 2020 creates a single financial statement record for the Year 2020

• A new API is introduced to read the data extracted for an Account+ Statement Year in the Form 1040extracted data + Schedule C extracted data and create a financial statement record for a particular year.

Generate Financial Statement Summary of the extracted data:

Once the financial statements are captured as part of application capture, these values are usually used in scorecard card evaluation to arrive at an overall risk score. In order to facilitate this , a configuration has been provided to move the key financial metrics to relevant party and application fields.

8.   Fixed Issues

For the details of the issues fixed in a release of Q2 Origination, see the Post GA section of that particular release's Release Notes.

9.   Known Issues

There are no known issues in this release.

10.   New Objects

This section briefly describes the objects added in this release.

11.   Modified Objects

This section briefly describes the objects modified in this release.

12.   New REST APIs

There are no REST APIs added in this release.

13.   Modified REST APIs

There are no REST APIs modified in this release.

14.   New Global Methods

This section briefly describes the global methods added in this release.

14.1 Modified Global Methods

There are no global methods modified in this release.

15.   Post Spring'22 Release

Follow this section for the details on the issues fixed in the patches on the Spring'22 release.

15.2 Issues fixed in the February 16, 2024, patch

15.2.1 Communication messages are not loading (Jira ID: PDRFF-2871/GD-8272)

Fixed Version

This issue has been fixed in the following versions:

Q2 Origination: Spring'22 (3.8005.20)

Issue Description

The messages on the loan team communication page are not loading, and the following error is being displayed:

Resolution

This issue is fixed by restricting the tagging to only Standard users in the Loan Team Messages. So, now only the users who have UserType as Standard in the Loan Team Messages can be tagged. Previously, all users within an org were eligible for the tagging.

15.3 Issues fixed in the October 16, 2023, patch

15.3.1 Users are able to edit the messages with restricted permissions (Jira ID: PDRFF-2440/GD-7858)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Spring'22 (3.8005.18)

• CL Originate Skuid Extension: Spring'22 (3.8005.18)

Issue Description

The users with the custom profile are able to edit the created messages despite the restricted permissions.

Resolution

This issue is fixed as the restricted permissions are working correctly and are not allowing the users with the custom profile to edit the created messages.

15.4 Issues fixed in the December 30, 2022 patch

15.4.1 SalesForce error while trying to save a new phone for a contact (Jira ID: GD-7121)

Fixed Version

This issue has been fixed in the following versions:

• Q2 Origination: Spring'22 (3.8005.14)

• CL Originate Skuid Extension: Spring'22 (3.8005.16)

• CL Common: Spring'22 (3.8002.4)

Issue Description

When a single account is added as party to multiple applications, for example parties with party type dealer, broker and that Account/Contact record is subsequently updated, it gives the following error:

Resolution

This issue is fixed.

In the Custom Setting> Org Parameters>Manage(genesis)>Closed Status> (Specify the party type. For example: Dealer, Broker.)

15.5 Issues fixed in the October 12, 2022 patches

15.5.1 Collateral ownership record is getting deleted while editing party (Jira ID: GD-6990/PDRFF-1262/GD-6960)

Issue Description

If more than 20 records are created for collateral ownership, on editing the party/contact for an application, 20 collateral ownership records are saved and the extra records are deleted from the Collateral tab.

Resolution

This issue is fixed. Now the user can create 300 collateral ownership records for a few contracts.

15.5.2 Changing Loan Closing Date resets Days Convention (Jira ID: GD-6984/GD-6969)

Issue Description

On editing the Expected Close Date field of an application, the Days Convention field is getting updated to 365/365. However, the Days Convention field should not change its value.

Resolution

This issue is fixed.

15.6 Issues fixed in the July 15, 2022 patch

15.6.1 Attachments are not showing on the Documents tab after moving from the Messages and Notes tab (Jira ID: GD-6662)

Issue Description

On the Documents tab, on navigating from the Messages and Notes or the Details section, the uploaded attachments are not displayed under the File column.

Resolution

This issue is fixed.

15.7 Issues fixed in the July 1, 2022 patch

15.7.1 Task generation evaluates all task setup records against application causing performance degradation (Jira ID: GD-6676/TO-1885/PDRFF-1087)

Issue Description

Currently in the system, during task generation, each of the applications is evaluated against the configured task generation rules. If there are multiple applications to be evaluated against multiple task generation rules, the system is causing performance degradation.

Resolution

The task evaluation logic is modified so that an application does not need to be evaluated for all the configured task generation rules. The application is to be evaluated against the rules that are configured for the product for which the application is created.

15.8 Issues fixed in the June 21, 2022 patch

15.8.1 Spring – Change version of apex.js and connection.js to latest Salesforce versions (at least 50+) (Jira ID: GD-6661)

Issue Description

Salesforce is retiring API version up to 20 by March 2022 and 21-30 by March 2023.

Resolution

Hence, all the js files that use Ajax toolkit (apex.js and connection.js) should start using the latest versions. The application needs to be upgraded to use the latest API version that is 54.0.

15.9 Issues fixed in the May 30, 2022 patch

15.9.1 Getting attempt to de-reference a null object error on the Application Snapshot page on click of the View button (Jira ID: GD-6569)

Issue Description

After editing the dynamic query to capture the Application Snapshot manually, when the user clicks on the View option to view the snapshot that is captured manually, the system is throwing the following error:

Resolution

This issue is fixed.

16.   Change Record