Q2 Gro 3.23.6

  • Updated

June 28, 2023 (Q2 Gro 3.23.6)

This release includes the following updates:

What's New

Updated the Online Banking (OLB) Enrollment Adapter to Support Account Linking

The Online Banking Enrollment adapter has been updated to support linking accounts using applicant data. For configuration information, expand the Developer information section below.

For a list of additional values you can use to link applicant accounts, see Linking applicant accounts. (GRO-13295)

Enhanced the Q2 Gro Admin Portal to allow stored driver's license images to be purged

The Gro Admin Portal now allows users with the Administrator role to purge stored driver's license images within a specified date range. For more information, see Purge Images.

Caution

Once purged, a driver's license image can't be recovered.

(GRO-13259)

Note

The following change requires Q2 Gro 3.23.6.21 or later.

Additional Changes

  • Updated the apple icon in the Gro Admin Portal Queues section to use a new image. (GRO-13750)

Adapter Changes (Back-End Only)

Added the Ability to Submit Certificate of Deposit Products to Fiserv Signature Cores

FIs using Fiserv Signature cores can now define CD products for use within the Q2 Gro application. (GRO-14285)

Fixes

  • Updated file validation to include server-side validation for files uploaded in the Gro Admin Portal. For configuration information, expand the Developer information section below.

    (GRO-13571)

  • Fixed an issue with the Fiserv Premier SOA core where the second address line was not being sent to the core. (GRO-13669)

Adapter Fixes (Back-End Only)

  • Fixed an issue where the internal core adapter erroneously reported that the customer was not found during the existing member check. (GRO-11348)

  • Fixed an issue where the Gro application workflow did not send the joint applicant's email address or phone number to the core. (GRO-14936)

April 30, 2024 (Q2 Gro 3.23.6.23)

Caution

When choosing to take this release, if your Financial Institution has implemented custom code through our client.webapp.custom.functions capability via the Admin Portal's Advanced Configuration, the stance on custom functions are as follows:

  • Q2 does not test custom functions and has not tested the compatibility of your custom code with this release.

  • Your Financial Institution should thoroughly test and verify your custom functions and application process are working as expected after being upgraded to this release.

What's New

Added Socure DocV Support to the Alloy KYC Adapter

Q2 Gro has updated the Alloy KBA adapter to include support for Socure DocV within the document verification process. The new configuration includes the "triggerCriteria" property in the client.webapp.custom.properties Type ID and will be automatically included for FIs that access Socure through Q2 Gro's Socure integration. However, in order for the new configuration to support Alloy, you need to add the configuration for Alloy statuses that you support. For configuration information, expand the Developer information section below.

(GRO-15624)

Updated Adverse Action Notice Email Template

The Adverse Action Notice email template now includes the following values for FIs that use Qualifile. Configurations are in included in the server.workflow.service.custom.portalActionSettings Type ID:

  • "applicantName"

  • "scoreNbr"

  • "reasonCd"

  • "reasonTxt"

  • "validGovernmentNumberTxt"

  • "recommendedActionList"

  • "fraudFinderResponseTxt"

The email template configuration has been updated to include the above values as an array in the server.custom.messages variable. For configuration information, see Adverse Action Notifications.

(GRO-11676, GRO-15323)

