SpinFire Manage 8.6.3 Release Notes
Overview
SpinFire Manage 8.6.3 adds improvements and fixes some critical bugs that may affect some customers.
Centro Version | 8.6.32701.19001 |
Latest supported ArangoDB version | 3.11.x |
Earliest supported ArangoDB version | 3.11.0 |
New Features
Allow optional database migration from ArangoDB to an internal (application-managed) database.
NB this only applies to SpinFire Publish (formerly known as CAD Publisher) and not SpinFire Manage (formerly known as Centro)
Other Improvements
Centro Web App installer automatically applies necessary permissions to CentroPool
Hide Catalog settings in Admin Application Settings tab
Remove SpinFireLicenseFolderLocation config item (was unused)
Remove Coordinate branding and consolidate navbar dropdown items
Replace PDF template from Actify to SpinFire Publish
Bug Fixes
Pipeline actions fail with authorization error
ArangoDB deploy module 30.00 fails on fresh installs
Parsing and handling of float values causes errors when locale uses comma as decimal separator
Cannot restore Snapshot in SFW
Pipeline services do not follow ProgramDataRoot setting
PageName is null when recording session metric for Error page
Failures from BucketController endpoints are not logged
Windows Server 2012 is no longer officially supported for Centro Web/File Server Environment and we recommend customers to update to a more recent Windows Server version. While the software may work with Windows Server 2012, we no longer include it in our testing process.
We removed MSMQ from the prerequisite installations. This communication configuration can still be used but is optional and not the default configuration.
If running Centro on a Windows 10 or a Windows 2016 system, one must create a MIME Type for wasm, otherwise the SpinFire Web module fails to load models.
Windows 11, Windows 2019 and Windows 2022 systems have this MIME type set by default.
SDK Users: Note that when building the CentroActionsIntegrationExample, adding a Core.Standard.dll
reference to the project is now also required alongside the previous references.
Supported Environments
Centro Web / File Server Environment | Minimum | Recommended | Optimum |
---|---|---|---|
Operating System | Windows Server 2016/2019/2022 (64-bit) Windows 10/11 (64-bit) | Windows Server 2016/2019/2022 (64-bit) | Windows Server 2016/2019/2022 (64-bit) |
CPU/Processor * | Intel i7 8 Core 4 GHz (or equivalent) | Intel i7 8 Core 4 GHz (or equivalent) | |
Memory | 16 GB | 64 GB | 128 GB |
Disk Space † | 10 GB free | 50 GB free | 100 GB free |
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.
Database Environment | Minimum | Recommended | Optimum |
---|---|---|---|
Operating System | Debian Linux v7.0+ Windows Server 2016 | Debian Linux v12.0+ Windows Server 2016/2019/2022 (64-bit) | Debian Linux v12.0+ Windows Server 2016/2019/2022 (64-bit) |
Memory | 8 GB | 16 GB | 32 GB |
Disk Space | 10 GB free | 20 GB free | 50 GB free |
Client Environment | Minimum | Recommended | Optimum |
---|---|---|---|
Browser | WebGL Compatible Browser
| Chrome FireFox Edge | Chrome / Edge |
Memory | 2 GB | 4 GB | 8 GB |
Prerequisite Installations
Microsoft .NET Framework 4.8
Microsoft .NET Framework 4.8 offline installer for WindowsInternet Information Services (IIS)
SDK: Visual Studio Projects using the Centro SDK must now target .NET Framework 4.6.2 minimum and turn on automatic binding redirects.