Spring 2022 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.

The contents of this document are applicable to all the customers who have installed the Q2 IntegrationsSpring 2022 version (3.8000) 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 Portal.

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.

1.1 Purpose of this document

This document provides information on the following for the Spring 2022 release:

• Installation information

• Upgrade considerations

• System performance

• New features and enhancements

• Fixed issues

• Known issues

• New and modified objects

• New and modified REST APIs

• New and 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.

1.4 List of Abbreviations

2.   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.

3.   Upgrade considerations

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

4.   System performance

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

5.   New features and enhancements

This section briefly describes the new features and enhancements added in this release.

5.1 Transunion Consumer Credit (Jira IDs: INTCL-1000, INTCL-1540)

Feature Description

The Transunion Consumer Credit Report is a compilation of data on an individual that is helpful in making decisions in many types of consumer transactions. The Credit Report contains various data about the consumer, including indicative information (name, addresses, date of birth, and Social Security number), employment information, and the consumer’s credit history. This information is obtained from credit grantors, public records, collection agencies, and employers.

The following are the available two versions:

• Standard Credit Report

• Enriched Credit Report

This feature allows the user to check creditworthiness of a business by allowing the user to make a request, receive response, store the responses in the database, and see the information sent back from Transunion Consumer Credit on the UI.

The user has the option to view the pdf report for the credit details. This feature also allows the user to check on any errors which occurs and take appropriate actions on them.

5.2 Experian Consumer Credit (Jira ID: INTCL-1293)

Feature Description

Experian's credit profile report gives accurate, current, and complete information to perform Credit Profile checks, Automotive Credit checks, Health Care Credit checks, Employment Insight credit checks, Telecom-Electric-Cable (TEC) Credit checks and Connect Check Credit Checks.

Q2 is integrating for consumer credit check by Experian for the following serving:

Credit Profile Credit Check: The credit profile report is a composite history of a consumer's credit and identification information. It is the most comprehensive credit decision-making tool used in the industry today, providing timely and in-depth credit information that allows faster, more accurate, and cost-effective decisions.

The Credit profile report is a composite history of a consumers’ credit and identification information. It is the most comprehensive credit decision-making tool used in the industry today, providing timely and in-depth credit information that allows faster, more accurate, and cost-effective decisions.

This feature allows the user to get credit profile of a business by allowing the user to make a request, receive response, store the responses in the database, and see the information sent back from Experian Consumer Credit on the UI. This feature also allows the user to check on any errors which occurs and take appropriate actions on them.

5.3 ABBYY Integrations

5.3.1 ABBYY OCR Integration for Schedule C of Form 1040 (Individual Tax Return) (Jira ID: INTCL-1499)

Feature Description

ABBYY FlexiCapture Cloud is a cloud-based solution on ABBYY FlexiCapture Distributed that is hosted in the Microsoft Azure cloud environment. ABBYY FlexiCapture Cloud is a data capture service that uses ABBYY Content IQ technology to classify documents and extract data for further processing in document management systems.

This epic provides OCR capability for Tax Form 1040 Schedule C. The Schedule C is a place to report the revenue from business, as well as all the types of expenses incurred to run the business. The business income minus the business expenses is a net profit (or loss). This is reported as income on Form 1040.

This feature allows the users to upload documents for OCR, view the status of the uploaded documents on the UI and download the results file. The users can also see any errors and take appropriate action on them.

5.3.2 ABBYY OCR Verification UI (Jira ID: INTCL-1331)

Feature Description

When the data is OCRed in ABBYY, there could be errors in the document (such as special characters in numeric fields), or certain characters might need confirmation. You can now correct the data for the OCRed document using the verification screen. The corrected data is then downloaded in the result file and stored in the database.

This feature allows the users to view the data OCRed by ABBYY OCR and make corrections and save the corrected data.

5.3.3 Refactoring of RATA Geocoding integration from SOAP to REST API (Jira ID: INTCL-1330)

Feature Description

Geocoding is the process of converting addresses such as a street address into geographic coordinates (latitude and longitude), which is used to place markers on a map, or position the map. The geocoding allows lenders to determine if a loan is in a low to moderate-income tract, which can enable originators to ask for higher premium pricing when selling their loans on the secondary market.

This feature handles the refactoring of RATA Geocoding integration from SOAP to REST API.

5.4 UI Redesign and UI Enhancements

