This chapter discusses how to:
Define notification templates for Approval Framework.
Define users for Approval Framework.
This section discusses how to enter generic template definitions.
Page Name |
Definition Name |
Navigation |
Usage |
WL_TEMPLATE_GEN |
PeopleTools, Workflow, Notifications, Generic Templates |
Enter generic template definitions. |
|
URL_TABLE |
PeopleTools, Utilities, Administration, URLs |
Use this page to identify the URL that the notification process places within the email. The user then uses this URL to navigate back into their system to perform the required task. Note. An example of the format to use is http://servername/psp/employeeportaldomain/. |
Access the Generic Template Definition page (PeopleTools, Workflow, Notifications, Generic Templates).
You use generic templates to establish common formats for ad hoc notifications.
For approvals, the first bind variable is used to store the URL that appears in the email.
See Also
Enterprise PeopleTools PeopleBook: Workflow Technology, Using Notification Templates
This section discusses how to:
Attach workflow roles to users.
Define workflow for user profiles.
Define user lists.
Page Name |
Definition Name |
Navigation |
Usage |
USER_ROLES |
PeopleTools, Security, User Profiles, User Profiles, Roles |
Attach workflow roles to users. |
|
USER_WORKFLOW |
PeopleTools, Security, User Profiles, User Profiles, Workflow |
Define workflow for user profiles. |
|
EOAW_USER_LIST |
Enterprise Components, Approvals, Approvals, User List Setup |
Define user lists. |
Access the User Profiles - Roles page (PeopleTools, Security, User Profiles, User Profiles, Roles).
Use this page to attach workflow roles to users. A role is a class of users who perform the same type of work, such as clerks, buyers, or managers. A role describes how people fit into workflow.
Role user IDs determine how to route worklist items to users and how to track the roles that users play in the workflow.
See Also
Enterprise PeopleTools PeopleBook: Security Administration, Administering User Profiles
Access the User Profiles - Workflow page (PeopleTools, Security, User Profiles, User Profiles, Workflow).
Use this page to define alternate users who are part of the workflow process. You can define alternate users to handle approvals during the absence of the primary approver and supervisor.
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. Note. For workflows that are built using the Approval Framework, if the current role user is unavailable for assignment, the system checks for a alternate user recursively until it either creates a cycle or finds a valid substitute. In other words, the system sends routings down multiple levels of alternate user IDs if necessary. For example, suppose that user A specifies user B as his alternate user, and user B specifies user C as his alternate user. If both user A and user B are out of the office the same time, the system sends workflow routings originally intended for user A to user C. |
|
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. |
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. Note. If you’re using PeopleSoft Human Capital Management (PeopleSoft HCM) applications, this field shouldn’t appear. If it does, you must set your workflow system defaults. |
|
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. |
This option is not used in Approval Framework. It will reassign the worklist, but not the underlying data in Approval Framework. |
Access the User List Definition page (Enterprise Components, Approvals, Approvals, User List Setup).
Use this page to define user sources for use with steps in the approval process. The PeopleSoft product delivers a set of default user list roles corresponding to the roles within an organization.
When you select a user list source type, you must also select a corresponding value. You can add a new user list or change a current list.
Note. You can only select one user list source for a user list.
Note. The SQL Definition, Query, and Application Class user list sources are dynamic, and can use input values to help identify users.
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. |
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. |
|
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. Note. UserList Attributes are used for application class User Lists and Route Control is used for role based user lists. |
Route Attributes
If User List Source is Role, the Route Attributes section is displayed. This option enables the Route Control filters.
Route Control Profile |
Select the route control profile to use. |
Record Name |
Record the user passes in that stores the values used in the route control. Note. Route control checks against fields, Approval Framework needs to know which record contains the field. |
Route Control Type |
Route control attribute. Note. Route control attribute is defined on the User Profile Roles page in the route control link. |
Field Name |
Field on the record mapped to the attribute. |
See Also
Enterprise PeopleTools PeopleBook: PeopleCode Developer's Guide