/
05/04/2023 - v6.2.189

05/04/2023 - v6.2.189

 

05/04/2023 - v6.2.189

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 (Mandatory Quarterly Update)

  • STRATUS Workstation - Yes

  • RazorGage Workstation - Yes

  • Print Workstation - Yes

  • Lightning - Yes

Mandatory Quarterly STRATUS Addin for Revit and AutoCAD

All companies must install the 6.2 STRATUS Addin for Revit and AutoCAD.

Abort Publish When Duplicate UniqueId Detected in Multiple Fabrication Parts

All companies should review their active models to understand the impact of this publish change.

Duplicate GUID Causes

A defect existed in Revit that allowed multiple Fabrication Parts to share the same UniqueId in the model which could break downstream workflows such as creating Package MAJ or PCF files leading to missing or incorrect parts in the Fabrication file. The defect was patched in Revit 2019.2.2, 2020.1, 2021 and later versions to prevent the creation of duplicates, unfortunately there was no automated way provided to fix existing instances of duplicates in models. If a model that was originally authored in an affected version of Revit is upgraded to a newer version that does not contain the defect, the duplicates will unfortunately still exist. To ensure STRATUS is working with validated models this release introduces a check during STRATUS publish to ensure the model does not contain duplicates.

Update 5/11/23

Autodesk has identified additional ways a duplicate GUID can be generated. GTP is working with Autodesk on more flexible ways to correct issues like this in future releases of supported Revit versions.

  1. GUID may be stored on the ITM - Some STRATUS customers have noted that their project started with Revit 2022 or later, after the defect was patched, yet they are still having duplicate GUIDs in their published models. Autodesk just informed GTP that the a duplicate GUID may be stored on the ITM itself, which results in new instances of those parts being created having that ID. 

    1. Resolution: None yet.

  2. Revit Type Selector - A certain sequence of steps with the Revit Type Selector can also result in duplicates and sets the GUID to 00000000-0000-0000-0000-000000000000.

    1. Resolution: No resolution from Autodesk yet but GTP has provided a macro to address the affected parts. See section 3. Detect Duplicate UniqueIds Using a Revit Module

  3. Moving/Copying parts – Moving/Copying parts caused duplicated GUIDs

    1. Resolutions: A fix was released for 2019 through current versions.

End Update 5/11/23

 

STRATUS Message When Duplicate GUID Detected

If any duplicates are detected the publish process will be aborted with a message similar to the following.

Resolutions and Work Arounds

If duplicates are detected, there are 3 options:

1. Deduplicate the ElementIds in the Revit model and Publish the Model

  1. After receiving the cancel publish message (above), review the latest Revit publish log file at: %appdata%/GTP STRATUS Logs/Revit

  2. Copy the ElementIds from the log file and paste them into the Revit model using the “Select by ID” tool.

  3. Deduplicate (delete and redraw) each ElementId. A new Id will be associated with the new part.

  4. Save and republish the model when done.

Below is an example of a GTP STRATUS Log that includes ElementId’s.

2. Continue Publishing with Duplicates (Temporary)

For customers who temporarily accept duplicate UniqueIds, the .json publish configuration can be modified to allow Fab parts with Duplicate Ids to be published. This pathway will be eliminated in a future release in Q3 of 23'.

  1. Open settings.json at: %appdata%/GTP Software Inc/STRATUS

  2. Modify the file by adding the line "AllowFabPartsWithDuplicateGuidsToPublish": true as shown below. Note: The lines in your file might be different. Make sure you add a comma to the preceding line Ex… after the “Warning”):
    "RemoteMinimumLogLevel": "Warning",
    "AllowFabPartsWithDuplicateGuidsToPublish": true

  3. Publish the model. The existing MAJ or PCF file issues will continue.

3. Detect Duplicate UniqueIds Using a Revit Module

Separate from the duplicate UniqueId detection built-in to the STRATUS Addin, duplicate UniqueIds can be detected by running the application macro module below.

Update 5/12/23

On 5/11/23, Andy Robins created a new macro that fixes the issue where the Revit Type Selector sets the GUID to 00000000-0000-0000-0000-000000000000.
On 5/12/23, Andy Robins improved the macro so that all a user has to do is run the macro and save the model. This eliminates the steps of locating elementIds in a log file, copy/paste the element ids into Revit, and run a Fabrication report.

  • The instructions below have been rewritten for this new macro

  • A new DuplicationCheck macro will need to be download.

