1 06/16/2023 - v6.2.2

06/16/2023 - v6.2.2

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.

Revit and AutoCAD Addin - Yes
STRATUS Workstation - Yes
RazorGage Workstation - No
Print Workstation - No
Lightning - Yes

Added 2024 Support (Revit and CADmep)

Added 2024 Revit and CADmep support. Download and install the latest GTP STRATUS Addin from the Help page.

Added Autodesk SVF2 / STRATUS V2 Viewer

Added Autodesk SVF2 / STRATUS V2 Viewer (STRATUS refers to this as the V2 viewer) which provides the newest viewing technology, the fastest performance, and lowest memory consumption for Revit & AutoCAD models. Companies can opt-in to this feature (see below). A new GTP STRATUS Addin is not required.

Note: By adding the SVF2 feature, the STRATUS Manage Cache feature has been removed as it no longer provides performance benefits with SVF2 enabled.

With regard to V2 viewer activation, customers have the following choices:

None (Default) - The current SVF technology (V1 viewer in STRATUS) will continue working in all viewers and no option to upgrade a model to the V2 viewer will be available.
Test - After publishing a model (6.2 release or later) the STRATUS viewers will display the V1/V2 drop-down selector, and all newly published models will use the V1 viewer. Users can manually upgrade the model from V1 to V2 or downgrade back to the V1 viewer.
1. Please submit a ticket to the STRATUS Service Desk to request that your company be set to Test the SVF2 Viewer. Once the Service Desk changes your SVF2 setting to Test, republish models and the V1/V2 options will be available in the viewer. A model converted by one user will be applied to that model only and is converted for all users in the company.
Convert - After publishing a model (6.2 release or later) all newly published models will use the V2 viewer. Users can manually downgrade the model from V2 to V1 or upgrade back to the V2 viewer.
1. Please submit a ticket to the STRATUS Service Desk to request your company be set to Convert the SVF2 Viewer. Once the Service Desk changes your SVF2 setting to Convert, republish any models to use the V2 viewer. A model converted by one user will be applied to that model only and is converted for all users in the company.

Added Support in STRATUS Project Areas for Revit Rotated Scope Boxes

Added support to Projects > Areas for Revit Rotated Scope Boxes so that they display and are imported correctly, that parts are assigned to the rotated areas, and that scope boxes display correctly in Display Mode.

In Revit:
In a Viewer > Display Modes > Areas > Regions:

Added Sleeves to the Package Point List Export File

After generating a Point List for a package, under the Jobsite tab the CSV export download file will include the Revit Nested Families (eV_Point) for sleeves and hangers.

Added Import CSV to Assemblies Dashboard

Added the ability to Import CSV to the Assemblies Dashboard. Within the imported .CSV file, only STRATUS.Assembly.Name is required.

To Import CSV to the Assemblies Dashboard:

Either export a CSV or Excel file or create your own CSV file. In this example, the CSV file will first be exported, edited, and then imported.
On the Assemblies Dashboard, select the Assembly Report you want to import and click the CSV button..
Open the downloaded file similar to the following.
Edit the file as needed.
1. Only the STRATUS.Assembly.Name header and column data is required. If it is not in the file, the following message will display during the import process after step #7 below.
2. New rows can be created in the CSV file that include unique STRATUS.Assembly.Name. After the import process below, these new rows will be added to the Assemblies Dashboard and will include Empty or default values where no value was entered in the CSV file.
3. Existing rows in the STRATUS Assemblies Dashboard can be edited but not deleted in the CSV file.
Once the CSV file has been edited, from the Assemblies > Dashboard, click the Import CSV button. The Import Assemblies dialog will display.
Click the Browse button to locate the file. The Upload Assemblies CSV File dialog similar to the following will display. Notice the 10 MB max file size limit.
Click the Upload button.
Once the file has uploaded, the Status will be a green check.
Click the Close button.
The Import Assemblies dialog will display again, this time with the message “Upload complete. Ready to import.” Click the Import button.
Unless there is an issue with the import, the Import was successful message will display. Click Ok.
The page will refresh and the updated data will display in the table.

Added Query

Under Admin > Company > Queries, added the Parts in Last Year query.

Added Call to OpenAPI

Added to the OpenAPI a call to GET list of project areas by Id.

Updated Multi-select Dashboard Filters

For any dashboard report (Assembly, Packages, Containers, Parts (on Package Viewer > Items)) where there is a table column Filter option, the Select All and Deselect All buttons were added. Below is an example on the Assemblies > Dashboard using the Status filter.

Click the Filters button. The Select All and Deselect All buttons will display.
1. Select All- Click the Select All button to add all filter options to the search. Each option can be removed by clicking its X.
2. Deselect All - Click the Deselect All button to remove all filter options from the search.
3. One or more options can be selected selected.

Updated MAJ Create Date to Dashboards

Updated the Dashboards (Packages and Assemblies) with the MAJ file create date.

Below is an example of the dashboard date and then the Attachments fly-out date. The create date has been added to all attachments in this fly-out.

Updated Admin > Users

