Overview

Centro 7.13.0 improves users' interactions with Catalog parts, updates importer support, and fixes a number of issues.

Centro 7.13.0 Changes

  • Importer Updates:

Importer

Supported Versions

Autodesk AutoCAD

2.5 to 2022 (2D and 3D)

Autodesk Revit

2015 to 2022 (3D)

Catia v5

R10 to V5-6R2022 (R32) (2D),

Up to V5-6R2022 (R32) (3D)

JT

Up to 10.6

Minor Changes

  • Admin Area

    • Admin Tags panel pagination error.

  • Catalog Parts

    • "Copy Download Link" option added to Resource menu.

    • Change Projects Catalog Part hamburger menu to visible show/hide eye button.

    • Fixed Catalog Part Page tab group cutting off in smaller windows.

    • Disable resource name inputs after they are uploaded.

    • Guarantee that the name of the download assembly .ZIP file matches the name of the top level assembly item.

  • Installation

    • Install every required redistributable as part of the WebApp installer.

    • Display the default connection to localhost when no HOST parameter is passed to setup.bat.

  • Misc.

  • Projects

  • SDK

    • Add a CallAsync overload with no return type in Centro.Public.

  • Search

    • Add modify date to search results (Search Page).

    • Display more than 12 Favorited Parts.

  • SpinFire Web

    • SpinFire Web engine updated.

Bug Fixes

  • Catalog Parts

    • Previous Activity log for deleted Project should show that Project has been deleted.

    • Tags added after upload are not added to the resource.

    • Error shown after editing an existing Link.

    • Resource selection count does not reset when switching parts in the assembly view.

    • The Resources tab doesn't display information about resources in certain scenarios.

    • Error when using Download History Report.

  • Miscellaneous

    • An error appears when the user tries to disable any user in list in an APM context.

    • Collapse state for Catalog Homepage sections may not remembered correctly.

    • Tags filter doesn't load filterable tags for the correct part when child is selected.

  • Pipelines

    • Concurrent CadToCatalog actions may generate a write-write conflict.

    • Processing the same CAD file with several "CAD to Catalog" do not add all tags to Catalog Part.

    • CAD to SpinFire Action does not create output folder when it doesn't exist.

    • It is not clear whether a retried action eventually succeeded or if it kept failing.

    • A job whose actions all succeeded after 1 or more retries should not be marked as Finished With Errors.

    • Pipeline Host fails to start in some network environments when there are a lot of Pipelines.

    • "Transparent background" option in CADToPNG action has no effect.

    • Pipeline in inconsistent status may allocate jobs while ARCHIVED.

    • Prevent ARCHIVED pipelines from being redeployed at start-up

  • Search

    • Error when purging resources when ShapeStore inaccessible.

  • SpinFire Web

    • Unable to load SFW files stored at location B while visiting from location A.

Supported Environments

Note

Centro 7.13.0 only officially supports ArangoDB 3.8.x or higher.

Note that starting with ArangoDB 3.9, an Enterprise subscription can no longer be provided by Actify. Customers are encouraged to migrate to the free Community version from here on, or otherwise purchase an ArangoDB subscription for extended ArangoDB support.
Related Topics

Centro Web / File Server Environment

Minimum

Recommended

Optimum

Operating System

Windows Server2012/2016/2019 (64-bit)

Windows 10 (64-bit)

Windows Server 2012/2016/2019 (64-bit)

Windows Server 2012/2016 /2019(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

Ubuntu Linux v12.04 / v14.10 / v15.04

Debian Linux v7.0 or v8.0

Debian Linux v8.0

Windows Server 2008 R2 (64-bit)

Windows Server 2012/2016 (64-bit)

Debian Linux v8.0

Windows Server 2008 R2 (64-bit)

Windows Server 2012/2016 (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

  • FireFox

  • Chrome

  • Microsoft Edge (on Chromium-Based)

Chrome

FireFox

Edge

n/a

Memory

2 GB

4 GB

8 GB

Prerequisite Installations