1 11/4/2021 - v5.0.0.11

11/4/2021 - v5.0.0.11

New Publish Addin

The long-awaited next-generation publish add-in is released in this version. Benefits include:

Decreased time spent publishing from the desktop.
During a model publish, the current model version will be available to STRATUS users except for a few minutes when the database is being updated. This means that the amount of time the model is not available has been sharply reduced.
Most model failures that occur will happen in the cloud where they can be analyzed and in many cases fixed without any impact on users.
Large model publishes will overall take significantly less time to publish.
At the request of users, selecting a Folder (BIM 360 Folder) is no longer an option. See the Configure Default Publish Folder Path section for configuration instructions.

Configure Publish Folder Path - Default Settings

By default, the A360 Publish Folder Path for each project is set to Project Files\STRATUS.
The project can be selected in the Publish dialog.
After the model has been published, STRATUS will create sub-folders (Ex. Hosptial and RVT).
1. Note: This will create a folder named “STRATUS” in the folder you chose. If you already have a folder named “STRATUS”, this will be the root folder used when publishing. If you have a folder name like “Stratus”, where the case does not match, please rename it to be spelled with all caps.
Additional sub-folders (Ex. MAJ, PCF, Parts, Assemblies, Packages, Reference, CSV) will be created as those file types are generated in STRATUS.
1. Syntax: Project Files\STRATUS\Project sub-folder\
2. Example: Project Files\STRATUS\Hosptial \RVT\Hosptial.rvt
3. Example: Project Files\STRATUS\Hosptial \ESJ\Hosptial .esj
4. Example: Project Files\STRATUS\Hosptial \MAJ\Hosptial .maj
5. Example: Project Files\STRATUS\Hosptial \Packages\GTP00002-FP-0001\Attachment01.pdf
If this file structure is not how your company organizes files, then see the following sections for more information.

Configure Publish Folder Path - Existing Projects

By default, the A360 Publish Folder Path for each project is set to Project Files\STRATUS. To set the A360 Publish Folder Path to a different \Project Files sub-folder:

In BIM360, create a Project Files sub-folder (Ex. NEBRASKA).
In STRATUS, go to Admin > Company > Projects and identify the project whose path needs to be edited (Ex. GTP - ITM - CAD - Revit).
Under A360 Folder Path, click the cell, and edit the path to match the BIM360 path. (Example: Project Files\NEBRASKA)
1. Note: The path must include Project Files\
2. Note: If the Project Files sub-folder was not created in the correct path in A360, a message similar to the following will display:
3. Note: STRATUS will automatically create sub-folders to the A360 Folder Path when the model is published, packages created, and MAJ files generated.
  1. Possible sub-folders include: DWG, RVT, ESJ, MAJ, Packages and Package Names.
With the project selected in the Publish dialog, the model will be stored in the A360 Folder Path (Ex. Project Files\NEBRASKA).
The model will be saved to A360 as follows:
1. Syntax: Project Files\NEBRASKA\Project sub-folder\
2. Example: Project Files\NEBRASKA\School\RVT\School.rvt
  1. Note: References files are located in the RVT sub-folder.
3. Example: Project Files\NEBRASKA\School\ESJ\School.esj
4. Example: Project Files\NEBRASKA\School\MAJ\School.maj
5. Example: Project Files\NEBRASKA\School\Packages\GTP00002-FP-0001\Attachment01.pdf

Configure Publish Folder Path - Newly Activated Projects

A newly activated project is a new BIM 360 project that has been added to STRATUS by clicking the Add Projects from BIM 360 Docs button under Admin > Company Projects. The Default Company A360 Root Folder Path provides for a consistent folder structure for all newly activated projects. By default, the Default Company A360 Root Folder Path is set to Project Files\STRATUS.

To configure a different Default Company A360 Root Folder Path for future projects:

Under Admin > Company > Projects, click the Default Company A360 Root Folder Path link.
Enter the path with sub-folders separated by backslashes (\) (Ex. Project Files\STRATUS - Pipe).
When the model is published the Default Company A360 Root Folder Path sub-folders in A360 will be created.

New Publish Addin - Beta Testers

For Beta Testers of the new Publish Addin, for any computer from which you have published using the next-gen publishing addin, please do the following:

Open a Windows file browser.
Paste the following into the path bar and press Enter.
%appdata%\GTP Services, LLC\STRATUS
Replace the Settings.json file in the STRATUS folder with the file located HERE.

Updated Pipe Cuts Management

Under Admin > Company > Pipe Cuts, updated how Connectors and Saddles are managed. In addition, an issue was fixed that handles spaces used for Bevel Connector Names.

Previously, content had to be entered for each Nominal Size even if all other columns included the same content. With this change, the Nominal Size (Ex. 24) is interpreted as “equal to or less than” so that all smaller sizes (Ex. 2.5) are automatically included and receive the same settings.

Updated Actions > Tracking Apply Buttons

Updated Actions > Tracking “Apply to” buttons to clarify which parts and assemblies the tracking status change will be applied to.

Apply to Visible - The Apply to Visible button is enabled when nothing is selected in the model. The hover text reads “Create new tracking entry for visible assemblies or parts“. The Apply to Selected button is disabled.
- When Apply to Visible is clicked, the following prompt will display:
- When Apply is clicked, a message similar to the following will display:
Apply to Selected - The Apply to Selected button is enabled when any part or assembly is selected in the model. The hover text reads “Create new tracking entry for selected assemblies or parts“. The Apply to Visible button is disabled.
- When Apply to Selected is clicked, the change will be applied without a prompt and a message similar to the following will display:

Updated Templates with Package Category Report Field

Under Admin > Company > Templates, updated the Assembly Viewer Template Type to include report fields that contain the Package Category. For example, the report field STRATUS.Assembly.PackageName can be further limited by the specific Package Category (Ex. .Fabrication Production or .Fabrication Release). If “STRATUS.Assembly.PackageName.Fabrication Production” is used in the template, then, when the associated report is run, the STRATUS Sheet will only display the package name when it is associated with the “Fabrication Production” package category.

Updated Templates Report Field to Include STRATUS.Assembly.PackageCategory

Under Admin > Company > Templates updated the Report Field drop-down to include the STRATUS.Assembly.PackageCategory. This provides the ability to include the Package Category of the Assembly in a report.

Updated Locked Icons During Model Publish

When a publish is initiated the model is “Locked”. Users will notice the following:

Models Viewer - The Models > Viewer canvas is highlighted in red, the publish icon displays next to the model name, and the Actions > Assemblies buttons hover text reads “Disabled during publishing.”
Assemblies Viewer - The Assemblies > Viewer canvas is highlighted in red and the publish icon displays next to the model name.
Assemblies Dashboard - The publish icon displays next to the model name, the Assemblies > Dashboard buttons to Edit or Delete an assembly item are disabled, and the hover text reads “Disabled during publishing.”

Updated Report Field Prefix and Suffix to Only Apply If There Is A Value

Updated the Report Field so that if a prefix or suffix is used, it will only display in reports if the field includes a value, otherwise, it will be blank.

Fixed an Issue with the API Attachment Download Path

Fix an issue with the API attachment download path for the call: /v1/attachment/{id}/download

Fixed an Issue Displaying Specific CID’s Under System Filters

Fixed an issue where some parts published from CAD were not included under Filters > Systems. Also fixed an issue where oval duct size was identified.