Additional Changes

  • Updated Advanced Queue Routing's standard configuration for a new default email template. The new standard configuration will be automatically applied when updating Q2 Gro. For information about the default configuration for Advanced Queue Routing, see Advanced Queue Routing. (GRO-15926)

  • Added the ability for Q2 Gro's PDF Exporter to export all PDFs and the index file within the same zipped file. For customers using this feature, the values zipFile, zipFileExtension, and zipFilePrefix were added to the server.workflow.service.pdfftp.connectionDetails Type ID and the value documentPathValue was added to the server.workflow.service.custom.indexFileSettings Type ID. For more information, see Q2 Gro-PDF Exporter Integration. (GRO-15357)

  • Updated the Email dropdown on the Emails page in the Q2 Gro Admin Portal to include an Adverse Action option, which provides the ability to edit the Adverse Action email template from within an application. (GRO-14341)

  • Added the ability to hide membership information in the Private Info section of an application in the Q2 Gro Admin Portal. To apply this configuration, set thedisplaySEGCategoriesOnApplicationDetailsPageanddisplaySEGChoicesOnApplicationDetailsPageattributes tofalse in the client.webapp.custom.propertiesType ID. (GRO-14906)

  • Enhanced Q2 Gro's security by adding a configuration that only allows applicants from specified countries to apply. The applicant's location is determined by the geographical location of their device. The allowApplicationsFrom array configuration was added to the client.webapp.custom.properties Type ID and uses two-letter country codes to specify which countries are allowed. For example, "allowApplicationsFrom": ["US"]. For more information about country codes, see Country Codes on the ISO website. (GRO-15501)

  • Improved applicant workflow security to improve protection against application exploits. (GRO-15632)

  • Updated the Image Exporter feature to support column ordering in the index files. For configuration information, see Q2 Gro-PDF Exporter Integration. (GRO-15930)

  • Updated the Delayed Funding feature to be disabled in the default configuration. You must enable the Delayed Funding feature if you wish to use it. For more information, see Saving funding data for referred applicants. (GRO-16575)

  • Updated the default configuration for the Image, PDF, and Security log exporters to no longer require manual changes. All configurations for these features will now be automatically applied, which includes the following Type IDs:

    • For Image Exporter:

      • server.database.export.images

      • server.workflow.service.custom.indexFileSettings

      • server.quartz.settings.jobs

    • For PDF Exporter:

      • server.workflow.service.pdfftp.connectionDetails

      • server.report.pdf.settings

      • server.workflow.service.custom.indexFileSettings

      • server.quartz.settings.jobs

    • For Security Logs Exporter:

      • server.service.export.securityLog

      • server.quartz.settings.jobs

    (GRO-15502)

