Release notes are essential documents that provide clients with detailed insights into the changes, enhancements, and updates applied to the Digital Agent platform. They serve as a crucial communication tool, informing clients about new functionalities, improvements, and other modifications that may be available to them.

Purpose:

The primary purpose of release notes is to ensure transparency and keep clients informed about the continuous development and enhancement of the Digital Agent platform. They help clients understand the value of the updates and how they might benefit from new features and improvements.

Site Clone Improvement - Blog Cloning

Behavior for Team Sites

Enhancement to the process of cloning blog entries from one team site to another! This update ensures that the author information is handled more efficiently and accurately. Here’s how it works:

Use Case 1a:

Scenario: Cloning a "Team A" website to create a "Team B" website.
Outcome: If the blog on the "Team A" site has an Alias set for the author, this Alias will be retained and copied over to the blog on the "Team B" site.

Use Case 1b:

Scenario: Cloning a "Team A" website to create a "Team B" website.
Outcome: If the blog on the "Team A" site does not have an Alias set for the author, the blog on the "Team B" site will automatically use the Hub owner of the "Team B" site as the author.

Important Note:

This improvement applies only to blogs cloned from "Team A" to "Team B" sites.
Regular blogs newly created on the "Team B" site will not be affected by this change.

We believe this update will streamline your content management process and ensure a smoother experience when cloning sites.

Sort Option Enhancement

Sorting Field: You can now easily sort the content within the update widget with Digital Agent logged in view, allowing you to quickly find the information you need.

How It Benefits You:

Improved Efficiency: Locate updates faster by sorting them according to your preferences.
Better Organization: Keep your widget content neatly organized for a more streamlined workflow.

This enhancement is designed to make your interactions with the platform more efficient and enjoyable.

Menu Label AODA (Bedrock Only)

An important issue affecting accessibility compliance was identified prior to the release of version 5.12, we discovered that menu labels were being used as pages, which did not meet AODA (Accessibility for Ontarians with Disabilities Act) compliance standards. An improvement was provided in release 5.12 which had to be delayed in order to allow customers ample time to adjust the pages / menu labels.

What You Need to Do:

Review the Report: A report detailing the impacted parent pages (excluding Menu Labels) was provided..
Manual Update Required: Update these parent hierarchy pages by converting them to Menu Labels.
Mandatory Fix: This step is essential to be performed in production prior to the deployment of release 5.14 in production.

Timeline:

There is ample time to perform the changes in production while release 5.14 is being tested by the Digital Agent team and customer UAT testing is being performed. This change cannot be delayed.

Expansion of Variables (Bedrock Only)

Dynamic Content is a feature in Digital Agent that allows the users to use information stored in our databases as part of the piece of content they are writing. This information can be used as part of the content itself or inside logic blocks to create if-else conditions and loops that will shape that content.

With this feature enables, not only, users to create future-proof content (ex, if they use this to expose their phone number, whenever that number changes in their profile, the content will be automatically updated), but also marketing users to create 'one-size fits all' contents, that will be populated with the information from the website that is using that piece.

Reference the DA Knowledge Base for additional Supporting documentation which can be found from the Jira Board under Project Pages - under Digital Agent Product, Content Utilization / Management, How to use Dynamic Content.

WCAG Enhancements (Bedrock Only)

The following are minor enhancements that have been made to continue WCAG AA compliance of Digital Agent Widgets for the Bedrock Theme.

Widget Scope

Event Widget Improvement
- Upcoming events”, and “Previous Events” will announced as tab,
- Event date and time will be announced
Blog Category Improvement
- Heading Level should only increase by one
- Alt text added to Element
Latest Blog Post
- Image Alt Text will not be present for reader
My Biography
- Heading Level should only increase by one
- Adding Tabindex to Biography Name , Job Title , Body
- Add Role , Alt Text and TabIndex to Biography Profile Image
- Tab Focus added for Disclosures
My Team
- Heading level should only increase by one on content
- Heading level should only increase by one in Disclosure
Contact Map
- Page does not start with a level 1 heading adjustment

These changes may impact the appearance of sites, and it is essential to review and test various elements to maintain consistency.

Key Points:

