Programming Workflow Activity Guide-1

Programming Workflow
Activity Guide
n l y
e O
U s
A I
O
l &
na
D18544GC10
te r
1.0
July 2004 I n
D41910
c le
r a
O
Copyright © 2004, 2005, Oracle. All rights reserved.
This document contains proprietary information and is protected by copyright and other intellectual property laws. You may
copy and print this document solely for your own use in an Oracle training course. The document may not be modified or
altered in any way. Except where your use constitutes "fair use" under copyright law, you may not use, share, download,
upload, copy, print, display, perform, reproduce, publish, license, post, transmit, or distribute this document in whole or in part
without the express authorization of Oracle.
The information contained in this document is subject to change without notice. If you find any problems in the document,
please report them in writing to: Oracle University, 500 Oracle Parkway, Redwood Shores, California 94065 USA. This
document is not warranted to be error-free.
If this documentation is delivered to the United States Government or anyone using the documentation on behalf of the United
States Government, the following notice is applicable:
U.S. GOVERNMENT RIGHTS

The U.S. Government’s rights to use, modify, reproduce, release, perform, display, or disclose these training materials are
restricted by the terms of the applicable Oracle license agreement and/or the applicable U.S. Government contract.
Oracle, JD Edwards, and PeopleSoft are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be
trademarks of their respective owners.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
CONTENTS
Preface Programming Workflow...................................................................................................v

Typographical Conventions and Visual Cues .....................................................................v
Lesson 1 Course Overview ...............................................................................................................1
Lesson 2 Technology Overview........................................................................................................3
Lesson 3 Evaluating Processes for Workflow Automation ...........................................................5

Activity 1: Explaining Process Reengineering and Workflow Automation Concepts ....6
Lesson 4 Designing Workflow Process Prototypes.........................................................................7

Activity 2: Defining the Credit Limit Workflow Process................................................8
Lesson 5 Creating a Workflow Project .........................................................................................11

Activity 3: Creating a Project for Workflow Development...........................................12
Lesson 6 Designing Message Templates........................................................................................15

Activity 4: Designing Credit Limit Message Templates ...............................................16
Lesson 7
l y
Designing Workflow Data Structures............................................................................21
Activity 5: Designing the Credit Limit Workflow Data Structures ...............................22
n
Lesson 8
e O
Creating a Workflow Process in OMW.........................................................................25
Lesson 9
U s
Activity 6: Creating the Credit Limit Workflow Object................................................26
Describing Workflow Modeler.......................................................................................29

I
Activity 7: Exploring Workflow Modeler .....................................................................30
A
Lesson 10
O
Designing Workflow Tasks.............................................................................................31
&
Activity 8: Designing Tasks for the Credit Limit Approval Process.............................32
l
Lesson 11
a
Designing Workflow Transitions and Conditions ........................................................39
n
Activity 9: Creating Transitions and Transition Conditions..........................................40
Lesson 12
te r
Attaching a Workflow Process to an Application ........................................................45
I n
Activity 10: Attaching the Credit Limit Workflow to an Application ........................46
Lesson 13
c l e
Setting Up Distribution Lists..........................................................................................51
Activity 11: Setting Up a Credit Limit Distribution List.............................................52
Lesson 14
r a Designing Recipient Rules and Conditions ...................................................................59
O
Lesson 15
Activity 12: Designing Recipient Rules and Conditions.............................................60
Analyzing Workflow Processes ......................................................................................65

Activity 13: Using Process Task Monitor ...................................................................66
PeopleSoft Proprietary and Confidential iii

Programming Workflow Contents
Activity 14: Using the Advanced Analysis Application .............................................67
Lesson 16 Administering Workflow Processes...............................................................................69

Activity 15: Changing Queue Security........................................................................70
Lesson 17 Final Course Activity ......................................................................................................71

Activity 16: Designing a Capital Projects Approval Workflow Process.....................72
Lesson 18 Course Review ...............................................................................................................115
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
iv PeopleSoft Proprietary and Confidential

Preface
Programming Workflow
Typographical Conventions and Visual Cues