Fixes

  • Fixed an issue where drivers licenses, when uploaded to the Document List section of an application in the Q2 Gro Admin Portal as a PDF file, contained an additional appended ".pdf" after the file extension. (GRO-16659)

  • Fixed an issue where uploading an image for the primary applicant to an application also uploaded an image for the joint applicant, prior to the joint image being overwritten. (GRO-18459)

  • Fixed an issue where, when both Qualifile and Decision on Application Attribute were enabled, the Qualifile Adverse Action email was incorrectly sent when the Decision On Application criteria wasn't satisfied. (GRO-16752)

  • Fixed an issue in the Q2 Gro Admin Portal where the ID State and ID Country fields were displaying incorrect information. (GRO-15851)

  • Fixed an issue for FIs with Qualifile enabled where Socure reports overwrote previously generated reports for the same applicant instead of generating new reports. (GRO-10888)

  • Fixed an issue where the Q2 Gro application didn't capture e-signatures for applicants completing the application workflow from touchscreen laptops. (GRO-13765)

  • Fixed an issue where an application's internal comments section didn't properly update values for the mailing address and second address fields in the Q2 Gro Admin Portal. (GRO-17840)

  • Fixed an issue where security log, PDF export, and image export jobs failed intermittently. (GRO-13883)

  • Fixed an issue where special characters incorrectly displayed as "??". Now, special characters display correctly. (GRO-14373)

  • Fixed an issue where an application always proceeded to the Bank Transfer page when bankXferPageAfterPlaid was set to true, regardless of the application's funding verification outcome. Now, the application workflow only proceeds to the Bank Transfer page if the applicant passes funding verification. (GRO-14576)

  • Fixed an issue where internal comments were incorrectly translated when the applicant had their browser set to use Spanish. Now, internal comments display in English, unless otherwise specified in Q2 Gro's language configuration.

    Note

    This fix only applies to new applications and won't affect existing applications that previously experienced this issue.

    (GRO-14991)

  • Fixed an issue where applicants were redirected to the Thanks For Applying page if they immediately exited the Plaid funding workflow using the X icon. (GRO-18461)

  • Fixed an issue where applicant values that included trailing spaces and hyphens caused the Q2 Gro Image Exporter and PDF Exporter not to work as expected. (GRO-15079)

  • Fixed an issue where the Queue Routing workflow was falsely triggered by documents being uploaded to the Identification page. (GRO-15134)

  • Fixed an issue where, once generated, reports couldn't be opened from the Reports section of the Q2 Gro Admin Portal. (GRO-16378)

  • Fixed an issue where images downloaded from the Private Information section of an application didn't open properly and displayed an error. (GRO-16379)

  • Fixed an issue where Socure's Document Verification page only displayed part of its page title. (GRO-16393)

  • Fixed an issue on mobile devices where the on-screen numeric keypad didn't display when an applicant interacted with the Social Security Number (SSN) fields while their values were masked. (GRO-17839)

  • Fixed the following issues for driver's license capture:

    • Users received a blank page instead of a prompt to upload the back of their photo ID. (GRO-17476)

    • Users could upload the front of their driver's license using Front Driver's License Capture during the application process, but the file didn't properly save in the Q2 Gro Admin Portal. (GRO-16656)

  • Fixed an issue where loading icons were missing when users logged into the Q2 Gro Admin Portal. (GRO-16182)

  • Fixed an issue where referred applications, including those with funding that hadn't yet been captured, didn't receive funding within the Delayed Funding workflow. The issue was occurring for returning applicants whose funding was captured in a previous application or whose funding wasn't yet captured in the current application. (GRO-16441)

  • Fixed an issue where an unlabeled additional field displayed above the First Name field in an application by adding "prefixEnabledAdmin":false to the client.portal.custom.properties Type ID.

    GRO-17480.png

    (GRO-17480)

  • Fixed an issue within the application workflow where users were able to draw their signature outside of the Signature field on the Signature page. (GRO-17470)

  • Fixed an issue where some icons did not display correctly within the application workflow. (GRO-16277)

  • Fixed an issue where the default Plaid configuration caused the Congratulations page not to display if an applicant failed funding verification during the Plaid funding workflow. If you are experiencing this issue, expand the Developer information section below to see the configuration to apply.

    Developer information

    Apply the configuration shown below to the server.workflow.service.status.rules Type ID.

    {
    "verifyFundingBalance": {
        "stop": "pending",
        "continue": "pending"
    }
}

    (GRO-15727)

  • Fixed an issue where documents uploaded using Q2 Gro Communicator were exported in unsupported formats and didn't open properly. (GRO-16006)

  • Fixed an issue where selecting Next repeatedly from the Verify Identity page incorrectly skipped multiple steps of the application workflow. (GRO-16481)

  • Fixed an issue where Socure DocV was incorrectly triggered during the application workflow for applicants that failed OFAC. (GRO-15459)

  • Fixed an issue where applicants that had already selected a funding option and moved onto the next step of the application workflow could return to the Funding Options page by selecting Back and then advance again to the next step without needing to select a funding option. (GRO-16482)

  • Fixed an issue where URLs in the footer didn't open properly. (GRO-15533)

  • Fixed an issue where, when the Mailing State field was empty, applicants could progress to the next step of the application workflow by selecting an autofill value for their mailing addresses' state, even if the state was not available in the configuration. (GRO-15548)

  • Fixed an issue where the Mailing Address dropdown didn't automatically expand for returning applicants. (GRO-15610)

  • Fixed an issue where applications with a pre-filled value in the State dropdown displayed an error and the Thanks for Applying page appeared immediately after selecting a different value in the State dropdown. (GRO-16012)

  • Fixed an issue where .zip files generated file names that didn't match the associated file name shown in the index file. (GRO-17128)

  • Fixed an issue where, when multiple images had the same file name, they overwrote each other when sent together in the same FTP file transfer. For more information, see Setup guide for image file transfers using SFTP or FTPS.

    Note

    This fix only applies to new applications and doesn't update existing applications.

    (GRO-16795)

  • Fixed an issue where the Mailing Address field in the Joint Applicant section of an application couldn't be modified. (GRO-17246)

  • Fixed an issue where the Country field in the Joint Applicant section of an account application displayed a label of undefined instead of its assigned label value. (GRO-17303)

  • Fixed an issue where, when emailed, security log files were sent in the body instead of as an attachment. (GRO-17446)

  • Fixed an issue where, when the Decision on Applicant Attributes feature was enabled for ZIP Codes, applications were incorrectly referred when the ZIP Code had zeroes appended to it (for example 90210-0000). Now, applications are decisioned using only the first five digits of the ZIP Code and applications will no longer be incorrectly referred. (GRO-16799)

  • Fixed an issue where, when selected, custom questions using the singleCheckbox attribute on custom pages prevented other UI elements from loading properly. Now, custom questions using a single checkbox will load additional custom questions when selected. (GRO-16864)

  • Fixed an issue where selecting the delete Icon_Trash-delete.png icon next to a product didn't remove the product from the Products Applied For section of an account application in the Q2 Gro Admin Portal. (GRO-17094)

  • Fixed an issue where the information in the Identification section of an application in the Q2 Gro Admin Portal didn't update properly when an applicant navigated forward then backward in the application workflow, then selected a different ID Type. (GRO-17466, GRO-17583)

  • Fixed an issue on mobile devices where the Select a Product page only displayed a part of its title. (GRO-17469)

  • Fixed an issue in the Q2 Gro native app where external URLs were opening in the in-app browser but didn't allow for navigation back to the application. (GRO-17477)

  • Fixed an issue where taking a driver's license photo and attempting to upload it from within the Q2 Gro application prevented the customer from advancing through the application process. (GRO-17827)

  • Fixed an issue where applicants were incorrectly receiving errors when attempting to utilize Delayed Funding within the application workflow. (GRO-17658)

  • Fixed an issue where an application's internal comments did not properly reflect changes to the mailing address and second address fields in the Q2 Gro Admin Portal. (GRO-17840)

  • Fixed an issue with the Authenticated workflow where, when the language was set to Spanish, some UI text was incorrectly displayed in English. (GRO-17857)

  • Fixed an issue where users who were locked out due to incorrect password attempts were able to log in during the lockout period with valid credentials. (GRO-18162)

