The grosslists compile measures and activities from all governance models.
Removing Nodes from the Grosslist
Default Behavior – “Use Entire List” Setting Not Activated
“Use Entire List” Setting Activated
Considerations When Using the Entire List
What Applies to the Read Access Feature?
Description
The grosslists are separate scorecards for measures and activities, each containing only one column with measure or activity nodes. These scorecards cannot be deleted.
Every measure and activity created is automatically linked to its respective grosslist, in addition to being linked to the scorecard it is added to. This connection is always made directly to the Vision level and cannot be changed.
The grosslists therefore provide an overview of all measures and activities in the entire database, and these are displayed here regardless of their connections or periodicity.
Purpose and Function
The purpose of the grosslists is to help locate measures and activities that lack a connection in the scorecard where they were originally created, or that are difficult to find for other reasons—for example, due to complex filtering in views.
Measures and activities can lose connections, for instance during reorganizations, and in such cases the grosslist provides a way to locate the measure or activity and restore its connection so that the consolidation chain is reestablished.
There are also cases where a connection is intentionally removed at a certain level in the regular scorecard to prevent the node from being displayed—for example, at the top level. In that case, the node can still be found in the grosslist. (For another method of hiding nodes at the top level, see How do I change the main department of a node?)
The grosslists can also be used to include activities or measures in other scorecards. See Allow selecting nodes/measures in views.
Permissions
Users who are granted permission to modify and delete nodes in the grosslists will be able to modify and delete all nodes visible in these lists (on the departments where the user has access), even if those nodes are linked to scorecards the user would not normally have permission to access.
Therefore, be cautious when assigning permissions to the grosslists—especially if views of the grosslists have been added to menus. For this reason, standard permissions do not include access to the grosslists.
If you have the Read Access feature enabled, read more here: grosslists and Read Access.
Removing Nodes from the Grosslist
When you remove a node from the grosslist, all of its connections are removed. This means the node will disappear from all scorecards when it is deleted from the grosslist.
Observe: The node will be removed from all scorecards if it is deleted from the grosslist.
Setting “Use Entire List”
Under the “Other” tab in the administration menu for scorecards, there is a setting called “Use entire... list” This option is typically not checked by default.
The name is somewhat misleading, as the grosslists always exist in the database regardless of this setting. Here, “use” means making the grosslists behave more like regular scorecards. Connections to the grosslist will then function more like standard links. However, all measures and activities still automatically receive a connection to the grosslist.
This setting may be suitable for customers who need a shared measure database to be used across multiple scorecards. An alternative approach could be to create an additional standard scorecard that consolidates all measures.
Please read the “things to consider” section below and contact Stratsys before activating “Use grosslist” in your existing database.
Default Behavior – “Use Entire List” Setting Not Activated
By default, the connection in the grosslist functions more like a mirror of the regular scorecard connections, and the node appears in the grosslist only as long as there is at least one remaining connection to another scorecard.
The node will also be removed from the grosslist once the final connection for the last department in the consolidation chain is deleted.
During version management, any nodes that only have a connection to the grosslist will be removed. This also applies to activities, regardless of their status.
When choosing to delete completed activities during version management, the nodes are removed from all selected scorecards—but not from the grosslist. These will, however, be automatically deleted from the grosslist during the next year’s version management, as only the grosslist connection remains.
Thus, completed activities disappear from the regular scorecard immediately upon cleanup, but from the grosslist with a one-year delay.
“Use Entire List” Setting Activated
When the “Use entire... list” setting is activated, the grosslist functions more like a regular scorecard. This enables active work directly within the grosslist—for example, adding activities and measures, creating custom or filtered views, and more.
Without this setting enabled, such nodes would be automatically removed during version management. However, with the setting active, no nodes are deleted from the grosslist during version management.
Likewise, completed activities are not removed from the grosslist during post-versioning clean-up—neither immediately nor the following year. However, it is possible to delete activities one by one if needed, or request a scripted bulk removal from Stratsys through consultation.
Considerations When Using the Entire List
Activating the “Use entire list” setting introduces certain side effects. Please review the following before deciding to activate grosslists for operational use:
Reporting Periodicity:
If the nodes in the grosslist have different periodicities, we do not recommend using a view based on the grosslist for data entry. It can be difficult for users to determine which period their comments will apply to. However, if all nodes use the same periodicity—for example annual—it is acceptable to use the grosslist for input.
Automatic Copying Behavior Changes:
If you use automatic copying for measures/activities, these may be distributed to far more departments than intended. Normally, the distribution is governed by the left-side node connection—only departments made visible through that linked node receive the automatic copy.
In the grosslist, however, the connection is made directly to the Vision level, which removes this limitation. As a result, auto-copying will affect all underlying departments targeted by the automation, regardless of how the linked node is distributed.
Node Deletion:
Deleting nodes now requires an explicit user action—even if the node only exists in one other scorecard—because the grosslist is now treated as its own scorecard. Users must actively choose whether to remove only the connection to the current scorecard or to delete the node entirely using the “Remove from all scorecards” option.
Cleanup of Activities:
No automatic cleanup of completed activities will be possible from the grosslist if it is in use. Over time, this may result in the list containing a large number of activities.
Cleanup assistance can be requested from Stratsys through a consulting engagement.
What Applies to the Read Access Feature?
If you have the Read Access feature enabled, refer to the following section for important considerations: grosslists and Read Access.