Defining Dataset Rules

Dataset rules define datasets for use in conjunction with each dataset role’s security rules. Defining dataset rules creates Structured Query Language (SQL) statements that select the dataset displayed for each rule.

To use dataset rules and roles:

1. Define dataset rules, which are based on a synchronized record.

   You define a dataset rule to return a subset of rows from the selected synchronized record based on the dataset role to which you will link the rule.

   These dataset rules are based on views that can join to any record in your PeopleSoft system.

   For each rule condition, the user specifies a field that comes from the search record name defined in the dataset rule. When the specified field has neither a prompt or translate table edit, the following system variables, which are delivered as system data to all applications, can be used to filter the condition:

   • %Blank

   • %Date

   • %EmployeeID

   • %PersonID

   • %Time

   • %UserID

2. Assign the dataset rules to dataset roles, according to role security and data requirements.

   Each dataset role can have multiple dataset rules. You can use existing dataset roles, or create new dataset roles by selecting from existing PeopleTools security-based user roles.

   See PeopleTools: Security Administration, “Understanding Roles”.

3. Ensure that the original user roles on which dataset roles were based are associated with appropriate user IDs.

   Each user ID can have multiple user roles.

   See PeopleTools: Security Administration, “User Profiles - Roles Page”

Use the Dataset Rules page (EOEC_DATASET) to define the rules that make up a dataset.

Image: Dataset Rules page

This example illustrates the fields and controls on the Dataset Rules page. You can find definitions for the fields and controls later on this page.

The number of rule conditions in a dataset rule is limited only by your performance requirements. You can set a series of rule conditions that can navigate through as many records as necessary.