1 08/18/2022 - v5.3.1.31

08/18/2022 - v5.3.1.31

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.

Updated Revit View Check

Before a publish, the addin will verify that the Revit model includes at least one active 3D view under Collaborate > Publish Settings.

Added Multi-select Drop-downs

Added the ability to multi-select options on some drop-downs.

Examples:

Filters - Allows for multi-select of filter options.
Assemblies > Dashboard > Packages - Allows for multi-select of packages to add to an assembly without the collapsing of the drop-down between every selection. To remove a package from the selected list, either click the item in the drop-down or click the x associated with the package name.

Added Container Updates

Manually Add Part to Container Contents and Remove it from the Drop-down List

In this example, the (4) highlighted parts will be added to the container by selecting each and clicking the Add part to container button.
After adding each part, the part is removed from the drop-down list.
By clicking the Remove button associated with any part, the part will be removed from the container Contents and will be available in the Part drop-down list.
If a different container is selected (Shelf South) and the same project, model, package or assembly has been selected, all of the parts will be available including the parts that have been added to other containers.
In this case, when the user attempts to add parts that are in other containers, the “Move items” dialog will display.
1. Move - Click Move to move the part from the other container to the new container. As a result, the part will be removed from the old container.
2. Cancel - Click Cancel to cancel the action.

STRATUS.Part.ContainerType Update

Add the STRATUS.Part.ContainerType field to a report to display the hierarchy of containers and parent containers in a semicolon-separated list.

Added Date & Time Control Per User

Added to Account Settings > Profile a Date & Time section to control how dates and times are displayed per user.

To use this feature:

Open the Profile page by clicking your badge > Account Settings > Profile.
By default, Date & Time settings are configured as follows:
To change settings:
1. Time Zone - Select your time zone.
2. Date - Select your preferred date display.
3. Time - Select your preferred time display.
4. System = Select either 24 hour or 12 hour (includes AM and PM after the time.)
Note: A sample of any displays at the bottom of the Date & Time section.
Click Save to save any changes.
Refresh any open page to display the configured Date & Time settings.
1. Submit a STRATUS Service Desk desk ticket if you find a scenario that does not display the date/time as configured.

Added Package Actuals Data Source Definition

