PRPC uses prefixes to identify:
Each of these prefix types is described in detail below.
A prefix for a work item ID is the initial character or text that appears before a dash character. This usually corresponds to the standard property Work-.pyWorkIDPrefix, and ordinarily is between one and five characters long.
For example, the prefix of work item Q-1432 is Q. The prefix of the work item MORT-763-K4 is MORT.
You can specify a prefix value on the Details tab of an application rule, or through a data transform.
A RuleSet version number has three segments, in the form NN-NN-NN, known as the major, minor, and patch level.
In access groups and other instances that reference a RuleSet version, you can enter only a prefix, omitting trailing portions.
For example, if you enter DELTA:04-38 in the Application RuleSets list of the Application rule form, operators associated with that application rule may find and execute rules in 04-38-01 through 04-38-99. The prefix 04-38 acts as a wildcard.
The keywords locate
, prompt
, and others as an initial portion of a page name have special meanings. See page.
Standard property names start with px, py, or pz. You can override px and py properties in your application, but cannot create new properties with any of these three prefixes.
When searching the class structure to find a rule, PRPC follows pattern inheritance, using a sequence of prefixes of the class name. The dash character delimits segments of the name.
For example, when looking for a rule in a context of the class DELTA-HISTORY-MORTGAGE-APPLICATION, the system searches through rules that have the following class as the Applies To key part:
For some of these prefixes, no class may exist.
major version, minor version, patch version, pattern inheritance, version, work item ID | |
Understanding work item IDs
About Application rules |