Graviton Approval Framework Presentation
- 2. Agenda History of Approval Workflow Engine (AWE) The Approval Framework Foundation Process Flow of AWE AWE Terminology & Approval Process Setup Next Step Q & A
- 3. History of Approval Workflow Engine The foundation of AWE is PeopleTools Workflow Business Process, Activity, and Events The Approval Workflow Engine (AWE) is a product that evolved from eProcurement. Adopted early with Expenses in 8.9 AWE delivered with PeopleTools in PT 8.49. Consolidated code line between HCM and FSCM in PS 9.0. AWE delivered as Enterprise Component with PS 9.1. Expanded to more FSCM modules with new features in 9.2.
- 4. Process Flow of AWE What, How, When, & Who Developers Define… What & Who Implementers Define… How & When (What) Transactions: The Transaction Registry is used to identify how the calling application will interact with AWE. (How) Approval Process Definitions: The Approval Process Definition pages allow the functional analyst to define the workflow steps to be executed in order for the transaction to be approved. (When) Configurations: The Approval Process Configuration page allows the user to define events that trigger notifications. (Who) User Lists: User Lists are generated by User Roles, SQL Definitions, PS/Query options and Application Packages.
- 5. Process Flow of AWE
- 6. AWE Terminology & Setup (What) Transactions
- 7. AWE Terminology & Setup (How) Approval Process Definitions
- 8. Stages, Paths and Steps
- 9. Stages •Stages are used to contain one or more Paths •Stages execute sequentially •Each Stage must complete before the next begins •Stages can be defined at the Header or Line level, not both •Multiple stages can exist for either line or header level
- 10. Paths •More than one Path can exists per Stage •Path processing is done in parallel •ie, Routing line items to different User Lists •Paths can have either Static or Dynamic Source •Static source, is set number of Steps •Dynamic source, User List runs again until no returns •Dynamic can use Approval Authorization Criteria.
- 11. Path Detail
- 12. Steps •Step is a unit of work that must complete before advancing. •When the Path is Static, there can be multiple steps. •When the Path Dynamic, there can only be one Step and the user list cannot be based on a Role. •Steps are triggered based on criteria resolving to true.
- 13. Step Details
- 14. Criteria • 3 Levels of Criteria • 3 Types of Criteria • Evaluates to Boolean (true or false) • Satisfy All Criteria • Header/Line Record.Field Values • Monetary Criteria
- 15. AWE Terminology & Setup (When) Transaction Configuration
- 16. AWE Terminology & Setup (Who) User List Setup -Source • 4 Types of User List • Only Returns OPRID • Site Specific, Customize • Role User List exposes Route Control • Uses WF Routing & Role • Uses Security User Profile Role Route Control
- 17. 8950 CAL CENTER DRIVE, BUILDING ONE, SUITE 203 SACRAMENTO, CA - 95826 PHONE:(888) 472-8481 (916) 588-2655 PSOFT@GRAVITONCONSULTING.COM WWW.GRAVITONCONSULTING.COM