This section discusses:
• Typographical conventions.
• Visual cues.
• Country, region, and industry identifiers.
• Currency codes.
Typographical Conventions
This table contains the typographical conventions that are used in this guide:
Typographical Convention
Bold
Description
n l y
Indicates PeopleCode function names, method names, language
literally in the function call.

e O
constructs, and PeopleCode reserved words that must be included
Italics
s
Indicates field values, emphasis, and PeopleSoft or other book-
U
length publication titles. In PeopleCode syntax, italic items are
A I
placeholders for arguments that your program must supply.
We also use italics when we refer to words as words or letters as
KEY+KEY O
letters, as in the following: Enter the letter O.
Indicates a key combination action. For example, a plus sign (+)
l & between keys means that you must hold down the first key while
you press the second key. For ALT+W, hold down the ALT key
n a while you press the W key.

Monospace font
te
“ ” (quotation marks)
r Indicates a PeopleCode program or other code example.
Indicate lesson and chapter titles in cross-references and words that
I n are used differently from their intended meanings.
c l e
. . . (ellipses) Indicate that the preceding item or series can be repeated any
number of times in PeopleCode syntax.
r a { } (curly braces) Indicate a choice between two options in PeopleCode syntax.

Options are separated by a pipe ( | ).
O [ ] (square brackets) Indicate optional items in PeopleCode syntax.
PeopleSoft Proprietary and Confidential v

Programming Workflow Preface
Typographical Convention Description

& (ampersand) When placed before a parameter in PeopleCode syntax, an
ampersand indicates that the parameter is an already instantiated
object.
Ampersands also precede all PeopleCode variables.
Visual Cues
Training courses contain the following visual cues.
Notes
Notes indicate information that you should pay particular attention to as you work with
the PeopleSoft system.
Note. Example of a note.
If the note is preceded by Important!, the note is crucial and includes information that
concerns what you must do for the system to function properly.
Important! Example of an important note.
Warnings
n l
Warnings indicate crucial configuration considerations. Pay close attention to warning
messages.
y
Warning! Example of a warning.
e O
Cross-References
U s
A I
Training guides provide cross-references either under the heading “See Also” or on a
separate line preceded by the word See. Cross-references lead to other documents, such
O
as PeopleBooks, that are pertinent to the immediately preceding documentation.
Example:
l &
n a
te r
Example of cross-reference to a PeopleBook
I n
Currency Codes
c l e
r a Monetary amounts are identified by the ISO currency code. The following currency
codes appear in this guide:
O •
•
USD (U.S. dollars)
EUR (Euro)
vi PeopleSoft Proprietary and Confidential

Lesson 1
Course Overview
This lesson has no activities.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O
PeopleSoft Proprietary and Confidential 1

Course Overview Lesson 1
Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
l y
______________________________________________________________________
n
O
______________________________________________________________________
e
s
______________________________________________________________________
U
I
______________________________________________________________________
A
O
______________________________________________________________________
l &
______________________________________________________________________
n a
r
______________________________________________________________________
te
I n
______________________________________________________________________
cle ______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________
2 PeopleSoft Proprietary and Confidential

Lesson 2
Technology Overview
This lesson has no activities.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O

Technology Overview Lesson 2
Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
l y
______________________________________________________________________
n
O
______________________________________________________________________
e
s
______________________________________________________________________
U
I
______________________________________________________________________
A
O
______________________________________________________________________
l &
______________________________________________________________________
n a
r
______________________________________________________________________
te
I n
______________________________________________________________________
cle ______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________

Lesson 3
Evaluating Processes for

Workflow Automation
n l y
e O
U s
A I
O
l &
na
te r
I n
c l e
r a
O

Evaluating Processes for Workflow Automation Lesson 3
Activity 1: Explaining Process Reengineering and Workflow

Automation Concepts
In this activity, you will review the activity overview and:
• Explain business process reengineering concepts.
• Explain workflow automation concepts.
Slide 37 _______________________________________________________________________________________________________
Activity Overview
Questions and Answers
Answer the following questions about business process reengineering and workflow
automation:
Question Answer
Why should a company analyze its business
processes before implementing a workflow
management system?
What is the first step in process reengineering?
Give an example of a business process.
What is an organization schematic?
n l y
What are some of the common criteria for evaluating
the performance of a business process?
e O
After completing process reengineering, processes
that have many manual steps are likely candidates
U s
for workflow automation.
1. True
A I
2. False
O
streamline business processes?
l &
In general, how does workflow management
n a
te r
This concludes the activity. Do not continue.
I n
c l e
r a
O

