1 08/17/2023 - v6.3.1

08/17/2023 - v6.3.1

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 or wait until the mandatory quarterly update is made available. 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.

Mandatory Uninstall / Reinstall of all GTP Software

All installed GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article. Not only is this the mandatory quarterly update, but a new installation and AutoUpdate process is being implemented.

Revit and AutoCAD Addin - Yes. This is not only a mandatory quarterly STRATUS Addin install, but all GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article.
STRATUS Workstation - Yes. All GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article.
RazorGage Workstation - Yes. All GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article.
Print Workstation - Yes. All GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article.
Lightning - Yes. All GTP software must be uninstalled and reinstalled according to the Installation of GTP Software on Windows article.

Fixed Publish Issue Matching Item Number when Sleeves, Saddles, Hangers Included

For Revit 2020 and newer, fixed an issue where identical parts received non-matching item numbers because sleeves, saddles, or hangers were being detected and mistranslated as a pipe branch.

In this example, prior to the change, the Part Template property used for Item Numbering was Diameter. The 2 pipes (below) were the same diameter, but included sleeves and received non-matching item numbers.

With this change, the sleeves are ignored and the pipes with the same diameter receive matching item numbers.

Added Field Columns

Display Name

Added to all fields under Admin > Company > Fields, a Display Name column. The purpose of this column is to use a Field Display Name in reports rather than the full name of the expression. There are rules as to when the Display Name is used, for example if there is not a Report Field header. See examples below.

Three Examples: The screen shot below highlights which column heading will be used and in the order each will be used.

Report Field Header under Admin > Company > Report > Report Field > Header.
Example: In Report Fields, the Header = Total Pipe Length - H which takes precedence over the Fields Display Name = Total Pipe Length - F.
Field Display Name under Admin > Company > Fields > Display Name.
Example: In Report Fields, there is no Header for the field in row #3, therefore, the Fields Display Name = Total Pipe Length - F displays.
No Field Display Name or Report Field Header
Example: The field does not have a Display Name under Fields, nor does it have a Header under Report Fields. Therefore, the column header uses the Field Name (Ex. TotalPipeLength_NoName).

Part Filter

For those who write Field Expressions and Filters, this is a big upgrade for you, especially if you prefer to write filters rather than expressions!

The newly added Fields > Part Filter column provides administrators with the ability to filter parts before they are processed by the Field Expression. As a result, the Field Expression will process a filtered subset of the model parts rather than the entire model which will result in faster report generation and less complicated Field Expressions.

Example - Pipe Length

Old Field Expression - The top row displays the Old Field Expression which had to query for the CID, then query parts, and then query categories to give a result.

New Part Filter - The bottom row displays the selected Part Filter (see the referenced filter below). Referencing the Part Filter makes for a simpler Field Expression (Ex. {Length}). In many cases, the Filters will have already been written and in used in viewers under Filters > Company. Expressions with a part filter will return an empty result for parts which don't match the filter.

The Part Filter referenced above does all the pre-filtering including the ServiceType, CID, Source, Product Name, and Category so that your field expression only has to ask for the {Length}.

As a result, the report (below) includes both the OLD and NEW fields to show they result in the same values.

