05/14/2024 - v7.2.1 - STRATUS

Yellowstone Release Known Issues Log

Notice

This Release Notes article is published approximately one week before the actual release date to provide companies with information about the upcoming release. Information within this article may change. Release Notes are then integrated into the STRATUS Knowledge Base within one week of the release date.

Publish Updates

The following is a list of updates related to the STRATUS Addin for Revit and AutoCAD used for publishing models to STRATUS. This information will help companies determine if they want to update software. Customers who encounter a publish issue that has been fixed by an updated version of the software will be required to install the latest software version.

To update to the latest installers see the Installation of GTP Software on Windows article for more information.

• Revit and AutoCAD Addin - Yes - Required for FLEX model viewer publishes

• STRATUS Workstation - Yes - Recommended, but not Required

• RazorGage Workstation - No

• Print Workstation - No

• Lightning - Yes - Recommended, but not Required

Release Highlights

Added Password Requirements to Enforce NIST Guidelines

Added Password Requirements to enforce NIST Guidelines. No one will be forced to change their password in this release unless a new password is created.

See the Password Requirements article for more information.

Summary

• Characters required include:

  • A - Z

  • a - z

  • 0 - 9

• Password restrictions

  • 16 characters minimum and 64 characters maximum

  • Last 3 passwords cannot be re-used

  • Password must be reset annually

  • While special characters are allowed they are not required.

Updated Item Numbering and Tagging

Major updates have been made to Item Numbering and Tagging.

Summary of the Changes to Numbering and Tagging

Open

The STRATUS.Part.Number will now be treated consistently across the STRATUS platform, similar to how STRATUS.Part.AssemblyName is currently used. This means STRATUS.Part.Number will be the primary reference for part numbers in all contexts, ensuring that it is always up-to-date.

1. The Renumber Parts When Creating or Modifying Assemblies setting has been moved to the Numbering Schemes page for project-level control.

2. The Use Number Rule Setting for Matching Parts and Matching Parts Get Same Item Number settings have been removed since you can control this with the Numbering Rules. We interrogated our database and found that every STRATUS customer already had these turned on.

3. The Enable 'Authoring Software Is Right' For Item Numbering in the Company and Project Admin has been removed since the same can be achieved with the Authoring Software is Right numbering rules.

4. STRATUS part tags ONLY display the value from/in STRATUS.Part.Number property.

5. The renumber button updates the STRATUS.Part.Number property only

6. The Display - Item Numbers toolbar button has been renamed to Display Tags And Item Numbers Toolbar. It no longer creates tags when pressed, it only shows or hides existing tags. Number and tag creation can still be automated for assemblies by using the Renumber Parts When Creating or Modifying Assemblies setting in the numbering scheme.

7. Tags will now dynamically display the current values of whatever property they are referencing. For standard item number tags, they will reference the STRATUS.Part.Number property. Any tags that reference a blank value will be removed upon deletion of the value.

   1. Of note: Existing static tags will not disappear with this update, but will be updated to dynamic tags once a change has been made to the STRATUS.Part.Number property or once new tags are placed.

8. These functions have now been broken out to allow discrete control over the creation of part numbers and tags. These are as follows:

   1. Renumber Parts - Only acts to renumber parts based on numbering rules and schemes. There are no changes to the functionality in how numbers are generated on parts. Additional functionality has been added that allows you to now filter to parts in viewers and renumber only them.

   2. Create Tags - Creates tags according to your numbering scheme for any parts that are not already tagged, but that have a value in STRATUS.Part.Number. Additional functionality has been added that allows you to now filter to parts in viewers and tag only them.

   3. Renumber and Tag Parts - Operates the Renumber Parts and Create Tags functions sequentially.

9. The “Bulk Delete - Delete All Item Numbers And Tags” functionality has been replaced by two distinct functions and they are as follows:

   1. Delete Part Item Numbers - Removes values applied to the STRATUS.Part.Number property for all parts in the view. Any tags that now reference a blank value are also removed.

   2. Delete All Tags - Removes any visible tags when this button is clicked.

10. Project roles have been added to control the availability of these new and modified features in the models, packages, and assemblies viewers.

Project Roles

Open

Settings - Numbering Schemes