The Schedule configuration table enables companies to define a package’s actual progress and hours. How the calculation is made is determined by the Method (Tracking Status or Report Field (Ex. A field that calculates MCA hours ). Once configured, the package data is calculated on the Package’s > Properties > Actual section.

Configure Package Actuals Data Source

To configure actual progress and hours, go to Admin > Company > Settings > Schedule.
Phase - For each Package Phase (Office, Purchasing, Shop, Field), the Progress and Hours can be configured.
1. Progress - All 4 package phases (Office, Purchasing, Shop, Field) are listed.
2. Hours - Select one label:
  1. Spent Hours - Defined by your company.
  2. Earned Hours - Defined by your company.
  3. Remaining Hours - Defined by your company.
  4. Custom - Enter your own label.
Method - The method of how the row will be calculated.
1. Tracking Status - When the method is set to Tracking Status, the actual data will use the Phase percent configured for the package’s tracking status under Admin > Company > Tracking Statuses (See Example - Progress set to Tracking Status below).
2. Report Field - When the method is set to Report Field, a report field will be selected in the row’s Source column.
3. None - When the method is set to None, the corresponding cell under Package’s > Properties > Actual will be grayed out.
Source - When Report Field is the method, a source (the report field) is selected.
Advanced Reporting
1. Checked - When checked, the hours row will display for all phases here in schedules and on the Package’s > Properties > Actual section.
2. Unchecked - When unchecked, the hours row will not display for any phase here in schedules or on the Package’s > Properties > Actual section.

Example - Progress set to Tracking Status

In this example, the following Phase percent complete values will be used.

The Progress Method for all Phases has been set to Tracking Status. As a result, the actual Progress ( % ) will use the Phase percent configured for the package’s tracking status under Admin > Company > Tracking Statuses (see above).
In the Package’s > Properties > Actual section:
1. A package has been created and the initial Can Package tracking status is Issued which is 20% complete for the Office phase. No other phase has started so 0% displays.
2. Once the package’s tracking status changes to Packaged, the Office Progress ( % ) changes to 60%. No other phase has started so 0% displays.
3. When the package’s tracking status changes to Fabrication in Progress, Office is updated to 100%, Purchasing to 100%, and Shop to 20%.

Example - Hours Report Field

In this example, Shop and Field Earned Hours will be calculated using a Report Field.

Select a field that provides the hours for any given phase.
In the Package’s > Properties > Actual section the values, if any, will display. A dash displays if a Report Field has been configured but the calculation resulted in no value.

Added Estimated Hours Calculation

The Estimated Hours Report Field column has been added to Admin > Company > Package Categories. When configured, Estimated Hours will be calculated in two different places (see examples below).

Configure

Go to Admin > Company > Package Categories.
For the Package Category in the Estimated Hours Report Field column, select a custom Report Field that generates the estimated hours.

Example 1: Package’s > Properties > Planning

When the Estimated Hours Report Field has been configured for the selected package’s Package Category, in the Package’s > Properties > Planning section, the calculated value for Estimated Hours will display.

Example 2: New Package

When the Estimated Hours Report Field has been configured for the selected package’s Package Category, during the new package creation process under Models > Viewer > Actions > Packages, the Estimated Hours will be calculated as parts are selected.

Added Disable Delete Assembly Based on Tracking Status

Previously the Delete assembly button (Assemblies > Dashboard and Packages > Items) was displayed when the user had the Delete permission regardless of the Can Assemble tracking status constraint. This update disables the Delete button when the Tracking Status does not have Can Assemble checked. In this case, the Delete button will be disabled and the hover text will display.

Added Date Options to Naming Conventions

Added Date options to Admin > Company > Naming and Numbering > Naming Conventions > Default Values.

Updated Date Filter to Stick after Refresh

Updated Date Filters to stick after the page is refreshed.

Updated STRATUS Workstation to use Chromium Browser

Updated STRATUS Workstation to allow firms to optionally use the MS-Chromium browser for login. The application now supports both Chromium and Internet Explorer.

Fixed Assemblies > Dashboard Tracking Status Updates

Fixed an issue on the Assemblies > Dashboard where updating the Tracking Status of (1) part that was attached to an assembly would update the parent assembly. With this change, the Tracking Status between parts and the parent assembly update correctly when changing/updating the tracking status:

When the assembly is updated to a new tracking status, all parts will update to match.
When (1) part attached to an assembly is updated, only that part’s tracking status will update.
When all parts attached to an assembly are updated, the assembly will update to match.
When the assembly and parts are in a tracking status like “Shipped”, then one or more parts are changed to a lower-numbered tracking status like “Issued for Fabrication”, then the assembly will update to reflect that lower tracking status “Issued for Fabrication”.

Fixed a Generate CSV Issue

Fixed a Generate CSV/Excel issue when in Packages > Items on a specific package, and the user switches from package A to package B, then clicks the “CSV” generation button, the generated data would be from package A. With this fix, when switching to package B, the page is refreshed so that the correct CSV file is generated.

Fixed a Project Role Disabled Issue

Fixed an issue under Admin > Company > Project Roles where a Project Role became disabled after the “Project Admin” project role was selected under the Select Roles to Display dialog.

Fixed a Window Select Issue

Fixed an issue when using the Window Select tool in the Models Viewer that all parts were not selected, specifically gaskets and solder joints.

Fixed a Project Role Sort Issue with Tracking Statuses

Fixed an issue under Admin > Company > Project Roles > Tracking Statuses where the list did not sort alphanumerically.

Fixed an Issue Displaying Dates in Properties

Fixed an issue in the viewers' Properties panel displaying the STRATUS.Part.CreatedDT and STRATUS.Part.ModifiedDT. The issue below is fixed.

Researched Length Discrepancy STRATUS vs Revit

Researched a length discrepancy where STRATUS reports length as 4'-11" but the Revit length reports it as 4'-11 1/8". Andy found that STRATUS directly reflects what Revit is reporting, however, Revit is displaying contradictory values compared to MAJ/FabReports within Revit. This issue has been logged with ADSK as a bug with Revit.