To create and use a Revit duplicate GUIDs Application Module:

  1. In STRATUS go to Help > Downloads and click the DuplicationCheck link.

    1. Note: If you downloaded the DuplicationCheck.zip file prior to 5/12/23 at 8:00AM CT, please delete it and download again as it has been edited.

  2. Unzip and open the file. This is a .txt file that will be used to create an Application Macro in Revit so that duplicate GUID detection can be run in any Revit model.

  3. Open any Revit project.

  4. To Create a New Module - In Revit click Manage > Macro Manager > Application tab > Module and then paste the name DuplicationCheck for the Module name.

     

  5. Click OK.

  6. The Module will display.

     

  7. In addition, a separate window similar to the following will open. Close this window.

     

  8. To Create a New Macro - Within the Macro Manager with the DuplicationCheck Module highlighted, click Macro button and then enter the same name, DuplicationCheck for the Macro name.

     

  9. Click OK.

  10. A separate window similar to the following will open. Highlight everything and delete.

     

  11. With the DuplicationCheck file downloaded, unzipped, and opened from step #1, copy all of the text.

     

  12. Paste the text it into the Macro in step #10.

     

  13. Click Build > Build Solution.

     

  14. Close the macro window.

  15. Run the DuplicationCheck macro on any Revit project, click Manage > Macro Manager > Application tab > Expand the DuplicationCheck Module in the Macros column > Select the DuplicationCheck Macro > click Run.

     

  16. When no duplicates GUIDs are found , a message similar to the following will display.

     

     

  17. When duplicate GUIDs are found a message similar to the following will display. Notice that this macro informs you how many duplicates have been fixed and need to be fixed.

     

     

  18. Once it is done, save or save as the project.

  19. If you re-run the DuplicationCheck macro, a message similar to the following will display depending on what kind of duplicate GUIDs were in the model.

     

Added Numbering Rule for 'Authoring Software Is Right'

At the company level for item numbering, added the ability to determine which parts will be numbered by the Authoring software (Revit) and which parts will be numbered by STRATUS (Renumber - All Item Numbers). The existing item numbering will continue to work without any changes.

