August 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.
The contents of this document are applicable to all the customers who have installed the latest version of Q2 IntegrationsAugust 2023 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.
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 August 2023 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. 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
There are no new features and enhancements added in this release.
For a detailed description of the new features and enhancements, see the Q2 Integrations User Guide published over the Q2 Customer Portal.
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 FICO LiquidCredit SBSS 7 PACU Issues (Jira ID: PDRFF-2304)
6.1.1 Parsing issue
Issue Description
Parsing issue was seen.
Resolution
The issue is resolved.
6.1.2 The Report Selection ID is placed incorrectly
Issue Description
The Report Selection ID, which is a required request parameter when calling Experian or D&B was placed in the org level, but ideally it should be placed in the account level.
Resolution
This issue is fixed now and the following changes have been made:
The changes are made in Integration API configuration >> Request Mapping >> JSON file
| Changes Made | Where? |
|---|---|
|
Add the following code: |
In JSON File: |
|
Remove the following code from Connection details: |
7. Known issues
There are no known issues in this release.
8. New and modified objects
This are no objects added or modified in this release.
For details on all the Q2 Integrations objects, see Q2 Integrations Data Dictionary.
9. New and modified REST APIs
There are no REST APIs added or modified in this release.
For details on all the Q2 Integrations REST APIs, see Q2 Integrations REST APIs Guide.
10. New and modified global methods
There are no global methods added or modified in this release.
For details on all the Q2 Integrations global methods, see Q2 Integrations Global Methods Guide.
11. Post GA release
Follow this section for the details on the issues fixed in the patches on the August 2023 release of Q2 Integration.
11.1 Issue fixed in July 15 patch
11.1.1 Requests to integrations such as Equifax Apply are failing when called from the dealer portal via workflow (Jira IDs: INTCL-2371 and PDRFF-3071)
Fixed Version
CL Utilities version 4.3000.1
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.
12. Change record
| S.No | Change Date | Description of Change |
|---|---|---|
| 1. | September 22, 2023 | Published release notes for August 2023 General Availability release. |
| 2. | July 15, 2024 | Added section 11.1. |