Calculated and Stored Properties

For certain properties, you can define an expression to calculate the property value and then store that value for a node in a viewpoint.

You configure the Calculate and Store option as a parameter override to the Default Type at the application or node type level. See Editing Property Parameters.

Note:

The Calculate and Store option is available for the CoreStats.Parent property only.

Calculating and Storing the Parent of a Node

For hierarchy viewpoints only, you can calculate and store the value of the CoreStats.Parent property when adding or inserting a node during these operations:

  • Loading a request file when the parent is undefined
  • Creating request items from compare differences when the source parent is undefined (when the source viewpoint is a list and the target is a hierarchy)
  • Generating subscription request items when the source parent is undefined (when the source viewpoint is a list and the target is a hierarchy)

Considerations

  • When creating the expression to calculate the parent, you can select from these fields for the node object in the expression builder:

    • dimension
    • name
    • nodeType
    • properties (Node properties only. Relationship properties are not available when calculating the parent.)

    See Using Expressions to Define Custom Business Logic.

  • The expression for the calculated parent must refer to an existing node in the target viewpoint. You cannot define an expression to create a parent node.
  • When creating request load files, use the <Unknown> keyword in the parent column of a request load file (where an expression is configured for the CoreStats.Parent property) to calculate the value for that parent .Leaving a blank in the parent column will cause the node to become a top node.
  • For requests generated from compare differences and subscriptions, when request actions are created for a node in a target viewpoint which has the CoreStats.Parent property and the parent is unknown, the system uses the <Unknown> keyword in the parent column of the generated request file attachment to indicate that the value for the parent should be calculated.
  • The node type of the calculated parent is based on the configuration of the hierarchy set in the target viewpoint:
    • If the node type for the node being inserted allows children in the hierarchy set, the node type for the parent is set to the same as the node type for the child.
    • If the node type for the node being inserted does not allow children in the hierarchy set and there is one other node type in the hierarchy set that does allow children, the node type for the parent is set to that other node type.
    • If the node type for the node being inserted does not allow children in the hierarchy set and there are more than one additional node types in the hierarchy set that allow children, the node type for the parent is set to the same as the node type for the child.