To define numbering rules:

  1. Under Admin > Company > Naming and Numbering > Numbering Rules, 2 tables define numbering rules.

    1. STRATUS is Always Right (Default) - The STRATUS is Always Right table includes the company’s existing numbering rules. These numbering rules are applied to parts that meet the Part Filter when the Renumber - All Item Numbers button is clicked in the STRATUS viewer and the STRATUS.Part.Number property is updated for each part in the filter. See the STRATUS Is Always Right article for more information. Parts that meet the STRATUS is Always Right Part Filter will not be numbered by the authoring software.

    2. Authoring Software Is Right - The Authoring Software Is Right table must first be enabled. See step #2 (below). Once enabled, these numbering rules are applied to parts that meet the Part Filter when the Revit model is published to STRATUS. Parts that meet the Authoring Software Is Right Part Filter will not be numbered by STRATUS.

       

  2. To enable the Authoring Software Is Right table, check the the Enable 'Authoring Software Is Right' For Item Numbering setting under Admin > Company > Settings > Corporate. Click Save when done.

     

    1. Enable for all projects?

      1. Unchecked - When the Enable for all projects? checkbox is unchecked, then under Admin > Project Settings > Item Numbering, the Enable 'Authoring Software Is Right' For Item Numbering checkbox will be independently applied to each project.

      2. Checked - When the Enable for all projects? checkbox is checked, then under Admin > Project Settings > Item Numbering, the Enable 'Authoring Software Is Right' For Item Numbering will be checked and disabled for all projects and Enable 'Authoring Software Is Right' For Item Numbering will be applied. In addition, the Item Numbering Scheme can be selected per project.

         

         

  3. Once enabled, rules can be added to the Authoring Software Is Right table. Click the New Rule button.

    1. Name - Enter the name of the Numbering Rule.

    2. Part Filter - Select the Part Filter. These parts will not be numbered when the Renumber - All Item Numbers button is clicked in the viewer. Instead, they will be numbered by the Property To Map Number From.

    3. Property To Map Number From - The Property To Map Number From field is the Revit field that contains the data to be used for the item number. In the example above, the Diffuser rule’s Property To Map Number From is Mark, which is a property in Revit (below).

       

  4. Add Rule to a Numbering Scheme (and set order) - After any rule has been defined, it must be added to a Numbering Scheme. The Order may also need to be changed depending on Part Filters.

    1. Click New Rule, and select the rule.

    2. The rule be ordered last.

       

    3. Order - The Order determines which Part Filter is run first. When a part matches a Part Filter, it will no longer be available to match other Part Filters.

    4. Rule Type - Notice the Rule Type column informs users whether the rule is Authoring Software Is Right or STRATUS is Right.

  5. When are Numbering Rules applied?
    Note: Parts can match more than one filter. The Numbering Scheme Numbering Rules (see screen shot it step above) are processed one at a time and the Numbering Rule’s Part Filter that first matches the part will take precedence.

    1. In STRATUS - When the user clicks the Renumber - All Item Numbers button in the STRATUS viewer:

      1. The Numbering Scheme Numbering Rules are processed one at a time.

      2. For all parts whose first Part Filter match is associated with a Numbering Rule in the STRATUS Is Always Right table, the STRATUS.Part.Number property will be populated according to the Numbering Rule that matches.

      3. Note: Parts will not be renumbered for all parts whose first Part Filter match is associated with a Numbering Rules in the Authoring Software Is Right table as the STRATUS.Part.Number property is populated from Revit.

    2. From STRATUS to Revit - When the Revit model is imported:

      1. The Numbering Scheme Numbering Rules are processed one at a time.

      2. For all parts whose first Part Filter match is associated with a Numbering Rule in the STRATUS Is Always Right table, the part’s STRATUS.Part.Number property will update Revit. The Revit field updated is defined under Admin > Company > Settings > AutoCAD & Revit > Specific to Revit > Property To Map To Item Number.

    3. From Revit to STRATUS - When the Revit model is published:

      1. The Numbering Scheme Numbering Rules are processed one at a time.

      2. For all parts whose first Part Filter match is associated with a Numbering Rule in the Authoring Software Is Right table, the Property To Map Number From field will populate the STRATUS.Part.Number property in STRATUS.

  6. Example: Authoring Software Is Right

    1. In this example, the Diffuser matches the Authoring Software Is Right Numbering Rule and correctly sets the Mark value from Revit as the STRATUS.Part.Number value in STRATUS.

       

    2. After clicking Renumber - All Item Numbers

      1. The Number and STRATUS.Part.Number will be the same.

      2. The Diffuser matches the Authoring Software Is Right Numbering Rule and correctly sets the Mark value from Revit (Ex. 33) as the tag in STRATUS.

         

Added Automation - Generate on Tracking Status (BOM)

Continued automation development when a package’s tracking status changes configured on the Admin > Company > Package Categories page. This time a package BOM can be automatically generated.

To generate a BOM report for a Package Category when the Tracking Status changes:

  1. For the Package Category (Ex. BOM Trigger) click the associated BOM link. 

  2. The Generate on Tracking Status drop-down will display.

  3. Select a Tracking Status (Ex. Spooled).

     

  4. Change the Tracking Status of any package that uses the associated Package Category (Ex. BOM Trigger) to the selected Tracking Status (Ex. Spooled). This tracking status change can be anywhere a package tracking status can be changed (Ex. Packages > BOM, Packages > Tracking, Packages Dashboard, etc.).

     

  5. A BOM will be automatically be generated and will display on the Package’s BOM tab. It will take time to generate the BOM depending on the number of parts.
    Note: This automatically generated BOM only occurs once when no existing BOM has been previously been generated for the package. If a BOM exists for the package and the package’s tracking status is changed to the tracking status that normally triggers a BOM, a new or 2nd BOM will not be generated.

Added Automation - Generate on Tracking Status (Cut Lists)

Continued automation development when a package’s tracking status changes configured on the Admin > Company > Package Categories page. This time a package Cut List can be automatically generated.