Styling Dependencies:
- Changes depend on the styling defined either at the site level or through the virtual theme.
Importance of Logged Out View:
- View sites in logged-out mode to identify elements that may need adjustments due to shifts in headings.
Testing Requirements:
- Virtual Theme Testing: Test a variety of sites on each virtual theme to identify potential changes needed. Once the release is deployed to production any changes to styling that are required in the virtual theme will need to be performed through the Digital Agent user interface.
- Template Testing: Test a range of sites based on cloned templates to identify necessary adjustments specific to those templates. Once the release is deployed to production any changes to styling that are required in the virtual theme will need to be performed through the Digital Agent user interface.

File Manager Distorted Image Improvement

After investigating the files thumbnail stretch view, we discovered instances where images exceeded their container's width, causing them to appear stretched.

To address this, Digital Agent has been upgraded to automatically resize images within the container when viewed in grid view. This enhancement ensures that images maintain their proper dimensions, improving the overall user experience in file manager view.

Twitter Logo (Bedrock Only)

Twitter Logo Change: The Twitter logo has been updated to "X." for the following widgets for clients that are on Bedrock. This will not impact clients that have their own custom Theme.

Team Profile
Pre-approved Profile
Footer - Reference to the twitter image was updated.
Biography

Enhancement to - French DA Application

For clients utilizing the French version of the Digital Agent (DA) application, the theme section of the website creation tool has been enhanced. This update focuses on improving the user experience by adding more detailed French content.

Information:

Enhanced French Details:
- The theme section now includes additional French content, providing a richer and more comprehensive user experience for French-speaking users.
No Functional Changes:
- While the content has been improved, there are no changes to the existing functionality. The enhancements are purely focused on content enrichment.

SVG Support With Cropper

For clients that have Dual Logo Management capability available and enabled, the Dual Logo Management feature has been enhanced to support SVG (Scalable Vector Graphic) file format. Continue utilizing the same user interface and selecting SVG along with PNG and JPG which are available today.

SVG (Scalable Vector Graphics) is often preferred over PNG (Portable Network Graphics) or JPG (Joint Photographic Experts Group) in certain situations due to its unique characteristics:

Scalability: SVG images are resolution-independent and can be scaled to any size without losing quality. This makes them ideal for logos, icons, and graphics that need to look sharp on screens of varying sizes and resolutions. PNG and JPG images, being raster-based, can lose quality when scaled up.

File Size: SVG files are typically smaller in size compared to PNG and JPG files, especially for images with complex shapes and gradients. This can lead to faster load times for web pages and lower bandwidth usage.

Locator Service Enhancement

Current State

Digital Agent’s "Locator" feature enables the sharing of detailed information about individuals, teams, branches, and regions for consumption and with third-party service providers. This feature is powered by the Digital Agent’s Locator API.

Digital Agent’s locator API has information as JSON response which clients consume for applications such as “Find an Advisor”

Current Endpoint

Request Type	Digital Agent Locator Standard API Endpoint
Advisor	/advisors
Branch	/branches/{branch-id}
Office	/offices/advisors
Braches	/branches

Enhancement

Individual advisor, that is a member of a team, will have additional information on the Team website. Detail information below on the changes for each request type.

Advisor name, phone, email, job title, profile photo, advisor website and Team website.

/advisors endpoint

An aggregate process of the individual advisor profile to have the Team website url. An individual profile is going to have a teamWebsites field. Team website is a json array format.

API Request/Response

Request URL:/advisors

Parameter: ?api_token={token}&name=Namexxx

Response:

