Q2 Gro 3.24.4

  • Updated

May 10, 2024 (Q2 Gro 3.24.4.1)

This release includes the following updates:

What's New

  • Enhanced the workflow for document verification to provide users with the ability to confirm whether they have the required documents ready before they start the process. If not, applicants can select I don't meet the criteria and be taken to either the Funding page, for FIs using delayed funding, or to the Thank You page. The following images show an example of the experience before and after this enhancement:

    Before

    Page_DocVerification2.png

    After

    page_DocVerification1.png

(GRO-14039)

  • Updated Q2 Gro to only allow applicants to upload the file types configured in the fileTypes array in the client.webapp.custom.properties Type ID. For an example configuration, expand the Developer information section below.

    (GRO-15094)

  • Updated the default configuration to include configuration for Adverse Action notifications so that FIs don't need to manually perform any configuration to use this feature. (GRO-15323)

  • Updated the Files Sent section of applications in the Q2 Gro Admin Portal to include both the Disclosures and Queue Routing attachments. (GRO-16677)

  • Updated the Q2 Gro Admin Portal to no longer include the Funnel Report, as it is deprecated. (GRO-17786)

  • Added the ability to configure each of the mailing address state dropdowns separately so that each can display its own list of states. Expand the Developer information section below to see the available configuration options for these dropdowns.

    (GRO-18650)

  • Enhanced internal comments to log a comment when a user manually moves an application from one queue to another. (GRO-18679)

  • Updated the Adverse Action Notification email to include the date and time when a notification email was sent. To include this information in the Adverse Action Notification email template, add the "{7} : timestamp" parameter to the server.workflow.service.custom.portalActionSettings Type ID. (GRO-18683)

  • Enhanced data capture and storage by including the Joint Signature field under the Joint Applicant section of an application in the standard web app and in the Admin Portal. (GRO-18711)

  • Updated field configuration to replace the following legacy configurations with new ones:

    • For the requiredFields object in the client.webapp.default.properties.json Type ID:

      "requiredFields": {
    "mothersMaiden": false,
    "idNumber": true,
    "idNumberJoint": true,
    "firstName": true,
    "jointFirst": true,
    "middleName": false,
    "lastName": true,
    "jointLast": true,
    "homeAddressLine1": true,
    "homeAddressCity": true,
    "employerPhone": false,
    "jointEmployerPhone": false,
    "employmentDuration": false,
    "jointEmploymentDuration": false,
    "employerName": false,
    "jointEmployerName": false,
    "income": false,
    "incomeApp2": false,
    "jobTitle": false,
    "jobTitleApp2": false
},

      Note

      The fields shown in the code example above may appear differently for FIs who have configured additional fields in the client.webapp.custom.properties Type ID.

    • For the validationFields object, replace the existing configuration using the same fields from the requiredFields configuration, above. For more information, see Validation fields.

      (GRO-18891)

    Updated the validationFields object in the client.webapp.custom.properties Type ID to now include a configuration to display a red asterisk * next to each field where required-value is set to true.

    Note

    This configuration is only included in the validationFields object, where showAsteriskOnMandatoryFields is set to true.

    (GRO-18944)

    Added the ability for existing users with the Configuration Specialist role to delete email templates from the Emails page in the Q2 Gro Admin Portal. For more information about user roles, see User role comparison table. (GRO-19178)

