Approval Workflow Engine (AWE) With Custom Example

March 25, 2018 | Author: Siji Surendran | Category: Workflow, Database Transaction, Information Technology Management, Systems Engineering, Technology


Comments



Description

Approval Workflow Engine (AWE) With a Custom ExampleTable of Contents 1. ABSTRACT...............................................................................................................................................................2 2. WORKING WITH APPLICATION WORKFLOW ENGINE............................................................................3 3. HOW TO USE APPROVAL WORKFLOW ENGINE..........................................................................................5 4. SUMMARY/CONCLUSION.................................................................................................................................19 5. REFERENCE..........................................................................................................................................................19 Page 1 of 19 A set of approvers then carries out tasks related to the transaction. Abstract The Approval Workflow Engine (AWE) is the engine that provides the framework and capabilities for creating. all of the steps in approval workflow are defined using PeopleSoft pages rather than underlying PeopleSoft PeopleCode. running. the process of submitting a promotion and getting it approved requires defining who will approve the promotion. and use transaction approvals that meet their organizational requirements. The Approval Workflow Engine enables three levels of users to develop. For example. such as a promotion.Approval Workflow Engine (AWE) With a Custom Example 1. approval workflow provides an alternative workflow that is much easier to create. which requires advanced technical skills in PeopleSoft PeopleTools to create and maintain. and maintain. For example. This document describes how to create and implement Approval Workflow Engine process in a custom PeopleSoft application with an example and this example is a basic level. Approval workflows are triggered when requesters submit a transaction. In contrast to the standard PeopleSoft workflow. and how it will be routed to approvers. Page 2 of 19 . The engine uses a series of database objects combined with application component configuration settings to determine how to process approvals using workflow. and managing approval processes. In this example we are doing only header record level approvals. The application hands the transaction over to the Approval Workflow Engine. configure. which finds the appropriate approval process definition and launches the approval workflow. the order in which they will approve it. so functional users can design and maintain workflow using these online PeopleSoft pages instead of requiring technical developers to create workflow rules. configure. monitor transaction statuses. Approval Flows Page 3 of 19 . This includes setting up stages. This AWE enables both the header and line level approvals. these transactions typically have children records (line-level records) of this header record. which provides a common implementation that other applications can use. Application developers integrate their applications with the approval workflow engine framework using the Register Transactions page. and audit approvals. which finds the appropriate approval process definition and launches the approval workflow. Working with Application Workflow Engine The main things in the approval workflow Engine are. and a set of approvers carry out tasks related to the transaction.  Functional business analysts Functional business analysts design approval workflow for use with an application. Then. and notifications for each approval process ID. Header. Making this possible is the approval workflow engine. The register stores the approval process IDs those developers create for applications. and use transaction approvals that meet their organizational requirements. where they register an application with the engine and describe its components. the framework for building and interpreting workflow approvals brings together these users:  Application developers Application developers adapt applications for approval with minimal coding.  Approval flows. event handler. Analysts identify the application-supplied transaction definition on which to base approval process definitions.  The approval workflow process. using a defined setup process.Approval Workflow Engine (AWE) With a Custom Example 2. such as a requisition. recipients.  End users End users create transactions and then use an approval process with approvers and reviewers within an approval flow. Approval workflow process Approval workflows are triggered when requesters originate a transaction. To implement the approval workflow process. steps. The PeopleSoft approval workflow process is a framework that enables three levels of users to develop. the application hands the transaction over to the approval workflow engine.and line-level approvals.and Line-Level Approvals Many PeopleSoft transactions have a top-level record (known as a header) with keys that uniquely identify a single transaction in an application. and records. Using this process. the different end users can approve or deny requests. configure. They use the Approval Process Definition page to define processes for approving transactions. After an end user creates an application transaction and submits it for approval.  Header. These processes can be used repeatedly to guide transactions through their approval process. paths. or both. Path entry criteria determines whether or not a path executes for a given transaction or transaction line.  Steps A step represents one or more approvers or reviewers. The approval process consists of:  Stages A stage is one part of an approval process that can contain multiple parallel paths but must be at the same header or line record level. The system executes stages in sequence where one must complete before the next one begins. A stage can be at either a header level or at a line level. Each step can also have a set of reviewers. A line is a child of the header. A stage consists of one or more paths.  Paths A path contains a sequence of steps. Stages at a line level make it possible for approvers to sign off separately on individual line items for a single transaction. through the Worklist. Within a stage. However. Separate criteria for each step determine whether or not that step executes. paths execute in parallel. the workflow proceeds without waiting for reviewers to act. Reviewers are notified about transactions that are pending approval by email.Approval Workflow Engine (AWE) With a Custom Example Approvals use two levels of processing: header and line. Business analysts set up the approval process definition that determines the flow of the approval at both levels. The workflow engine sees each header and each line as individual pieces. A header stage acts on the unique header while a line stage acts on each line. Page 4 of 19 . Steps within a path execute in sequence. Approval Workflow Engine (AWE) With a Custom Example 3. How to use Approval Workflow Engine 1) Create the custom PeopleSoft Application where do we want to implement AWE Step 1: Create the page to trigger the approval workflow by the user Step 2: Create the page to approve/deny the approval workflow by the approvers Page 5 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 3: Create the Cross Reference table Step 4: Create the custom event handler class Custom Appln Package Step 4: Create the header record as view to use in the setup Page 6 of 19 . Approval Workflow Engine (AWE) With a Custom Example 2) Configure the Custom AWE process Step 1: Register the custom AWE process Page 7 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 2: Configure the transactions Page 8 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 3: Setup the Process Definitions Page 9 of 19 . Approval Workflow Engine (AWE) With a Custom Example Page 10 of 19 . Approval Workflow Engine (AWE) With a Custom Example 3) Application Codes to call and use the AWE process Step 1: Code to initialize the custom AWE process Step 2: Code to call the he custom AWE process Page 11 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 3: Code to initialize the custom AWE process in the approval page Step 4: Code to Approve/Deny the request Page 12 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 5: Code in the approval page to enable the approval action field 4) Set the user profile for approvals Page 13 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 1: Set the requester’s Supervisor id Requestor id is VP1 VP1’s Supervisor id is VP2 Step 2: Set the Supervisor’s Supervisor id Supervisor id is VP2 VP2’s Supervisor id is SVP1 5) Working on the AWE example Page 14 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 1: Login as Requestor (VP1) Step 2: Create a request Step 3: Monitor the Approvals Page 15 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 4: Login as Supervisor (VP2) Page 16 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 5: Approve the request Step 6: Check Monitor the Approvals Page 17 of 19 . Approval Workflow Engine (AWE) With a Custom Example Step 7: Login as Supervisor’s Supervisor (SVP1) Step 8: Approve the request Step 9: Check the request status and it will be as approved Page 18 of 19 . configure.Approval Workflow Engine (AWE) With a Custom Example 4. 5. so functional users can design and maintain workflow using these online PeopleSoft pages instead of requiring technical developers to create workflow rules. Reference  PeopleSoft Enterprise Supply Chain Management 9. and maintain. For example.0 Common Information PeopleBook Page 19 of 19 . all of the steps in approval workflow are defined using PeopleSoft pages rather than underlying PeopleSoft PeopleCode. Summary/Conclusion Creating custom Approval Workflow engine is possible and it is easier to create.
Copyright © 2024 DOKUMEN.SITE Inc.