Adapter Changes (Back-End Only)

Enhanced Certificate of Deposit (CD) Product Configuration for the Jack Henry SilverLake System® Core Adapter

The Q2 Gro configuration was updated to enhance CD product functionality on the Jack Henry SilverLake System® core adapter. The following changes were made for this enhancement:

  • Updated calculations for the CD account maturity date and next pay date by applying a new configuration for the cdNewTimeFormat property to ensure that CD products always maintain the correct time format.

  • Added a new configuration parameter, origBal, to the server.workflow.service.custom.submissionWorkflowSettings Type ID. This parameter allows for an exact initial amount to be set for CD products.

  • Enhanced backward compatibility:

    • Setting the cdNewTimeFormat parameter to false or omitting it from your settings will leave CD products and associated workflow as they are without applying any changes. In order to apply this configuration, you must set the parameter to true and include it in your settings.

    • Omitting the origBal parameter from your configuration will leave your CD products and associated workflows as they are without applying any changes. The parameter is configured to retrieve its value from the product amount settings within the server.workflow.service.custom.submissionWorkflowSettings Type ID's acctAdd section in the list of products.

      Note

      Each product needs to be configured with an assigned value. If the value for a particular product is left empty, it will automatically be assigned a value of 1.0, which will be sent to the core.

    • Added the ability to configure CD product terms to use the following time formats:

      Note

      Configuration is available within the server.workflow.service.custom.submissionWorkflowSettings Type ID's acctAdd section in the list of products.

      • Days—to use a time format as a set number of days, configure "term": "90D" with "cdTermUnits": "Days".

      • Months—to use a time format as a set number of months, configure "term": "6M" or "term": "6" with "cdTermUnits": "Months".

      • Years—to use a time format as a set number of months, configure "term": "2Y" with "cdTermUnits": "Years".