OLD Field (Ex. CSG _ Pipework _ Dashboard _ Total Pipe Length which uses the report field column header Linear Feet Of Pipe (Total))
NEW Field (Ex. QA_CSG _ Pipework _ Dashboard _ Total Pipe Length which uses the report field column header QA_Linear Feet Of Pipe (Total)

Example - Earned Labor

Old Field Expression - The top row displays the Old Field Expression which had to query for the parts to see if it they were past a certain tracking status.

New Part Filter - The bottom row displays the selected Part Filter (see the referenced filter below). Referencing the Part Filter makes for a simpler Field Expression.

Added to Package Categories

Package Creation Report (Additional Fields)

Additional Fields are used to enter or display package data while creating new packages or viewing existing packages. Additional Fields are Editable Fields that have been added to a report under Report > Report Fields. The report is associated with a Package Category under Admin > Company > Package Categories when it is selected in the Package Creation Report column.

Note: Prior to this updated feature, these fields were named “Custom Fields” and the criteria for display included all editable fields from all Package Dashboard reports that were not hidden in the report.

See the end of this section for examples of Additional Fields.

To control which Fields display in the Additional Fields section:

Fields - Under Admin > Company > Fields, identify or create one or more editable fields. See the Is Editable checkbox in the Fields (Admin) article for more information.
Report - Under Admin > Company > Reports, identify or create a report that includes:
1. Report Item Type = Package.
2. Editable Fields - One or more editable fields (step #1).
3. Checkbox - The checkboxes (Model Viewer, Package Viewer, Packages Dashboard) do not need to be checked, but can be checked if the report needs to display.
4. Hidden (Unchecked) - A Report Field that needs to display as an Additional Field cannot have the Hidden checkbox checked for the selected report.
5. Sort Index - The Sort Index is not applied to the fields in the Additional Fields section.
Package Creation Report - Under Admin > Company > Package Categories, identify a Package Category that will use the fields from step #1 and #2 above. Select the report in the Package Category’s Package Creation Report property.
1. Note (Empty) - For any Package Category whose Package Creation Report is Empty, the Additional Fields sections will be populated with STRATUS.Field.* fields that meet all of the following rules:
  1. Is Editable (Checked) - Under Admin Company > Fields, the field’s Is Editable checkbox is checked.
  2. Report Item Type = Package - The fields from above have been added to any report whose Item Type is Package.
  3. Hidden (Unchecked) - The fields added to the report(s) above do not have the Hidden checkbox checked.
Examples of Where Additional Fields Display
1. Package Creation - Package Creation under Models Viewer > Actions > Packages > Selected Package Category (step #3), or, Packages Viewer > Actions > Packages > Selected Package Category (step #3). Note: Additional Fields and Estimating Information fields update dynamically as parts are added to the package.
2. Package Creation - Package Creation under Packages > Dashboard > New Package > Selected Package Category (step #3).
3. Package > Properties > Additional Fields - For a package associated with the Package Category (step #3), open a package’s > Properties tab. The Additional Fields should match the report.

Default Assembly Report

The Default Assembly Report option enables administrators to select a default report to display when loading an assembly for the first time in the Assemblies > Viewer. The selected report is associated with a specific Package Category. Therefore the default report will only apply to assemblies included in packages within the Package Category.

To use the Default Assembly Report:

Report - Under Admin > Company > Reports, identify or create a report that will be the default report when an assembly loads for the first time under Assemblies > Viewer > Parts > Report. The report needs to include:
1. Report Item Type = Part
2. Assembly Viewer = Checked
Default Assembly Report - Under Admin > Company > Package Categories, identify a Package Category (Ex. Mechanical Piping Fabrication) that will use the report identified in step #1. Select the report (Ex. CSG _ Pipework _ Spool BOM) in the Package Category’s Default Assembly Report property.
Identify a package whose Package Category (Ex. Mechanical Piping Fabrication) was configured in step #2.
Open an assembly from that package for the first time. The Assemblies > Viewer > Parts > Report will be the Default Assembly Report selected (Ex. CSG _ Pipework _ Spool BOM) in step #2. If the user chooses to change the report, the last viewed report for that assembly will display on subsequent page refreshes.

For various scenarios, the order of operations is as follows:

Example above - If an assembly is associated with a singular package whose Package Category has the Use Assemblies checkbox checked, the assembly will use the Default Assembly Report as configured under Admin > Company > Package Categories > Default Assembly Report.
If an assembly is associated with more than one package whose Package Category has the Use Assemblies checkbox checked, it will use the Default Assembly Report as configured under Admin > Company > Package Categories > Default Assembly Report for the package that it is being opened from.
If the assembly is not associated with a package, it will default to current functionality and use the “Assembly Filter” in reports to select which report should be used upon first view.

Advanced Estimating User Data Fields

15 User Data fields can be added to Advanced Estimating under Admin > Company > Package Categories. These User Data fields display and update dynamically in the package creation dialog.

These fields can make information available to the user as they make packages so they can make better decisions about size and scope and preview dashboard report information before the package is created.
The User Data Field column names use the Display Name under Admin > Company > Fields. If no display name has been entered the full name of the field expression will display.
The data shown in the User Data fields updates dynamically as parts are selected and removed prior creating the package.
After the package has been created, any addition or removal of parts forces the User Data fields to recalculate.
Switching the Package Category after a package has been created forces the User Data fields to recalculate.
Boolean and “drop-down list” fields (includes Possible Values) can be edited during the package creation process.

To use User Data Fields:

Under Admin > Company > Package Categories, for any Package Category, click the Advanced Estimating checkbox.
The Advanced Estimating section will display a column for all four project phases and includes the Add User Data button. Only package category rows where the Advanced Estimating checkbox has been checked can be edited (indicated by the row being highlighted in yellow).
Click the Add User Data button. The User Data # column will be inserted.
Click the User Data drop-down and select a field. Available fields include:
1. STRATUS.Company.*
2. STRATUS.Project.*
3. STRATUS.Package.*
4. STRATUS.Field.*
Continue to add User Data fields as needed. In the example below, there are 3 User Data fields populated for the Package Category = Mechanical Piping Fabrication, but up to15 User Data fields can be added.
During the package creation process with the Package Category = Mechanical Piping Fabrication, the User Data fields will display in the Estimating Information section.
1. With no parts added to the package yet, all fields display 0.
2. Note: The “Estimating Information” was previously labeled “Hours Estimated” since more than hours can be included.
3. As parts are added to the package, the User Data fields dynamically populate.

* Added CAD Sheet Tab and Markup to Package

Added CAD Sheet to Package. The CAD Sheet can also use the Markup tools previously implemented in the Assemblies Viewer.

There are 2 ways for a CAD Sheet to display in a Package. In either case, CAD Sheets in STRATUS are created from Sheets selected in the Revit Publish Settings.

Method 1 - Create Package in STRATUS and Rename Sheet in Revit

In STRATUS, create a Package (Ex. Duct Sections and with the Incrementor XXX the name will be Duct Sections001).
In Revit, create or rename a Sheet with the same name (Ex. Duct Sections001).
In Revit, re-publish the model with the Sheet(s) selected in Revit Publish Settings.
In STRATUS, go to the Packages > Viewer. If the CAD Sheet tab did not previously exist for the package, it does now.
CAD Sheet Markup tools display. Markup is also available in the Assemblies Viewer.

Method 2 - Create Revit Sheet and Create Package with the Same Name

In Revit, publish or re-publish the model with the Sheet(s) selected in Revit Publish Settings (Ex. North Level 1 - Lighting Plan).
In STRATUS Models > Viewer, create a new package whose name matches one of the sheets in Revit Publish Settings (Ex. North Level 1 - Lighting Plan).
1. Alternatively, on the Packages > Dashboard, the Import CSV option can be used to import packages whose names match one or more Revit Sheet names.
In STRATUS, go to the Packages > Viewer. The CAD Sheet tab will display with the Revit Sheet displayed.
CAD Sheet Markup tools display. Markup is also available in the Assemblies Viewer.

Added Part Report Fields

Added Part Report Fields, which return the name of the assembly the part is connected to and only displays a value for the end parts in an assembly.

The added Part Report fields include:

STRATUS.Part.C1ToAssembly
STRATUS.Part.C2ToAssembly

Example - Report

Example - Label

Below is an example of a Label A and Label that would be placed on either end of a cut.

Added Container Settings

Added Use Containers Setting to Package Categories

Added the Use Containers setting to Admin > Company > Package Categories which by default, is checked for all package categories.

To configure the Use Containers checkbox:

Use Containers - Under Admin > Company > Package Categories:
1. Unchecked - When the User Containers checkbox is unchecked, packages created with the Package Category will not display in Containers.
2. Checked (Default) - When the Use Containers setting is checked (default), packages created with the Package Category will display in Containers.
The setting is initially used in two places:
1. Containers Assign Package Display
  1. Use Containers checked - When User Containers is checked and a package is created using the associated package category, the package will display in the Containers > Assign > Package drop-down.
  2. Use Containers unchecked - In the example below, User Containers is unchecked for the Default package category.
  3. As a result, a package created using the Default package category, the package will not display in the Containers > Assign > Package drop-down.
2. Containers > Dashboard Filter for STRATUS.Container.Package Report Properties
  1. See the Added STRATUS.Container.Package Report Properties section for more information.
  2. When the STRATUS.Container.Package Report Properties are used in a report they can be used to filter Packages.

Added STRATUS.Container.Package Report Properties

Added STRATUS.Container.Package Report Properties including:

STRATUS.Container.PackageId
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Package ID will display on the table if any data is available for that particular package.
STRATUS.Container.PackageName
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Package Name will display on the table if any data is available for that particular package.
STRATUS.Container.PackageNumber
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Package Number will display on the table if any data is available for that particular package.
STRATUS.Container.ProjectId
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Project ID will display on the table if any data is available for that particular package.
STRATUS.Container.ProjectName
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Project Name will display on the table if any data is available for that particular package.
STRATUS.Container.ProjectNumber
- Where: Containers Dashboard
- Property Purpose: When a package is using a category that has the "Use Containers" checked (in the Admin Company Package Categories). The Project Number will display on the table if any data is available for that particular package.

Note: A field may return a semi-colon separated list of values if container contents include items with multiple values.

Added UniqueValues() Function

The UniqueValues() function may be passed an optional second argument as true if you want the quantity displayed in front of each unique value in the result.

Configuration

Field Data Type: String
Field Expression Syntax: UniqueValues({array},true)
Example: In the example below, the Parts Description List field results in the description of each part and the UniqueValues() function is applied to it.

Results

Added Option to Ignore BOM Line Items with 0 QTY

Added the Ignore Zero Quantity Line Items option which can remove BOM Line Items that have 0 QTY from the BOM. When a BOM is generated if “Size”, “Description”, and “Material” are blank, a row for that item will not be generated.

Best Practice: For optional BOM Line Items that depend on certain part properties, it is best practice to create a custom field which returns a value of 0 when the BOM Line Item is not present and 1 (or other number) when it is, then map that field to the QTY under Admin > Company > Part Templates > BOM Line Item Mappings.

To change the Ignore Zero Quantity Line Item option:

Access the BOM Settings dialog either via:
1. Admin > Company > Package Categories > BOM Settings for the package category.
2. Open the BOM and click the BOM Settings button.
A BOM Settings dialog similar to the following will display. Note: The Package Category will display in the title.
Ignore Zero Quantity Line Items
1. Unchecked (Default) - Line Items whose QTY is 0 will display in the BOM.
2. Checked - Line Items whose QTY is 0 will not display in the BOM.

Added STRATUS Sheet Tags/Dimension Labels Move and Hide

Added the ability to all STRATUS Sheets (Packages, Assemblies) to Move and Hide tags and dimension labels.

To move or hide tags/dimension labels in the STRATUS Sheet:

If neither the Dimensioning or Display - Item Numbers tool is turned on in the 3D viewer:
1. Neither Dimension or Item Numbers will display in the 3D Viewer.
  Note: In the example below, the STRATUS Sheet Report > Template > View Style settings for Render Dimensions and Render Item Numbers is checked, therefore, these display in the STRATUS Sheet but are not editable.
2. Neither Dimension or Item Numbers will will be editable in the STRATUS Sheet.
When either Dimensioning and Display - Item Numbers tools are turned on in the 3D Viewer:
1. Either Dimensions, Item Numbers, or both, like in the example below, will display in the 3D Viewer.
2. Either Dimensions, Item Numbers, or both, like in the example below, will be editable in the STRATUS Sheet.
To Move or Hide STRATUS Sheet dimensions and/or Item Numbers, with either Dimensioning and Display - Item Numbers tools are turned on in the 3D Viewer, click the Adjust view orientation and annotation button.
The Item Number tags and Dimensioning labels will display. Hover over a tag or label and the Move and Hide buttons display.
1. Move - Note: Moving a dimension or a tag will affect all viewports as well as the 3D viewer. As a result, after moving a dimension, the Cancel button does not move the dimension back to a previous position, rather it is saved.
  To move the tag/label:
  1. Click the blue move button and let go of the mouse.
  2. Move your mouse toward where you want to place the tag. The tag will disappear as you move your mouse. A leader will display and will follow your mouse.
  3. Click the mouse when you are ready to place the tag. The tag will display.
  4. Click Save or Cancel. When the viewer refreshes, the dimension is moved in the STRATUS Sheet and the 3D viewer.
2. Hide - Click the hide button. The tag will change to be semi-transparent with gray text on the viewport being edited.
3. Click Save. When the viewer refreshes, the dimension is hidden in the STRATUS Sheet, but remains visible in the 3D viewer.

*Added Filters Date Range Option

The Filters Date Range Option has been added to the Packages > Viewer and the Assemblies > Viewer. It was previously implemented in the Models > Viewer on 09/20/2022. See the Viewer Filters Tracking Date Range article for more information.

*Updated Activities User Filter

Under Admin > Company > Filters, updated User filter to only display user’s who have an activity rather than all STRATUS users.

Updated OpenAPI Activities Disable Total to Activities

Added the disabletotal property to all Get calls. The total count property will be 0 when ‘disabletotal’ = true. This new optional flag improves paging performance. See the Example 3: Using C# to get Paged Activities (disabling total for better performance) article for more information.

Updated Automated Tracking Comment Message

Updated the Tracking Comment message when STRATUS automatically updates the tracking status. Examples of when this can occur include:

Downgrade a part's tracking status on that package which forces the whole package to downgrade
Updates during the import/publish process for packages/assemblies/parts
Adding an assembly to a package
Only applies to new tracking log entries

Updated Package Planning Link Phase Calculations Default

When a new package does not include any Phase Start dates, the Link Phase Calculations button, under the Package’s > Properties > Planning button, will default to On (Enabled) rather than Off (Disabled). This way, when dates are entered in the Planning table, they automatically calculate without having to remember to enable the Link Phase Calculations button.

Updated Add New Row to Data Tables

Updated the Add New row to data tables display to ensure that the new editable row is located at the top of the data table and that it is highlighted yellow regardless of how the table is sorted. This update has been applied to many similar data tables. Below is one example:

Go to Containers > Dashboard.
Sort one of the columns (Ex. Name).
Click the New Container button. The editable new row displays at the top of the data table.