Spring’22 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.
This document provides information about the new and enhanced functionality in Q2 Portal, Spring’22 General Availability (GA) release. You can access the release notes of the previous releases from the Q2 Customer Portal or from the Q2 Lending Help Center.
The contents of this document are applicable to all the customers who have installed the Q2 PortalSpring’22 version (3.8002) for the first time or have upgraded from an earlier version.
1.1 Purpose of this Document
This document provides information on the following for the Spring’22 release:
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
| Abbreviated Term | Description |
|---|---|
| JS | JavaScript |
2. Introduction
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.
3. 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.
4. Upgrade Considerations
For information on the upgrade steps, see release-related steps in the Q2 Product Upgrade Guide.
5. System Performance
To view the batch jobs performance statistics for Q2 Portal without customizations under test conditions, see the Q2 Performance Benchmarking Guide.
6. New Features and Enhancements
This section briefly describes the new features and enhancements added in the Spring’22 release of Q2 Portal.
For a detailed description of the new features and enhancements, see the following guides published over the Q2 Customer Portal:
Q2 Portal User Guide
Q2 Portal Administration Guide
6.1 New Features
6.1.1 Configure timeout for custom remote action API calls (Jira ID: CP-2175)
Feature Description
By default, all the API calls in Portal are set to timeout after 30 seconds. However, the Salesforce allows to set the timeout to a maximum of 120 seconds. This feature allows Portal admin to configure timeout at each action level or at the application level in global settings.
This will help the Portal admin in the cases where an API takes more than 30 seconds to send a response and needs the API call to happen in a single call.
6.1.2 Widget Library (Jira ID: CP-2152)
Feature Description
This feature allows a Portal admin to add a particular Actor (along with all its dependencies) to the Widget Library through a simple user interface. This allows Portal admin to reuse an actor easily.
After adding an Actor to the Widget Library, if required, a Portal admin can also make the changes to the added Actor.
6.1.3 Add or edit a Widget version to JSON (Jira ID: CP-2155)
Feature Description
This feature allows a Portal admin to add or update a version number to the Widget when adding or editing a Widget to the Widget Library. The version details are maintained at each Widget level.
6.1.4 Portal Theme Selector (Jira ID: CP-2069)
Feature Description
This feature allows a Portal admin to add, remove, and update one or more CSS files to their Portal application. The Portal admin can then use one of the uploaded CSS files as theme for their Portal application.
This feature is available only through the Portal user interface.
6.2 Developer Tools
6.2.1 Hiding the dog-ear for agents (Jira ID: CP-2070)
Feature Description
This feature allows Portal admin to restrict an agent's access to the Portal Builder. The agent's Salesforce profile must be modified to revoke access to the ComponentStructure and NavigationStructure objects. This ensures that the dog-ear is hidden.
6.2.2 Add custom classes to MUI Theme (Jira ID: CP-2037)
Feature Description
This feature allows the Portal admin to configure custom classes at actor level at different DOM levels.
6.2.3 MINT Global Loader (Jira ID: CP-2129)
Feature Description
This feature allows Portal admin to configure the Global Loader to the Mint Theme by selecting the Position 'Global'. A Portal user will see this loader until and unless the page gets loaded.
6.2.4 Disabling trigger on structures based on org setting (Jira ID: CP-2107)
Feature Description
This feature allows Portal admin to disable triggers based on the org parameter setting for "Disabling Triggers". This is helpful when importing or exporting records from one Org to another.
6.2.5 Use Right feature for JSON diff tool (Jira ID: CP- 2149)
Feature Description
Along with the "use left" button, a "use right" button is added to the JSON diff tool. When comparing JSON data using the JSON diff tool, this feature allows the Portal admin to select the JSON data appearing on the right side instead of the data shown on the left side.
6.3 New UI Features
6.3.1 Align the text for Stepper (Jira ID: CP-2160)
Feature Description
This feature allows a Portal admin to change the alignment of Stepper labels. In a horizontally oriented Stepper, a Portal admin can align the labels to right or bottom.
6.3.2 Editable checkbox is removed for Queue View (Jira ID: CP-2151)
Feature Description
This feature removed the Editable checkbox from Queue View and makes the Queue View as read-only.
6.3.3 Dynamic Container Actor (Jira ID: CP-2022)
Feature Description
This feature allows Portal admin to use the dynamic container actor in MUI. The dynamic container actor is already available in MINT.
In MUI, in a dynamic container only one accordion can be expanded at one time. When a user expands another accordion, the previously expanded accordion is closed. However, in MINT, a user can expand all the accordions independently.
6.3.4 Search and filter on multiple values in a picklist (Jira ID: CP-1961)
Feature Description
This feature allows Portal users to search and filter on multiple values in a picklist. When a user starts typing a word, the system autocompletes the word and shows the related values to filter. The feature is helpful when a user wants to search big picklists such as countries, party type, list of users.
A Portal admin can also customize the message that will be displayed when no matching value is found in the list.
6.3.5 Configure the option text for reference fields (Jira ID: CP-2046)
Feature Description
This feature allows Portal admin to configure the option text for reference fields thus allowing Portal users to query multiple fields inside the reference query without effecting the display text of reference field drop-down.
6.3.6 Touch target optimization for mobile users (Jira ID: CP-1584)
Feature Description
This feature allows mobile users to see and use larger touch targets. In mobile view all the bottom buttons at an actor level will spread total viewport with each button of equal width.
The Portal admin has an option to stack the buttons using additional configuration ("stackActions") at actor appearance level. This applies to primary and secondary action buttons and brings these to full width or 50/50. If there are three buttons the ratio is 33/33/33.
6.3.7 Context-sensitive keyboards for mobile users (Jira ID: CP-2060)
Feature Description
This feature allows mobile users to use mobile-optimized keyboards, so that they can enter numeric values.
For fields allowing for only numeric input, the numeric keypad is automatically invoked on smaller form factors. This includes, but is not limited to, fields like phone numbers, dates, currency amounts, social security numbers, taxpayer identification numbers, and postal codes - with and without text entry templates.
7. Fixed Issues
This section describes the issues fixed in the Platinum release of Q2 Portal.
Jira ID | Issue Description |
|---|---|
The Apply functionality is not working for filter | |
The timeout configuration is not working having more than one record action | |
For existing actor, the fields shouldn't show editable whereas the actor is not editable | |
On Using existing query with Picklist data type navigates blank page | |
The reference query does not take the default value | |
The unique actor name should be allowed in MUI/MINT separately | |
Dates comparison failing with latest math.js version (9.5.0) | |
Stepper actor is not able to add to widget | |
The editable form shouldn't be enabled on creating new queue view actor | |
Unable to create a new actor with existing VF page | |
The fields are interchanging for JSON diff while import actor/nested actor | |
The mint theme is not working, it loads then navigates blank page | |
Disclosure should be able to close on using dialog directly. | |
Delete Theme shouldn't be active once deleted and created again with the same name | |
Save functionality should be validated for update a theme | |
Creating theme with same name should throw error message | |
Upload/Create theme [TA1] should validate only with CSS files | |
The update of any record with the existing data creating a new record | |
For Accordion Entry Collapse is not working | |
Save is not working - Dynamic container | |
Datetime showing incorrectly | |
Fix URL syntax to make it work with lightning community | |
Highlight Entry by condition is not working for List/Card view | |
In detail view, if "queryWithDefaultNew": true is not configured in the property. in the API newRecord method is getting called instead of query method | |
The Multiselect Picklist Auto Complete field is not allowing all the values at a time | |
Add null check for branding value in converters | |
The importing of an actor on new VF page shows incorrect JSON locally w.r.t imported | |
When applying text field variant as filled the field UI overlaps | |
If aria-label is missing in accessibility in appearance JSON, error is thrown, and screen goes blank | |
Field Columns not configurable from builder in MUI in Detail View | |
Detail view readable form shouldn't display all the records | |
Highlighting specific fields entry not working. | |
Define a data query for an actor, under section name and section title, don't drag/drop the fields name. After defining the data query for an actor, it shows fails to load | |
In define data query when swapping between existing component structure name | |
The Auto triggering dependent save actions navigates blank page on saving and reloading the page | |
For currency, validation functionality is not working | |
Builder versions popup shows wrong Portal Document version. | |
Group_BY_Collapse/Expand and Entry Collapse/Expand functionality is not working Editable Queue View | |
The title is missing in Queue view for grouping | |
The builder has issue while selecting parent-child category | |
The JSON diff page was showing differences even for a cloned page. | |
The Import/Export actor/widget wasn’t taking values and showing conflict for the following attributes:
| |
The field Headers are not representing as required field for list view | |
Highlight functionality is not working for Queue Editable form | |
Mui Filter Panel does not display its content | |
Uploading document as content document through community link wasn’t working | |
Space in actor name should be disallowed | |
The Auto complete Address field is not displaying address properly for Mint theme | |
The label alignment section of Stepper must be removed from the builder for MINT | |
The actor is losing [TA2] data when user rename the query and the updated query is not listing under components | |
When an iFrame is loaded as part of a page, the browser network shows multiple APEX call which is not the case without an iFrame | |
As the local "sortBy": "Sort by" is mentioned which is different than "sortBy": "Sort By" from the imported one, its always showing the difference in JSON structure and the JSON are not collapsed | |
Fields like SSN and Account number value need to be encrypted like ***-*-1234. | |
Value from number-related field should not be string | |
Not able to calculate total amount in multi-step calculation | |
For a field as link and for which the defaultValue is not a mandatory field, but if user don't provide defaultValue, then field as link is not working | |
Range slider in List View grows actor width | |
Update "Portal JS CSS files to load" static content to point to 3.7 AWS URLs | |
When a google address without postal code is selected, the postal code field is showing previously entered data and not getting reset | |
When we try to trigger an upload action from a normal button through actions property in handler, it’s not getting triggered | |
Currency setting not working |
8. Known Issues
This section briefly describes known issues known in the Spring’22 release of Q2 Portal.
Jira ID | Issue Description |
|---|---|
The increment/decrement feature is not working for all the fields across the Portal and a user can directly enter the value. For example, for a currency field with a value 2000, if a user wants to increase the value to 2010, the increment button is not working. User must specify 2010 directly in the currency field box. | |
The JSON diff tool is not working for Mac Safari browser |
9. New and Modified Objects
This section briefly describes the new and modified objects in the Spring’22 release of Q2 Portal.
For more details on the added and modified objects, see Q2 Portal Data Dictionaries Guide.
9.1 New Objects
There are no new objects added in the Spring’22 release of Q2 Portal.
9.2 Modified Objects
There are no objects modified in the Spring’22 release of Q2 Portal.
10. New and Modified APIs
There are no APIs that are added or modified in the Spring’22 release of Q2 Portal.
11. Global Methods
This section briefly describes the global methods that are added or modified in the Spring’22 release of Q2 Portal.
For more details on the added and modified global methods, see Q2 Portal Global Methods Guide.
11.1 New Global Methods
There are no new global methods added in the Spring’22 release of Q2 Portal.
11.2 Modified Global Methods
There are no new global methods modified in the Spring’22 release of Q2 Portal.
12. Post GA Release
Follow this section for the details on the issues fixed in the patches on the Spring’22 release.
12.1 Issue fixed in June 19 patch
12.1.1 Google Places API Issue (Jira IDs: CP-2630)
Fixed Version
Q2 Portal version 3.8.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
Log in to your Salesforce account.
Open the Configuration Manager application from the App Launcher (
).
On the Configuration Manager tab, go to CL Portal > Available Upgrades.
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.
In the Enter Version section, in the Version box, specify 3.8.2 to upgrade Q2 Portal to the specified patch release.
Select Save.
After a successful upgrade, a success message is displayed.
12.2 Issue fixed in September 5 patches
12.2.1 Portal with large number of Actors and Actions not saving from Portal Builder (Jira ID: CP-2540)
Fixed Version
Q2 Portal version 3.8000
CL Common version 3.8002.7
Issue Description
A Portal Administrator is not able to save a Portal version from the Portal Builder if the Portal version has more than 400 Actors or 800 Actions.
Resolution
The code is improved to allow a Portal Administrator to save a Portal version with up to 430 Actors and 850 Actions.
13. Change Record
| Change Date | Description of Change |
|---|---|
| May 2022 | Published release notes for Spring’22 General Availability release. |
| September 2023 | Added section 12.2. |
| June 19, 2024 | Added section 12.1. |