To generate a Cut List report for a Package Category when the Tracking Status changes:

  1. For the Package Category (Ex. Cut List Trigger) click the associated Cut List link. 

  2. The Generate on Tracking Status drop-down will display.

  3. Select a Tracking Status (Ex. Issued for Fabrication).

     

  4. Change the Tracking Status of any package that uses the associated Package Category (Ex. Cut List Trigger) to the selected Tracking Status (Ex. Issued for Fabrication). This tracking status change can be anywhere a package tracking status can be changed (Ex. Packages > Tracking, Packages Dashboard, etc.).

     

  5. A Cut List will be automatically be generated and will display on the Package’s Cut Lists tab. It will take time to generate the Cut List depending on the number of parts.
    Note: This automatically generated Cut List only occurs once when no existing Cut List has been previously been generated for the package. If a Cut List exists for the package and the package’s tracking status is changed to the tracking status that normally triggers a Cut List, a new or 2nd Cut List will not be generated.

Added to Open API

Added the following to the STRATUS - Open API

Package

PATCH - /v2/package/{id}/field

PATCH - /v2/package/{id}/fields

Assembly

PATCH - /v2/assembly/{id}/field

PATCH - /v2/assembly/{id}/fields

Part

PATCH - /v2/part/{id}/field

PATCH - /v2/part/{id}/fields

Added, Updated, or Fixed Admin > Queries

Pre-defined queries under Admin > Company > Queries are increasingly being used to export (Download) data for Power BI reports. In this release:

Added Queries

  • Package Categories

  • Tracking Statuses

  • Packages within Last Year Tracking Entries

  • Properties in Reports

  • Parts by Model in last year

    • Note: If there are too many results, the list of parts can only be viewed after clicking the Download button and opening the file.

       

Updated Queries

  • Packages within Last Year - Added columns CategoryId, NumAssemblies, and NumParts (loose parts)

Fixed Queries

  • Stations

  • Tools

Added Properties STRATUS.Container.Tracking*

Added STRATUS.Container.Tracking* properties that can be used in a report to track the log of a container including the following:

STRATUS.Container.Station
STRATUS.Container.TrackingComments
STRATUS.Container.TrackingHours
STRATUS.Container.TrackingStatusIndex
STRATUS.Container.TrackingStatusHoursLog
STRATUS.Container.TrackingStatusLog
STRATUS.Container.TrackingStatusLogBy
STRATUS.Container.TrackingStatusLogComments
STRATUS.Container.TrackingStatusLogDT
STRATUS.Container.TrackingStatusLogDivision
STRATUS.Container.TrackingStatusLogStation

Added Export BOM As CSV or Excel

Added to the Packages > BOM tab a CSV and Excel button which can be used to export the BOM table “as is” to a file.

Improved Publish and Import Performance for CADmep

Determined that one of the publish/import API calls could be eliminated which is speeding up the publish/import process in general, but noticeably (Ex. 8 hours to 30 minutes) on large CADmep models.

Improved Dashboard Performance (Packages, Assemblies, Containers)

Improved Dashboard performance for Packages, Assemblies, Containers with faster load times and more responsive navigation (scrolling, drop-downs, etc.) as the dashboard is loading.

Updated Attachment Workflow

The workflow to add attachments has been updated to include a file name confirmation.

  1. Click the option to Add Attachment which is available in many places in STRATUS. A find file dialog similar to the following will display.

  2. Select the file and click Open. The new Confirm File Name dialog will display where a user can enter a new file name or click Ok to accept the file name

  3. Click Ok. Once the file is uploaded, the Attachment successfully uploaded message will display and the attachment will display in the list of Attachments.

     

  4. Repeat step #2. If the same file name is selected, the File Name in use message will display and will include several options:

     

    1. Cancel - Click Cancel to cancel the attachment process.

    2. Replace - Click Replace to replace the existing attachment with the selected attachment.

    3. Use Attachment - The Use Attachment button suggests a unique file name by adding (1) and incrementing this value as needed.

Updated Part Template Names For Fabrication Parts (ITM)

Part template names for fabrication parts (ITMs) have caused confusion for end users (shop/VDC) as well as the STRATUS site admins.  Current functionality is to give the pattern the name of the first source file name that STRATUS sees.  For example,  when a user publishes a model with pattern 2041 (pattern for pipe) it will retain the name of the first kind of pipe it sees (carbon, copper, etc.) even though it represents all types of pipes.

To resolve the issue all part template names for fabrication parts have been changed to match the following pattern:
“Fabrication (ITM) pattern <Pattern Number> from <Authoring Software>”

Example:
“Fabrication (ITM) pattern 2041 from Revit”

The pattern number is coming from the “PattNo.” column and the authoring software is coming from the “Type” column. The part template name should be human-readable.

