Configuring Approval Transactions
To select and define elements that determine what triggers a notification, who receives the notification, and the content of the notification, use the Configure Transactions (EOAW_TXN_CONFIG) component.
For HCM transactions, the workflow engine requires that you enter specific values in the User Utilities section to enable it to interact with the Approval Framework and Delegations. In the User Utilities Package field, you must select the value HCSC_USER_UTILITIES. In the User Utilities Path field, you must select the value UserUtilities. PeopleSoft HCM delivers these values.
The user utilities class checks users against delegation to determine if the users have delegated their authority. If not, then the user utilities class determines whether the users have an alternate user in their user profiles.
The Events section defines the information to build the default URL to include in notification for each of the participants that you specify in the Notifications section.
This topic lists the page used in configuring approval transactions.
|
Page Name |
Definition Name |
Usage |
|---|---|---|
|
EOAW_TXN_NOTIFY |
Configure how the system uses the particular implementation of approval triggers by configuring all the events and notifications associated with your approval process IDs. Note: Oracle PeopleSoft delivers Notification Composer Framework to manage the setup and administration of all notifications in one central location. Once you have adopted the Notification Composer feature, you must use it to create new notifications and manage your existing notifications. Notifications delivered with HCM Image 47 or later must use Notification Composer. For more information about Notification Composer Framework, see Understanding Notification Composer. |