Defining Users for Approval Framework

User Profiles - Roles Page

USER_ROLES

Attach workflow roles to users.

User Profiles - Workflow Page

USER_WORKFLOW

Define workflow for user profiles.

User List Definition Page

EOAW_USER_LIST

Define user lists.

Role Name

Select a role to assign to this user. Role users are the people who participate in automated business processes.

Dynamic

Appears if the definition of this role is dynamic. This value is driven by PeopleSoft PeopleCode. Dynamic users can obtain membership in a role programmatically. You can run a batch process that executes predefined role rules and assigns roles to user profiles according to these rules. This approach is called dynamic membership, and users who become role users of a particular role programmatically are dynamic role users.

Static role users, on the other hand, obtain their membership through an administrator adding a role to their user profile manually.

Route Control

Select to access the User Route Control Profiles page, where you can select a route control profile for the workflow.

The PeopleSoft Workflow Administrator enables you to define route controls. For example, suppose you want to route requisitions to different buyers, depending on which vendor supplies the ordered items, which business unit is requesting the items, and which department needs the items. You can define a route control for each factor—vendor ID, business unit, and department—and specify a range of values for each buyer.

View Definition

Select to access the Roles - General page, where you can change the role name definition. You can also view the user ID of the role member to ensure that you selected the appropriate definition for inclusion in the role.

Alternate User ID

Select a user to receive worklist items when this user ID is temporarily unavailable. In situations where the current role user is unavailable, the system automatically forwards the current role user's new work items to the specified alternate role user. The system doesn’t reassign items already in the user’s worklist.

From Date and To Date

Enter a date range when the current user ID is not going to be available. The system uses these values to forward routings to the alternate user.

Supervising User ID

Select the user ID of this user’s supervisor. The system uses this value when forwarding information to the user’s supervisor and uses the PERSONAL_DATA record to determine the supervisor.

Worklist User

Select to indicate that this role user can receive approval routings. Clear the check box if the user is not a PeopleSoft user. You can select Worklist User, Email User, or both.

Email User

Select to specify that this role user can receive email. Clear the check box if email is not available.

Reassign Work To

This option is not used in Approval Framework. It will reassign the worklist, but not the underlying data in Approval Framework.

Role

Select to use a role as the source for this user list. A role is a list of users who perform the same type of work, such as buyers or managers. Each role has a set of parameters that determine the limits of the role in the organization and in the workflow process.

SQL Definition (structured query language definition)

Select to use an SQL definition as the source for this user list. The SQL must return OPRID field.

Query

Select to use a query as the source for this user list. When a source is defined as a query, the system determines who should receive a work item based on the field values on the page that triggers the routing.

Application Class

Select to use an application class as the source for this user list.

When you select an application class, the system passes the originator of the transaction and then determines the approver for that originator. For subsequent approval steps, the system passes the approver from the previous step.

Include Users as Input

Select to indicate that the system uses the originator of a transaction as the first step in each path. For subsequent steps in each path, the system uses the approver from the previous step.

This field is not available when the User List Source is User List.

Transaction Keys as Input

Select to have the system base the approval routing on transaction keys. Transaction keys are key fields in a database table. System actions depend on the approval level at which a user list is being used. If the approval is at the header level, the system uses transaction record keys from the header record.

This field is not available when the User List Source is User List.

User List Attributes

This section is only available when the User List Source is Application Class.