Lesson 4
Designing Workflow Process

Prototypes
n l y
e O
U s
A I
O
l &
na
te r
I n
c l e
r a
O

Designing Workflow Process Prototypes Lesson 4
Activity 2: Defining the Credit Limit Workflow Process

• Locate tasks on the Credit Limit workflow diagram.
• Locate transition conditions on the Credit Limit workflow diagram.
Slide 44 _______________________________________________________________________________________________________
Activity Overview
The credit department wants to monitor requests to change a customer’s credit limit.
When a credit limit is increased or decreased, the credit manager for the account is asked
to accept or reject the change. If the credit limit change is approved, the database is
updated and notification is sent to the originator that the change was approved. If the
change was not approved, the originator is notified that the change was rejected.
Examine the Credit Limit workflow process diagram below and answer the questions that
follow:
Change Credit Limit Triggering Event
n l y
CREDIT LIMIT APPROVAL
Enter Workflow Send Message to Approver
e O PROCESS
U s
Approve
A I Reject
Update Credit in O Send "Rejected" Message to

Originator
Database
l &
n a
te r
Send "Accepted" Message to
Originator
I n
Diagram of the Credit Limit Approval workflow process
cl e
Answer these questions:
O ra Question
What is the triggering event that starts the Credit
Limit workflow process?
Answer
What are the individual tasks in the Credit Limit

workflow process?

Lesson 4 Designing Workflow Process Prototypes
Question Answer
What is the triggering event that starts the Credit
Limit workflow process?
Are there any transition conditions (conditional
logic) that affect the path the workflow will take?
If so, what are they?
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O

Designing Workflow Process Prototypes Lesson 4
Notes
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
______________________________________________________________________
l y
______________________________________________________________________
n
O
______________________________________________________________________
e
s
______________________________________________________________________
U
I
______________________________________________________________________
A
O
______________________________________________________________________
l &
______________________________________________________________________
n a
r
______________________________________________________________________
te
n
______________________________________________________________________
I
cl e______________________________________________________________________
r a ______________________________________________________________________
O ______________________________________________________________________

Lesson 5
Creating a Workflow Project
n l y
e O
U s
A I
O
l &
na
te r
I n
c l e
r a
O

Creating a Workflow Project Lesson 5
Activity 3: Creating a Project for Workflow Development

1. Create a project.
2. Add an owner to the project.
3. Advance the project to the programming status.
Slide 53 _______________________________________________________________________________________________________
Activity Overview
All development in PeopleSoft EnterpriseOne is done within the context of a project.
Because you will be developing a new Credit Limit workflow process in the activities
that follow, you need to create an OMW project for the new workflow object. The project
will also contain all the other objects that you create or modify for the Credit Limit
workflow.
The system administrator has defined Object Management Workbench to function in this
way:
• New projects are named sequentially (beginning with 101) as follows: TRN<last two
•
digits of your user ID>101.
New projects begin at a status 11.

n l y
• The release value is the current software release.
e O
• s
The planned completion date should be five days after the project is created.
U
•
I
The person who creates the project will be added to the project in the originator role.
A
O
Important! The classroom workstations are set up to replicate a real business
environment. Therefore, everyone is completing this course in a shared database; any
l &
changes that you make could affect the entire class. Please do not make any changes in
the database unless instructed to do so in an activity or by the instructor.
n a
activity.
te r
Note. Use STA<last two digits of your user ID> for the user name and password in this
Creating a Project I n
c l e
To create a project:
r a 1. From Solution Explorer, click the Tools menu.
O 2. Click Object Management Workbench.
3. In Object Management Workbench, click Add.

Lesson 5 Creating a Workflow Project
4. Under the Object Management Workbench section of the Add EnterpriseOne Object
to the Project form, select the OMW Project option.
5. On the Project Revisions form, select the Summary tab.
6. Enter the following information:
Field Value or Status

