/
04/07/2021 - v3.5.24.17

04/07/2021 - v3.5.24.17

04/07/2021 - v3.5.24.17

Added AsFeetInch() Function Expression Function

Added the AsFeetInch() function to the expression engine. This function provides the ability to format decimal dimension values as feet-inch for display purposes in custom field expressions. This is useful when you want to format a value that does not use the Report Engine Display Format value, like a bottom of pipe calculation on a sticker, for example, which uses the raw Storage Format value.

Below is an example of AsFeetInch():

Generic Syntax: AsFeetInch(Feet, Precision (optional, defaults to 8), Format (optional, defaults to 0, 0=feet-inch-fraction, 1=inches-fraction))

This example will return a formatted string with the feet, precision of 2, as feet-inch fraction:
AsFeetInch(STRATUS.Field.GTP Linear Feet,2,0)

Field Configuration:

Report Property Configuration Example:

Packages Dashboard Report Example:

Added TrackingStatusBy() Expression Function

Added the TrackingStatusBy() function to the expression engine. This function is used to determine the name of the user who made a specific tracking status change.

Below is an example of TrackingStatusBy():

Generic Syntax: TrackingStatusBy({STRATUS.*.TrackingStatusLog}, TrackingStatus, {STRATUS.*.TrackingStatusLogBy}, UseLastIndex)
Note: UseLastIndex defaults to False which will return the last username that changed the tracking status to the configured tracking status. If it is set to True, it will return the username who first changed the tracking status to Packaged.

This example will return the UserName who first changed the tracking status to Packaged if found, otherwise empty:
TrackingStatusBy({STRATUS.Package.TrackingStatusLog}, 'Packaged', {STRATUS.Package.TrackingStatusLogBy}, True)

Field Configuration:

Report Property Configuration Example:

Packages Dashboard Report Example:

Added Report Properties

STRATUS.*.Processor, STRATUS.*.Station, and STRATUS.*.TrackingStatusLogProcessor for Report Properties

Added STRATUS.*.Processor, STRATUS.*.Station, and STRATUS.*.TrackingStatusLogProcessor for reporting.

This includes the following:

  • STRATUS.Part.Processor

  • STRATUS.Assembly.Processor

  • STRATUS.Package.Processor

  • STRATUS.Part.Station

  • STRATUS.Assembly.Station

  • STRATUS.Package.Station

  • STRATUS.Part.TrackingStatusLogProcessor

  • STRATUS.Assembly.TrackingStatusLogProcessor

  • STRATUS.Package.TrackingStatusLogProcessor

Added STRATUS.Project.ManufactureSourceType Report Property

Added the STRATUS.Project.ManufactureSourceType Report Property as an available Field Property to be used in reports where Item Type = Part. The field will match the value set under Admin > Company > Projects > Manufacturer Source Type.

Added BOM and Purchasing Properties to Package Reports

The following BOM and Purchasing Properties can be added to a Packages Dashboard report.

  • STRATUS.Package.CanBOM - Set Format = Boolean. When checked, indicates that the Package is in a Can BOM Tracking Status.

  • STRATUS.Package.HasBOM - Set Format = Boolean. When checked, indicates that a BOM has been generated for the Package.

  • STRATUS.Package.BOMIsLocked - Set Format = Boolean. When checked, indicates that the Package BOM has been Locked. As a result, this BOM will be available in the Purchasing module to send requests to suppliers.

  • STRATUS.Package.BOMGeneratedDT - Displays the date the BOM was generated. When setting the Report Field Format:

    • String - Use String to display the date and time. Packages, where a BOM has not been generated, will display a blank cell.

    • Date - Use Date to display the date only. Packages, where a BOM has not been generated, will display the word Empty.

  • STRATUS.Package.BOMRequiredDT - Displays the BOM Required Date. When setting the Report Field Format:

    • String - Use String to display the date only. Packages, where a BOM has not been generated, will display a blank cell.

    • Date - Use Date to display the date only. Packages, where a BOM has not been generated, will display the word Empty.

  • STRATUS.Package.BOMProcessor - Displays the current Processor for the BOM.