Configuration settings for Item Numbering and Tagging rules has been moved to the Naming and Numbering tab. Below is the Numbering Schemes tab.

Custom Tags

Custom Tags for Item Numbering, Notes, and Properties display dynamically as model information changes, while Field and Alias tags are static.

Added Dashboard Column Visibility Setting

Added to all dashboards a Column Visibility Settings feature which enables each user the ability to control columns they see in each report. Admins will no longer need to create entire new reports to limit or expand columns.

To use the Column Visibility Settings feature:

1. On the report, click the Column Visibility Settings button.

2. The Column Visibility Settings dialog will display with a list of the report fields contained in the report. By default all columns are checked visible.

3. Uncheck or Check individual report fields, or click the checkbox adjacent to the Column Visibility Settings heading to check or uncheck all checkboxes. When done click Apply.

4. Only the checked columns will be visible.

5. Button Indicators:

   1. By default, when all Columns are checked both bars will be hollow.

   2. When one or more Columns are unchecked, one bar will be shaded.

       

6. Notes:

   1. When a user switches to a different report that has not been customized, all report field columns in the new report will be checked by default.

   2. Each report will retain the user's specific settings until one of the following occurs:

      1. The user updates their selection of visible items on each specific report.

      2. The report is updated by an administration under Admin > Company > Reports in which case all report fields will be visible.

Updated Attachments Table Rollup

Updated the Attachments table for Packages and Assemblies to rollup all associated attachments. Expand any Source Type to display the rollup content (Ex. PDV, CSV, image, Markup Tools, etc.).

Added Filter to Generate MAJ File

Added Filter to breakout MAJ files. Currently, creating a MAJ file is limited to a single MAJ file for a package. With this feature multiple MAJ files can be created based on a filter to where some items can go to the coil line and other items to a plasma table. This eliminates the need to create separate packages. To use this feature:

1. Create one or more filters under Admin > Company > Filter. In this example, the 2 filters both use the CutType Property, but the value is DecoiledStraight for one and MachineCut for the other. Note: The filte name will be used to name the generated MAJ file.

2. Apply the filter to a package category under Admin > Company > Package Categories.

   1. Under MAJ Filters, click New MAJ Filter to add one or more filters.

   2. If a report is selected for MAJ under Generate on Tracking Status, the generated reports will apply the MAJ Filters.

3. When generated, the MAJ files will display in the package’s Attachments tab.

Added Model Shipping Address as a Reportable Property

Added Model Shipping Address as a reportable Property which makes project shipping addresses accessible outside of the Package BOM report.

To configure:

1. Shipping Addresses: Under Projects > Shipping Addresses, enter or import shipping addresses. (Optional) By setting the default to one a row, the Shipping Address on the Models > Dashboard will default to the selection.

2. Models Shipping Addresses: In the Models > Dashboard, select the Shipping Address. If a default was set (above), it will be automatically selected for all models. Note: The Shipping Address value can be overridden as needed.

3. Report Setup:

   1. Reports can be setup for the following Item Types

      1. Assembly

      2. Container

      3. Container Details

      4. Package

      5. Package Details

      6. Part

   2. Example

4. Report Fields: In each report, the following Report Fields are available:

   1. STRATUS.Model.ShippingAddress

   2. STRATUS.Model.ShippingAddress.Name

   3. STRATUS.Model.ShippingAddress.Address1

   4. STRATUS.Model.ShippingAddress.Address2

   5. STRATUS.Model.ShippingAddress.City

   6. STRATUS.Model.ShippingAddress.State

   7. STRATUS.Model.ShippingAddress.Zip

   8. STRATUS.Model.ShippingAddress.Attention

   9. STRATUS.Model.ShippingAddress.Instructions

   10. STRATUS.Model.ShippingAddress.Phone

5. Template: Users can reference the STRATUS.Model.ShippingAddress Report Fields on the following Template Types:

   1. Package Sheet

   2. Assemblies Sheet

   3. Package BOM

   4. Container Details

Updated Auto Consolidation in BOM Settings

Currently when selecting the Auto Consolidation, in the BOM Settings, like parts do not merge because they have separate Part Templates.

With this change, when consolidating items with the same Size, Description, Material, and Unit of Measure the Auto Consolidation will not consider the Part Templates. Everything happens in the background. The functionality is the same for the user.

Consolidated:

Updated Pipe Cuts

Connectors New Root Gap Setting

Updated Pipe Cut Connectors with a Root Gap configuration option. The Root Gap is the gap between two connecting pipes and is specified when the gap is not modeled with a part so pipe cutting software can account for it during fabrication. The Root Gap column defaults to 0 and is exported within the PSVR file when the value is greater than zero. Root Gap does not impact cut lengths or reporting in STRATUS.

1. Under Admin > Company > Pipe Cuts > Connectors, set a Root Gap value.

2. Generate a .PSVR file. Root Gap values greater than 0 will be included in the exported file.

Olets New Cut Surface Setting

Updated Pipe Cut Olets with a Cut Surface configuration option. The Cut Surface is the pipe diameter reference for olet hole cuts and may be either ID (inside diameter) or OD (outside diameter). The Cut Surface column defaults to OD and can be changed to ID. The value will be exported within the PSVR file.

1. Under Admin > Company > Pipe Cuts > Olets, the Cut Surface is set to OD by default or can be changed to ID.

2. Generate a .PSVR file. The Cut Surface value will be included in the exported file.

    

Updated Lightning Catalog Parts Add/Remove Activities

Updated Lightning Catalog Parts Add/Remove Activities

Fixed and Updated User Management

Updated Add New Users in Disabled Status

When adding new users using the Refresh Users from Autodesk Construction Cloud button under Admin > Company > Users, the newly added user(s) will be disabled. As a result, newly added users do not consume a license until their Status is manually changed from Disabled to Active.

Updated Default Project Role Issue

Updated the Assign New User Role dialog selection results.

1. A Default Project Role is selected.

2. The Admin clicks Next. The Assign New User Role dialog displays. The Role for every existing project will be set to the selected Default Project Role.

    

3. To change a Role for a specific project, click the current role and select a new Role. Note: Checkboxes are only used to add the user to the project.

Fixed Issue with Default Project Role when Adding User to Project

Fixed an issue under Admin > Project > Team, where after clicking the New button, if the user selected in the User drop-down has an existing default project role, that role should automatically display in the Project Role drop-down.

Fixed Issue Updating a User

Fixed an issue updating a user under Admin > Company > Users, where after removing a user’s access to a project by unchecking the project, the user user was incorrectly removed from all projects. With this fix, the user will only be removed from the unchecked projects.

Updated Report Column Width Word Wrapping

Updated report column widths so that word wrapping does not occur in the middle of a continuous text string.

Fixed an Issue with Email Notifications

Fixed an issue when under Account Settings > Notifications, when Package > Tracking Status Changed was checked and a tracking status to a package was made, an email was not received.

Updated API for Number Property

Companies who reference the Number property in any API call need to update the property to STRATUSPartNumber.

Removed Purchasing and Supplier References

Removed Purchasing, Receiving, and Supplier references from the website. Contact the STRATUS Service Desk to toggle these features back on.

Fixed Issue with 'Add Lightning Catalog Parts' to Package under Items

Fixed an with the Add Lightning Catalog Parts feature limiting the number of parts that could be added. See the Lightning Catalog Parts article for more information.

Fixed Issue Where Deliverables Did Not Generate Without an Area

Fixed an issue generating Deliverables when the model parts did not have an area (Ex. STRATUS.Part.BIMArea). With this fix:

1. Deliverables will be generated when the parts do not have a STRATUS.Part.BIMArea

2. The Deliverables without area checkbox option has been added to the Area Selection Filter.

05/07/2024 - v1.0.2 - FLEX

Viewer (Beta)

To enable publishing to FLEX, you will need the 7.2.1 or newer version of the add-in. There is also a settting on Admin-Company-Projects to enable each project to be published to FLEX. Only Revit models are currently supported on Flex.

This initial rollout includes tracking status and package filters. We are working on performance optimizations, particularly for larger models. Additional features will be continuously added in future releases, further refining the model viewer's functionality and user experience.

Added the Ability to Create a Package

Added a New Package button to the Packages page. The button will be enabled whenever the device is connected to the internet.

The new Package button opens a menu to define your package properties and upload attachments. The package will be available on the STRATUS website at the time of creation.

Added Support for Scanning the Container QR codes

Added the ability to scan container QR codes and update the status of those containers.