Understanding PeopleSoft Mobile Approvals for Treasury

The PeopleSoft Mobile Approvals feature provides an option to approve transactions using a mobile device using the Fluid User Interface as opposed to using the Classic User Interface. Approvers continue to take Approval Workflow Engine (AWE) actions on PeopleSoft transactions pending their approval, but can do so using small or large form factors.

Mobile Approvals provides a convenient option to review and approve pending transactions from a mobile device. Approvals for Treasury in the PeopleSoft Fluid User Interface include these:

• Settlement Approvals

• Deal Approvals

• Deal Confirmations

For information about approving deals and deal confirmations in Fluid, see Approving Deals Using PeopleSoft Fluid User Interface and Confirming Deals Using PeopleSoft Fluid User Interface.

In order to use the Mobile Approval feature, applications must utilize the Approval Framework, also known as AWE. All transactions must be created in the database, and adhere to the Approval Framework logic and configuration within each application. For more information, see Setting Up PeopleSoft Mobile Approvals for Treasury.

PeopleSoft Treasury uses Enterprise Components - Fluid Approval Framework technology, which consists of Enterprise Objects Approval Workflow (EOAW), Application Workflow Engine (AWE), and Enterprise Objects Page Composer (EOPC). A minimum tools release of 8.55 is required for Fluid Approvals.

Oracle PeopleSoft delivers Notification Composer Framework to manage the setup and administration of 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.

For more information about Notification Composer Framework, see Understanding Notification Composer