5.4.1 UI Redesign (Jira IDs: INTCL-1544, INTCL-1332, INTCL-1292)

Feature Description

This handles the UI redesign of the following integrations:

• Meridian Link Consumer Credit

• DocuSign

5.4.2 UCC Search Enhancement (Jira ID: INTCL-1500)

Feature Description

UCC (Uniform Commercial Code) is a collection of standardized laws on the contracting and trade of goods that has been adopted by the majority of states in the U.S., one of which governs the assignment and management of liens on collateral pledged to loans. When a financial institution originates a commercial loan, the financial institution must submit a UCC-1 financing statement to give notice that it has or may have an interest in the personal property of a debtor. Since the many commercial loans are secured, providing financial institutions with the ability to submit UCC Filings is an important component of the commercial loan origination process.

This new enhancement gives the user the ability to do UCC search by ‘Customer Nick Name’ and any address apart from customer’s primary address. To accomplish this after selecting the party the system allows the user to enter ‘Customer Nick Name’ if they want to search by customer nick name instead of company name.

5.4.3 Socure ID+ Enhancement - Decision Module (Jira ID: INTCL-1462)

Feature Description

Socure ID+ provides Identity (IDV) and Document Verification (DV) services through various modules (such as Fraud, KYC, Email risk, Address risk, Phone risk, Global watchlist, Alert list, Social, and Document Verification) using machine learning algorithms.

This feature is enhanced by adding a Decision module based on user requirement along with the above modules.

The Decision module from Socure ID + returns a simple interpretable recommendation for a transaction based on underlying logic that defines intermediary outcomes when certain criteria is met.

5.4.4 LexisNexis Business InstantID - KYC UI Enhancement (Jira ID: INTCL-1542)

Feature Description

Currently the system allows to do a KYB for the business along with doing the KYC for the individuals associated to the application. Which individuals can be sent for KYC along with the business are determined by the Micro-workflow using API configuration.

This feature is enhanced to allow users to add a section for the details that displays the information about the linkage of the authorized respective to the business.

5.5 Framework Enhancements (Jira IDs: INTCL-1461, INTCL-1371, INTCL-1367, INTCL-1365)

5.5.1 Support for XML request generation

Feature Description

The Integration Framework introduced the Request Templatization wherein the request payload can be generated using the request mapping file directly without the need to write Adapters for the same. This was only supported for JSON at the time.

As a part of this release, the framework is enhanced to support for XML payload generation as well using the same set of configurations. Attributes for XML are also supported with some extended configurations to be done in request mapping. Based on the Content-Type defined in the API Configuration, the template generator either generate the XML or JSON payload.

• JSON -> application/json

• XML -> application/xml

The following fields that are introduced within the Request Mapping:

• useRequestGenerator → This boolean flag in the Request Mapping enables the Framework to pregenerate request body based on the request mapping provided.

• delimiter → This fields can take the delimiting character from the hierarchical path of the request,if not provided. The default value is $$.

• isMandatory → This boolean flag at each field level within a request map is used to perform mandatory checks within the framework itself and throw error if not returned rather than performing it in adapters

• objectAlias at Fields Level → This overrides the object alias at the object level to take precedence and form the JSON path structure.

• A new JSON Array is introduced in the Request Mapping “XMLAttributes” to define the attributes/namespaces for the XML Nodes.

  The following is the format to be defined for XMLAttributes:

  

5.5.2 Enhance integration response processor

Feature Description

Limitations

• Existing response mapping supports mapping the values returning from external APIs to Q2 records only, as they use Integration Framework Mappers to map one static value to another static value.

• Performing of operations such as Logical, Arithmetic, and String manipulation on the response mapping is not present in the existing implementation of response mapping processors.

• Currently, wherever some operations need to be performed on returned values, it can be performed by writing additional response processor code in individual adapters.

• Any change in mappings that cannot be handled with response mappings is required to have a new build.

Improvements: Added support to perform arithmetical and logical operations on the returned values before updating or inserting records.

Advantages

• Reduces boilerplate code in adapters to perform covered operations on API returned values.

• No new builds are required if mappings change in an adapter and if those changes can be handled through enhanced response mappings.

• Integration Framework Mapper remains relevant as it can still be used on the result of operations.

• Improves reusability with request processor.

5.5.3 Response Body Templatization