Fixes

  • Fixed an issue with the Existing Member workflow where, when the skipCart parameter was applied to the landing page URL, the applicant couldn't progress forward. (GRO-17937)

  • Fixed an issue where the Advanced Queue Routing feature didn't work as expected in multi-tenant environments. (GRO-18652)

  • Fixed an issue with the authenticated workflow where a security warning message was causing joint applications to fail after the KBA workflow step. (GRO-19698)

  • Fixed an issue where a physical address starting with the letter "P" or "B" triggered a configuration that incorrectly recognized the address as a PO Box.

    Note

    For example, an address such as "PMB 234" or "PMB234" would trigger this result.

    (GRO-16192)

  • Fixed an issue where the Delayed Funding workflow didn't work properly when both Socure Document Verification and Delayed Funding were enabled but Socure's publicKey property didn't contain any information. (GRO-16862)

  • Fixed an issue where Q2 Gro Admin Portal users couldn't modify mailing address information for the joint applicant and the associated internal comments displayed "null". (GRO-17246)

  • Fixed an issue where, after driver's license capture, information in the Address field of an application was erroneously appended with "None." (GRO-17356)

  • Fixed an issue where, after the Q2 Gro environment was rebooted, File Exporter and Image Exporter functionality didn't work properly. (GRO-17788)

  • Fixed an issue where, after funding was submitted for an application, the Dynamic Risk Engine (DRE) erroneously ran and caused the funded application to revert to "Pending" status. (GRO-17952)

  • Fixed an issue where some steps in the authenticated workflow couldn't be disabled, causing the application's status to be incorrect. (GRO-18113)

  • Fixed an issue where required fields didn't display a red asterisk * when the showAsterisksOnMandatoryFields property in the client.webapp.custom.properties Type ID was set to true. (GRO-18397)

  • Fixed the following issues:

    • Moved the zipRegexValidatorclient.webapp.custom.properties configuration to the validationFields, so all UI validation configurations would be in one JSON object.

    • Fixed an issue where the joint applicant mailing address link would not show by default.

    • Fixed an issue where the Use Same as Primary button would not populate for both physical and mailing addresses.

    (GRO-18437)

  • Fixed an issue with where the application workflow was proceeding forward even when mandatory fields Issued Date and Expiration Date for the driver's license were left empty. (GRO-18742)

  • Fixed an issue where, after being removed, default queues were added back to the Q2 Gro Admin Portal. The following queues are included in the default queue configuration, which will not be added back to the Admin Portal:

    • Default

    • Incomplete

    • KYC Failed

    • KBA Failed

    • Decisioning Failed

    • Risk Failed

    • Core Failed

    • Pending Funding

    • Funding Failed

    • Completed

    (GRO-18790)

  • Fixed an issue where Decision on Application was incorrectly referring applicants based on email address criteria. (GRO-18890)

  • Fixed an issue where the internal comments for Decision on Application Attribute were incorrectly displaying a value of "null" for joint applicants. (GRO-18955)

  • Fixed an issue where Social Security Number didn't automatically populated for returning applicants in the Admin Portal, causing applications to look like they had bypassed the applicant's Social Security Number (SSN) verification. (GRO-18982)

  • Fixed an issue on the Document Verification page where some of the text in the page title was cut off. (GRO-19615)

  • Fixed an issue where applicants could proceed forward in the application workflow without having to enter information in Birth Date fields by entering information into Birth Dates fields initially, selecting Next, selecting Back to return to the previous page, removing the information they previously entered, and selecting Next again. (GRO-19621)

  • Fixed an issue with Delayed Funding where, when Plaid funding failed, the Bank Transfer page incorrectly displayed and prevented the applicant from navigating to other pages. (GRO-19624)

  • Fixed an issue where the Camera Camera icon image icon on the Identification page could not be selected. This fix introduces a new Close button to exit the camera's photo mode, as shown in the image below. The configuration is available as "closeSnap" : "Close" from the client.custom.messages.en Type ID.

    Camera's photo mode image

    (GRO-19637)

  • Fixed an issue where the Overdraft Service and Account Disclosures dialogs didn't display for joint applicants when each dialog's associated link was selected from the Almost Done page. (GRO-19651)

Adapter Changes (Back-End Only)

  • Updated the Jack Henry SilverLake System® adapter to allow Certificate of Deposit (CD) accounts to start with a balance of $0.00. Previously, the "Certificate amount cannot be zero" error displayed when the starting balance was $0.00. Now, a new errorOverride configuration is included in the server.workflow.service.custom.submissionWorkflowSettings Type ID to suppress this error. (GRO-18868)

  • Upgraded the FIS Horizon adapter framework version to allow for improved logging and error handling. These changes allow Q2 support to better (and more quickly) troubleshoot any issues that may arise going forward. (GRO-19362)