Updated the Admin > Company > Users > Add New User dialog. Alternatively, use the Refresh Users From BIM 360 button to add users from your BIM 360 Docs Member Directory. If the user is not in your BIM 360 Member Directory, the user needs to follow the login instructions for the Non-BIM 360 user Login.

To Add Individual Users to your Company:

Click the + New User button. The Assign New User Role dialog will display.
1. First Name (Required) - This will be the user's display name (First Name).
2. Last Name (Required) - This will be the user's display name (Last Name).
3. Email (Required) - The user's email. This email will be used to sign in to STRATUS.
4. Company Role - Set the user's company role.
  1. Standard User (Default) - By default, a new user's company role is set to Standard. A Standard User cannot access Admin > Company, where all the settings reside.
  2. Administrator - The Administrator company role receives email messages that Standard users do not receive. The Administrator company role will receive the STRATUS Subscription Expiration email notification. The email will be sent 60 days, 31 days, 14 days, 7 days, 1 day, and on the expiration date to everyone whose Company role is Administrator. The email subject will be similar to: STRATUS Alert - The STRATUS subscription for COMPANY A will expire on MM/DD/YY. The email message will be similar to: “The STRATUS monitoring system detected that your company's STRATUS subscription will expire on MM/DD/YY. Contact Sales at sales@gogtp.com concerning renewal options.”
  3. Other - All Company Roles created by the company Administrator under Admin > Company > Company Roles will display in the drop-down.
5. Group - A user can be added to a group, which makes it easier to add users to a new project. To use the Group feature:
  1. Click the Group link associated with the user. The Group drop-down will display. This is a list of all default and Custom groups previously added.
  2. Select an existing group or click Custom to add a new group.
    1. Custom - To name the Custom group finish adding data to the remaining fields and then click the Next button. The user will display in the Users data table and the Group will be Custom.
    2. Click the Custom text. The Group dialog will display.
    3. Click the drop-down. The Custom link will display.
    4. Click the Custom blue link. The word Custom will be highlighted in a text box.
    5. Enter the name of the new group (Ex. Field) and then click the Save button.
    6. The new group name will display in the Group dialog drop-down. Click the Save button again.
    7. The new field name will display for the user.
    8. Click the web browser page refresh button to make the new group available in the Group drop-down for other users moving forward.
6. Status - A user's status can be:
  1. Active (Default) - Active users consume one of your STRATUS licenses and can access any project under Admin > Project > Teams where the user has been added as a Team Member.
  2. Disabled - A Disabled user can no longer access STRATUS for the company. The user can still access other companies that have given the user access to STRATUS. STRATUS retains the disabled user’s records so that their name can be displayed in places where they made changes like tracking status. A Disabled user does not consume a STRATUS license.
    1. Note: You are not able to switch out licenses by editing users, as this would eliminate existing audit trails and history of that user. Instead, an unused account can be Disabled which will increase your license count by 1. You can then create a new user with the appropriate name and email, and this will consume a license.
7. Default Project Role - The Default Project Role is the way to automatically assign a project role to a user when new projects are added to STRATUS from BIM 360 using the Refresh Users from BIM 360 button. By default, the Default Project Role is None. New Project Roles can be created by an Administrator under Admin > Company > Project Roles. Out-of-the-box Project Roles include the following:
8. Add to New Projects - Used to control which users are added to new projects. By default, the checkbox is unchecked.
9. Can Book Training - Can Book Training indicates users who can schedule training with the GTP Customer Success team. By default, Can Book Training will be checked for anyone whose Company Role is Administrator.
  1. Checked - When checked, the SCHEDULE TRAINING button will display for the user and the user can schedule training with the GTP Customer Success team.
  2. Unchecked - When unchecked, the SCHEDULE TRAINING button will not display for the user, and a message to contact the STRATUS company administrator will display.
10. Notify on Update - A company administrator can specify who should receive software updates and announcements by clicking the Notify on Software Update checkbox associated with each user. By default, the checkbox is unchecked.
11. Expiration Date (not editable) - The Expiration Date is set bas
Click Next. The Assign New User Role dialog will display.
1. Locate or search for the project(s) to add the user to
2. Project - Check the checkbox for each project.
3. Role - Select the user’s Role which are defined under Admin > Company > Project Roles and click the Save button in the drop-down.
Click the Save button or click the Back button to make additional edits. Edits, except for name and email, can also be made once the new user has been saved.
The page will refresh and the new user will display.

Updated ZPL for Tools

Under Admin > Company > Tools:

Removed the Edit Label Template button where Type = ZPL Printer.
The Edit Label Template button will only display for tools where Type = Cut List or RazorGage tools. Default Label Template content is provided for RazorGage and Cut List types.

Updated Packages Dashboard Auto Dates

When setting a package’s Planning dates under Packages > Viewer > Properties > Planning, the dates and duration can be set manually, automatically using the Link Phase Calculations toggle), or a combination of both. With this update, making changes has been made easier, the Reset Planning Dates button resets the package as if it were a new using Package Category Duration Days (if any), and editing from the Packages Dashboard adheres to individual package settings for Link Phase Calculations and other date/duration settings.