Project ID TRN<last two digits of your user ID>101
Description Credit Limit Approval
Status 11 (New Project Pending Review)
Type 02 (Enhancement)
Severity 03 (Not Critical/No Workaround)
Product System Code 55 (Reserved for Clients)
Release <current release>
7. Select the Dates tab.

Date Started
Planned Completion Date
(Populated by the system)
<five days past start date>
n l y
Date Entered
Completion Date Blank
e O
(Populated by the system)
U s
9. Select the Attachments tab.
A I
O
10. Enter the following information: This project was created to add the Credit Limit
Approval workflow process.
l &
Adding an Owner to the Project
n a
r
To add an owner to the project:
te
I n
1. Expand the new project to reveal the Objects and Owners nodes.
2. Focus on the Owners node.
c l e
3. Enter the following information on the Search tab:
r a Field Value or Status
O Category
Search Type
Owners
User ID
Search STA1* (TCA1* for instructor)

Creating a Workflow Project Lesson 5
4. Focus on your user ID.
5. Move your user ID into the project by clicking the Add Object or User to Project
arrow.
6. On the Add User to Project form, use the visual assist to select the developer role
(02).
7. Expand the Owners node to verify your addition.
Advancing the Project to the Programming Status

To advance the project to the programming status:
1. Focus on the project ID: TRN<last two digits of your user ID>101.
2. Click the Advance Project button in the center column.
3. On the Confirm Status Change form, use the visual assist on the blank field to select
the programming status: 21.
n l y
e O
U s
A I
O
l &
n a
te r
I n
c l e
r a
O

Lesson 6
Designing Message Templates
n l y
e O
U s
A I
O
l &
na
te r
I n
c l e
r a
O

Designing Message Templates Lesson 6
Activity 4: Designing Credit Limit Message Templates

In this activity, you will review the activity overview and design message templates for
the Credit Limit Approval workflow process.
Slide 62 _______________________________________________________________________________________________________
Activity Overview
Review the Credit Limit Approval diagram in Activity 2 and answer these questions:
Question Answer
How many messages are there in the Credit Limit
Approval workflow process diagram?
Describe the purpose of each workflow message.
In the TRN<last two digits of your user ID>101 project, create the required message
templates for the Credit Limit Approval workflow process. Use variables in each
message, if appropriate, to provide specific data regarding:
• The customer whose credit limit has changed.
• The old and new credit limits.

n l y
• The employee who changed the customer’s credit limit.
e O
U
sequentially through the alphabet for additional messages:s
Name the messages as follows, starting with A for the first message, and continuing
• I
LM553<last two digits of your user ID>A for the first message.
A
•
O
Follow the same naming convention for subsequent messages, using the letters B, C,
and so on, at the end of each name.
l &
n a
te r
Important! The classroom workstations are set up to replicate a real business
environment. Therefore, everyone is completing this course in a shared database; any
changes that you make could affect the entire class. Please do not make any changes in
I n
the database unless instructed to do so in an activity or by the instructor.
cl e
Note. Use STA<last two digits of your User ID> for the user name and password in this
activity.
r a
O
Designing Message Templates for the Credit Limit Approval Workflow Process
To design message templates for the Credit Limit Approval workflow process, access
OMW:

Lesson 6 Designing Message Templates
Task View Navigation

EnterpriseOne Menus Foundation Systems, Tools, Application Development Tools, Cross
Application Development Tools, Object Management Workbench.
Creating the Credit Limit Approval Request Message
To create the credit limit approval request message:
1. Select the Objects node of the Credit Limit Approval project.
2. Click Add.
3. On the Add EnterpriseOne Object to the Project form, select Data Item and then click
OK.
4. On the Data Dictionary Item Type form, click Yes to create a glossary data item.

Alias LM553<last two digits of your user ID>A
Glossary Group Y
Product Code 55
Product Reporting Code
Description
55
Credit Limit Approval Request
n l y
Error Level 3
e O
U s
A I
6. On the Item Glossary tab, enter text that is similar to the following information:
The credit limit for customer &1, &2, was changed from &3 to &4 on &5 by &6.
O
Your approval is required for this change to take effect.
&
7. Click OK to return to the OMW.
l
a
8. The LM553<last two digits of your user ID>A message should now be listed as an
n
te r
object under the Credit Limit Approval project.
Creating the Credit Limit Accepted Message
I n
To create the credit limit accepted message:
cl e
O ra 2. Click Add.
OK.

