This has greatly segregated the designing of workflow to the functional team and the supporting objects to the Technical Developer. Unlike Workflow, there is no requirement of creation of Components, steps, rules and routing in Application Designer. In this way PeopleSoft has tried to simplify the workflow process making it more configurable. Starting with a simple AWE workflow we need to carry out few steps. Lets create a simple AWE workflow which consists of only one step.
|Published (Last):||14 October 2010|
|PDF File Size:||6.72 Mb|
|ePub File Size:||11.92 Mb|
|Price:||Free* [*Free Regsitration Required]|
This has greatly segregated the designing of workflow to the functional team and the supporting objects to the Technical Developer.
Unlike Workflow , there is no requirement of creation of Components,steps,rules and routing in Application Designer.
In this way peoplesoft has tried to simplify the workflow process making it more configurable. Starting with a simple AWE workflow we need to carry out few steps.
Lets create a simple AWE workflow which consists of only one step. The requester requests for some amount for an asset. When the requester submits the request, the approvers get the notification by email and worklist. One of Approver approves the request and the Asset status is set to Approved else Denied. Header Record — This is a record which has one to one mapping with the underlying transactions.
I created a XREF record as below. Transaction Component Now we need a component which will trigger the workflow or where the requester will submit the requests. Component Structure in App Designer. I have added 3 buttons :Approve, Deny, Submit. The buttons as suggested by their name are to Submit, Approve or Deny a Request.
At this moment all three buttons are visible but we will control its visibility as we progress. We will later see how this page is customized to fulfill our requirements. Event Handler — AWE is controlled by events, when a request is submitted, a event takes place, when a request is approved a event triggers, when a request is denied , a event take place.
If we want to do other stuffs than what the delivered app package does, we need to create our Event Handler ,extending the core EOAW classes. But, later we will see that we need to create an event handler to tackle our requirement. Configuring AWE , Registering the transaction. Enter the Cross Reference Record which we defined in Step2. In Notification Options Select as below.
Now it is not required. We do not need these as of now. Fill the Default Approval Component as below. We do not need these items for our simple AWE. As of now we have not created any Event Handler for our workflow , so we will use the delivered App package and Class as shown below.
Thread Class is used to control what is displayed in the Approval Monitor. This can be created as below. Userlist defines the list of user who will be getting the notification when some event triggers. Adding the Approval Process Setup. Since, we are creating approval process of only one step. We will create only one stage,one path and one step in the setup. Click on Definition Criteria and set it as Always true. Click on Alert Criteria and set it as Always true. Click on Path Criteria and set it as Always true.
Click on Step Criteria and set it as Always true. All Criteria is now set, So a tick is appearing in each criteria link. Criteria are used to determine whether to enter a path,step,stage or not. Lets code that when user clicks on Submit , it launches the AWE workflow. When the Approver , approves the request it completes the workflow as approved and vice versa.
We have written the code on buttons but we still have not launched the AWE. The best place to trigger AWE events are at SavePostchange as all the validations are done by that point.
For Approving the running Workflow the DoApprove method has to be called. Similar is the case for DoDeny. Below is the code:.
PeopleSoft AWE – Approval Workflow Engine