[

{

"id": "419803",

"displayName": "Namexxx, CFA",

"sortingName": "Namexxx L.",

"position": "Director - Advisor",

"position2": "Senior Manager - Portfolio Focus",

"position3": "",

"bio": "",

"email": "name.xxxx@domain.com",

"photo": 561413,

"city": "City Name",

"address": "343 Best Street, Suite 34",

"province": "ON",

"postalCode": "L7K0W5",

"phoneNumber": "111-222-3333",

"website": "http://customer_environment.com/web/name.xxx",

"teamWebsites": [

{

"name": "Team Name 1",

"website": "http://customer_environment.com.com/web/teamgroup"

{

"name": "Team Name 2",

"website": "http://customer_environment.com/web/Team2group"

}

….

]

/branches/{branch-id} endpoint

API Request/Response

Request URL:/branches/{branch_id}

Parameters: ?api_token={token}

Response:

[

{

"id": "419803",

"displayName": "Namexxx, CFA",

"sortingName": "Namexxx L.",

"position": "Director - Advisor",

"position2": "Senior Manager - Portfolio Focus",

"position3": "",

"bio": "",

"email": "name.xxxx@domain.com",

"photo": 561413,

"city": "City Name",

"address": "343 Best Street, Suite 34",

"province": "ON",

"postalCode": "L7K0W5",

"phoneNumber": "111-222-3333",

"website": "http://customer_environment.com/web/name.xxx",

"teamWebsites": [

{

"name": "Team Name 1",

"website": "http://customer_environment.com.com/web/teamgroup"

{

"name": "Team Name 2",

"website": "http://customer_environment.com/web/Team2group"

}

….

]

/offices/advisors endpoint

API Request/Response

Request URL: /offices/advisors

Parameters: ?api_token={token}&branches=15939,15247

Response:

[

{

"id": "419803",

"displayName": "Namexxx, CFA",

"sortingName": "Namexxx L.",

"position": "Director - Advisor",

"position2": "Senior Manager - Portfolio Focus",

"position3": "",

"bio": "",

"email": "name.xxxx@domain.com",

"photo": 561413,

"city": "City Name",

"address": "343 Best Street, Suite 34",

"province": "ON",

"postalCode": "L7K0W5",

"phoneNumber": "111-222-3333",

"website": "http://customer_environment.com/web/name.xxx",

"teamWebsites": [

{

"name": "Team Name 1",

"website": "http://customer_environment.com.com/web/teamgroup"

{

"name": "Team Name 2",

"website": "http://customer_environment.com/web/Team2group"

}

….

]

/branches endpoint

No changes needed on this API.

API Request/Response

Request URL: /branches

Parameters: ?api_token={token}

Response:

[

{

"id": 15846,

"name": "Longview",

"city": "Longview",

"address": "1302 Judson Rd.",

"province": "TX",

"postalCode": "75601",

"phoneNumber": "903-753-5343",

"website": "http://us.rbcwealthmanagement.com/web/longview",

"distance": 0.0,

"latitude": 32.5154,

"longitude": -94.738625,

"advisors": 6

…

]

Informational:

Locator API Testing:

All clients utilizing the Locator API will need to test internal applications utilizing the API. The change is in the structure of the JSON and should not have any impact for if the consumer application follows proper JSON structure utilization.

SSO Environment Upgrade

This release includes essential infrastructure upgrades for clients with Single Sign-On (SSO) enabled and is part of the ongoing maintenance / upgrades to Digital Agent.

Informational:

SSO Functionality Testing:
- All clients with SSO enabled in production must test SSO login to ensure it continues to work as expected in UAT.
  .
UAT SSO Bypass Turned Off:
- To eliminate confusion regarding login framework in use, the bypass of SSO in the User Acceptance Testing (UAT) environment will be disabled.
Sign-Off Requirement:
- Sign-off on release 5.14 is confirmation that the SSO functionality is performing correctly post-upgrade.

In-Application Support Capability

Digital Agent now offers interactive in-app tutorials (Add-on) designed to enhance user experience by providing step-by-step guidance directly within the application. These tutorials help users navigate complex features and processes, ensuring they can make the most of the software without leaving Digital Agent.

This feature is tailored for new users accessing Digital Agent for the first time and serves as a valuable refresher for existing users. Upon a user’s first login, they will be guided through an onboarding tutorial to familiarize them with the platform's core functionalities and features.

If interested please contact your sales account manager.

Dashload Customer Domain Improvement

Dashload Improvement addressed issues related to exceptions in the publishing updates for custom domain pages, by implementing changes to Dashload for the custom domain process. A particular issue involving a Biographie widget was identified, where there was a mismatch leading to the "Read more" link pointing to the root domain instead of the custom domain. This issue was rectified through corrections in the custom domain configuration.