This release includes the following updates:
-
Updated the configuration for
validationFields
in theclient.webapp.custom.properties
Type ID to no longer include the field configurations shown below. This change was implemented to ensure that these fields are always indicated as required.Caution
Do not make any modifications to these configurations, as these fields are required for successful account opening.
"validationFields": { "#ssn1TxtFld": { "required": { "value": true } }, "#DOBApp1Month": { "required": { "value": true } }, "#ssn1TxtFldApp2": { "required": { "value": true } }, "#DOBApp2Month": { "required": { "value": true } } }
(GRO-19448)
-
Enhanced Q2 Gro's security by adding a configuration that improves the strength of security authentication tokens used when resetting passwords. (GRO-16092)
-
Fixed an issue where the Adverse Action email only displayed one of Qualifile's key reasons for declining an applicant. Now, the Adverse Action email will display all four key reasons. Additionally, the Adverse Action email template was revamped to include different body text and was updated to include additional body parameters in the
server.workflow.service.custom.portalActionSettings
Type ID. For more information, see Configuring Adverse Action notifications. (GRO-18911) -
Enhanced security for Q2 Gro API Endpoints by doing the following:
-
Restricted access to the /admin/migration/tenant/export endpoint to only allow users with the Change Manager role.
-
Enabled application fetching based on the selected queue to enhance the Q2 Gro Admin portal's Search function.
-
Fixed an accessibility issue where the Select Suffix field label text on the Contact Info page didn't announce properly for screen readers. (GRO-20072)
-
Fixed an issue where screen reader users cycling through UI elements with the Tab key within the unauthenticated workflow received an incorrect element tag announcement for the How you use my information clickable element on the Get Started page. This element is now properly announced as a button.
(GRO-19935)
-
Fixed an issue where uploaded documents were being removed from applications when applicants updated their personal information from another page and navigated back to the page where they uploaded their document. Now, if an applicant modifies their first or last name after uploading documents, they will instead be removed and asked to reupload any documents to proceed through the application. (GRO-19923)
-
This release includes the following updates:
Added support for the pinch-to-zoom gesture on mobile browsers to enable users to dynamically zoom and scale the page. (GRO-20305)
Replaced API GET calls with POST calls as application was including all sensitive data in the URL such as mobile number and one-time password (OTP). This ensures enhanced security and best practices of data handling.
Note
Q2 Gro recommends you to update GET calls with POST calls for any future changes.
(GRO-19764)
Updated the Q2 Gro OLB adapter to support Caliper API V2 keys as Q2 is in the process of deprecating API V1 keys. This ensures improved security and performance.
Note
Q2 Gro recommends you to open a Salesforce case to enable this support.
(GRO-17932)
Enhanced the autoCloseCD
configuration to support the ability for the FIs using FIS Horizon core to set whether or not to auto close CD accounts upon maturity. To configure CDs to not auto close, update the autoCloseCD property in the server.workflow.service.submitApplication.settings
Type ID as follows:
{ "mappings": { "autoCloseCD": { "cd_special1": "N", "cd_special2": "N", "cd_01yrnp": "N" } } }
Note
By default, autoCloseCD
configuration values are set to "Y".
(GRO-20823, GRO-20367)
Updated the FDIC logo and verbiage to satisfy the updated FDIC requirements. The updated logo will not be enabled by default. To enable the updated logo, update the client.webapp.logo.fdicLogo
Type ID as follows:
"fdicLogoEnabled": false, "fdicCertValue": "987"
Note
By default, the cert value is 987
. It can be changed to meet the needs of your FI.
(GRO-20430)
Modified the showNewHeader
property in the client.webapp.custom.properties
Type ID to support the display of the Bank and FDIC logo in the header and first page of the application. To enable the logo visibility, use the new fdicHeaderEnabled
property in the client.webapp.logo.fdicLogo
Type ID as follows:
"fdicLogoCertValue": "987", "fdicLogoEnabled": false, "fdicHeaderEnabled": false
(GRO-20783)
This release includes the following update:
Updated the FDIC logo with white background to support any colour for the FI's background in the web application. The updated logo is not enabled by default. To enable the updated logo, update the client.webapp.logo.fdicLogo
Type ID as follows:
"fdicLogoCertValue": "987", "fdicLogoEnabled": false, "fdicHeaderEnabled": false
Note
By default, the cert value is 987
. It can be changed to meet the needs of your FI.
(GRO-20763)
This release includes the following updates:
Updated system handling of joint applicant data in situations where a joint applicant was removed from an application. Now, if an applicant removes joint information from the application, all associated information is automatically purged. This helps you to maintain data integrity and reduces extraneous information in the application. (GRO-20808)
-
Fixed an issue on the where users could navigate to the Verify Identity page without entering a phone number. This issue occurred in situations where users navigated back to the Get started page from the Verify Identity page after entering a phone number initially, then removing it. (GRO-20707)
-
Fixed an issue with joint applications where applications would not load within the Gro Admin Portal. (GRO-19421)
-
Fixed an issue on the Edit Emails page in the Gro Admin Portal where the Font Family and Font Size selectors were blank and could not be modified. (GRO-20723)
-
Fixed an issue where the Nacha file generator did not properly filter applications from the database. To resolve this issue, FIs must explicitly specify valid statuses in the
server.workflow.service.achftp
Type IDAchApplicantStatusFilter
property as defined in theclient.workflow.portal.applicationStatusOptions
Type ID. As a result of this fix, only applications with specified statuses will be retrieved. If theAchApplicantStatusFilter
property is left blank, only approved applications will be retrieved and invalid or unspecified statuses will be treated as an error, to ensure clarity and data precision when processing applications using the Nacha file generator. (GRO-20809) -
Fixed an issue where running the Image Exporter intermittently failed and returned SQL errors in the log files. (GRO-20726)
-
Fixed an issue where the Default queue was populated automatically for any existing FIs.
To resolve this issue, FIs must explicitly specify the required value for the new configuration
generateDefaultQueues
specific to each tenant. If you set"generateDefaultQueues": true
and enable the queue routing ("server.queue.routing.enabled": true
), this configuration creates the default queues if it did not exist already. If any other cases (eithergenerateDefaultQueues
or queue routing or both are set tofalse
) the Q2 Gro does not creates default queues if it did not exist already.TypeId: server.queue.routing.settings { "generateDefaultQueues": false // default value - false }
Note
By default,
generateDefaultQueues
config value is set tofalse
.(GRO-20607)