(GRO-17710)

Updated Q2 Gro Fiserv Premier® Adapter Name ID Configuration

Added a new Fiserv Premier attribute, createNewIdsForExisting, in the server.workflow.service.submitApplication.settings Type ID that prevents new Name IDs from being created for existing customers. To enable this feature, set createNewIdsForExisting to false. (GRO-15670)

Updated Q2 Gro Fiserv Premier® Adapter Name ID Configuration

Added the headerSetting parameter in the server.workflow.service.submitApplication.connectionDetails Type ID for the Fiserv Premier adapter configuration that handles the FI's core adapter version. This new configuration will override the FI's default version and replace it with the configured version. (GRO-16218)

Additional Adapter Changes

  • Enhanced the Jack Henry SilverLake System® core mapping call responsible for adding new customers by allowing it to populate values for the customer's state and ID number as well as for the server.workflow.service.custom.submissionWorkflowSettings Type ID. For configuration information, expand the Developer information section below.

    Developer information

    For example, if the customer's ID type is a driver license and the state is Texas (TX), the new configuration appears as shown below.

    <AbbrCustDesc>TXDL810000042</AbbrCustDesc>

<AbbrCustDesc>PP123456</AbbrCustDesc>

<AbbrCustDesc>MID123456</AbbrCustDesc>

<AbbrCustDesc>TXID123456</AbbrCustDesc>

    (GRO-15352)

  • Enhanced Q2 Gro by migrating the following core adapters to Q2 Gro's independent service layer to allow core adapters to receive updates separately from Q2 Gro.

    • FIS Horizon (GRO-15470)

    • Fiserv DNA® (GRO-17099)

    • Fiserv Premier (GRO-17468)

    • Jack Henry SilverLake System® (GRO-15017)

    • Jack Henry Symitar® (GRO-15482)

  • Updated the Internal Comments section for the Alloy KBA adapter to include additional information about the applicant's identity verification process. For configuration information, expand the Developer information section below.

    Developer information

    To use this feature, apply the configuration shown below to the server.custom.messages.en Type ID.

    {
    "internalCommentsGetKYCCheck": "KYC Check: {0}"
}

    (GRO-14538)

  • Added the ability for the Fiserv Premier adapter to associate a new or existing joint applicant's name ID and address ID with a primary existing portfolio ID, which will prevent errors from happening when the createNewIdsForExisting parameter is set to false in the server.workflow.service.submitApplication.settings Type ID. (GRO-15958)

  • Enhanced Q2 Gro code continuity by converting all instances of Apache Groovy script in the Jack Henry Symitar® SymXchange™ adapter to JSON. (GRO-17170)

Adapter Fixes (Back-End Only)

Q2 Gro API

  • Fixed an issue in the Q2 Gro API where application data was incorrectly copied from one application to another. (GRO-16703)

  • Fixed an issue where the Q2 Gro API returned duplicated details for abandoned applications. (GRO-18659)

Alloy

  • Fixed an issue with the Alloy adapter where new internal comments weren't configured by default in FI environments. (GRO-16668)

  • Fixed an issue where the Alloy adapter failed at the KBA step. (GRO-16179)

FIS

  • Fixed an issue where FIS ID verification incorrectly used physical address data from a customer's IDs in place of state data. (GRO-15458)

  • Fixed an issue where the value from the Middle Name field wasn't passed to FIS IDV for OFAC and Identity Verification. (GRO-18681)

TransUnion KBA

  • Fixed an issue where the TransUnion KBA adapter didn't properly connect to TransUnion's IDMV/IDMA service. (GRO-16936)

  • Fixed an issue where the TransUnion KBA adapter experienced a "connection refused" error when attempting to connect to TransUnion. (GRO-18085)

  • Fixed an issue where new modifications to TransUnion Credit Report caused Knowledge-Based Authentication (KBA) within the TransUnion KBA adapter to not work properly. (GRO-17796)

