August 2024 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 Integrations August 2024 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 Portal or from the Q2 Lending Help Center.
1.1 Purpose of this document
This document provides information on the following for the August 2024 release:
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. 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. New features and enhancements
This section briefly describes the new features and enhancements added in this release.
For a detailed description of the new features and enhancements, see the following guides published over the Q2 Customer Portal:
-
Q2 Integrations User Guide
-
Q2 Integrations Administration Guide
4.1 Equifax Apply - APAC (Jira ID: INTCL- 2224)
Feature Description
Equifax Apply is an individual consumer credit origination product offering that enables access seekers to receive credit reporting data on credit applicants. Equifax Apply contains the latest scores from Equifax, which are designed to allow subscribers to obtain bureau based risk profiles (scores) on new credit applicants and to help credit providers make more informed and optimal credit assessment decisions.
4.2 Socure Integrations - Predictive Document Verification (Jira ID: INTCL-2339)
Feature Description
Predictive Document Verification (DocV) confirms the authenticity of a government-issued ID, matches the Personal Identifiable Information (PII) extracted from the ID against the input information, and matches the image in the ID with the consumer-submitted selfie using facial biometric analysis.
5. Fixed issues
This section briefly describes the issue fixed in this release.
5.1 Requests to integrations such as Equifax Apply are failing when called from the dealer portal via workflow (Jira ID: INTCL-2377)
Issue Description
If a dealer, using a dealer portal, triggers the workflow that is used to send a request to an integration such as Equifax Apply, and the Log Request Response checkbox is selected in the integrations API configurations, then the request to the integration is failing.
This is because when the Log Request Response checkbox is selected in the integrations API configurations, a response file ID must be generated as part of the integrations response and stored; because the dealer, using the dealer portal did not have the necessary permissions to generate and store this response file ID, the request was failing.
Resolution
The issue is resolved and the required permissions are added for the portal users.
6. Known issues
This section briefly describes the known issue with this release.
6.1 Exception in parsing response from XML to JSON when the reference ID has blank space (Jira ID: PDRFF-3253)
Issue Description
When a request is sent to an integration such as Equifax and the value of any of the fields in the response have blank space in between, the system is unable to convert the XML to JSON as required to process the response.
Workaround
To convert the XML response to JSON, as an alternative to the "intframework.XmlToJson.parseDocumentToMap(doc);" available out-of-the-box in integrations package, use the following script:
String jsonContent = Intframework.XmlToJSON.convertXmlToJson(resp, true);
Map<String, Object> mapFromXmlContent = (Map<String, Object>) JSON.deserializeUntyped(jsonContent);
For example:
List<StaticResource> staticResourceList = [SELECT Id, Body FROM
StaticResource WHERE Name = 'EquifaxCompanyResponse'];
String resp = staticResourceList[0].Body.toString();
String jsonContent = Intframework.XmlToJSON.convertxmlToJson(resp, true);
System.debug(jsonContent);
Map<String, Object> mapFromXmlContent = (Map<String, Object>) JSON.deserializeUntyped(jsonContent);
System.debug('mapFromXmlContent ' + mapFromXmlContent);
7. New and modified objects
This section briefly describes the objects added or modified in this release.
For a complete list of the Q2 Integrations objects, see the Q2 Integrations Data Dictionary.
7.1 New objects
The following object is added in this release:
7.1.1 Identification Type (Update the picklist values for the Identification Type field)
This object stores the information received in the Socure's Predictive Document Verification (DocV) API response.
The following table describes the new fields added to this object. All these fields are optional:
Field API Name | Description |
---|---|
intdm__Account__c | This field represents lookup to Account. |
intdm__BirthDate__c | This field specifies the birthdate provided on the identification information. |
intdm__City__c | This field specifies the city provided on the identification information. |
intdm__Contact__c | This fields represents lookup to Contact. |
intdm__Country__c | This field specifies the country name in the address on the identification information. |
intdm__Date_of_Issuance__c | This field represents Date of issuance of identification information. |
intdm__Document_UUID__c | This field specifies the Universal Unique Identifier (UUID) of the uploaded documents. |
intdm__Expiration_date__c | This field represents expiration date of the document. |
intdm__First_Name__c | This field specifies the first name provided on the identification information. |
intdm__Identification_Number__c | This field represents Unique identification number of the document. |
intdm__Identification_Type__c | This field represents the type of identification information, could be Drivers License, Passport, and so on. |
intdm__Last_name__c | This field specifies the last name provided on the identification information. |
intdm__Processing_Status__c | This field represents the current state of the document verification process. |
intdm__Reference_ID__c | This field specifies the reference ID of the transaction. |
intdm__State_Province__c | This field specifies the state or province provided on the identification information. |
intdm__Status__c | This field represents the outcome of the document verification process, such as Accept, Reject, or Resubmit |
intdm__Street_Address__c | This field specifies the street address provided on the identification information. |
intdm__Zip_Code__c | This field specifies the zip code of the address provided on the identification information. |
7.2 Modified objects
The following objects are modified in this release:
-
Identification Information (genesis__Identification_Information__c)
-
Provide read permissions for custom objects and fields to the required users
7.2.1 Identification Information (genesis__Identification_Information__c)
Personal Identification Information for an individual is taken from this object.
The following table describes the modified fields of this object. All these fields are optional:
Field API Name | Description |
---|---|
genesis__Identification_Type__c |
With the August 2024 release, to support the Socure's Predictive Document Verification (DocV) integrations, the following values are added to the Identification Type field of the Identification Information object:
|
7.2.2 Provide read permissions for custom objects and fields to the required users
To improve the security posture of Integrations packages and implement the secure code practices recommended by Salesforce and Q2, the Field-level security is added to all the read operations in this release.
8. New and modified REST APIs
This section briefly describes the REST APIs added or modified in this release.
For a complete list of the Q2 Integrations REST APIs, see the Q2 Integrations REST APIs Guide published over the Q2 Customer Portal and the Q2 Lending Help Center.
8.1 New REST APIs
The following REST APIs are added in this release:
8.1.1 Equifax Apply Consumer Credit API
API Name | Description |
---|---|
Equifax Apply Consumer Credit API |
This REST service handles Equifax Apply Consumer Credit requests. |
8.1.2 Equifax Apply Previous Inquiry API
API Name | Description |
---|---|
Equifax Apply Previous Inquiry API |
This REST service handles Equifax Apply Previous Inquiry requests. |
8.1.3 Socure Predictive Document Verification (DocV) API
API Name | Description |
---|---|
Socure Predictive Document Verification (DocV) API |
This REST service handles Socure Predictive Document Verification (DocV) requests. |
8.2 Modified REST APIs
There are no REST APIs modified in this release.
9. New and modified global methods
This section briefly describes the global methods added or modified in this release.
For a complete list of the Q2 Integrations global methods, see Q2 Integrations Global Methods Guide.
9.1 New global methods
The following global methods are added in this release:
9.1.1 Equifax Apply Consumer Credit
This class handles Equifax Apply Consumer Credit requests.
The following table describes the global methods or webservice methods added to this class:
Global Method/Webservice Method Name | Description |
---|---|
runSynchronousIntegrationService | This is a web service that is called to check if the feature has been granted permission to run by the current user. |
9.1.2 Equifax Apply Previous Inquiry API
This class handles Equifax Apply Previous Inquiry requests.
The following table describes the global methods or webservice methods added to this class:
Global Method/Webservice Method Name | Description |
---|---|
runSynchronousIntegrationService | This is a web service that is called to check if the feature has been granted permission to run by the current user. |
9.1.3 Socure Predictive Document Verification (DocV) API
This class handles Socure Predictive Document Verification (DocV) requests.
The following table describes the global methods or webservice methods added to this class:
Global Method/Webservice Method Name | Description |
---|---|
runSynchronousIntegrationService | This is a web service that is called to check if the feature has been granted permission to run by the current user. |
9.2 Modified global methods
There are no global methods modified in this release.
10. Post August 2024 release
Follow this section for the details on the issues fixed in the patches on the August 2024 release of Q2 Integrations.
11. Change record
S.No | Change Date | Description of Change |
---|---|---|
1. | August 23, 2024 | Published the release notes for the August 2024 General Availability release (4.6001). |