Default - When a new package is created, the Link Phase Calculations toggle is off and users can manually change any individual setting (Ex. Start Date, End Date, or Duration), but this change will not impact other dates or settings. In addition, no date or phase is has the radio button selected to lock the setting.
Link Phase Calculations toggle to on - Click the Link Phase Calculations toggle to on when you want to base all phase dates off a date or duration change. For each change made in the Planning table, all of the phase dates will be updated based on that change.
Note: The Link Phase Calculations toggle button can be toggled on or off for each individual user but any updated dates or durations display immediately for all users.
Link Phase Calculations toggle to off - Users can toggle the Link Phase Calculations setting to off to return to the default behavior.
Reset Planning Dates - The Reset Planning Dates button is now on the Packages Dashboard making it easier to reset planning dates to the default. This button is still in the Planning table under Properties for each package.
Packages Dashboard - Editing a package in the Packages Dashboard will adhere to individual package settings for date/duration locks and Link Phase Calculations.

Fixed an Issue where Editing the Package Duration Changed the Duration for Existing Packages

Fixed an issue where editing the package duration days at the company and project level changed the duration days for existing packages. With this fix, Administrators are prompted as to how they want to handle duration changes.

Users now have ability to apply duration days modifications in three different ways. The following Confirm Save dialog will display when editing company and project level duration days settings (described below):
1. Apply to Existing Packages w/o Duration Days
  1. This option will recalculate package durations that have at least one “Empty” start/end phase date for the specific Package Category/Planning Phase.
  2. Note: For this to trigger and recalculate, their must be at least one start date in the planning phase of the package.
2. Apply to All Existing Packages
  1. This option will recalculate ALL existing package durations across the project that have duration days.
3. Do Not Apply to Existing Packages
  1. This option will not recalculate any package durations within the project.

The Confirm Save Dialog (described above) will display when editing company and project level duration days settings as follows:

Under Admin > Company > Package Categories > Duration Days:
1. After updating a Package Category > Duration Day and then clicking the Save button.
2. The Confirm Save modal will display.
3. Select an option and Save.
Under Admin > Project > Settings:
1. Add 3 new features:
  1. Duration Day Updates - When a day has been updated, the Package Category will highlight, showing there has been a change (Ex. 250).
  2. Reset - Added a reset blue button in the upper right that will set all the data back to Company Settings.
  3. Override Company Options For This Project - To enable the project override dialog, check Override Company Options For This Project option. When checked, this Project option will override Company settings made under Admin > Company > Package Categories.
2. Make updates to a given Package Category/Phase.
3. Click Save.
4. The Confirm Save dialog will display.
5. Select an option and Save.

Fixed Package Dashboard Issue with Field Expressions in Custom Reports

Fixed a issue where a Field Expressions did not correctly populate a custom report (Ex. Package Dashboard report).

For all companies: A user from each company should click the Clear Cached Calculated Field Values and Reload Data Table button in the packages dashboard for each Project/Model, otherwise old incorrect values might still display.

Hotfixes (Between 5/4 - 6/14)

Fixed an Issue Where STRATUS.Assembly.ConnectedAssembly Did Not Display Data

Fixed an issue where the following fields did not display data on an Assemblies Dashboard report.

STRATUS.Assembly.ConnectedAssembly.Single
STRATUS.Assembly.ConnectedAssembly.Multiple

Fixed a Company Filter Issue

Fixed an issue on large models with complex company filters, where the Filters > Company tool was selected and the viewer took several hours to complete processing to display. In one example where there 227,000 parts, the time to display Company Filters was reduced from 2 hours to 1 hour. Team GTP is looking for ways to further reduce load time of these filters. Note: The model below is still loading:

Fixed a Publish Issue Where the Packages Viewer Did Not Lock

Fixed an issue where during the model publish process, the Packages > Viewer did not lock to prevent users from adding new assemblies.

Fixed Issue Deleting User from Project Team

Fixed an issue deleting a user from Admin > Project > Team.

Fixed Issue Adding New Part Properties to Part Template

Fixed an issue where new Part Properties were not added to the Part Template during the model publish process.

Fixed Issue with Matching Parts Get Same Number

Fixed an issue where matching parts did not get the same Item Number. With this change, the determination for matching parts has been simplified: for a part to receive the same item number as another part, all checked Item Number Properties for the Part Template must be equal (Ex. Length and Size). The only exception is the Length property tolerance (see below).

Added Tolerance For Length Properties When Comparing Parts For Item Numbering

Added tolerance for length properties when comparing parts for item numbering. Previously a 10' pipe would not match a 10' 0.001” pipe. When lengths are less than the following, the parts will qualify to receive the same item number:

Imperial (1/16” or less)
Metric (1.5 mm or less)

Added Package Properties to API Endpoint

Added the following properties to the endpoint: https://api.gtpstratus.com/v1/package/{packageId}/report/{reportId}

Assembly.PackageId
Assembly.PackageName

Fixed Slow Renumbering Issue

Fixed an issue where renumbering was very slow.

Fixed Issue Attaching a PDF to a Package

Fixed an issue attaching a PDF file type to a Package.