Many daily tasks are part of a larger process thatinvolves several steps and people working together, such as the approvalof a promotion. To facilitate this type of multiuser process, PeopleSoftprovides approvals functionality, which enables you to automaticallytrigger workflow notifications to inform the next approver in theprocess of pending transactions.
Many PeopleSoft applications are delivered withpredefined approval processes. However, these topics provide the PeopleSoftHCM product line specifics of the Approval Framework functionality.While this document lists the HCM navigation and additional topicsspecific to setting up HCM Approval Framework, more detailed overviewsand field descriptions are documented in the companion documentation PeopleSoft Approval Framework.
Related Links
Approvals Terminology
The following terms are important to the understandingof the approvals functionality and are used throughout these topics:
PeopleSoft Approval FrameWork AWE Slideshare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. Part 3 – Contains Testing & Demonstration AWE Workflow in PeopleSoft with different User ( Create A Simple AWE PeopleSoft Part – 3) Part 4 – Contains Necessary Record, Component Record, Application Packages PeopleCode that need to write for AWE Workflow ( Create A Simple AWE PeopleSoft Part – 4) So Lets Start. PeopleSoft Approval Workflow Engine (AWE) is a recent entrant into the PeopleTools family – introduced only in 8.48 AWE provides capabilities for creating, running, and managing approval processes within PeopleSoft. Approval workflows are triggered when employees, managers or users, submit a transaction, such an Expense Sheet.
Approval Process | A generic term referencing the business processof how a particular transaction is routed for approval within an organization. |
Approval Framework | Engine that provides capabilities for the creation,execution, and management of approval processes. |
Approval Process Definition | The definition of an approval process within theApproval Framework. The definition may contain stages, paths, steps,varying hierarchies, and criteria, among other configurable parameters. |
Approval Process DefinitionID (Process ID) | The ID associated with a particular approval processdefinition in the Approval Framework. Each transaction registeredwith the Approval Framework must have at least one process ID defined. |
Request | A transaction that uses the Approval Framework forapproval processing. For example, a promotion, transfer time off request,job requisition, and so on. |
Approval Step or Step | A step has one or more approvers, whose actionsare tracked. A step can be configured to require a set number of approversto act, and has criteria which govern whether or not the step is tobe active for the request under consideration. Steps are sequential. |
Approval Path or Path | A path is a sequence of steps. For example, steptwo routes to its approvers only after step one is approved. A givenapproval could actually go through multiple approval paths based onsome decisions. Paths can be mutually exclusive or parallel. Theyall converge at the final approval. |
Approval Stage or Stage | A stage is a collection of approval paths. Approvalstages come in a single sequence (stage 1, stage 2, and so on). Anapproval stage runs when it's immediately preceding stage finishes.When an approval stage runs, all the approval paths within it runsimultaneously. The approval stage is considered complete when allapproval paths within it have finished. |
Approver | The person who has been determined to have the authorityto approve (deny, pushback, and so on) a request. Lg stove serial number location. The LG.com website utilizes responsive design to provide convenient experience that conforms to your devices screen size. Play Chess Online. Tactics Training. Access to over 30,000 tactical positions, all taken from actual games and presenting a wide range of difficulty. Receive a tactical rating and track performance via statistics and graphs. Train Tactics. Endgame Training. Play up to 5. Completely free chess tactics and strategy training site with over 70.000 interactive checkmate problems and tactics puzzles. Join now this rapid growing community and soon you will notice great improvements in your chess skills!!! |
Requester and Originator | The requester is the person for whom you want theApproval Framework to treat as the initiator of a request. In mostcases the requester and originator are the same person. However, whenusing the Delegation feature the requester and originator of a requestcan vary. For example, if a manger delegates a transaction to a directreport and that direct report submits the transaction, the directreport is the originator and the manager is the requester. |
Subject | The person for whom a transaction is being processed.For example, Karen submits to her boss, Russell, a promotion requestfor one of her employees, Robbin. Karen is the requester (originator),Robbin is the subject, and Russell is the approver. |
Supervisor or Manager | The person who has management responsibilities forthe requester or for an approver, as defined in your direct reportsettings during implementation. |
Approvals Administrator or Approval Framework Administrator | The system administrator who is responsible forconfiguring, managing, troubleshooting, and maintaining approvals. |
Event or Approval Event | The Approval Framework engine is event driven. Eventsare typically actions that can be taken by a user in the system, actionssuch as submit, approve, deny, push back, and so on. |
Status or Approval Status | Statuses typically represent the overall state atransaction is in, such as pending, on hold, approved, denied, terminated,and so on. |
Approval Criteria | Rules used to decide whether or not approval isrequired. Approval criteria fields and dimensions are data elementsand attributes that are used to define the approval criteria. |
Approval Hierarchy | The organizational hierarchy that models the actualapprovals required by a transaction type (for example, approval hierarchyby supervisor or department). |
User List | Collection of users (PeopleSoft Operator IDs) expressedas the result of an SQL statement, PeopleSoft role, or PeopleSoftApplication Class. |
Alternate Approver or Alternate User ID | A user can have another user in the system as hisor her alternate approver for a specified period of time. This isset on the Workflow page of the User Profile component within PeopleToolssecurity. |
Delegation | Delegation is when a person authorizes another toserve as a his or her representative for a particular task of responsibility.With the Delegation feature, users can authorize other users to performmanagerial tasks on their behalf by delegating authority to initiateor approve managerial transactions. |
Approval Framework
The Approval Framework is the engine that providesthe framework and capabilities for creating, running, and managingapproval processes. The engine uses a series of database objects combinedwith application component configuration settings to determine howto process approvals using workflow.
Approval workflows are triggered when requesterssubmit a transaction, such as a promotion. The application hands thetransaction over to the Approval Framework, which finds the appropriateapproval process definition and launches the approval workflow. Aset of approvers then carry out tasks related to the transaction.
The Approval Framework enables three levels of usersto develop, configure, and use transaction approvals that meet theirorganizational requirements. For example, the process of submittinga promotion and getting it approved requires defining who will approvethe promotion, the order in which they will approve it, and how itwill be routed to approvers.
In contrast to the standard PeopleSoft workflow,which requires advanced technical skills in PeopleSoft PeopleToolsto create and maintain, approval workflow provides an alternativeworkflow that is much easier to create, configure, and maintain. Forexample, all of the steps in approval workflow are defined using PeopleSoftpages rather than underlying PeopleSoft PeopleCode, so functionalusers can design and maintain workflow using these online PeopleSoftpages instead of requiring technical developers to create workflowrules.
Related Links
Approvals Business Process Flow
Within the approvals business process flow:
- Application developers registerinformation with the Approval Framework by using the Register Transactionspage, where they register an application with the engine and describeits components, event handler, and records.As part of defining the registry, application developers create arecord and table in which to store cross-reference information andset up notification templates for events. This definition determinesthe pending approval workflow process and tells an application whichtransaction is being approved or denied. Application developers alsolink the transaction component.Note: PeopleSoft Human Resources delivers many transactionsthat are registered with the Approval Framework. Do not modify these transaction registry definitionsbecause the system requires their setup to be as delivered. For acomplete list of delivered transaction registry definitions, accessthe Register Transactions component by navigating to select Set Up HCM, then select Common Definitions, then select Approvals, then select ApprovalsSetup Center, then select Register Transactions.
- Functional business analystsdefine the approval process definition for an application transaction.The approval process definition includes settingup approval stages, paths, steps, recipients, and notifications foreach approval process ID. Analysts identify the approval transactionregistry entry on which to base approval process definitions and thendefine the details of the process.Functional business analysts also define or reviewuser list definitions, email template definitions, and transactionconfiguration settings.After completing the setup, functional businessanalysts are responsible for maintaining and troubleshooting approvalprocess transactions.
- Requesters submit a transactionfor approval.This action launches the approvalprocess. The Approval Framework reads the approval process definitionand queues the transaction for approvers.
- The system queues an approvaltask to an approver or reviewer using email notification, Worklistentry, or both.The URL encoded in the Worklistentry points to the corresponding approval component.
- Approvers take actions on transactions.They can approve or deny requests, monitor transactionstatuses, and audit approvals. When an error or violation of criteriaor rules occurs during the approval process, the system notifies theapprovals administrator, who interacts to resolve the issue.
- Reviewers view the transaction.
Image: Approval business process flow
This diagram details the business process flow ofimplementing and using approvals functionality. It shows tasks thatapplication developers, business analysts, and end users perform inconjunction with approval workflow.
Related Links
Sources of Information
The Approval Framework is a common component thatis shared across multiple PeopleSoft applications both within HCMand other product families. For the HCM product family, you'll finddocumentation pertaining to the Approval Framework in various locations:
- These present topics list theApproval Framework functionality that applies to the setup steps,navigation paths, and details that are specific to the HCM productfamily.
- Application-specific HCM documentation(such as PeopleSoft Absence Management) expand on all of the above texts by providing approval workflowdetails that relate to delivered business processes.
- The PeopleSoft Approval Framework describes the common ApprovalFramework functionality that applies to all product families.
Before implementing, you should read all relevantsources of information to gain a complete understanding of how thepieces fit together.
See Approval Framework.
Implementation of HCM Transactions for ApprovalFramework
PeopleSoft delivers many approval transactions thatare already configured to work with the Approval Framework. For deliveredtransactions, you should review the delivered transaction data withinthe application pages to ensure that the data fits your business processes.
Peoplesoft Approval Workflow
To review delivered HCM transactions for use withthe Approval Framework:
Peoplesoft Awe Workflow 9.2 Version
- Register the approval transactionin the Approval Framework through the Register Transactions page.See Registering Approval Transactions.
- Link Human Resources self-servicetransactions to the Approval Framework through the Workflow Transactionspage.See Linking Workflow Transactions.
- Set up the configuration optionsfor the approval transaction on the Configure Transactions page.See Configuring Approval Transactions.
- Set up the approval process definitionthrough the Setup Process Definitions component.See Setting Up Approval Process Definitions.To set up the approval process definition:
- Define the stages, paths, andsteps of the approval process definitions on the Setup Process Definitionspage.
- Define criteria for workflowapproval processes at the definition, path, and step level on theCriteria Definition page, which is accessed through links on the SetupProcess Definitions page.
- Set up path details for workflowapproval processes on the Approval Path Definition page.
- Define step details for approvalworkflow processes on the Approval Step Definition page.
- Define dynamic approvals throughvarious components.See Defining Dynamic Approvals.
- Create email templates for theapproval transaction on the Generic Template Definition page.See Defining Notification Templates for Approvals.
- Maintain user list definitionsfor the approval transaction on the User List Definition page.See Defining Users for Approvals.
- Set up the Notification and EscalationManager.See Setting Up the Notification and Escalation Manager.
- Set up the appropriate permissionlists, roles, and web libraries through PeopleTools security components.See Setting Up Security for Approvals.
Peoplesoft Awe Workflow 9.2 Login
If you need to implement other transactions foruse with the Approval Framework besides the delivered transactions,you must complete additional implementation steps. These steps includethose involving object construction within PeopleTools ApplicationDesigner and those involving setup within application pages. For technicaldetails on how to implement additional approval transactions, seethe PeopleSoft Approval Framework