Winter'22 Release Notes

1.   Preface

This is a living document, and its contents may be updated often. Any changes to the contents of this document are listed in the Change record section. 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 PortalWinter'22 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.

1.1 Purpose of this document

This document provides information on the following for the Winter'22 release:

• Installation information

• Upgrade considerations

• 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

None.

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.   New features and enhancements

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

4.1 New Framework Features

4.1.1 Ability to parse Nested $ syntax. (JIRA ID: CP-2318)

Feature Description

This feature allows a Portal Admin to write a nested expression so that $ expressions can have an inner $ expression. This feature is helpful for the dynamic container to get the counts based on nested query expressions. To use this feature, we should set "enableNestedExpParsing" to true in global settings. Inner Expressions should be resolved to a simple type of data, like a string or a number but not an array or an object.

4.1.2 Unable to reload Dynamic Container's internal actors (JIRA ID: CP-2329)

Feature Description

This feature allows a Portal Admin to reload a particular child actor. In a dynamic container, a lot of child actors get rendered on the page based on the parent actor's record count and have the same actor name.

4.1.3 Support add/remove a value from $interaction values. (JIRA ID: CP-2309)

Feature Description

This feature allows a Portal Admin to add or remove a value from the selected list using an action other than the default checkbox selection action. For example, When a user removes a selected item from the cart, the main list is also updated to indicate that the item is deselected.

4.1.4 Enhance the existing CRUD operation to add a new Record with some data. (JIRA ID: CP- 2299)

Feature Description

This feature allows users to add new records with data provided by a user to a table without saving this record data to the backend. A user can add multiple records to a list view or card view before saving them in the backend.

4.1.5 Conditional mandatory fields (JIRA ID: CP-2214)

Feature Description

This feature allows a Portal Admin to configure one or more fields as mandatory based on evaluation criteria. For example, from the passport number and driving license number fields, a user should provide details only for one of these fields.

4.1.6 upsert CRUD operation (JIRA ID: CP-2299)

Feature Description

This feature allows Portal Framework to support updating an existing record using the edit operation along with adding a new record via a new method named "upsert". For the Upsert crud operation to edit the records, the edit action has to be configured at the record level.

4.1.7 $children Syntax & Contains function (JIRA ID: CP-2273)

Feature Description

This feature provides the following functionalities to a Portal Admin:

• $children: A Portal administrator can access all the children's data corresponding to a parent dynamic actor and count the number of records. This is helpful to show the number of records available or selected by an end-user.

• Contains: This function helps to figure out if a value is present in a list of values or not.

4.1.8 MultiSelection feature enhancements (JIRA ID: CP-2273)

Feature Description

This feature allows a Portal Admin to lock a row for selection/deselection based on some condition. For example, it was already checked in the back end. Use the enableRecord and enableSelectAll configurations for list view with multiple selections configured, so that a previously selected record can be disabled based on that condition.

4.2 Developer Tools

4.2.1 Search option should be available while defining the actor after import (JIRA ID: CP-2193)

Feature Description

This feature allows a Portal Admin to search for an existing Actor while building a Portal page after importing Nested Actor, Widget, and Nested Widget.

4.2.2 Implement the Create Actor Search functionality for Containers (JIRA ID: CP-2362)

Feature Description

This feature allows a Portal Admin to search for an existing container (Tabs, Steps, or Accordions) while building a Portal Page.

4.3 UI Components

4.3.1 Dynamic container entries rendered as Tiles (JIRA ID: CP-2326)

Feature Description

This feature allows a Portal Admin to configure the dynamic container entries to render as tiles or a list of records. In a tile view, the title from the parent actor will not be rendered, so we should have a title in the child actor rendered conditionally. Also, a portal admin can provide a toggle switch for an end user to switch between a list and tiles.

4.3.2 Information bubble feature (JIRA ID: CP-2298)

Feature Description

This feature allows a Portal Admin to configure an inline tooltip or information bubble for an input field with an info icon at the end of the field. In mobile view (for mobile devices), a user has to tap and hold the information icon to view the tooltip added through the bubble feature and the required tooltip for the list view.