Designing Message Templates Lesson 6

Alias LM553<last two digits of your user ID>B
Glossary Group Y
Product Code 55
Product Reporting Code 55
Description Credit Limit Change Accepted
Error Level 3
6. On the Item Glossary tab, enter text that is similar to the following information:
The credit limit for customer &1, &2, has been approved for &3.
8. The LM553<last two digits of your user ID>B message should now be listed as an
object under the Credit Limit Approval project.
Creating the Credit Limit Rejected Message

To create the credit limit rejected message:
2. Click Add. n l y
e O
OK.
U s

A I
Field
O Value or Status
l&
Alias LM553<last two digits of your user ID>C
Glossary Group
n a Y
Product Code
t e r
Product Reporting Code
55
55
I n
Description Credit Limit Change Rejected
c l e
Error Level 3
r a 6. On the Item Glossary tab, enter text that is similar to the following information:
O The credit limit change to &1 for customer &2, &3, has been rejected.

Programming Workflow Activity Guide-1

Uploaded by

Copyright:

Available Formats

Programming Workflow Activity Guide-1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Programming Workflow Activity Guide-1

Uploaded by

Copyright:

Available Formats

Programming Workflow

U.S. GOVERNMENT RIGHTS

Preface Programming Workflow...................................................................................................v

Lesson 1 Course Overview ...............................................................................................................1

Lesson 2 Technology Overview........................................................................................................3

Lesson 3 Evaluating Processes for Workflow Automation ...........................................................5

Lesson 4 Designing Workflow Process Prototypes.........................................................................7

Lesson 5 Creating a Workflow Project .........................................................................................11

Lesson 6 Designing Message Templates........................................................................................15

Describing Workflow Modeler.......................................................................................29

Analyzing Workflow Processes ......................................................................................65

PeopleSoft Proprietary and Confidential iii

Activity 14: Using the Advanced Analysis Application .............................................67

Lesson 16 Administering Workflow Processes...............................................................................69

Lesson 17 Final Course Activity ......................................................................................................71

Lesson 18 Course Review ...............................................................................................................115

iv PeopleSoft Proprietary and Confidential

Typographical Conventions and Visual Cues

• Country, region, and industry identifiers.

literally in the function call.

n a while you press the W key.

I n are used differently from their intended meanings.

r a { } (curly braces) Indicate a choice between two options in PeopleCode syntax.

O [ ] (square brackets) Indicate optional items in PeopleCode syntax.

PeopleSoft Proprietary and Confidential v

Typographical Convention Description

Note. Example of a note.

Important! Example of an important note.

vi PeopleSoft Proprietary and Confidential

PeopleSoft Proprietary and Confidential 1

2 PeopleSoft Proprietary and Confidential

PeopleSoft Proprietary and Confidential 3

4 PeopleSoft Proprietary and Confidential

Evaluating Processes for

PeopleSoft Proprietary and Confidential 5

Activity 1: Explaining Process Reengineering and Workflow

• Explain business process reengineering concepts.

• Explain workflow automation concepts.

6 PeopleSoft Proprietary and Confidential

Designing Workflow Process

PeopleSoft Proprietary and Confidential 7

Activity 2: Defining the Credit Limit Workflow Process

• Locate tasks on the Credit Limit workflow diagram.

• Locate transition conditions on the Credit Limit workflow diagram.

Change Credit Limit Triggering Event

Update Credit in O Send "Rejected" Message to

What are the individual tasks in the Credit Limit

8 PeopleSoft Proprietary and Confidential

This concludes the activity. Do not continue.

PeopleSoft Proprietary and Confidential 9

10 PeopleSoft Proprietary and Confidential

Creating a Workflow Project

PeopleSoft Proprietary and Confidential 11

Activity 3: Creating a Project for Workflow Development

2. Add an owner to the project.

3. Advance the project to the programming status.

New projects begin at a status 11.

r a 1. From Solution Explorer, click the Tools menu.

O 2. Click Object Management Workbench.

3. In Object Management Workbench, click Add.