Feature Description

Framework response mapping supports null check and support for constant or default values and supports for different delimiters.

Null check: Any field marked as “isMandatory” in response mapping needs to be present in the third-party response and without which DB operations are not executed, it returns the following generic exception:

“The fields marked as mandatory in response are missing”.

Implementation: A new keyword is introduced in response mapping at a field level.

{
"externalField": "applicationNumber",
"fieldAPI": "Name",
"isMandatory": true
},

Support for constant values: A default value is defined for a given field in the mapping if its value is not present or missing or if it expects some static value. This is applicable for both Request & Response Mapping.

Implementation: A new keyword “defaultValue” is introduced in the request or response mapping at a field level to achieve this.

Request Mapping:

Response Mapping:

Support for Delimiters: Currently, in response mapping, the dot (.) separator is used to traverse the child field in the given response hierarchy. Only dot delimiter is supported currently, unlike in the request where you can use a delimiter of your choice.

Implementation: A new keyword delimiter is added in response mapping so that the user can use any delimiter for relationship mapping.

Response Mapping:

5.5.4 Nested Array Feature

Feature Description

Current Challenge: To construct an N-D array based on records retrieved from multiple queries, it is difficult to track the updates in the framework.

Solutions: Added two new fields in request mapping at filter level and those are used to define in field level to get parent and child reference, and the referencesToObjectAlias field must be objectAlias of parent mapping.

New fields:

• childReferenceFieldAlias; This field is defined in parent mapping to map with child records, that can have multiple values by comma separation like childReferenceFieldAlias ": "contactId, accountId".

• parentReferenceFieldAlias; This field is used to map with parent records in child mapping.

6.   Fixed issues

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

6.1 Integrations Logs are not captured due to multiple requests (Jira ID: INTCL-1443 / PDRFF-681)

Issue Description

While performing Book To Core action, the integrations logs are not capturing with the following system exception:

“Exception Type: System.DmlException.”

Resolution

This issue is fixed now, and the logs that exceed 131070 characters are stored in a file.

6.2 Error while adding party types to an application (Jira ID: INTCL-1235, INTCL-1239 / PDRFF-473)

Issue Description

While performing Book To Core action, if the added parties are other than Borrower, Co-Borrower, Payee, Agent, Guarantor, and Grantor then the system is throwing Party Type is missing or invalid message.

Resolution

The code is fixed to address this issue. All Party Types are now supported from Create Account Coresmen Adapter as Secondary Relationships.

An application can now have two parties; a primary party as Borrower, and a secondary party as one of the following:

• Guarantor

• Signer

• Cosigner

• Beneficial owner

• Beneficial Owner Certifier

• Beneficial Owner Manager

• Builder

• Dealer

• Direct Contact

• Employee

• Entity

• Ground Lease Lessor

• Lessee

• Lessor

• Loan Officer

• Notary

• Related Entity

• Reviewer

• Subsidiary

• Vendor

6.3 Call to Create Account API is failing (Jira ID: INTCL-1440 / PDRFF-670)

Issue Description

While creating an account, the call to Create Account API is failing with the following error:

“Record/Action mismatch in SECCUST.”

Resolution

This issue is fixed by the correct mapping of the following party types in the core:

• Borrower

• Cosigner

• Guarantor

• Power of Attorney

• Signer

• Trustee

• Co-Borrower

• Grantor

6.4 Socure ID+ Enhancement to add Decision Module (Jira ID: INTCL-1438)

Issue Description

The Decision module displays a simple interpretable recommendation section for a transaction based on underlying logic that defines intermediary outcomes when certain criteria are met. The system must display the details that are provided from Socure ID+ decision module.

Resolution

To configure this change, perform the following steps:

1. Go to the Integrations API Configurations.

2. Click Socure KYC-Fraud API Config.

3. Go to Request and Response Mapping section, and then click Edit.

4. Add the following code:
   

   Copy

   {
   "externalField": "DecisionModuleRequired",
   "value": "Yes"
   }

5. Click Save.

6.5 Refactoring of RATA Geocoding Integration from SOAP to REST API (Jira ID: INTCL-1330)

Enhancement Description

Geocoding is the process of converting addresses such as a street address into geographic coordinates such as latitude and longitude, which is used to place markers on a map, or position the map. In this patch the RATA Geocoding integration code is refactored from SOAP (XML code) to REST (JSON code) API.

