Skip to main content

CM2WebShare Release Notes 5.0.x

Raise a support ticket

OVERVIEW​

This release of the FYB CM2WebShare Connector includes all fixes and enhancements that were shipped in the earlier releases of the product. For details of the earlier release, please refer to the relevant release notes.

BREAKING CHANGES

Custom theme CSS files will need to be updated to change the ID's of the elements to suit the new CM2WebShare application. Please refer to the CSS Guide for how to update to the latest design.

DEPENDECY UPDATE 5.0.15​

PACKAGE UPDATES​

The following packages have been updated:

  • word-wrap updated to 1.2.4
  • tough-cookie.js updated to 4.1.3
  • crypto-js updated to 4.2.0
  • @babel/traverse updated to 7.23.2
  • axios updated to 1.6.0
  • browserify-sign updated to 4.2.2
  • postcss updated to 8.4.31

RELEASE 5.0.12​

NEW FEATURES​

NEW TECH STACK​

The application has been rewritten with new frontend and backend frameworks and is now built with React JS and .NET Core which significantly increase performance and stability.

NOTES ADDED TO RECORD ON USE​

When editing, viewing or downloading a record using CM2Webshare a note is added to the record in Content Manager.

TRUNCATE TITLE​

If the table value is larger than the column the titles will be truncated.

ENHANCED FEATURES​

FASTER TABLE LOAD​

CM2WebShare has significantly reduced table load times compared to previous versions. This is due to the new tech stack and in addition subfolder content is only loaded when the subfolder is expanded.

EMAIL ICONS​

Emails will now display with an email icon instead of a blank file icon.

BUG FIXES​

Resolved an issue that prevented ePathway table links from loading when clicked on. This was due to a change in the URL encoding format.

IMPORTING OF LEGACY SETTINGS​

Resolved an issue that prevented older versions of CM2WebShare's settings being imported into the lastest version of CM2WebShare.

LIMITATIONS​

Any links that were made with CM2WebShare 3.0.1 and below must be recreated using the latest version.

ELECTRONIC RECORD FILTERING​

Electronic record filtering can only be used on electronic documents that are not stored within a hierarchical structure.

COLUMN LIMIT​

It is recommended that no more than five or six columns are used per table. More columns may result in unintended visual issues with the table.