Added to the Container Details Report Aliases and Fields

Added to the Container Details report type the ability to use Aliases and Fields. In this example, the Alias is used to display a Supplier Code (Ex. Supplier Code, Code, Ferguson Code) for a part; and the Field displayed is the Length Total for the Part and for the Assembly.

  1. Configure the Alias similar to the following:

     

  2. In the Containers module, select a container and run the report. The Alias for Supplier Code displays one of the codes defined by the alias.

Added BIM Abbreviation to Assemblies

Added BIM Abbreviation (STRATUS.Part.BIMAbbreviation property) to assemblies. To use the STRATUS.Part.BIMAbbreviation property:

  1. Under Admin > Project > Template configure, import, and assign Areas to the model. Make sure that the Abbreviation column associated with the Area is filled in. If you edit the Abbreviation, click the Assign Parts (All Models) button to apply the abbreviation to parts. See the Areas (Admin) article for more information.

     

  2. The STRATUS.Part.BIMAbbreviation property will display:

    1. In the Properties panel.

       

    2. In a report where Item Type = Part and Assembly Viewer is checked. For example, it will display under Assemblies > Viewer > Parts with the report selected.

Added Ability to Select Connected on Multiple Parallel Runs

The select connected feature in model viewers has been expanded to allow users to select multiple parts and multiple groups of parts.

Example 1:

  1. In this case, all of the conduits at the end of a bank of conduit runs have been selected.

  2. Click Select Connected has the effect of grabbing all of the downstream parts.

Example 2:

  1. In this case, the ends of two different spools have been connected.

  2. Click Select Connected has the effect of grabbing all of the parts between the selected parts.

Added Ability to Place BIM Area Path on TigerStop Labels

Added the ability to place the BIM Area Path on TigerStop labels. To place the BIM Area Path on TigerStop labels:

  1. Edit the Label Template of your TigerStop Tool by adding the {{areaPath}} property to the label template. See the Label Template section of the Tools (Admin) article which refers to the Label Printing for Zebra (ZPL) Compatible Printers article. Below is an example:

     

  2. Under Admin > Project > Template configure, import, and assign Areas to the model. See the Areas (Admin) article for more information.

  3. Add parts to a package.

  4. Generate a Cut List.

  5. Send the Cut List to the TigerStop workstation.

  6. Process a cut list item in the TigerStop workstation. The label will now include the Area Path which includes the full BIM Area tree description with (e.g. Root | Level | Area).

Added to Master Reports an ‘Omit if Empty’ Option

Under Admin > Company > Reports where the Report Item Type is Master Report, added an Omit if Empty option. When the sub-report is checked and the report is run, if the checked sub-report contains no data, it will be omitted from the report. This is especially useful when a Part Filter sub-report filters out all parts in the model.

Added Control For Where Reports Can Be Accessed

For some companies, the list of reports in the Models Viewer and Packages Viewer has become too long. The solution is to enable companies to control where reports display, namely, the Model Viewer, Package Viewer, Assembly Viewer, and/or the Packages Dashboard.

Updated Font Style

The Font used for the STRATUS website has been changed to a cleaner style.

Fixed an Issue where Ancillary Material length Reported as 0

Fixed an issue where the Ancillary Material length reported as 0 using ancillary kits when configured as Ancillary Material on connectors.

Fixed Packages Dashboard Sorting Issue

Fixed a Packages Dashboard issue when sorting Required dates soonest to latest (up arrow on the sorting column) “Empty” should display at the top of the sort, not the bottom of the sort.

Fixed a Packages Dashboard Issue with Editable Date Field

Fixed an issue where an editable report field that impacted a date did not update the date on the Packages Dashboard.

Fixed a Character Limit Issue in Field Expressions

Fixed a character limit issue in the Field Expression text box under Admin > Company > Fields. There is no limit to the number of characters that can be included in a Field Expression.

Fixed a Project Roles Issue

Fixed a Project Roles issue where Models was unchecked for a Project Role and this prevented those users from viewing the Packages Dashboard.