Skip to main content

FYB Connect Release Notes 2.0.X

Raise a support ticket

OVERVIEW​

This release of the FYB Connect App includes all fixes and enhancements that were shipped in the previous releases of the product. For details of the last release, please refer to the relevant release notes.

HOTFIX UPDATE 2.0.16​

BUG FIXES​

CM2SP NOT ARCHIVING ALL ITEMS​

Fixed issue with CM2SP not archiving all items in Saved Search connections

HOTFIX UPDATE 2.0.15​

SECURITY​

.NET 10 UPGRADE​

This application has been upgraded to .NET 10, providing improved performance, security, and reliability while keeping the application aligned with the latest Microsoft technology standards.

Action required: Administrators must ensure .NET 10 is installed on the application server as part of this upgrade.

BUG FIXES​

CONTAINER TITLE NOT SET WHEN MATCHING CLASSIFICATION NAME AVAILABLE​

Fixed issue where a container's title was not being set when it matched a classification title, resulting in blank container titles.

RECORD TYPE USUAL BEHAVIOUR NOT APPLYING CORRECTLY​

Fixed issue where the "Disable Record Type Filters" setting was not being applied to the record type behaviour check in record searches.

EMPTY TITLE ON ARCHIVE​

Fixed issue where records could be archived with an empty title.

CPU EXHAUSTION FROM CONCURRENT SCHEDULER RUNS​

Fixed issue where concurrent scheduler runs and unbounded parallelism could cause excessive CPU usage.

CM AND SP TOKENS EXPIRING DURING MANUAL ARCHIVE​

Fixed issue where Content Manager and SharePoint tokens could expire during a long manual archive operation, causing it to fail.

MANDATORY FIELD CHECKS ON CONNECTION CREATION​

Fixed issue where owner, home and assignee fields were incorrectly required when creating connections.

PACKAGE UPDATES​

  • @microsoft/signalr updated to v10.0.0
  • react-router-dom updated to v7.18.2
  • @typescript-eslint/eslint-plugin updated to v8.0.0
  • @typescript-eslint/parser updated to v8.0.0
  • eslint updated to v8.57.0
  • vite updated to v7.3.7
  • minimatch overridden to v11.0.1 (security)
  • brace-expansion overridden to v5.0.9 (security)
  • Microsoft.AspNetCore.Authentication.JwtBearer updated to v10.0.0
  • Microsoft.AspNetCore.Authentication.Negotiate updated to v10.0.13
  • Microsoft.EntityFrameworkCore updated to v10.0.0
  • Microsoft.EntityFrameworkCore.SqlServer updated to v10.0.0
  • Microsoft.EntityFrameworkCore.Tools updated to v10.0.0

LIMITATIONS​

SYNCING LARGE FILES​

Please note that syncing large files can lead to high CPU usage.

FILESHARES​

FILE TRANSFER LIMIT​

Due to limitations of the Content Manager Service API, the maximum file size that can be transferred to Content Manager using the 365|2CM and FileShare module is 2 GB. See Uploading Large Files to IIS / NET. Core / ASP.NET for more information.

3652CM​

FILE TRANSFER LIMIT​

Due to limitations of the Content Manager Service API, the maximum file size that can be transferred to Content Manager using the 365|2CM and FileShare module is 2 GB. See Uploading Large Files to IIS / NET. Core / ASP.NET for more information.

CM2SP​

SHAREPOINT ACCESS CONTROLS​

CM2SP does not support applying a Content Manager Record's access controls to the associated SharePoint Document when transferring Records

FILE TRANSFER LIMIT​

The maximum support file size of a single file when transferring Records from Content Manager to SharePoint is 500MB