Spring 2023 Release Notes

1.   Preface 

This is a living document, and its contents may be updated often. Make sure that you have the latest version for use.

This document provides information about the new and the enhanced features in the Spring'23 release of Q2 Integrations. You can access the release notes of the previous releases from the Q2 Customer Portal.

The contents of this document are applicable to all the customers who have installed the Q2 Integrations Spring'23 version (4.2001) for the first time or have upgraded from an earlier version. 

1.1 Purpose of this Document 

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

• Installation Information
• Upgrade Considerations
• System Performance
• New Features and Enhancements
• Fixed Issues
• Known Issues
• New and Modified Objects
• New and Modified APIs
• Post GA Release
• 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 Integrations. 

4.   Upgrade Considerations 

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

5.   System Performance 

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

6.   New Features and Enhancements 

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

6.1 Enable to use the enhanced XML parser for proper parsing (JIRA ID: INTCL-2003)

Feature Description 

The Q2 Integration framework has been migrated to use an enhanced XML parser that parses all child nodes at every level. 

6.2 Fetch Financial statements via Codat Integration (JIRA ID: INTCL-1975)

Feature Description

Codat is an aggregator that integrates with many platforms such as accounting, banking, and commercial.

These platforms maintain the financial statements of many SMB companies (FI's borrowers). By implementing the Q2 Codat adaptors, Financial Institutions (FIs) are able to auto-populate the SMB borrower's financial statements (Balance Sheets and Income Statements) into its pre-existing financial spread template. Auto-populating the financial template became possible due to the Normalized financial statements from Codat. This integration makes the loan application process faster by eliminating the need for a loan officer to fill the financial spread manually.

6.3 Direct Integration Failover (Consumer Credit)  (JIRA ID: INTCL-2054)

Feature Description

Problem: Currently, if a credit bureau's server is down, the loan application can't be processed due to the unavailability of a credit report.

Solution: In Integration failover mechanism is built (using Orchestrator) which auto switches the connection from one credit bureau to the next set credit bureau (per the defined execution priority order) if the previous bureau connection fails. This prevents the loan application from getting stuck due to server issues or timeout issues with the set bureau.

6.4 Use Existing Credit Pull (Consumer Credit + Commercial Credit) (JIRA ID: INTCL-2056, INTCL-2057)

Feature Description

This development provides FIs the flexibility (option) to reuse the existing credit pull for a party/Individual borrower/SMB borrower, if the existing pull happened within a set duration, and was done from the same credit bureau. This is useful in saving the cost of FI that may be incurred in pulling the same credit again which was already pulled by it. This also prevents the applicant's credit score from taking a hit due to multiple hard inquiries.

6.5 MeridianLink SmartAPI Integration Frozen File Support (JIRA ID: INTCL-2010, INTCL-2025)

Feature Description

Problem: Meridianlink has a duplicate detection feature, that returns an "on-file" credit report when ordered for a principal whose file has been ordered within a specified period. This function prevents a new report from being ordered from the bureau when within the time limit mentioned previously. In cases where the bureau file provides a frozen file response, this is problematic because Meridianlink continues to provide the frozen file response even after the credit file has been unfrozen by the consumer.

Solution:

• Meridianlink's 'Upgrade' request function is implemented to override the duplicate detection and force a credit file order from the bureau. FI users will now be able to initiate an upgrade credit report order and can re-order an unfrozen credit report for a previously returned frozen report.

• Credit freeze will now be identified, based on the normalized parameter <ResultStatusType> which is an ML field, which displays the normalized text "NoFileReturnedCreditFreeze" in case of credit freeze for any of the three bureaus.

6.6 Meridianlink SmartAPI Too Many Infile Error Recovery (JIRA ID: INTCL-2011)

Feature Description

Problem: If a user continues to submit a request that is missing required data, Meridianlink sends a "Too many submissions on the same borrower and bureau" error message, which prevents a credit pull from being initiated again for that borrower. 

Solution: If the error message "Too many submissions on the same borrower and bureau" is received, then the system allows the user to send a new 'upgrade' request. 

6.7 Support Path Parameters from Integration Framework (JIRA ID: INTCL-1855)

Feature Description

Problem: Currently by using isUrlParameter, it is possible to set query parameters in the URL from the configuration itself, but the users don't have any provision to set the path parameters in the URL from the framework, need to write code to do so. 

Solution: Introduced a new boolean config option "isPathParameter" in request mapping, if set to true, the field is replaced with its value in the URL based on the key (externalField) mentioned in the request mapping.

6.8 Map insurance company address (JIRA ID: INTCL-2078, INTCL-2087)

Feature Description

Problem: It is not a good business practice not to have a full insurance company address that is associated with a collateral. 

Solution: Include the full company address that is associated with a collateral, so it is easier to track in case of a default.

6.9 Remove first payment date and maturity date for a single payment frequency (JIRA ID: INTCL-1918)

Feature description

Problem: For any single payment frequency, maturity date, and first payment date are useless, there is only one single payment that will be made, thus those fields don't make sense to have.

Solution: Remove those fields from the UI. 

6.10 Add Periodic interest rate change cap to the floating interest user interface (JIRA ID: INTCL-2052)

Feature description

Problem: For any floating loan, this field is critical for users to know what the min/max interest rate change the rate will exhibit, thus, adding it to the UI is necessary rather than entering it in runtime.

Solution: Add a new field in the interest rate UI so users don't have to enter it in runtime.

6.11 Doc Library Upgrade (JIRA ID: INTCL-2072)

Feature description

Problem: Document Library upgrade is critical to be up to date, so the financial institutions have the latest compliance documents.

Solution: Upgrade to the latest doc lib version.

6.12 Map NAICS code description (JIRA ID: INTCL-2037)

Feature description

Problem: Some FIs prefer to have the industry NAICS code description in the general information in runtime, it helps in data collection for the industry their clients are in.

Solution: Map the NAICS code description. 

6.13 Map Driver License information (JIRA ID: INTCL-2088)

Feature description

Problem: Some FIs prefer to have some individual entity's driver's license information collected and printed in their closing documents, we did not have this mapping.

Solution: Map driver's license information.

6.14 Payee Name reference to the Financial Institution when Origination Fee is paid to Lender (JIRA ID: INTCL-2036)

Feature description

Problem: Fee payee's name is blank on the document when the fee is paid to the lender.

Solution: Fee payee name will derive from Financial Institution information custom setting when Fee is 'Paid to lender'.

7.   Fixed Issues 

This section briefly describes the issues fixed in the Spring'23 release of Q2 Integrations.

8.   Known Issues 

This section briefly describes known issues in the Spring'23 release of Q2 Integrations.

9.   New and Modified Objects 

This section briefly describes the new or modified objects in the Spring'23 release of Q2 Integrations.

9.1 New Objects

The following table describes the objects added in the Spring'23 release of Q2 Integrations:

9.2 Modified Objects

The following table describes the objects modified in the Spring'23 release of Q2 Integrations:

10.   New and Modified APIs 

This section briefly describes the new and modified APIs in the Spring'23 release of Q2 Integrations.

10.1 New APIs

The following table describes the APIs added in the Spring'23 release of Q2 Integrations:

10.2 Modified APIs

There are no APIs modified in the Spring'23 release of Q2 Integrations.

11.   Global Methods 

There are no global methods added or modified in this release.

12.   Post GA Release

Follow the latest section for the details on the issues fixed in the patches on the Spring'23 release of Q2 Integrations.

13.   Change Record