A Workflow Setup in PeopleSoft (source: PeopleBooks v8.

3)
The following steps, in our experience, always cause frustration among clients trying to set up workflow with PeopleSoft. It is difficult enough to design and setup workflow without introducing unnecessary complexity. Even then, simply following the steps (below) is not even enough, as one requires an understanding of PeopleSoft's Business Process Designer methodology, and how the objects manipulated in the steps below relate to one another. If clients manage to get it going, the end-result almost always contains reduced functionality, is more likely to be impacted by upgrades, and has a much higher cost of ownership. In Application Designer, select File > New and select the map type and click OK. Add the icons you want to include in your map. When you add these types of icons to the map, specify an existing activity or business process that the icon is to represent. Connect the activities, decision points, and subprocesses in the appropriate order. Define the properties of the map. Define the properties of the icons on the map. Create a worklist record definition. Add the key fields from the search record for the page group users use to process the worklist entries. Add a character field named COMMAND_PARM if users work on work items using an external program. Add fields to provide descriptive information in the user's worklist. Save the record definition using a name that ends with _WL. Create a database table using the record definition you saved (note: you now have to alter a table and do data conversion if you change the worklist fields) Define the workflow objects. Display the activity to which you want to add the event. Click the Event button in the toolbar, then click where you want the event to appear on the map. Connect the event icon to the icon for the step that triggers it. Double-click the event icon or right-click the icon and select Component Properties. Enter a name and description of the event. Specify whether the event is active. Identify the record that triggers this event. Click the Edit Business Rules button. Enter the PeopleCode that triggers the business event. Save the PeopleCode, then click OK to close the Event Definition dialog box. Create a Worklist routing. Create the business event that triggers the worklist routing. Click the Worklist button in the toolbar, then click where you want the routing icon to appear on the map. Connect the routing to the event that triggers it. Double-click the worklist icon or right-click and select Component Properties. Enter a name and description for the routing. Click the Attributes button. In the Worklist Attributes box, select the record definition to use for storing and displaying work items. Specify what activity works the items from this worklist.

In the Worklist Page Attributes group box, specify how users retrieve work items from the worklist. Specify the timeout parameters. Click OK to close the Worklist Attributes dialog box and return to the Worklist Properties dialog box. Click the Field Mapping button. Highlight the field into which you want to map a value, then click the Change button. To add a new field to the map, click the Add button. Select the field into which you want to place routing data. Identify the value for the selected field. If you map the field to a role name, provide values for any bind variables. If you map the field to a record field, specify whether the system copies the assigned value directly into the worklist field or replaces the assigned value with a value from the Translate Table. Click OK to add the field and its value to the routing dialog box. Repeat for each field you want to add to the routing. Close all the dialog boxes by clicking OK in each one. Create an email routing. Create the business event that triggers the email routing. Connect the routing to the event that triggers it. Double-click the email icon or right-click it and select Component Properties. Enter a name and description for the routing. Click the Attributes button. Select any settings you want to apply to the email message. Click OK to return to the Email Definition dialog box. Click the Field Mapping button. Highlight the field you want to map a value into, then click the Change button. To add a new field to the map, click the Add button. Select the field into which you want to place routing data. Identify the value for the selected field. If you map the field to a role name, provide values for any bind variables. If you map the field to a record field, specify whether the system copies the assigned value directly into the field or replaces the assigned value with a value from the Translate Table. Click OK to add the field and its value to the routing dialog box. Repeat for each field you want to add to the routing. Close all the dialog boxes by clicking OK in each one. Create an Approval Rule Set. In the Application Designer, select File > New and select Approval Rule Set and click OK. Save the rule set and assign an effective date. Open the Approval Rule Properties dialog box. Enter descriptive information about the Approval Rule Set. Temporarily suspend the use of this approval rule set (optional). Specify whether users can approve their own transactions. Move to the Use tab. Enter the name of the Business Process associated with this rule set. Specify the event to trigger when all required approvals have occurred. Specify currency units for the approval rules. Specify the currency unit for the transaction. Click OK to close the properties dialog box. Add approval steps to the rule set. Click the Approval Step button on the toolbar. Click the place on the Approval Rule Set where you want the step to appear. Double-click the rule step icon or right-click it and select Component Properties.

Enter an icon description. In the Route to Role list box, select the role that performs this step. In the Equally Authorized Roles field, select all the roles that are qualified to process the transaction at this step. Specify what the user sees when a transaction requires Further Processing for approval. Specify whether the system can bypass this approval step if there's additional approval required. In the Appr Step and Appr Path boxes, specify which step you're defining. Move to the Rules tab to specify the approval parameters. Specify what transactions the specified role users have the authority to approve. Move to the Events tab to specify which business events are triggered, depending on the action of the approver at this step. In the Pre-Approved Activity/Event group box, select the business event to trigger when this approver approves the transaction. Specify what events to trigger if the user denies or recycles the transaction. Repeat entire procedure for each step in the approval process. Add pages WF_FUNCTIONS_01 and APPR_WRK_01 to the list of pages in the component. Add SaveEdit PeopleCode. Declare the external workflow functions Get_RoleUser and Virtual_Approver. Set values in the APPR_FIELDS_WRK work record to give the Virtual_Approver function the data it needs to check the approval rules. Call the Virtual_Approver function. Set the approval status record field to the value that Virtual_Approver returns. Add Workflow PeopleCode. Declare external workflow function Virtual_Router. Set values in the APPR_FIELDS_WRK.APPR_VR_ROW to give the Virtual_Router function the data it needs. Call the Virtual_Router function.