Skip to main content
Skip table of contents

Centro 7.0.1 Release Notes

Overview

Centro 7.0.1 adds a handful of new features and enhancements to help the user experience and to add some security improvements.

Enhancements

  • Allow users to change their password

  • Idle sessions will expire (users will be automatically logged out after a configured time expires; default 20 min)

  • Require a minimum length password

  • Job report feature to the Job Explorer (users can export to a file)
  • Remove need to add credentials in actions

  • Specific actions not be available for specified installation packages (example: CAD2CAD )

  • Create Catalog Part

Bug Fixes

  • Exception in console when user presses Select/Deselect all buttons
  • Admin area: "TypeError" in console, Projects tab shows nothing.
  • Menu flickers on Catalog page
  • Remove document key/rev/id from tooltips.
  • Missing tooltips over buttons on Catalog Parts in SearchResults
  • PipelineEditor: It is possible to select Activity tab for not deployed pipelines
  • Download selected button is active when user unselects all item in the tree
  • Empty Recycle bin is shown after restoring deleted resources
  • Admin menu flickers on page load
  • Existing uses of CADToSpinFireWeb need new upload_resource option
  • BOM Compare Main page - Text/fields overlapping in vertical view(Tablet)
  • After rerunning Recource to Catalog the job throws exception
  • Make hand cursor for section with arrow on CAD tab
  • The "Only select most recent jobs for each filepath" is showing the oldest job in Version 1.0.616.3334
  • Genetared SpinFire Web file is not shown on PartView
  • Make hand cursor for button on PartView page
  • Recent Event error icon shows the jobs from incorrect time range
  • Techsoft logo in the 3D PDF files
  • Filter doesn't work on PartView
  • Info tab is not updated when user changes pipeline selection
  • I.E. 11 Not working Properly with Catalog
  • Catalog: open parts in new tab doesn't work from homepage
  • AddCatalogResource stores file again even if no different
  • BOM Compare: Exception is thrown when user presses on thumbnail
  • Deployment script fails on arango 2.8
  • Trigger name cannot include certain characters (like '-'), but input allows this
  • Pipeline creates jobs for output files that don't match trigger conditions
  • Warning message is shown when user tries to publish CadAttributes to DataDoc
  • JobRequest: Fails when CatalogPart was not created from a CAD file
  • Unsuccessful thumbnail/SFW generation rows in resource table remain present even after selecting another part from the part tree.
  • Action duration text in JobsExplorer has same colour as the background
  • Re-running a job sometimes fails
  • Change slider position in case the user selects an another axis
  • Specify Site Name and Port Selection at Install for "Application of Parent Site" installs

Known Issues

See Centro 7 Known Issues

Supported Environments

Centro Web / File Server EnvironmentMinimumRecommendedOptimum
Operating System

Windows 7 (64-bit)
Windows Server 2008 R2 (64-bit)
Windows Server 2012 (64-bit)

Windows 7 (64-bit) Windows 7 (64-bit) 
CPU/Processor *

Intel i7 8 Core 4 GHz (or equivalent)

Intel i7 8 Core 4 GHz (or equivalent)

 

Memory8 GB16 GB32 GB
Disk Space 10 GB free50 GB free100 GB free

* It's recommended to have n+1 core processors where n = 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 EnvironmentMinimumRecommendedOptimum
Operating System

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

Debian Linux v7.0 or v8.0

Debian Linux v8.0Debian Linux v8.0
Memory8 GB8 GB16 GB
Disk Space

10 GB free

20 GB free

50 GB free

Client EnvironmentMinimumRecommendedOptimum
Browser

WebGL Compatible Browser

  • FireFox
  • Chrome
  • Internet Explorer 11+
  • Edge 

FireFox

n/a

Memory2 GB4 GB8 GB

Prerequisite Installations

 

 

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.