Parts of a Rule
A rule comprises the following parts:
- Changed Definition
Type of definition that is changing.
- Impacted Definition
Type of definition that is affected by the changed definition.
- Rule Set
A grouping or subset of rules.
The pillar, or application, for which this rule is written.
The pillar is derived from the RELEASELABEL in the PSRELEASE table. The specific SQL statement is:
select RELEASELABEL from PSRELEASE where RELEASEDTTM = (select max(RELEASEDTTM) from PSRELEASE)
The RELEASELABEL value is converted to <pillar> x.xx and is the key to look up the value in the rules file. For example, RELEASELABEL CRM 8.00.
Two core PeopleTools pillars provide rules that find the relationships between PeopleSoft metadata definitions, IDE and PPT.
When rules are selected from the rules files, the IDE and PPT rules are always used in addition to your application's pillar, for example FMS or HRMS.
Release version and used to determine the pillar value.
- Database Platform
The database platform for which this rule is written.
Note: If you want to run rules against a specific (non-default) database platform, create a new rule in your own rules file, and add your rule for the specific platform. Rule selection will choose a specific platform rule over the same rule, but for the default platform.
- Database Version
The database version for which this rule is written.
- Definition Name andDefinition Print Name
These fields contain the database column names that identify the definition. The definition name is the internal name used by the rules engine. The definition print name is used when displaying the name to the user. These values are usually the same.
For example, from the Field Impacting Record rule, RECNAME is one of the selected columns from the PSRECFIELD table. If the definition name and the definition print name is RECNAME. The rule is:
select DISTINCT RECNAME, FIELDNAME from PSRECFIELD where FIELDNAME = ':1' ORDER BY RECNAME
- Definition ID
The Application Designer object ID for the definition. This field contains the template to create an Application Designer object ID for the impacted definition. Change Impact Analyzer uses this objectID to open the definition within Application Designer.
For example, using the Field Impacting Record rule, the definition ID is 'RECORD'.RECNAME The elements of the name within single quotes (RECORD), are the literal string values of an Application Designer object ID class. If the RECNAME is Customer, then the Application Designer object ID is RECORD.Customer.
The SQL select statement that is executed (or in the case of a Java rule, the name of a Java class).
select DISTINCT RECNAME, FIELDNAME from PSRECFIELD where FIELDNAME = ':1' order by RECNAME
The parameter :1 refers to 1st element of the impacted definition name.
In the case of PeopleCode impacting PeopleCode, the rule is implemented by the class as in:
Java rules can execute more complex code than SQL code, however, Java rules are not documented in this release.
The action recommended for the definitions found.