TransUnion Credit Report

  • Fixed an issue with the TransUnion Credit Report adapter where reports were generated erroneously. (GRO-16136)

  • Fixed an issue with TransUnion credit reports where the logic that made decisions based on the credit report information wasn't functioning properly. (GRO-16683)

  • Fixed an issue with the TransUnion Credit Report adapter where its portal action didn't properly activate the Credit Report adapter from the Actions dropdown in the Q2 Gro Admin Portal. (GRO-17513)

FIS Horizon

  • Fixed an issue with the FIS Horizon core adapter where a joint applicant's Customer ID wasn't passed to the Q2 Gro Admin Portal web application. (GRO-18192)

Fiserv Premier

  • Fixed an issue with the Q2 Gro authenticated workflow where the Fiserv Premier adapter failed to retrieve the customer's name from the NameID property. (GRO-15464)

  • Fixed an issue where Fiserv Premier customers couldn't use self-signed certificates. (GRO-15710)

  • Fixed an issue where CD accounts couldn't be opened with the Fiserv Premier core adapter. (GRO-15771)

  • Fixed an issue where joint applicants attempting to open a CD account using the Fiserv Premier core adapter received an error and the account failed to open. (GRO-15783)

  • Fixed an issue where savings accounts were not properly created using the Fiserv Premier core adapter. (GRO-15949)

  • Fixed an issue with the Fiserv Premier core adapter where the account type code was not properly set for DDA or SAV products. (GRO-16836)

  • Fixed an issue where the Fiserv Premier core adapter didn't properly apply the configuration for the AccountingGroup property during customer account creation. (GRO-17189)

Fiserv Signature®

  • Fixed an issue where the Fiserv Signature core adapter failed if an applicant added a value to the ID Country field when ID Type was set to Passport. (GRO-16004)

  • Fixed an issue where the Fiserv Signature core adapter incorrectly set the employer start date to the current date, resulting in an incorrect Years on Job value. (GRO-17225)

  • Fixed an issue where the Fiserv Signature core adapter failed when the applicant selected a value from the Employment Status dropdown but didn't also need to select a value from the Employer's Name dropdown. (GRO-18540)

Fiserv XP2®

  • Fixed an issue where submitting loan applications via the Fiserv XP2 core adapter caused an error. (GRO-15481)

  • Fixed an issue where the Fiserv XP2 core adapter assigned more than one ID to each applicant on a joint application for existing applicants. (GRO-15708)

  • Fixed an issue where the Fiserv XP2 Credit Report submission failed if Qualifile had been run for the specified application. (GRO-18349)

Jack Henry SilverLake System®

  • Fixed an issue with the Q2 Gro Jack Henry SilverLake System® adapter where the joint applicant's ID state was not passed to the core and caused the application workflow to fail. (GRO-16097)

  • Fixed an issue where the Jack Henry SilverLake System® adapter incorrectly displayed "5 - Statement savings account" under the value column. (GRO-16242)

  • Fixed an issue where the Jack Henry SilverLake System® adapter prevented the Existing Member Workflow (EMW) from working properly. (GRO-16382)

  • Fixed an issue where the Jack Henry SilverLake System® adapter's internal comments incorrectly displayed the primary applicant's Customer ID in place of the joint applicant's Customer ID. (GRO-16491)

  • Fixed an issue in the Q2 Gro Admin Portal with the Jack Henry SilverLake System® adapter where the Account ID didn't display for accounts that were created manually from the Actions dropdown within an application. (GRO-16568)

  • Fixed an issue where the Jack Henry SiverLake System® core adapter didn't properly format internal comments for debit card creation. (GRO-17625)

  • Fixed an issue with the Jack Henry SilverLake System® core adapter where the Existing Member check failed intermittently. (GRO-18567)

October 2, 2024 (Q2 Gro 3.23.6.26)

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.

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-20820)

October 16, 2024 (Q2 Gro 3.23.6.27)

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