Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
05/07/2024 - v7.2.1 - STRATUS
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. 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.
To update to the latest installers see the Installation of GTP Software on Windows article for more information.
Revit and AutoCAD Addin - Yes
STRATUS Workstation - Yes - Recommended, but not Required
RazorGage Workstation - No
Print Workstation - No
Lightning - Yes - Recommended, but not Required
Release Webinar
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Added Password Requirements to Enforce NIST Guidelines
Added Password Requirements to enforce NIST Guidelines. No one will be forced to change their password with the release of this version.
See the Password Requirements article for more information.
Summary
Characters required include:
A - Z
a - z
0 - 9
Password restrictions
16 characters minimum and 64 characters maximum
Last 3 passwords cannot be re-used
Password must be reset annually
While special characters are allowed they are not required.
Added Dashboard Column Visibility Setting
Added to all dashboards a Column Visibility Settings feature which enables each user the ability to control columns they see in each report. Admins will no longer need to create entire new reports to limit or expand columns.
To use the Column Visibility Settings feature:
On the report, click the Column Visibility Settings button.
Image RemovedThe Column Visibility Settings dialog will display with a list of the report fields contained in the report. By default all columns are checked visible.
Image RemovedUncheck or Check individual report fields, or click the checkbox adjacent to the Column Visibility Settings heading to check or uncheck all checkboxes. When done click Apply.
Image RemovedOnly the checked columns will be visible.
Image RemovedButton Indicators:
By default, when all Columns are checked both bars will be hollow.
Image RemovedWhen one or more Columns are unchecked, one bar will be shaded.
Image Removed
Notes:
When a user switches to a different report that has not been customized, all report field columns in the new report will be checked by default.
Each report will retain the user's specific settings until one of the following occurs:
The user updates their selection of visible items on each specific report.
The report is updated by an administration under Admin > Company > Reports in which case all report fields will be visible.
Added Model Shipping Address as a Reportable Property
Added Model Shipping Address as a reportable Property which makes project shipping addresses accessible outside of the Package BOM report.
To configure:
Shipping Addresses: Under Projects > Shipping Addresses, enter or import shipping addresses. (Optional) By setting the default to one a row, the Shipping Address on the Models > Dashboard will default to the selection.
Image RemovedModels Shipping Addresses: In the Models > Dashboard, select the Shipping Address. If a default was set (above), it will be automatically selected for all models. Note: The Shipping Address value can be overridden as needed.
Image RemovedReport Setup:
Reports can be setup for the following Item Types
Assembly
Container
Container Details
Package
Package Details
Part
Example
Image Removed
Report Fields: In each report, the following Report Fields are available:
STRATUS.Model.ShippingAddress
STRATUS.Model.ShippingAddress.Name
STRATUS.Model.ShippingAddress.Address1
STRATUS.Model.ShippingAddress.Address2
STRATUS.Model.ShippingAddress.City
STRATUS.Model.ShippingAddress.State
STRATUS.Model.ShippingAddress.Zip
STRATUS.Model.ShippingAddress.Attention
STRATUS.Model.ShippingAddress.Instructions
STRATUS.Model.ShippingAddress.Phone
Template: Users can reference the STRATUS.Model.ShippingAddress Report Fields on the following Template Types:
Package Sheet
Assemblies Sheet
Package BOM
Container Details
Updated Item Numbering and Tagging
Major updates have been made to Item Numbering and Tagging.
Summary 1 from the epic
Simplify the Admin setup:
All numbering and tagging rules are controlled under Admin > Company > Naming and Numbering > Numbering Schemes
The Numbering Scheme is applied under Admin > Project > Settings
Standardize and make it clear what each numbering setting will do and when
Make number behavior consistent when importing and publishing
Separate Tagging and modifying the part number controls in the viewer to reduce mistakes
Improved Visibility Control:
Implement toggles for better visibility control: Show, Hide, Delete, Renumber
Integrate advanced controls, including move, off, and delete functionalities
User-Friendly Naming and Numbering:
Have individual buttons for tagging and modifying item numbers
Incorporate tooltips and instructions to guide users through naming and numbering schemes
STRATUS.Part.Number is the only number property recognized by STRATUS as anything more than a generic property on a part
Allow editing of STRATUS.Part.Number
Decouple “Number” and STRATUS.Part.Number
Only STRATUS.Part.Number should change when renumbering
Tags will display STRATUS.Part.Number
Auto-update tags when STRATUS.Part.Number changes without a page refresh
Summary of the Changes to Numbering and Tagging
Image RemovedThe STRATUS.Part.Number will now be treated consistently across the STRATUS platform, similar to how STRATUS.Part.AssemblyName is currently used. This means STRATUS.Part.Number will be the primary reference for part numbers in all contexts, ensuring that it is always up-to-date.
The Renumber Parts When Creating or Modifying Assemblies setting has been moved to the Numbering Schemes page for project-level control.
The Use Number Rule Setting for Matching Parts and Matching Parts Get Same Item Number settings have been removed since you can control this with the Numbering Rules. We interrogated our database and found that every STRATUS customer already had these turned on.
The Enable 'Authoring Software Is Right' For Item Numbering in the Company and Project Admin has been removed since the same can be achieved with the Authoring Software is Right numbering rules.
STRATUS part tags ONLY display the value from/in STRATUS.Part.Number property.
The renumber button updates the STRATUS.Part.Number property only
The Display - Item Numbers toolbar button has been renamed to Display Tags And Item Numbers Toolbar. It no longer creates tags when pressed, it only shows or hides existing tags. Number and tag creation can still be automated for assemblies by using the Renumber Parts When Creating or Modifying Assemblies setting in the numbering scheme.
Tags will now dynamically display the current values of whatever property they are referencing. For standard item number tags, they will reference the STRATUS.Part.Number property. Any tags that reference a blank value will be removed upon deletion of the value.
Of note: Existing static tags will not disappear with this update, but will be updated to dynamic tags once a change has been made to the STRATUS.Part.Number property or once new tags are placed.
These functions have now been broken out to allow discrete control over the creation of part numbers and tags. These are as follows:
Renumber Parts - Only acts to renumber parts based on numbering rules and schemes. There are no changes to the functionality in how numbers are generated on parts. Additional functionality has been added that allows you to now filter to parts in viewers and renumber only them.
Create Tags - Creates tags according to your numbering scheme for any parts that are not already tagged, but that have a value in STRATUS.Part.Number. Additional functionality has been added that allows you to now filter to parts in viewers and tag only them.
Renumber and Tag Parts - Operates the Renumber Parts and Create Tags functions sequentially.
The “Bulk Delete - Delete All Item Numbers And Tags” functionality has been replaced by two distinct functions and they are as follows:
Delete Part Item Numbers - Removes values applied to the STRATUS.Part.Number property for all parts in the view. Any tags that now reference a blank value are also removed.
Delete All Tags - Removes any visible tags when this button is clicked.
Project roles have been added to control the availability of these new and modified features in the models, packages, and assemblies viewers.
Project Roles
Image RemovedSettings - Numbering Schemes
When a user publishes a model or clicks Numbering Schemes control xyz
Number Assembled Parts - When parts in the viewer are included in an assembly, this setting controls what gets numbered when the Renumber Parts or Renumber and Tag Parts button is clicked in any viewer.
Number Unassembled Parts - When parts in the viewer are not included in an assembly, this setting controls what gets numbered when the Renumber Parts or Renumber and Tag Parts button is clicked in any viewer.
Renumber Parts on Modify Assembly:
will apply the numbering scheme automatically when an assembly is created or modified
will add tags for any parts that get a new number
will only delete tags if the part it was associated with was removed from the assembly or the numbering scheme does not apply a number to that part.
will not reset tag positions
STRATUS.Part.Number
STRATUS.Part.Number is the source of truth for item numbers in STRATUS.
If any Report, Field Expression, or Alias is using Number or Item Number properties, it should be changed to STRATUS.Part.Number.
Tagging and Reports - STRATUS.Part.Number is the only property used by STRATUS in item numbering tagging and reports. .
Edit Individual - An individual STRATUS.Part.Number can be edited in the Properties panel and in a Parts report.
Edit by Renumbering - STRATUS.Part.Number’s for all parts in the viewer can be renumbered.
Control the editability in the Part Template. See the Part Templates (Admin) article for more information.
Assemblies > Viewer > Parts - The default report now uses STRATUS.Part.Number
Image Removedhttps://gtpservices.atlassian.net/browse/SPVR-14836
Part tags should automatically update the value displayed when STRATUS.Part.Number is updated. There should not be a need to refresh the page.
Update STRATUS.Part.Number via part properties
Update STRATUS.Part.Number via assembly part report
The part tags should be updated on every viewer they display if STRATUS.Part.Number changes.
Update STRATUS.Part.Number via publish
If a tag is placed and the value updates to null or an empty string, we will automatically remove the tag. This should only happen if there is no value to display in the tag.
Custom Tags
Image RemovedWhen placing a Custom Tag:
Field and Alias tags are static once placed and will not update when either changes.
Display - Item Numbers Toolbar
This button replaces the Display Item Numbers button on the STRATUS Toolbar. The Display Item Number Toolbar button does not generates item numbers and tags, instead, separate buttons on the Display Renumber Toolbar for Renumber Parts, Apply Tags will be used.
Apply Tags Flyout Buttons
Image RemovedApply Tags
Click the Apply Tags button to display any placed tags in the viewer.
Delete All Tags Flyout Buttons
Image RemovedAdded Filter to Generate MAJ File
Added Filter to breakout MAJ files. Currently, creating a MAJ file is limited to a single MAJ file for a package. With this feature multiple MAJ files can be created based on a filter to where some items can go to the coil line and other items to a plasma table. This eliminates the need to create separate packages. To use this feature:
Create one or more filters under Admin > Company > Filter. In this example, the 2 filters both use the CutType Property, but the value is DecoiledStraight for one and MachineCut for the other. Note: The filte name will be used to name the generated MAJ file.
Image RemovedApply the filter to a package category under Admin > Company > Package Categories.
Image RemovedUnder MAJ Filters, click New MAJ Filter to add one or more filters.
Image RemovedIf a report is selected for MAJ under Generate on Tracking Status, the generated reports will apply the MAJ Filters.
When generated, the MAJ files will display in the package’s Attachments tab.
Image Removed
Updated Attachments Table Rollup
Updated the Attachments table for Packages and Assemblies. One example for applying this change is to simplify the batch reporting process.
to your workflow is that, a package’s sub-components
assembly attachment and parts in a package the package Attachments table will display all attachments by Source Type.
Image Removed
Image RemovedImage RemovedImage Removed
Image Removed
Updated Auto Consolidation in BOM Settings
Currently when selecting the Auto Consolidation, in the BOM Settings, like parts do not merge because they have separate Part Templates.
Image RemovedWith this change, when consolidating items with the same Size, Description, Material, and Unit of Measure the Auto Consolidation will not consider the Part Templates. Everything happens in the background. The functionality is the same for the user.
Consolidated:
Image RemovedUpdated Lightning Catalog Parts Add/Remove Activities
Updated Lightning Catalog Parts Add/Remove Activities
Fixed and Updated User Management
Updated Add New Users in Disabled Status
When adding new users using the Refresh Users from Autodesk Construction Cloud button under Admin > Company > Users, the newly added user(s) will be disabled. As a result, newly added users do not consume a license until their Status is manually changed from Disabled to Active.
Updated Default Project Role Issue
Updated the Assign New User Role dialog selection results.
A Default Project Role is selected.
Image RemovedThe Admin clicks Next. The Assign New User Role dialog displays. The Role for every existing project will be set to the selected Default Project Role.
Image RemovedTo change a Role for a specific project, click the current role and select a new Role. Note: Checkboxes are only used to add the user to the project.
Fixed Issue with Default Project Role when Adding User to Project
Fixed an issue under Admin > Project > Team, where after clicking the New button, if the user selected in the User drop-down has an existing default project role, that role should automatically display in the Project Role drop-down.
Image RemovedFixed Issue Updating a User
Fixed an issue updating a user under Admin > Company > Users, where after removing a user’s access to a project by unchecking the project, the user user was incorrectly removed from all projects. With this fix, the user will only be removed from the unchecked projects.
Image RemovedUpdated Report Column Width Word Wrapping
Updated report column widths so that word wrapping does not occur in the middle of a continuous text string.
Old Word Wrap
New Word Wrap
Image Removed
Image Removed
Image Removed
Image Removed
Fixed an Issue with Email Notifications
Fixed an issue when under Account Settings > Notifications, when Package > Tracking Status Changed was checked and a tracking status to a package was made, an email was not received.
Updated API for Number Property
Companies who reference the Number property in any API call need to update the property to STRATUSPartNumber.
Image RemovedRemoved Purchasing and Supplier References
Removed Purchasing, Receiving, and Supplier references from the website. Contact the STRATUS Service Desk to toggle these features back on.
Fixed Issue with 'Add Lightning Catalog Parts' to Package under Items
Fixed an with the Add Lightning Catalog Parts feature limiting the number of parts that could be added. See the Lightning Catalog Partsarticle for more information.Fixed Issue Where Deliverables Did Not Generate Without an Area
Fixed an issue generating Deliverables when the model parts did not have an area (Ex. STRATUS.Part.BIMArea). With this fix:
Deliverables will be generated when the parts do not have a STRATUS.Part.BIMArea
The Deliverables without area checkbox option has been added to the Area Selection Filter.
Image Removed
05/07/2024 - v1.0.2 - FLEX
Viewer (Beta)
This initial rollout includes tracking status and package filters. We are working on performance optimizations, particularly for larger models. Additional features will be continuously added in future releases, further refining the functionality and user experience of the model viewer.05/14/2024 - v7.2.1 - STRATUS
Yellowstone Release Known Issues Log
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. 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.
To update to the latest installers see the Installation of GTP Software on Windows article for more information.
Revit and AutoCAD Addin - Yes - Required for FLEX model viewer publishes
STRATUS Workstation - Yes - Recommended, but not Required
RazorGage Workstation - No
Print Workstation - No
Lightning - Yes - Recommended, but not Required
Release Highlights
Widget Connector | ||||||
---|---|---|---|---|---|---|
|
Table of Contents | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Added Password Requirements to Enforce NIST Guidelines
Added Password Requirements to enforce NIST Guidelines. No one will be forced to change their password in this release unless a new password is created.
See the Password Requirements article for more information.
Summary
Characters required include:
A - Z
a - z
0 - 9
Password restrictions
16 characters minimum and 64 characters maximum
Last 3 passwords cannot be re-used
Password must be reset annually
While special characters are allowed they are not required.
Updated Item Numbering and Tagging
Major updates have been made to Item Numbering and Tagging.
Summary of the Changes to Numbering and Tagging
Image AddedThe STRATUS.Part.Number will now be treated consistently across the STRATUS platform, similar to how STRATUS.Part.AssemblyName is currently used. This means STRATUS.Part.Number will be the primary reference for part numbers in all contexts, ensuring that it is always up-to-date.
The Renumber Parts When Creating or Modifying Assemblies setting has been moved to the Numbering Schemes page for project-level control.
The Use Number Rule Setting for Matching Parts and Matching Parts Get Same Item Number settings have been removed since you can control this with the Numbering Rules. We interrogated our database and found that every STRATUS customer already had these turned on.
The Enable 'Authoring Software Is Right' For Item Numbering in the Company and Project Admin has been removed since the same can be achieved with the Authoring Software is Right numbering rules.
STRATUS part tags ONLY display the value from/in STRATUS.Part.Number property.
The renumber button updates the STRATUS.Part.Number property only
The Display - Item Numbers toolbar button has been renamed to Display Tags And Item Numbers Toolbar. It no longer creates tags when pressed, it only shows or hides existing tags. Number and tag creation can still be automated for assemblies by using the Renumber Parts When Creating or Modifying Assemblies setting in the numbering scheme.
Tags will now dynamically display the current values of whatever property they are referencing. For standard item number tags, they will reference the STRATUS.Part.Number property. Any tags that reference a blank value will be removed upon deletion of the value.
Of note: Existing static tags will not disappear with this update, but will be updated to dynamic tags once a change has been made to the STRATUS.Part.Number property or once new tags are placed.
These functions have now been broken out to allow discrete control over the creation of part numbers and tags. These are as follows:
Renumber Parts - Only acts to renumber parts based on numbering rules and schemes. There are no changes to the functionality in how numbers are generated on parts. Additional functionality has been added that allows you to now filter to parts in viewers and renumber only them.
Create Tags - Creates tags according to your numbering scheme for any parts that are not already tagged, but that have a value in STRATUS.Part.Number. Additional functionality has been added that allows you to now filter to parts in viewers and tag only them.
Renumber and Tag Parts - Operates the Renumber Parts and Create Tags functions sequentially.
The “Bulk Delete - Delete All Item Numbers And Tags” functionality has been replaced by two distinct functions and they are as follows:
Delete Part Item Numbers - Removes values applied to the STRATUS.Part.Number property for all parts in the view. Any tags that now reference a blank value are also removed.
Delete All Tags - Removes any visible tags when this button is clicked.
Project roles have been added to control the availability of these new and modified features in the models, packages, and assemblies viewers.
Project Roles
Image AddedSettings - Numbering Schemes
Configuration settings for Item Numbering and Tagging rules has been moved to the Naming and Numbering tab. Below is the Numbering Schemes tab.
Image AddedCustom Tags
Custom Tags for Item Numbering, Notes, and Properties display dynamically as model information changes, while Field and Alias tags are static.
Image AddedAdded Dashboard Column Visibility Setting
Added to all dashboards a Column Visibility Settings feature which enables each user the ability to control columns they see in each report. Admins will no longer need to create entire new reports to limit or expand columns.
To use the Column Visibility Settings feature:
On the report, click the Column Visibility Settings button.
Image AddedThe Column Visibility Settings dialog will display with a list of the report fields contained in the report. By default all columns are checked visible.
Image AddedUncheck or Check individual report fields, or click the checkbox adjacent to the Column Visibility Settings heading to check or uncheck all checkboxes. When done click Apply.
Image AddedOnly the checked columns will be visible.
Image AddedButton Indicators:
By default, when all Columns are checked both bars will be hollow.
Image AddedWhen one or more Columns are unchecked, one bar will be shaded.
Image Added
Notes:
When a user switches to a different report that has not been customized, all report field columns in the new report will be checked by default.
Each report will retain the user's specific settings until one of the following occurs:
The user updates their selection of visible items on each specific report.
The report is updated by an administration under Admin > Company > Reports in which case all report fields will be visible.
Updated Attachments Table Rollup
Updated the Attachments table for Packages and Assemblies to rollup all associated attachments. Expand any Source Type to display the rollup content (Ex. PDV, CSV, image, Markup Tools, etc.).
Image AddedImage Added
Added Filter to Generate MAJ File
Added Filter to breakout MAJ files. Currently, creating a MAJ file is limited to a single MAJ file for a package. With this feature multiple MAJ files can be created based on a filter to where some items can go to the coil line and other items to a plasma table. This eliminates the need to create separate packages. To use this feature:
Create one or more filters under Admin > Company > Filter. In this example, the 2 filters both use the CutType Property, but the value is DecoiledStraight for one and MachineCut for the other. Note: The filte name will be used to name the generated MAJ file.
Image AddedApply the filter to a package category under Admin > Company > Package Categories.
Image AddedUnder MAJ Filters, click New MAJ Filter to add one or more filters.
Image AddedIf a report is selected for MAJ under Generate on Tracking Status, the generated reports will apply the MAJ Filters.
When generated, the MAJ files will display in the package’s Attachments tab.
Image Added
Added Model Shipping Address as a Reportable Property
Added Model Shipping Address as a reportable Property which makes project shipping addresses accessible outside of the Package BOM report.
To configure:
Shipping Addresses: Under Projects > Shipping Addresses, enter or import shipping addresses. (Optional) By setting the default to one a row, the Shipping Address on the Models > Dashboard will default to the selection.
Image AddedModels Shipping Addresses: In the Models > Dashboard, select the Shipping Address. If a default was set (above), it will be automatically selected for all models. Note: The Shipping Address value can be overridden as needed.
Image AddedReport Setup:
Reports can be setup for the following Item Types
Assembly
Container
Container Details
Package
Package Details
Part
Example
Image Added
Report Fields: In each report, the following Report Fields are available:
STRATUS.Model.ShippingAddress
STRATUS.Model.ShippingAddress.Name
STRATUS.Model.ShippingAddress.Address1
STRATUS.Model.ShippingAddress.Address2
STRATUS.Model.ShippingAddress.City
STRATUS.Model.ShippingAddress.State
STRATUS.Model.ShippingAddress.Zip
STRATUS.Model.ShippingAddress.Attention
STRATUS.Model.ShippingAddress.Instructions
STRATUS.Model.ShippingAddress.Phone
Template: Users can reference the STRATUS.Model.ShippingAddress Report Fields on the following Template Types:
Package Sheet
Assemblies Sheet
Package BOM
Container Details
Updated Auto Consolidation in BOM Settings
Currently when selecting the Auto Consolidation, in the BOM Settings, like parts do not merge because they have separate Part Templates.
Image AddedWith this change, when consolidating items with the same Size, Description, Material, and Unit of Measure the Auto Consolidation will not consider the Part Templates. Everything happens in the background. The functionality is the same for the user.
Consolidated:
Image AddedUpdated Pipe Cuts
Connectors New Root Gap Setting
Updated Pipe Cut Connectors with a Root Gap configuration option. The Root Gap is the gap between two connecting pipes and is specified when the gap is not modeled with a part so pipe cutting software can account for it during fabrication. The Root Gap column defaults to 0 and is exported within the PSVR file when the value is greater than zero. Root Gap does not impact cut lengths or reporting in STRATUS.
Under Admin > Company > Pipe Cuts > Connectors, set a Root Gap value.
Image AddedGenerate a .PSVR file. Root Gap values greater than 0 will be included in the exported file.
Image Added
Olets New Cut Surface Setting
Updated Pipe Cut Olets with a Cut Surface configuration option. The Cut Surface is the pipe diameter reference for olet hole cuts and may be either ID (inside diameter) or OD (outside diameter). The Cut Surface column defaults to OD and can be changed to ID. The value will be exported within the PSVR file.
Under Admin > Company > Pipe Cuts > Olets, the Cut Surface is set to OD by default or can be changed to ID.
Image AddedGenerate a .PSVR file. The Cut Surface value will be included in the exported file.
Image Added
Updated Lightning Catalog Parts Add/Remove Activities
Updated Lightning Catalog Parts Add/Remove Activities
Fixed and Updated User Management
Updated Add New Users in Disabled Status
When adding new users using the Refresh Users from Autodesk Construction Cloud button under Admin > Company > Users, the newly added user(s) will be disabled. As a result, newly added users do not consume a license until their Status is manually changed from Disabled to Active.
Updated Default Project Role Issue
Updated the Assign New User Role dialog selection results.
A Default Project Role is selected.
Image AddedThe Admin clicks Next. The Assign New User Role dialog displays. The Role for every existing project will be set to the selected Default Project Role.
Image AddedTo change a Role for a specific project, click the current role and select a new Role. Note: Checkboxes are only used to add the user to the project.
Fixed Issue with Default Project Role when Adding User to Project
Fixed an issue under Admin > Project > Team, where after clicking the New button, if the user selected in the User drop-down has an existing default project role, that role should automatically display in the Project Role drop-down.
Image AddedFixed Issue Updating a User
Fixed an issue updating a user under Admin > Company > Users, where after removing a user’s access to a project by unchecking the project, the user user was incorrectly removed from all projects. With this fix, the user will only be removed from the unchecked projects.
Image AddedUpdated Report Column Width Word Wrapping
Updated report column widths so that word wrapping does not occur in the middle of a continuous text string.
Old Word Wrap | New Word Wrap |
---|---|
Image Added | Image Added |
Image Added | Image Added |
Fixed an Issue with Email Notifications
Fixed an issue when under Account Settings > Notifications, when Package > Tracking Status Changed was checked and a tracking status to a package was made, an email was not received.
Updated API for Number Property
Companies who reference the Number property in any API call need to update the property to STRATUSPartNumber.
Image AddedRemoved Purchasing and Supplier References
Removed Purchasing, Receiving, and Supplier references from the website. Contact the STRATUS Service Desk to toggle these features back on.
Fixed Issue with 'Add Lightning Catalog Parts' to Package under Items
Fixed an with the Add Lightning Catalog Parts feature limiting the number of parts that could be added. See the Lightning Catalog Partsarticle for more information.
Fixed Issue Where Deliverables Did Not Generate Without an Area
Fixed an issue generating Deliverables when the model parts did not have an area (Ex. STRATUS.Part.BIMArea). With this fix:
Deliverables will be generated when the parts do not have a STRATUS.Part.BIMArea
The Deliverables without area checkbox option has been added to the Area Selection Filter.
Image Added
05/07/2024 - v1.0.2 - FLEX
Viewer (Beta)
To enable publishing to FLEX, you will need the 7.2.1 or newer version of the add-in. There is also a settting on Admin-Company-Projects to enable each project to be published to FLEX. Only Revit models are currently supported on Flex.
Image AddedThis initial rollout includes tracking status and package filters. We are working on performance optimizations, particularly for larger models. Additional features will be continuously added in future releases, further refining the model viewer's functionality and user experience.
Image AddedAdded the Ability to Create a Package
Added a New Package button to the Packages page. The button will be enabled whenever the device is connected to the internet.
Image AddedThe new Package button opens a menu to define your package properties and upload attachments. The package will be available on the STRATUS website at the time of creation.
Image AddedAdded Support for Scanning the Container QR codes
Added the ability to scan container QR codes and update the status of those containers.
Image Added