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 Q2 PortalAugust 2023 version (4.3000) 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:

• Installation information

• Upgrade considerations

• System performance

• New features and enhancements

• Fixed issues

• Known issues

• New and modified objects

• New and modified REST APIs

• New and modified global methods

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.

1.4 List of abbreviations

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 Portal.

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 Portal without customizations under test conditions, see the Q2 Performance Benchmarking Guide.

5.   New features and enhancements

This section briefly describes the new features and enhancements added in this release.

5.1 Framework features

5.1.1 Range Field - Mandatory max and min values (Jira ID: CP-2459)

Feature description

The "min" and "max" values of the range field are mandatory starting from Portal version 4.3, and they can only accept numeric values. If a Portal Administrators does not specify a value for the "min" and "max" parameters or provides non-numeric values, an error message is displayed in the Portal Builder.

5.1.2 Search functionality for Application Map (Jira ID: CP-2495)

Feature description

With this release, a search bar is available in the Application Map allowing users to search and filter stages, actors, and overlays. This feature enhances the navigation experience for the Portal Administrators, particularly when dealing with a substantial number of stages, actors, and overlays.

5.1.3 Cloudflare onboarding - configure S3 buckets (Jira ID: CP-2432)

Feature description

Q2 is committed to a defense-in-depth security strategy and has recently transitioned from our previous Amazon Web Services (AWS) Content delivery network (CDN) to Cloudflare, with the implementation completed on May 14th, 2023.

5.1.4 Performance improvement of the dynamic container (Jira ID: CP-2376)

Feature description

With this release, the Portal code has been modified to enhance performance when a Dynamic Container contains a large number of records. Portal Administrators are not required to make any configuration changes to benefit from this improvement.

5.2 Features

5.2.1 Clearing the applied filters should be accessible (Jira ID: CP-2481)

Feature description

When a Portal user wishes to remove all the applied filters at the same time, they can click on the "Clear All" link. From this release, the "Clear All" link for filters is accessible and can be operated with using keyboard keys.

5.2.2 Handling validation in dynamic container (Jira ID: CP-2508)

Feature description

With this release, Portal Administrators gain the ability to configure the dynamic container to handle the validation of its child Actors on performing a normal, save, and submit action at the dynamic container level, and display the error messages to the user.

Upon user interaction, all the configured child actors undergo validation. Error fields and accordions are highlighted, and the user is automatically scrolled to one of the following locations:

• If the accordion is in the expanded state, the user is scrolled to the first error field within the accordion.

• If the accordion is in the collapsed state, the user is scrolled to the accordion itself, allowing them to expand it to locate specific error fields.

5.3 UI components

5.3.1 Readable information bubble as a label for non-editable or read-only (Jira ID: CP-2469)

Feature description

With this release, the information bubble or tooltip is visible when the components are configured as non-editable or read-only in a list or card view.

5.3.2 Picklist radio buttons are not accessible (Jira ID: CP-2443)

Feature description

In the list view, when the picklist was rendered as radio buttons, no label was assigned to them. As a result, the radio buttons were not accessible. Additionally, when multiple picklists were present, screen readers read the options from various picklists as if they were from a single picklist.

With this release, the Portal Administrators have the capability to assign a label or name to a picklist using the ariaLabel property. This enhancement allows the picklist items to be accessible when rendered as radio buttons in a list view.

6.   Fixed issues

This section describes the issues fixed in this release.

6.1 Summer23 trial org facing internal server error (Jira ID: CP-2505)

Description

Users using the Salesforce Summer23 Trial Org were facing an internal server error when accessing one of the following Portal features:

• Shows All tab feature

• Documents upload and extractions

• Document view in classic for Lighting form

After receiving the internal server error the user is unable to access any feature of the Portal.

6.2 A time change in the local PC reflects on the Portal Builder as well (Jira ID: CP-2537)

Description

If users change the time or time zone in their laptop or desktop, the Portal Builder shows the changed time instead of showing the time as per the Salesforce org.

6.3 System displaying validation error for fields with valid values (Jira ID: CP-2516)

Description

A validation error for fields with valid values is being displayed when a users moves through different screen in a Portal.

When a user has entered all the information on a Portal screen and moved forward with the flow, and then If the user suddenly starts the process from the beginning of the flow, the fields are shown with the previously entered values. It is expected that the user can continue with the flow without any error as all the fields have the valid values, which user have entered previously.

However, the user was enable to proceed with the flow as one of the fields was showing a validation error. The user could only proceed after re-entering the value in that field.

6.4 Performance: Dynamic container loading all content in one short (Jira ID: CP-2538)

Description

A dynamic container with more than 50 child elements was impacting the performance of a Portal as all the child elements of the dynamic container were loading at once.

The performance of the Portal is improved by loading the child elements of a dynamic container only after expanding that particular child.

6.5 Save action throws an error and is unable to save (Jira ID: CP-2170)

Description

A Portal Administrator was not able to save a Portal version having more than 400 Actors or 800 Actions, from the Portal Builder.

This issue is fixed now with the save action working fine and as per the designed behavior.

6.6 Ability to differentiate valid vs invalid usernames via forgot password API (Jira ID: CP-2515)

Description

The Portal users were able to differentiate between valid and invalid usernames using the forgot password functionality. The server responses of the API call contain visible differences between the forgot password API call with a valid username and with an invalid username.

This issue is fixed now with the server responses of the API calls containing a success status for both valid and invalid usernames.

6.7 Misalignment of the search icon in the mint theme (Jira ID: CP-2525)

Description

The search icon in the Application Map of a Portal with the Mint theme was not aligned properly.

This issue is fixed now and the alignment is displayed as per the theme design.

6.8 Importing an actor JSON into the 4.2 Portal which is exported from 4.1 is failing (Jira ID: CP-2510)

Description

A Portal Administrators were unable to import an actor JSON exported from a Portal release version 4.1 into a Portal release version 4.2.

The issue is fixed to allow the Portal Administrators to import an actor JSON exported from a Portal release version 4.1 into a Portal release version 4.2.

6.9 Error message stays even after a value is added on field change (Jira ID: CP-2503)

Description

When a Portal user enters a value to a required input field and removes the entered value, an error is displayed to the user. The error message would not disappear after the Portal user assigned a value to the field.

The issue is resolved after adding the cross-field validation configuration using the relatedFields property.

7.   Known issues

There are no known issues in this release.

8.   New and modified objects

There are no objects added or modified in this release.

9.   New and modified REST APIs

There are no REST APIs added or modified in this release.

10.   New and modified global methods

There are no global methods added or modified in this release.

11.   Post GA release

Follow this section for the details on the issues fixed in the patches on the August 2023 release of the following packages:

• CL Utilities

• CL Common

• CL Portal Force

• Q2 Portal

11.1 Issue fixed in November 24 patch

11.1.1 Issue with the Click Record handler with a Context menu in List view (Jira IDs: CP-2555 and PDRFF-2523)

Fixed Version

• Q2 Portal version 4.3.1

Issue Description

In a Portal version that is configured to display the record details on clicking a record using a Click Record handler, and a Context menu to perform additional actions such as edit, delete, and modify, if a user clicks outside the Context menu, it is expected that no action is performed and the Context menu closes.

However, currently such a Portal version is not working as per the expected behavior and when a user selects the Context menu to view the list of additional actions, and then clicks outside of the context menu, the Context menu closes but the record details are displayed to the user. This behavior is observed in the List view only.

Resolution

The code is improved to fix the issue and no record actions are performed when a user clicks outside the context menu.

12.   Change record