Centro 8.1.0 Release Notes

Overview

Centro 8.1.0 adds more Mesh improvements, allows user account migration from LDAP to AzureAD, and fixes a number of bugs.

Centro 8.1.0 currently supports up to ArangoDB 3.10.x.

Starting with Centro 8.2.0, Actify will discontinue active support for ArangoDB 3.8.x and 3.9.x. We recommend migrating to ArangoDB 3.10.x.

Centro 8.1.0 Changes

• SDK: Added async variant of AbstractAction member PerformAction().
  Deprecated non-async variant.

• Mesh Changes:

  • Implement Mesh Rules to allow restricting file types to particular location types

  • Track Mesh Rules changes using Activities

  • Enable uploading to prem Location from cloud Location Catalog page

• Implement LDAP to AzureAD migration step via the Admin Area.

• Add Display Name when showing username in project permissions dialog (#CS-274) .

• Implemented scripts to allow merging secondary 3DSearch indexes to a central location’s index

• Show a Pipeline Scope Summary when viewing Pipeline details

• Made all issued cookies issued follow the SecureCookies setting

• Made filter selectors have a border when active. Clear filter buttons are now disabled (but visible) when inactive.

• Disabled `copyexternal` endpoint.

8.1.0 Bug Fixes

• Admin entry in top-right menu not working for some users.

• Comments for SFW resources not belonging to the Primary Resource.

• Some download endpoints not checking for IsInRecycleBin.

• Share State Snapshot errors after viewing a CAD view in SFW.

• Incomplete ACL preview for Modify.

• ShapeSearch diagnostic scripts.

• Icon not loading when viewing the version history of a deleted file.

• Not being able to add role permissions to a project in the Modify dialog.

• Pipeline details are not editable in some cases.

• Strange checkboxes appearing in the JobsExplorer page.

• Items on right-side navbar dropdown don't take all available width.

• Make it clear which page is open on the Activity tab of the pipeline.

• When viewing the version history of a deleted file, the icon is not loaded.

• SDK: Centro integration SDK tutorial lacks LogsFolderLocation key in the example App.config.

Supported Environments

It's recommended to have n+1 core processors where n is the number of total concurrent jobs running.

^† The amount of available free space is dependent on the amount and size of files and revisions uploaded as resources to the Catalog.

Prerequisite Installations

• Microsoft .NET Framework 4.8
  Microsoft .NET Framework 4.8 offline installer for Windows

• Internet Information Services (IIS)

• Microsoft Message Queuing (MSMQ)

• SDK: Visual Studio Projects using the Centro SDK must now target .NET Framework 4.6.2 minimum and turn on automatic binding redirects.