4.3.3 Expand all / collapse all feature for accordion, dynamic container, and queue/card view (JIRA ID: CP-2280)

Feature Description

This feature allows the Portal administrators or developers, for the dynamic container, list-view, card-view, and accordion, to override the default behavior if needed to have a single expand or multiple expand as needed.

Before this Improvement, the default behavior was as mentioned below:

• Mint Theme:

  • Dynamic Container, Component GroupBy – Multi Expand

• MUI Theme:

  • Dynamic Container, Accordion – Single Expand

  • Component GroupBy – Multi Expand

4.3.4 Data-model component to show global loader when data is loading. (JIRA ID: CP-2316)

Feature Description

This feature allows a Portal Admin to configure a loader when a data-model component is trying to fetch data from the backend. To enable this the Portal Admin has to configure "showLoadingAnimation": true under the new tab named Messages in the Edit actor using JSON view.

4.3.5 Implement MUI Text Field Icons and Input Adornments (JIRA ID: CP-2143)

Feature Description

This feature allows a Portal Admin to add an icon as a prefix, a suffix, or an action to an input field. For example, use an icon button to hide or reveal the password or to show the currency symbol for the field. Different material Icons can be found at https://material.io/tools/icons/. All icons are non-interactive.

4.3.6 MUI Ability to lock slider and slider text field (JIRA ID: CP-2314)

Feature Description

This feature allows a Portal Admin to lock the slider or slider text or both and make them non-editable. A Portal Admin can now:

• Make the slider field read-only (the user is unable to edit the field but is able to use the slider to change the value inside of the field)

• Make both field and slider non-editable (slider cannot be clicked or dragged)

• Locking applies to both the slider and text field at the same time.

4.3.7 Display/Mask Password (JIRA ID: CP-2348)

Feature Description

This feature allows a Portal Admin to add a toggle password eye icon to the password field to display or mask the password. The Show/Hide icon is clickable, the user can validate the password by clicking the icon.

4.3.8 Support for group by in dynamic container's list view (JIRA ID: CP-2361)

Feature Description

This feature allows a Portal Admin to group all parent records based on a key in a dynamic container but without any expand/collapse feature.

4.3.9 Hide/Show icon on LWC login page (JIRA ID: CP-2348)

Feature Description

This feature allows a Portal Admin to add the show/hide icon for the password field to let users show and hide their input value when entering their password. To view the password, a portal user can click the Hide/Show icon. This feature is applicable for the Lightening Web Components (LWC) and to use this feature, the Portal Administrator has to install the latest version of the Portal Force package.

5.   Fixed issues

6.   Known issues

There are no known issues in the Winter'22 release of Q2 Portal.

7.   New and modified objects

There are no new objects added or modified in this release.

8.   New and modified REST APIs

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

9.   New and modified global methods

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

10.   Post 4.1013 release

Follow this section for the details on the issues fixed in the patches on the Winter'22 release.

10.1 Issue fixed in May 29 patch

10.1.1 Google Places API Issue (Jira IDs: CP-2625)

Fixed Version

• Q2 Portal version 4.1.2

Issue Description

When a user enters the address details in Q2 Portal, Q2 Portal uses the Places API provided by Google to auto-complete the address.

To provide better results to users, Google has introduced a new version of the Places API and communicated that the older versions are planned to be deprecated. To ensure that Q2 Portal continues to work after the older versions of the Places API are deprecated, the Places API version in Q2 Portal needs to be updated.

Resolution

The Places API version in Q2 Portal is updated to the latest available version. Perform the following steps to upgrade Q2 Portal to the latest patched version.

Steps

1. Log in to your Salesforce account.

2. Open the Configuration Manager application from the App Launcher ().

   

3. On the Configuration Manager tab, go to CL Portal > Available Upgrades.

   

4. On the Available Upgrades tab, In the Enter User Credentials section, specify the AWS access key and access secret.

   Note:

   You can use the existing AWS keys.

   

5. In the Enter Version section, in the Version box, specify 4.1.2 to upgrade Q2 Portal to the specified patch release.

6. Select Save.

   After a successful upgrade, a success message is displayed.

11.   Change record