Rule Format

A rule is a statement that sets a specified outcome when certain conditions are met. In the GUI, rules are composed of nodes and conditions. Nodes are the logical connectors that describe the relationship between two statements (or conditions). Conditions are a statement of the requirements that must be satisfied, and can involve either user or field values.

The logical and node indicates that all of the specified conditions must be true to meet the requirements of the rule.

The logical or node indicates that one or more of the specified conditions must be true to meet the requirements of the rule.

The specific placement of the logical node is important to determining how it affects the meaning of the rule.

The following example shows an e-mail notification rule that asks Windchill RV&S to notify the user (administrator) each time a new change request is created or whenever a defect is assigned to the user. With the or node, the notification occurs whenever either of the events occurs.

The use of [New Value] in a rule condition indicates a change in a field value. One part of the condition indicates the field value before the change, and the other part indicates the value after the change. For example, in the rule above, Assigned User \<\> Assigned User[New Value] indicates that the new value of the Assigned User field is not equal to what it was before the item was saved. In other words, the value of the Assigned User field was changed during the item edit.

If document versioning is enabled, you can specify conditions for live and versioned document model items. For example, you can create an event trigger rule to run on versioned items only or an e-mail notification rule that sends an e-mail when a user edits a specific live item.

As a best practice, PTC recommends including the Item is live condition in all rules for live items. This improves the accuracy of rules.

With items, you can:

• define a rule to match versioned items only. For example, Item is versioned matches versioned items only.

With item IDs, you can:

• define a rule using a live item ID to match a single live item. For example, ID is = 123 and Item is live matches 123.

• define a rule using a versioned item ID to match a single versioned item. For example, ID is = 123–1.0 matches 123–1.0.

• You cannot define a rule using a live item ID to match the live item and all versions of the item.

• You cannot define a rule using live or versioned item IDs to match a range of live or versioned items, for example, ID is > 123-1.0 and < 123-2.0.

With document IDs, you can:

• define a rule using a live document ID to match a single live document. For example, Document ID is = 123 and Item is live matches content that is included in live document 123.

• define a rule using a versioned document ID to match a single versioned document. For example, Document ID is = 123–1.0 matches content that is included in versioned document 123–1.0.

You cannot define a rule using live or versioned document IDs to match a range of live or versioned documents, for example, Document ID is > 123-1.0 and < 123-2.0.