Server Administration > Change Packages for SCM > Change Package Reviewer and Watcher Rules
Change Package Reviewer and Watcher Rules
The Windchill RV&S administration client allows you to specify simple user and group lists of change package reviewers/watchers for a specific project. The Windchill RV&S server contains XML files that allow you to define more complex rules that resolve to a list of reviewers/watchers, only if the conditions specified in the rule(s) are met.
Change Package Reviewer and Watcher Rules Configuration File Location
In the installdir/config directory, the following files are used for change package reviewer and watcher rules:
The DTD files define rule elements and structure. The XML files allow you to define your rules. When defining your rules, refer to the DTD files for syntax, definition, and explanation of tags used in the XML files.
Conditions in Change Package Review and Watcher Rules
The conditions defined in change package reviewer and watcher rules can be associated with the values of change packages, change package entries, and item fields. All item fields are allowed in item field conditions; however, only certain change package and change package entry fields are valid. Full regular expressions are allowed when specifying field values (other than user or group field values), which facilitates the freedom when writing rules.
The ChangePackageReviewerRules.xml file is used for the purpose of illustration. The structure of the ChangePackageWatcherRules.xml file is exactly the same, except it does not contain voting or enumeration, and rejects specified policies. To define change package watcher rules in the ChangePackageWatcherRules.xml file, replace the word "Reviewer" in the XML tags with the word "Watcher.”
The ChangePackageReviewerRules.xml file starts with a single ReviewerRules element that contains zero or more ReviewerRule(s). Each ReviewerRule contains an optional Condition element followed by a single reviewerExpression, which defines the EnumerationPolcy and VotingPolicy to use. Each policy is optional, since default values are used if they are not specified. EnumerationPolicy and VotingPolicy in turn have an additional and optional Property element. The only valid property on the EnumerationPolcy element is the Property with the name ignoreRejects. These optional policies and properties are then followed by a Reviewer element which specifies optional Users, Group(s) of users, UserExpression(s) or GroupExpressions.
The Condition element must specify one of the condition operators And or Or which can be nested and one or more of leaf conditions (which must be enclosed between a logical operator) IssueFieldCondition(s), ChangePackageFieldCondition(s), MemberAttributeCondition(s) or ChangePackageEntryFieldCondition(s). Each of these (leaf) conditions allows you to specify which field (or in case of MemberAttributeCondition, which member attribute) it pertains to and which operator to use when comparing field (or attribute) values. Field values are specified within FieldValue tag, or UserFieldValue tag if the field is of User type, or GroupFieldValue if the field is of the Group (of users) type. In the case of MemberAttributeCondition, the value is specified between MemberAttributeValue tags.
Writing Logical Expressions
Case of a Single Condition
Condition Structure and Elements
Parsing Rules