Mercury 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 CL PortalMercury 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 Mercury release:

• Installation information

• Upgrade considerations

• New features and enhancements

• Fixed issues

• Known issues

• New and modified objects

• New and modified 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.

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 CL 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 Developer Tools

Feature Description

Implementations are costly and time-consuming; despite multiple ways to create steps and configure fields the process can be very manual and subject to errors and unintended code issues.

To address some of these issues, we added tools to the developer’s arsenal to write code faster and cleaner, while enabling multiple developers to work in the same org.

4.1.1 JSON Autocomplete (Jira ID: CP-1504)

Feature Description

The JSON autocomplete feature dynamically suggests and fills in the proper syntax structure, based on key strings the administrator enters. This reduces the number of keystrokes needed, plus it provides guardrails to format the syntax correctly. Both of which should reduce the time it takes to write and check the code.

4.1.2 JSON Help (Jira ID: CP-1593)

Feature Description

The JSON help feature adds a help panel in the JSON Editor mode to assist with finding the correct Keys, Types, and Values when writing new code.

4.1.3 JSON Diff (Jira ID: CP-1505 and CP-1506)

Feature Description

The JSON diff feature automatically compares two versions of the code to identify the differences. This is done at the time of code check-in to prevent overwriting someone else’s code if there are multiple developers working in the same org. The deltas are highlighted in different colors to aid in finding and resolving any discrepancies. Developers can choose between the two conflicting code snippets or manually edit the code.

4.2 Mobile Components (Jira ID: CP-1498)

Feature Description

For a select set of components, have mobile-specific settings to allow for various behaviors that conform to mobile norms. This keeps the most important and most-often used elements in sight, while providing obvious affordances for lesser-used elements.

4.2.1 List/Card Toggle

Feature Description

The list/card toggle feature allows for responsive behavior to show larger datasets in a list view on larger screens and in a vertically stacked card view on smaller form factors.

4.2.2 Mobile Stepper

Feature Description

The mobile-optimized stepper feature will truncate the steps to put focus on the current step and retaining context with the previous and next steps. All other steps will be outside of the viewport, but easily scrollable. This allows for better visibility for the current step and most relevant other steps.

4.2.3 Splitting Multiple Elements in a Component

Feature Description

The Splitting Multiple Elements in a Component feature allows for related elements that are horizontally aligned to be split into two rows (stacked vertically) on smaller form factors to aid readability and touch interactions.

One example of this the slider component, which includes a text field and the actual slider element. The two elements are dependent and therefore are usual displayed side-by-side. The vertical align on smaller form factors enables the form field to be easier to read and the slider is easier to slide via touch.

4.2.4 Modal Dialog Resizing

Feature Description

The Modal Dialog Resizing feature automatically renders as a full screen overpanel on smaller form factors. This allows for use of the full width for form fields without having to pinch and zoom.

4.2.5 Adaptive Content

Feature Description

The adaptive content feature allows for device-specific conditional rendering for an adaptive experience. This can be removing or changing text or other components to focus on mobile-specific information or functionality.

4.2.6 Responsive Menu

Feature Description

The responsive menu feature allows for similar elements to be rolled up under a menu icon on smaller form factors. This frees up the viewport to focus on the most important content or tasks, while providing an affordance to view supporting content or controls.

4.3 Security Enhancements

Feature Description

Protecting customer data is at the forefront of any financial relationship. As hackers are getting more sophisticated, we must keep pace and get ahead of the next breach attempt.

4.3.1 API Security Enhancement (Jira ID: CP-1377, CP-1500, and CP-1592)

Feature Description

The API security enhancement pushes action details directly to the back-end. This prevents storing, even temporarily, any personal information on the front-end, where it is easier for hackers and other bad actors to access.

4.4 Other UI Components

Feature Description

Users are looking for very nuanced experiences, to help them get in and out of flows quickly and intuitively. Google Material has set many standards for UI components. But since it is mobile and socialcentric, there needs to be further refinement or augmentation for business contexts.

This continues to leverage and extend Material UI, as well as the development of new interactive components.

4.4.1 Vertical Stepper with Substeps (Jira ID: CP-1072)

Feature Description

The vertical stepper moves the step indicator to the left sidebar to allow for more steps without extending beyond the viewport. As such, scrolling through the steps or the main content area are independent to allow for more user control. Substeps have been added to further breakdown Steps in smaller, more digestible bits.

Substeps can be hidden until the user reaches the step, or persistent in the stepper.

4.4.2 Page Skeletons (Jira ID: CP-1487)

Feature Description

Page skeletons create the scaffolding for how a page will render by reserving space for each component while data or content is being fetched or rendered. This prevents partial rendering where objects move about the screen, making it unreadable until all components have been rendered.

In addition to the scaffolding, each component area can have its own spinner while others have rendered, indicating that some data is ready, even when other objects are being fetched.

4.4.3 Table Summary (Jira ID: CP-1568)

Feature Description

The table summary feature provides the ability to add a row (or multiple rows) to a table to display aggregate data like item counts and totals.

4.4.4 Document Tree View (Jira ID: CP-1011)

Feature Description

The document tree view feature provides for unlimited tiers of documents, as long as a parent is defined. This can be used to group similar or related documents categories.

4.4.5 Slider Control (Jira ID: CP-1589)

Feature Description

This slider enhancement allows for handlers to trigger actions upon release of the mouse click. This adds the ability to update other dependent fields without requiring another user-initiated action to keep all the field values in sync.

An example would be a quotes page based on terms selected via a slider. Once the slider is moved to (and released) a different term length, the quotes should be automatically updated. Otherwise, a user could mistakenly thing the quotes are applicable to the newly selected term.

4.4.6 Field-level Edit Control (Jira ID: CP-1484)

Feature Description

Field-level edit controls allow for the restriction of autocomplete and copy/paste functionality to populate a field, and force to user to think about the content they are entering.

The former is useful to prevent quickly re-entering the current address in similar form fields like mailing address or previous address. The latter will prevent erroneous entries where the content should be identical. An example would be “Password” and “Confirm Password”. If the content was incorrectly entered in the first field, it could be copied and pasted into the second, and the user would not know about the error until it’s too late.

4.4.7 Conditional RegEx (Jira ID: CP-1482)

Feature Description

Conditional RegEx allows for different input templates based on values from other fields.

This allows for different phone number formats for landlines vs mobile phones, or different formats for Tax Identification Numbers for Sole Proprietors vs other legal business types.

5.   Fixed issues

There are no issues fixed for this release of CL Portal.

6.   Known issues

There are no known issues for this release of CL Portal.

7.   New and modified objects

There are no objects added or modified in this release.

8.   New and modified APIs

There are no 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 3.4 release

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

• Q2 Portal

• CL Utilities

• CL Portal Force

• CL Common

10.1 Issue fixed in May 24 patch

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

Fixed Version

• Q2 Portal version 3.4.4

Issue Description

When a user enters the address details in CL Portal, CL 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 CL Portal continues to work after the older versions of the Places API are deprecated, the Places API version in CL Portal needs to be updated.

Resolution

The Places API version in CL Portal is updated to the latest available version. Perform the following steps to upgrade CL 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 3.4.4 to upgrade CL Portal to the specified patch release.

6. Select Save.

   After a successful upgrade, a success message is displayed.

11.   Change record