01/26/2022 - v5.0.5.21
- 1 01/26/2022 - v5.0.5.21
- 1.1 Disabled the v1 Publisher
- 1.2 Added Project MAJ Dynamic Hole Setting
- 1.3 Added All Custom Fields to Packages > Properties
- 1.4 Added STRATUS.Part.TrackingStatusLogComments for Part, Assembly, and Package Reports
- 1.5 Added Purchase Status Fields
- 1.6 Added Address Fields for Processors
- 1.7 Added Ability to Filter and Report on Parent Families that Consist of Only Shared Nested Families
- 1.8 Added Ability to Attach a .rej File
- 1.9 Fixed Issues with Dimensions on Conduit
- 1.10 Fixed a Package ZPL Report Issue with QR Codes
- 1.11 Fixed a Display Issue with STRATUS.Part.Container
01/26/2022 - v5.0.5.21
Disabled the v1 Publisher
The v1 Publisher has been disabled. For information on the v2 publisher, please reference the Publish and Import documentation in the Knowledge Base.
Added Project MAJ Dynamic Hole Setting
Added to Admin > Project > Settings a MAJ Files Include Dynamic Holes setting. As per Autodesk, “This feature allows holes to be intelligently cut into rectangular straight developments when positioning taps\shoes, or any object, to the face of straight duct (CID 866). This eliminates the need to manually edit developments in CAMduct.”
Checked (Default) - Currently, STRATUS includes dynamic hole data when the model is published.
Unhecked - Disable dynamic hole data on next publish.
Added All Custom Fields to Packages > Properties
Added to Packages > Properties, all available company fields that:
Are associated with packages via a Packages Dashboard report
Are set as editable in the company field definition
Are not hidden in the report
Previously, only custom fields that included a value were displayed. Note: The display name will be the report column header and not the field definition name which is the same as when they appear in the “New Package” dialog.
Added STRATUS.Part.TrackingStatusLogComments for Part, Assembly, and Package Reports
Added STRATUS.Part.TrackingStatusLogComments for Part, Assembly, and Package Reports.
Example Report Item Type = Part
Example: Report Item Type = Assembly
Example: Report Item Type = Package
Added Purchase Status Fields
Added the following Purchase Status Fields which separates the package status from the parts purchasing status.
STRATUS.Part.PurchaseStatus
Where Available: In reports where Type is Part.
Property Purpose: When used the column will report the Purchasing status of its individual parts. For example, the Status is the Package status whereas the Purchase Status is status of parts in the Purchasing process:
STRATUS.Package.PurchaseStatusLowest
Where Available: In reports where Type is Package.
Property Purpose: When used the column will report the lowest tracking status for a package based on the statuses of its individual parts. For example:
If any part in a package has the status of None, then the lowest tracking status will be None.
If all parts in the package have a status other than None, then the lowest tracking status will be the lowest (Ex. Purchase Order Processed).
STRATUS.Package.PurchaseStatusList
Where Available: In reports where Type is Package.
Property Purpose: When used the column will report the number of parts in each Purchasing tracking status greater than 0. In the package below, there are 0 parts in None, 16 parts in Purchase Order Processed, and 2 parts in Shipped.
Added Address Fields for Processors
Under Admin > Company > Processors, added address fields (Country, Address, City, State, Zip) for Processors.
Added Ability to Filter and Report on Parent Families that Consist of Only Shared Nested Families
Added ability to filter and report on parent families that consist of only shared nested families. This did not previously exist because parent objects did not return an ID from Forge and did not contain native geometry. Below are report examples.
Create a family report
Create a Shared Nested Parent Family
Added Ability to Attach a .rej File
Added the ability to attach a remote entry job file *.rej from Fabrication.
Fixed Issues with Dimensions on Conduit
Fixed issues with dimensions on Conduit. The model will need to be re-published for these changes to display.
For a coupling on the end of a conduit, the dimension was being ignored with Auto Dimensioning as shown in the image below.
For a coupling on the end of a conduit, the dimension was being pulled from the far side of the connector in the coupling instead of to the end of the conduit.
Fixed a Package ZPL Report Issue with QR Codes
Fixed an issue where QR codes did not display correctly on a report run from the Models Viewer. The report was set up as follows:
Format = ZPL
Item Type = Package
Label Template - Included {{STRATUS.Package.QRCode}}
A Report Field - Included STRATUS.Package.QRCode
Fixed a Display Issue with STRATUS.Part.Container
Fixed an issue where STRATUS.Part.Container did not display a value. When a Part, Assembly, or Package is selected, the related field in the Properties panel should display.
STRATUS.Part.Container in viewer properties panel
STRATUS.Assembly.Container in a report
STRATUS.Package.Container in a Packages Dashboard report