Adapter Fixes (Back-End Only)

  • Fixed an issue with the Jack Henry Silverlake System® adapter where, when an application was created through the API, the Existing Customer Check failed intermittently. (GRO-18567)

  • Fixed an issue with the FIS IBS adapter where applications failed during core submission with a NoneType object error. (GRO-19264)

  • Fixed an issue where the Fiserv Signature® core adapter failed when selecting an employment status that didn't require the Employer's Name field to be completed. (GRO-18540)

  • Fixed an issue with the Fiserv XP2® core adapter where Existing Member Check failed and displayed an error with the NoneType object. (GRO-18905)

  • Fixed an issue with the the Fiserv Premier® adapter where authenticated applications were sometimes referred when a "GroException" error occurred. (GRO-18936)

  • Fixed an issue with the Q2 Gro API where custom data was missing from CSV files. (GRO-19268)

  • Fixed an issue with the Q2 Gro API where some primary and secondary applicant fields were not properly mapped and their associated values appeared in CSV files as "None." (GRO-19324)

  • Fixed an issue where the Q2 Gro API failed when internal comments related to Socure contained unsupported characters. (GRO-18927)

  • Fixed an issue with the TransUnion KBA adapter where all applications were failing and returning ActionCode "D" and targetGroup "Duplicate". (GRO-18128)

June 28, 2024 (Q2 Gro 3.24.4.3)

This release includes the following updates:

What's New

  • Updated the default configuration for the Advanced Queue Routing feature, which will be automatically deployed to FIs already using Gro. FIs using Gro for the first time will need to manually add the new default configuration. For more information, see Configuring Advanced Queue Routing. (GRO-16161)

  • Updated the configuration for the SWBC (Southwest Business Corporation) integration to use the PostCreditCardPaymentWithOriginTypeApplyTo Type ID for credit card inquiries, which contains the configuration for the originType field with a value of WEB. (GRO-19926)

  • Enhanced Q2 Gro API security by adding authorization configuration for resource requests. (GRO-12765)

Fixes

  • Fixed an issue where incomplete applications that had been manually routed by a Gro Admin Portal user were automatically returned to the Incomplete queue. (GRO-19718)

  • Fixed an issue where the Decisioning on Application attribute didn't decision correctly for primary and joint applicants, based on their provided Social Security Number (SSN). (GRO-18677)

  • Fixed an issue where users weren't logged out of the Q2 Gro Admin Portal after their session had expired. (GRO-18452)

  • Fixed an issue where hiding or showing the second address field removed the values in the field instead of showing or hiding the UI element. (GRO-19632)

  • Fixed an issue where locked out users attempting to reset their account password received a Failed Password Reset emailing containing an incorrect timestamp for the end of their lockout period. (GRO-18068)

  • Fixed an issue where the Gro application workflow erroneously displayed a missing ACH information error in internal comments and Delayed Funding failed for unrestricted applicants. (GRO-19650)

    Fixed an issue where the internal comments section contained unnecessary information associated with Socure Document Verification. (GRO-18204)

    Fixed an issue where applicants couldn't add PO Box information to mailing address fields. (GRO-19982)

    Fixed an issue where Authenticated workflow created new customer and portfolio IDs for existing customers on multiple cores. (GRO-20115)

September 18, 2024 (Q2 Gro 3.24.4.5)

This release includes the following updates:

What's New

Migrated Q2 Gro OLB Adapter APIs

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)

Configurable Auto Closed Setting for FIS Horizon CD Account

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)

Updates to FDIC Logo

Revised FDIC Logo for Digital Channels

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)

View Bank and FDIC Logo for Headers

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)

October 16, 2024 (Q2 Gro 3.24.4.6)

This release includes the following update:

What's New

Revised FDIC Logo for Web Application

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)

Related articles

IN THIS ARTICLE