“Autodesk.Fabrication.Item” = AutoCAD Fabrication part

“Autodesk.Revit.DB.FabricationPart” = Revit Fabrication part

Notes:

  • Revit families (parts without a “PattNo.”) are not be affected by this change.

  • This change does NOT affect “PattNo.” 2875 - “PattNo.” 2875 should use the current logic (it is a special case and needs to be handled separately to make the initial setup easier)

  • All fabrication parts that are not “PattNo.” 2875 should use the following format for their “Name”

    • “Fabrication (ITM) pattern <Pattern Number> from <Authoring Software>”

Updated Cut List Stations

Updated the Station drop-down list under Packages > Cut Lists to only display Stations that have a tool assigned.

For example:

  1. Under Admin > Company > Stations, the Tool for the Station below is Empty (not assigned).

     

  2. As a result, the Packages > Cut Lists > Station drop-down will not include the Station in the drop-down list.

Updated the Add Lightning Catalog Parts Dialog

Previously, the Add Lightning Catalog Parts dialog provided Filter options, but users still had to drill down in the Select Catalog to locate the parts (7 clicks in the example below). With this change, filtering to Material, for example, will immediately expand the Select Catalog to the items that meet the filter criteria.

v6.1.4 Hotfixes Applied Between 4/6 and 5/1

Updated Assemblies Dashboard and Viewer Filtering

In some cases with filters applied, the Assemblies Viewer was not correctly filtering out assemblies. With this ticket, assemblies that don’t match filters will be correctly filtered out, but additional messaging has also been added to help users understand the state of their filters. Below is an exmaple:

  1. In the example below, the Assemblies Dashboard initially displays with default filters:

    1. Package = (Unspecified)

    2. Division = (All)

    3. Status = (All) filters

  2. The Status filter is changed to Issued, but no assembly is in the Issued tracking status. So the red warning message displays “No items in this table or no matching filters.”

    1. Status = Issued

  3. With no assemblies matching the Dashboard filter, the Viewer tab is clicked. Since no assemblies match the filter, the message displays “No Assemblies match this filter as set in the Project Context bar. Please adjust your filters as necessary to view available assemblies.” In addition, the filter bar (Project, Model, View, Package, Division, Status, and Assembly) are disabled behind the STRATUS message.

     

  4. If the user attempts to continue by refreshing the web browser, instead of displaying no content, the normal Assemblies Viewer and right-side content will load, but the Assembly drop-down will have a red background and a message will display that says: “Active Assembly does not match Active Filters. Please adjust your filters as necessary to view available assemblies.”

     

  5. After clicking Ok, the filter bar (Project, Model, View, Package, Division, Status, and Assembly) is enabled and the user can modify one or more filters.

     

Updated Assemblies Viewer STRATUS Sheet to Automatically Display Item Numbers

Updated the Assemblies > Viewer > STRATUS Sheet to automatically display Item Numbers without having to click the Display - Item Numbers button in the 3D viewer. This change is especially usefully for batch printing so that each assembly does not have to be touched in order to generate a STRATUS Sheet with item numbers.
Note: The behavior of the selected report and STRATUS Sheet has not changed, namely that a report is associated with a Template, and the Template must include a View (Top, Front, or Isometric) that is configured with a View Style which controls the item number formatting.

  1. Previously, in the Assemblies > Viewer a user had to:

    1. Click the Display - Item Numbers button in the 3D viewer. This step is eliminated if the assemblies parts includes item numbers.

    2. Select the report in the Parts tab.

    3. Click the STRATUS Sheet tab for item numbers to display.

       

  2. With this change, as long as parts in the assembly have item numbers a user can:

    1. Select the report in the Parts tab.

    2. Click the STRATUS Sheet tab for item numbers to display.

Fixed Issues on Project > Admin > Teams

Fixed issues on Project > Admin > Teams page:

  1. New Users could not be added to projects as the Save button remained disabled.

  2. The list of users did not update when a different project was selected.

     

Fixed Assemblies Viewer Edit Assembly Name Display

Fixed an issue in the Assemblies > Viewer where after selecting a different assembly or changing a filter, the Edit Assembly Name would disappear.

Fixed Issue Printing Containers PDF Report

Fixed an issue printing a PDF report under Containers > Assign, selecting a container and a PDF report.

Fixed Issue Rounding Decimal Fields in Templates