Understanding Route Control Development

Additional routing options enable you to define complex, custom routing schemes without writing PeopleCode. Develop route controls in the following order:

1. Define route control types, which identify the factors on which you want to base routings: Business Unit, Department, Vendor ID, and so on.

   You can define route control types based on any prompt table.

2. Define route control profiles, which identify ranges of values for route control types.

   For example, one route control profile might list the vendor IDs for all software vendors, while another might list the IDs for all office supply vendors.

3. Assign route control profiles to role users.

   Assign the Vendors (Software) profile to the clerks who handle software and the Vendors (Office Supplies) profile to the clerks who handle office supplies.

4. When you define the routing in PeopleSoft Application Designer, assign one of the roles that is provided for use with route controls.

The route control query roles have runtime bind variables that correspond to:

• The route control types to use.

• The values for those types.

For example, the One Route Control Qry (one route control query) rule has four bind variables:

• One that specifies the single route control type to use.

• Two that you map to a value from the page that triggers the routing.

• One that you map to the user list role.

When a business event is triggered, the system decides to whom it should route the work item by:

• Binding the query bind variables using data from the page that triggers the event.

• Running the query, and checking each user’s route control profile to determine whether the user meets the selection criteria.

• Routing the work item to the appropriate role users.