Resolution

To configure this change, perform the following steps:

1. Activate Geocoding Integration Provider

   1. Log in to your Salesforce account and go to Integration Configuration Setup > Activate/Deactivate Provider.

   2. Select Active checkbox of Geocoding as the Provider Name, and then click Save.

      

      Note:

      If the Active checkbox is selected, please clear and reselect the check box again.

2. Create Named Credential Instance

   1. Log in to your Salesforce account and go to Q2 Integration > Setup.

   2. In the Quick Find box, search for Named Credentials, and then click it.

   3. Create two new credentials with the following details:

      

3. Configure the Created Named Credentials

   1. Configure the Authentication Named Credential:

      1. Log in to your Salesforce account and go to Q2 Integration > Integration API Configuration. Create or update Integration Configurations with the following created Authentication Named Credential detail:

         

         Note:

         The Authentication Named Credentials is the named credentials which has the token URL detail.

   2. Configure the API Named Credential:

      1. Log in to your Salesforce account and go to Q2 Integration > Integration API Configuration.

      2. Create or update Integration Configurations with the following created API Named Credential detail:

         

   3. Configure Connection Configurations

      1. Log in to your Salesforce account and go to Q2 Integration > Connection Configuration.

      2. Create or update Connection Configurations with the following details:

         

6.6 Call to the Create Collateral API is failing (Jira ID: INTCL-1393)

Issue Description

While performing Book To Core action, if the added parties are other than Borrower, Co-Borrower, Payee, Agent, Guarantor, and Grantor Party types then the system is throwing Party Type is missing or invalid message.

Resolution

The code is fixed to address the issue. All Party Types are now supported from Create Account Coresmen Adapter as Secondary Relationships.

An application can now have two parties: a primary party, Borrower, and a secondary party as one of the following:

• Guarantor

• Signer

• Cosigner

• Beneficial owner

• Beneficial Owner Certifier

• Beneficial Owner Manager

6.7 Request mapping information is missing (Jira ID: INTCL-1323 / PDRFF-468)

Issue Description

While performing Book To Core action for Create Collaterals Request API, few collateral does not have the request mapping in Integration API configuration.

Need to have request mapping information for the following Collateral Types:

• Inventory,

• All Assets,

• Accounts,

• Equipment,

• Household Goods (purchase money),

• General Intangibles

Resolution

The code is fixed to address the issue.

7.   Known issues

This section describes the known issues in this release of Q2 Integrations.

7.1 [RATA Geocoding]: Location Demographic Information object count is increasing by three instead of one. (Jira ID: INTCL-1583)

Issue Description

In a fresh org, while searching a geocode, a Location Demography Information object count is increasing by three instead of one.

7.2 The system displays Unresponsive page message when performing Book To Core functionality with multiple parties and collaterals. (Jira ID: INTCL-1236)

Issue Description

While performing Book To Core action with multiple parties and collaterals, the system displays the "page is unresponsive" with two buttons namely Wait and Close.

7.3 High integration performance response time is observed for Experian Premier Profile and PDF generation. (Jira ID: INTCL-1617)

Issue Description

While executing the Experian Premier Profile and Premier Profile PDF integrations, the systems response time is 90% higher than the earlier release.

7.4 Integration]: system is displaying “SObject row was retrieved via SOQL without querying the requested field” error. (Jira ID: INTCl-1186)

Issue Description

While executing integrations such as LaserPro, KYC, and FICO, a system is troughing a random error as “SObject row was retrieved via SOQL without querying the requested field.”

8.   New and modified objects

This section briefly describes the new and modified objects in the Spring’22 release of Q2 Integrations.

8.1 New objects

This section describes the object that is added in the Spring’22 release of Q2 Integrations.

8.2 Modified objects

This section describes the objects that are modified in the Spring’22 release of Q2 Integrations.

9.   New and modified REST APIs

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

9.1 New APIs

This section briefly describes the API that is added in the Spring’22 release of Q2 Integrations.

9.2 Modified APIs

There are no APIs modified in the Spring’22 release of Q2 Integrations.

10.   New and modified global methods

This section briefly describes the global method that is added in the Spring’22 release of Q2 Integrations.

11.   Post GA release

Follow this section for the details on the issues fixed in the patches on the Spring 2022 release of Q2 Integration.

12.   Change record