Point Value Nodes in Policy Designer

The Properties window for a Point Value node contains the items that are described in the following table.

Item	Description	Notes
Trigger check box	Specifies whether or not changes to the record that is associated with the node will result in policy execution.	None
Data Type list	Specifies the type of data that the node represents.	This property is not required, but selecting a value can help catch errors and facilitate policy execution. Note: The Data Frame option exists only for use by certain module workflow policies.

The following example illustrates how you can use the Point Value node to represent values from fields in different families for each policy instance. Consider the following nodes and connection.

In this example, the Point Value node Cost represents cost values of various types. This model evaluates each cost value to determine whether or not it is greater than 150.

The particular record and field containing each cost value are defined by policy instances. For example, you might create two policy instances, where:

• One policy instance maps the Cost field from the Action family to the Cost Point Value node.
• The other policy instance maps the Total Cost field from the Work History family to the same Cost Point Value node.

By using the Point Value node in this way, the policy can use one Input node to access values in multiple families and evaluate them against the same criteria.