Implement

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2016, Oracle and/or its affiliatesฺ
nse
li c e
ble
fe r a
a n s
o
R12.x Implement
n-tr
a n Oracle Workflow
) h as deฺ
sa t Gui
Volume I - Student Guide
u ฺ
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
D58320GC10
Edition 1.0
October 2009
D66008
Copyright © 2009, 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, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may
be trademarks of their respective owners.
nse
li c e
Authors
bl e
fe r a
Clara Jaeckel
a n s
Technical Contributors and Reviewers no n-tr
a
Leta Davis, Donna Johnson, Shivasmruthi Narayanasamy
) h as deฺ
u ฺ sa t Gui
This book was published using: oracletutor
ฺed uden
s t
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Table of Contents
Introduction to Oracle Workflow ..................................................................................................................1-1

Introduction to Oracle Workflow ..................................................................................................................1-3
Objectives ......................................................................................................................................................1-4
Enabling E-Business......................................................................................................................................1-5
Inter-Enterprise Business Processes ..............................................................................................................1-6
Traditional Workflow ....................................................................................................................................1-7
Workflow-Driven Business Processes...........................................................................................................1-8
Sample Workflow Process.............................................................................................................................1-10
Event-Based Workflow .................................................................................................................................1-11
Subscription-Based Processing......................................................................................................................1-12
System Integration with Oracle Workflow ....................................................................................................1-13
Business Process-Based Integration ..............................................................................................................1-14
Supported System Integration Types.............................................................................................................1-15 nse
Designing Applications for Change...............................................................................................................1-16 li c e
Designing Applications for Integration .........................................................................................................1-19 bl e
fe r a
Summary........................................................................................................................................................1-21
a n s
Oracle Workflow Components.......................................................................................................................2-1
no n-tr
Oracle Workflow Components ......................................................................................................................2-3
Objectives ......................................................................................................................................................2-4
a
h as deฺ
Oracle Workflow Architecture ......................................................................................................................2-5
Oracle Workflow Components ......................................................................................................................2-9
)
u ฺ sa t Gui
Workflow Engine ..........................................................................................................................................2-10
ฺed uden
Workflow Processes ......................................................................................................................................2-11
t
Supported Process Constructs........................................................................................................................2-13
s
k ac is St
Oracle Workflow Builder ..............................................................................................................................2-17
Business Event System Architecture .............................................................................................................2-18
j ri@ e th
Business Event System Components.............................................................................................................2-19
a
r a lh o us
Advanced Queuing, an Enabling Technology ...............................................................................................2-20
ri ( t
Oracle Database Communication Alternatives..............................................................................................2-21
j
a
Accessing Oracle Workflow Web Pages .......................................................................................................2-23
lh
A
Oracle Workflow Home Pages ......................................................................................................................2-24
d
she
Notification System .......................................................................................................................................2-25
Ra Worklist Web Pages ......................................................................................................................................2-26

E-Mail Notifications ......................................................................................................................................2-27
Directory Services .........................................................................................................................................2-28
Status Monitor Web Pages.............................................................................................................................2-29
Workflow Definitions Loader........................................................................................................................2-30
Workflow XML Loader.................................................................................................................................2-31
Workflow Manager........................................................................................................................................2-32
Service Components ......................................................................................................................................2-33
Oracle Workflow Documentation..................................................................................................................2-34
Summary........................................................................................................................................................2-35
Planning a Workflow Process.........................................................................................................................3-1
Planning a Workflow Process........................................................................................................................3-3
Objectives ......................................................................................................................................................3-4
Workflow Process Components ....................................................................................................................3-5
Oracle Workflow Builder ..............................................................................................................................3-7
Standard Activities ........................................................................................................................................3-8
Planning a Workflow Process........................................................................................................................3-10
Activity Results and Lookup Types...............................................................................................................3-13
Summary........................................................................................................................................................3-15
Copyright © Oracle Corporation, 2009. All rights reserved.
R12.x Implement Oracle Workflow Table of Contents

i
Diagramming a Workflow Process ................................................................................................................4-1
Diagramming a Workflow Process................................................................................................................4-3
Objectives ......................................................................................................................................................4-4
Creating a New Workflow Process................................................................................................................4-5
Creating a New Process from Top Down ......................................................................................................4-6
Creating a New Process from Bottom Up .....................................................................................................4-7
Diagramming a Process .................................................................................................................................4-8
Quick Start Wizard ........................................................................................................................................4-9

Defining an Item Type...................................................................................................................................4-12
Defining a Process Activity ...........................................................................................................................4-14
Top-Down Design .........................................................................................................................................4-17
<Default> Transition .....................................................................................................................................4-19
<Any> Transition ..........................................................................................................................................4-20
Editing a Transition .......................................................................................................................................4-21
Self-Looping Transitions ...............................................................................................................................4-23 nse
Customizing an Activity Node ......................................................................................................................4-24
li c e
Show Label in Designer Menu Options.........................................................................................................4-26
bl e
r a
Display Modes...............................................................................................................................................4-27
fe
a n s
Verifying a Process Definition ......................................................................................................................4-28
n-tr
Validation Performed by the Verify Command.............................................................................................4-29
Saving Process Definitions ............................................................................................................................4-31
no
Summary........................................................................................................................................................4-32
a
) h as deฺ
Defining Item Type Attributes and Lookup Types.......................................................................................5-1
u ฺ sa t Gui
Defining Item Type Attributes and Lookup Types........................................................................................5-3
Objectives ......................................................................................................................................................5-4
s t ฺed uden
Defining Item Type Attributes.......................................................................................................................5-5
k ac is St
Attribute Data Types .....................................................................................................................................5-7
Defining Item Type Attributes.......................................................................................................................5-9
j r i@ e th
URL Attributes ..............................................................................................................................................5-10
a
r a lh o us
Form Attributes .............................................................................................................................................5-13
j
Deleting Item
(
rAttributes t
Document Attributes......................................................................................................................................5-16
i ................................................................................................................................5-19
a
lhLookup Types.................................................................................................................................5-20
Defining
d A
Defining Lookup Codes.................................................................................................................................5-21
s h e Summary........................................................................................................................................................5-22
Ra Defining Messages and Notification Activities ..............................................................................................6-1
Defining Messages and Notification Activities .............................................................................................6-3
Objectives ......................................................................................................................................................6-4
Notification Activities ...................................................................................................................................6-5
Defining a Message .......................................................................................................................................6-6
Defining a Message Attribute........................................................................................................................6-8
Defining a Respond Attribute........................................................................................................................6-10
Defining a Message Result ............................................................................................................................6-11
Notification Details Web Page ......................................................................................................................6-12
HTML E-mail Notifications ..........................................................................................................................6-13
Plain Text E-mail Notifications Using Templated Response ........................................................................6-14
Plain Text E-mail Notifications Using Direct Response ...............................................................................6-15
Defining a Notification Activity....................................................................................................................6-16
Standard Voting Activity...............................................................................................................................6-18
Defining a Notification Activity Node ..........................................................................................................6-19
Defining a Timeout for a Notification ...........................................................................................................6-20
Defining a Dynamic Priority for a Notification.............................................................................................6-21
Defining a Performer for a Notification ........................................................................................................6-22
Special Message Attributes............................................................................................................................6-23

ii
Action History ...............................................................................................................................................6-30
Special Message Function .............................................................................................................................6-31
Embedding Oracle Application Framework Regions in Notifications ..........................................................6-33
Summary........................................................................................................................................................6-34
Testing and Monitoring Workflow Processes ...............................................................................................7-1
Testing and Monitoring Workflow Processes................................................................................................7-3
Objectives ......................................................................................................................................................7-4
Testing Workflow Processes .........................................................................................................................7-5

Administrator Monitor...................................................................................................................................7-8
Viewing Workflows in the Administrator Monitor .......................................................................................7-10
Viewing Activity History in the Administrator Monitor ...............................................................................7-12
Viewing a Status Diagram in the Administrator Monitor..............................................................................7-13
Viewing Responses in the Administrator Monitor ........................................................................................7-15
Viewing Workflow Details in the Administrator Monitor.............................................................................7-17
Viewing Error Information in the Administrator Monitor.............................................................................7-18
Viewing Child Workflows in the Administrator Monitor .............................................................................7-19
nse
Self-Service Monitor .....................................................................................................................................7-20
Viewing Workflows in the Self-Service Monitor..........................................................................................7-21 li c e
Viewing Notification History in the Self-Service Monitor............................................................................7-23 bl e
Viewing a Status Diagram in the Self-Service Monitor ................................................................................7-24 fe r a
n s
Viewing Responses in the Self-Service Monitor ...........................................................................................7-26
a
no n-tr
Viewing Error Information in the Self-Service Monitor ...............................................................................7-28
Summary........................................................................................................................................................7-29
a
h as deฺ
Viewing and Responding to Notifications......................................................................................................8-1
Viewing and Responding to Notifications.....................................................................................................8-3
)
ฺ s a Gui
Objectives ......................................................................................................................................................8-4
d u nt
Viewing Notifications from a Web Browser .................................................................................................8-5
e
t ฺ d e
a cs Stu
Worklist Pages...............................................................................................................................................8-6
Advanced Worklist ........................................................................................................................................8-7
k
j r i @ this
Notification Details........................................................................................................................................8-9
l h a use........................................................................................................8-14
Reassigning Notifications..............................................................................................................................8-12
Responding to a Group
i r a of Notifications
to
(Information........................................................................................................................8-15
r
Requesting More
j
A lhaWorklistDigital
Certificate-Based
Granting
Signatures .............................................................................................................8-16
Access..............................................................................................................................8-18
d
she Administrator Search for Notifications..........................................................................................................8-22
Ra Reviewing Electronic Signature Details ........................................................................................................8-24
Personal Worklist ..........................................................................................................................................8-26
Simple Search for Notifications.....................................................................................................................8-28
Advanced Search for Notifications................................................................................................................8-29
Creating a Personal Worklist View ...............................................................................................................8-31
Viewing Notifications Through E-mail .........................................................................................................8-33
E-mail Response Methods .............................................................................................................................8-35
HTML-Formatted E-mail Notifications.........................................................................................................8-36
Plain Text E-mail Notifications Using Templated Response ........................................................................8-39
Plain Text E-mail Notifications Using Direct Response ...............................................................................8-41
Viewing an E-mail Summary of Notifications ..............................................................................................8-43
Vacation Rules...............................................................................................................................................8-44
Maintaining Vacation Rules ..........................................................................................................................8-45
Defining Vacation Rules ...............................................................................................................................8-46
Summary........................................................................................................................................................8-49
Worklist Flexfields...........................................................................................................................................9-1
Worklist Flexfields ........................................................................................................................................9-3
Objectives ......................................................................................................................................................9-4
Worklist Flexfields ........................................................................................................................................9-5

iii
Benefits of Worklist Flexfields......................................................................................................................9-6
Defining a Specialized Worklist View Using Worklist Flexfields ................................................................9-7
Message Attributes in Worklist Flexfields Rules ..........................................................................................9-8
How Worklist Flexfields Rules Operate........................................................................................................9-9
Phase Numbers ..............................................................................................................................................9-10
Customization Levels ....................................................................................................................................9-11
Core Rules .....................................................................................................................................................9-12
Limit and User Rules.....................................................................................................................................9-14

Combining Core, Limit, and User Rules .......................................................................................................9-17
Worklist Flexfields Rules Example ...............................................................................................................9-18
Defining a Worklist Flexfields Rule: Entering General Properties ...............................................................9-20
Defining a Worklist Flexfields Rule: Selecting Filter Criteria ......................................................................9-22
Defining a Worklist Flexfields Rule: Selecting Message Attributes .............................................................9-23
Defining a Worklist Flexfields Rule: Mapping Attributes to Columns .........................................................9-25
Resolving Conflicts Between Worklist Flexfields Rules...............................................................................9-27
Maintaining Worklist Flexfields Rules..........................................................................................................9-28
Storing Message Attribute Values in Worklist Flexfields Columns..............................................................9-30 nse
Performing a Worklist Flexfields Rule Simulation .......................................................................................9-31
li c e
bl
Defining a Securing Function........................................................................................................................9-34 e
Creating a Personalized View for the Personal Worklist...............................................................................9-35
fe r a
a n s
Restarting Oracle HTTP Server.....................................................................................................................9-37
n-tr
Summary........................................................................................................................................................9-38
a no
Oracle Workflow Directory Service...............................................................................................................10-1
Oracle Workflow Directory Service ..............................................................................................................10-3
) h as deฺ
Objectives ......................................................................................................................................................10-4
u ฺ sa t Gui
Oracle Workflow Directory Service ..............................................................................................................10-5
Predefined Directory Service.........................................................................................................................10-6
s t ฺed uden
Directory Service Views................................................................................................................................10-7
k ac is St
WF_USERS View .........................................................................................................................................10-8
WF_ROLES View.........................................................................................................................................10-11
j ri@ e th
WF_USER_ROLES View.............................................................................................................................10-13
a
r a lh o us
WF_USER_ROLE_ASSIGNMENTS_V View ............................................................................................10-16
j ri ( t
Local Directory Service Tables .....................................................................................................................10-18
Ad Hoc Users and Roles................................................................................................................................10-20
lh a
Validating a Directory Service Data Model...................................................................................................10-21
d A
Setting Workflow Preferences.......................................................................................................................10-22
she Loading Roles................................................................................................................................................10-23
Ra Summary........................................................................................................................................................10-24
Defining Function Activities ...........................................................................................................................11-1
Defining Function Activities .........................................................................................................................11-3
Objectives ......................................................................................................................................................11-4
Function Activities ........................................................................................................................................11-5
Defining a Function Activity .........................................................................................................................11-6
External Function Activities ..........................................................................................................................11-8
Assigning a Cost to a Function Activity........................................................................................................11-10
PL/SQL Procedures for Function Activities ..................................................................................................11-11
Standard API for PL/SQL Procedures Called by Function Activities ...........................................................11-12
Standard API Parameters...............................................................................................................................11-14
Function Activity Execution Modes ..............................................................................................................11-15
Standard API Resultout Parameter ................................................................................................................11-17
Exception Handling .......................................................................................................................................11-18
Exception Handling Example ........................................................................................................................11-19
Defining Activity Details...............................................................................................................................11-20
Error Handling...............................................................................................................................................11-22
Looping .........................................................................................................................................................11-23
Defining an Activity Attribute.......................................................................................................................11-24

iv
Setting Activity Attribute Values ..................................................................................................................11-25
Summary........................................................................................................................................................11-26
Post-Notification Functions.............................................................................................................................12-1
Post-Notification Functions ...........................................................................................................................12-3
Objectives ......................................................................................................................................................12-4
PL/SQL Procedures for Notification Activities.............................................................................................12-5
Standard API for PL/SQL Procedures Called by Notification Activities ......................................................12-6
Post-Notification Function Execution Modes................................................................................................12-9

Standard API Resultout Parameter for a Post-Notification Function ............................................................12-11
Post-Notification Function Context Information ...........................................................................................12-12
Exception Handling .......................................................................................................................................12-13
Summary........................................................................................................................................................12-14
Workflow Engine.............................................................................................................................................13-1
Workflow Engine ..........................................................................................................................................13-3
Objectives ......................................................................................................................................................13-4
Overview of the Workflow Engine................................................................................................................13-5 nse
Initiating a Workflow Process .......................................................................................................................13-7 li c e
bl
Workflow Engine Processing ........................................................................................................................13-9 e
r a
Activity Statuses ............................................................................................................................................13-12
fe
a n s
Calling the Workflow Engine........................................................................................................................13-13
n-tr
Background Engines......................................................................................................................................13-14
Stuck Processes .............................................................................................................................................13-15
no
Timed Out Activities .....................................................................................................................................13-16
a
h as deฺ
Deferred Processing.......................................................................................................................................13-17
Oracle Workflow APIs ..................................................................................................................................13-19
)
u ฺ sa t Gui
Workflow Engine APIs .................................................................................................................................13-21
s t ฺed uden
Workflow Engine Bulk APIs.........................................................................................................................13-28
Summary........................................................................................................................................................13-29
k ac is St
Business Events ................................................................................................................................................14-1
j r i@ e th
Business Events .............................................................................................................................................14-3
a
r a lh o us
Objectives ......................................................................................................................................................14-4
( t
Business Events .............................................................................................................................................14-5
j ri
a
Event Properties.............................................................................................................................................14-6
lh Functions ........................................................................................................................................14-8
Generate
A
d Status for Events ..............................................................................................................................14-10
License
h e
s Defining an Event..........................................................................................................................................14-11
Ra Event Groups .................................................................................................................................................14-12
Defining an Event Group...............................................................................................................................14-13
Maintaining Events........................................................................................................................................14-14
Raising Events ...............................................................................................................................................14-16
Event Message Structure ...............................................................................................................................14-18
Raising an Event Manually............................................................................................................................14-19
Predefined Events ..........................................................................................................................................14-21
Summary........................................................................................................................................................14-22
Event Subscriptions.........................................................................................................................................15-1
Event Subscriptions .......................................................................................................................................15-3
Objectives ......................................................................................................................................................15-4
Event Subscriptions .......................................................................................................................................15-5
Event Manager Subscription Processing .......................................................................................................15-6
Local Event Subscription Processing ............................................................................................................15-7
External Event Subscription Processing ........................................................................................................15-9
Subscription Properties..................................................................................................................................15-10
Subscription Actions......................................................................................................................................15-14
Subscription Actions: Sending an Event to a Workflow Process ..................................................................15-15
Subscription Actions: Sending an Event to an Agent....................................................................................15-17

v
Subscription Actions: Sending a Notification................................................................................................15-19
Subscription Actions: Sending and Receiving Oracle XML Gateway Messages..........................................15-21
Subscription Actions: Invoking a Web Service .............................................................................................15-22
Subscription Actions: Running a Custom Rule Function ..............................................................................15-23
Subscription Properties..................................................................................................................................15-25
License Status for Subscriptions....................................................................................................................15-28
Deferred Subscription Processing..................................................................................................................15-29
PL/SQL and Java Subscription Processing....................................................................................................15-31

Defining a Subscription .................................................................................................................................15-33
Maintaining Subscriptions .............................................................................................................................15-35
Predefined Subscriptions ...............................................................................................................................15-36
Summary........................................................................................................................................................15-37
Systems and Agents .........................................................................................................................................16-1
Systems and Agents.......................................................................................................................................16-3
Objectives ......................................................................................................................................................16-4
Systems..........................................................................................................................................................16-5
nse
System Properties ..........................................................................................................................................16-6
Local System .................................................................................................................................................16-7 li c e
bl
External Systems ...........................................................................................................................................16-8
e
fe r a
Defining a System .........................................................................................................................................16-9
n s
Maintaining Systems .....................................................................................................................................16-10
a
no n-tr
Agents............................................................................................................................................................16-12
Standard Agents.............................................................................................................................................16-14
a
Agent Properties ............................................................................................................................................16-16
) h as deฺ
Custom Queue Handlers ................................................................................................................................16-21
u ฺ sa t Gui
Agents on External Systems ..........................................................................................................................16-22
Defining an Agent .........................................................................................................................................16-24
s t ฺed uden
Agent Groups.................................................................................................................................................16-26
k ac is St
Defining an Agent Group ..............................................................................................................................16-27
Maintaining Agents .......................................................................................................................................16-28
j ri@ e th
External System Registration ........................................................................................................................16-29
a
r a lh o us
Summary........................................................................................................................................................16-30
i ( t
Defining EventrActivities.................................................................................................................................17-1
j
a
lh ......................................................................................................................................................17-4
Defining Event Activities ..............................................................................................................................17-3
A
Objectives
shedEvent Activities .............................................................................................................................................17-5

Ra Event-Based Workflow Processes .................................................................................................................17-6
Event Activity Actions ..................................................................................................................................17-7
Receive Event Activities ...............................................................................................................................17-8
Receive Event Activities: Event Filter..........................................................................................................17-9
Receive Event Activities: Sending an Event to One Process........................................................................17-10
Receive Event Activities: Sending an Event to Multiple Processes .............................................................17-12
Receive Event Activities: Receiving an Event ..............................................................................................17-13
Raise Event Activities ...................................................................................................................................17-15
Send Event Activities ....................................................................................................................................17-16
Defining an Event Activity............................................................................................................................17-17
Event Details .................................................................................................................................................17-19
Defining Event Details: Receive ...................................................................................................................17-20
Defining Event Details: Raise .......................................................................................................................17-21
Defining Event Details: Send ........................................................................................................................17-23
Example: Order Processing ...........................................................................................................................17-25
Standard Activities ........................................................................................................................................17-26
Summary........................................................................................................................................................17-27
Business Event System APIs ...........................................................................................................................18-1
Business Event System APIs .........................................................................................................................18-3

vi
Objectives ......................................................................................................................................................18-4
Business Event System datatypes ..................................................................................................................18-5
Event Message Structure ...............................................................................................................................18-6
Agent Structure..............................................................................................................................................18-10
Parameter List Structure ................................................................................................................................18-12
Parameter Structure .......................................................................................................................................18-13
Raising Events Programmatically..................................................................................................................18-15
Event Data Generate Functions .....................................................................................................................18-21

Standard API for PL/SQL Event Data Generate Functions...........................................................................18-22
Standard API for Java Event Data Generate Functions .................................................................................18-23
Queue Handlers .............................................................................................................................................18-26
Standard APIs for PL/SQL Queue Handlers .................................................................................................18-27
Standard APIs for Java Queue Handlers........................................................................................................18-28
Subscription Rule Functions..........................................................................................................................18-30
Standard API for PL/SQL Subscription Rule Functions ...............................................................................18-31
Standard API for Java Subscription Rule Functions......................................................................................18-33
Predefined Subscription Rule Functions........................................................................................................18-35 nse
Event APIs.....................................................................................................................................................18-37
li c e
bl
Event Function APIs......................................................................................................................................18-39 e
Adding a Correlation ID to an Event Message ..............................................................................................18-40
fe r a
a n s
Business Event System Cleanup API ............................................................................................................18-42
n-tr
Summary........................................................................................................................................................18-43
a no
Error Handling ................................................................................................................................................19-1
Error Handling...............................................................................................................................................19-3
) h as deฺ
Objectives ......................................................................................................................................................19-4
u ฺ sa t Gui
Error Handling for Workflow Processes .......................................................................................................19-5
Default Error Process.....................................................................................................................................19-7
s t ฺed uden
Retry-only Process.........................................................................................................................................19-9
k ac is St
Error Handling for Subscription Processing ..................................................................................................19-11
Stop and Rollback Error Handling ................................................................................................................19-13
j ri@ e th
Skip to Next Error Handling..........................................................................................................................19-15
a
r a lh o us
Standard Error Agents ...................................................................................................................................19-17
j ri ( t
Error Handling Subscriptions ........................................................................................................................19-18
Warning Conditions in Subscription Processing ...........................................................................................19-19
lh a
Unexpected Events ........................................................................................................................................19-20
d A
Default Event Error Process ..........................................................................................................................19-21
she Event Warnings .............................................................................................................................................19-22
Ra External Event Errors ....................................................................................................................................19-23
Local Event Errors.........................................................................................................................................19-25
Default Event Error Process (One Retry Option) ..........................................................................................19-26
Summary........................................................................................................................................................19-27
PL/SQL Documents.........................................................................................................................................20-1
PL/SQL Documents.......................................................................................................................................20-3
Objectives ......................................................................................................................................................20-4
PL/SQL Documents.......................................................................................................................................20-5
Integrating PL/SQL Documents into Workflow Processes ...........................................................................20-6
Including PL/SQL Documents in Messages ..................................................................................................20-8
Standard API for a PL/SQL Document .........................................................................................................20-9
Standard API for a PL/SQL CLOB Document..............................................................................................20-11
Standard API for a PL/SQL BLOB Document..............................................................................................20-13
Summary........................................................................................................................................................20-15
Forced Synchronous Processing .....................................................................................................................21-1
Forced Synchronous Processing ....................................................................................................................21-3
Objectives ......................................................................................................................................................21-4
Forced Synchronous Processes......................................................................................................................21-5

vii
Process Definition Restrictions......................................................................................................................21-6
Summary........................................................................................................................................................21-9
Selector/Callback Functions ...........................................................................................................................22-1
Selector/Callback Functions ..........................................................................................................................22-3
Objectives ......................................................................................................................................................22-4
Item Type Selector/Callback Functions.........................................................................................................22-5
Defining a Selector/Callback Function for an Item Type ..............................................................................22-6
Standard API for a Selector/Callback Function.............................................................................................22-7

Standard API Parameters...............................................................................................................................22-9
Selector/Callback Function Commands.........................................................................................................22-11
Summary........................................................................................................................................................22-13
Master/Detail Coordination Activities ...........................................................................................................23-1
Master/Detail Coordination Activities...........................................................................................................23-3
Objectives ......................................................................................................................................................23-4
Master/Detail Coordination Activities...........................................................................................................23-5
Wait for Flow Activity ..................................................................................................................................23-9 nse
Continue Flow Activity .................................................................................................................................23-11 li c e
bl
Master Process Example................................................................................................................................23-12 e
r a
Detail Process Example .................................................................................................................................23-13
fe
a n s
Continue Flow Processing .............................................................................................................................23-14
n-tr
Summary........................................................................................................................................................23-15
a no
Customizing Workflow Processes ..................................................................................................................24-1
Customizing Workflow Processes .................................................................................................................24-3
) h as deฺ
Objectives ......................................................................................................................................................24-4
u ฺ sa t Gui
Customizing Workflow Processes .................................................................................................................24-5
Access Protection ..........................................................................................................................................24-7
s t ฺed uden
Access Levels ................................................................................................................................................24-8
k ac is St
Setting the Access Level................................................................................................................................24-10
Setting Protection and Customization Levels ................................................................................................24-11
j ri@ e th
Example of Access Protection .......................................................................................................................24-13
a
r a lh o us
Unsupported Customizations.........................................................................................................................24-15
( t
Preserving Customizations ............................................................................................................................24-16
j ri
a
Summary........................................................................................................................................................24-17
lh
A Loaders...........................................................................................................................................25-1
Workflow
d
sh e Workflow Loaders.........................................................................................................................................25-3
Ra Objectives ......................................................................................................................................................25-4
Workflow Definitions Loader........................................................................................................................25-5
Workflow XML Loader.................................................................................................................................25-7
Summary........................................................................................................................................................25-11
Specialized Workflow Monitoring .................................................................................................................26-1
Specialized Workflow Monitoring ................................................................................................................26-3
Objectives ......................................................................................................................................................26-4
Assigning Specialized Workflow Monitoring Privileges ..............................................................................26-5
Granting Restricted Access to Workflow Monitoring Data...........................................................................26-7
Granting Restricted Access Based on Item Types .........................................................................................26-8
Granting Restricted Access Based on Functional Criteria.............................................................................26-10
Granting Permissions for Administrative Actions.........................................................................................26-12
Summary........................................................................................................................................................26-13
Setting Up Oracle Workflow ..........................................................................................................................27-1
Setting Up Oracle Workflow .........................................................................................................................27-3
Objectives ......................................................................................................................................................27-4
Required Setup Steps.....................................................................................................................................27-5
Step 1: Setting Global Workflow Preferences ...............................................................................................27-6
Step 2: Setting Up an Oracle Workflow Directory Service ...........................................................................27-9

viii
Step 3: Running Background Engines ...........................................................................................................27-13
Step 4: Configuring the Business Event System............................................................................................27-16
Step 4: Event Message Communication ........................................................................................................27-17
Step 4: Setting Up Database Links and Queues.............................................................................................27-18
Step 4: Checking Database Parameters .........................................................................................................27-20
Step 4: Scheduling Agent Listeners...............................................................................................................27-21
Step 4: Scheduling Propagation.....................................................................................................................27-24
Step 4: Synchronizing License Statuses ........................................................................................................27-28

Step 4: Cleaning Up the WF_CONTROL Queue..........................................................................................27-29
Optional Setup Steps .....................................................................................................................................27-30
Optional Step 1: Partitioning Workflow Tables ............................................................................................27-32
Optional Step 2: Setting Up Additional Languages.......................................................................................27-34
Optional Step 3: Implementing Notification Mailers ....................................................................................27-36
Optional Step 4: Customizing Message Templates ......................................................................................27-39
Optional Step 5: Adding Worklist Functions to User Responsibilities..........................................................27-42
Optional Step 6: Setting the Notification Reassign Mode .............................................................................27-44
Optional Step 7: Enabling Bulk Notification Response.................................................................................27-45 nse
Optional Step 8: Setting Up Notification Handling Options .........................................................................27-46
li c e
Optional Step 9: Setting Up for Electronic Signatures ..................................................................................27-48
bl e
Optional Step 10: Customizing the Workflow Web Page Logo ....................................................................27-50
fe r a
a n s
Optional Step 11: Adding Custom Icons .......................................................................................................27-51
n-tr
Summary........................................................................................................................................................27-52
a no
Managing Service Components ......................................................................................................................28-1
Managing Service Components.....................................................................................................................28-3
) h as deฺ
Objectives ......................................................................................................................................................28-4
u ฺ sa t Gui
Oracle Workflow Manager ............................................................................................................................28-5
Service Components ......................................................................................................................................28-6
s t ฺed uden
Service Component Containers .....................................................................................................................28-7
k ac is St
Service Component Types.............................................................................................................................28-8
Accessing Service Components in Oracle Workflow Manager.....................................................................28-9
j ri@ e th
Managing Service Components.....................................................................................................................28-10
a
r a lh o us
Service Component Container Logs ..............................................................................................................28-12
j ri ( t
Service Component Startup Modes ...............................................................................................................28-13
Agent Listeners..............................................................................................................................................28-14
lh a
Agent Listener Configuration Wizards..........................................................................................................28-17
d A
Notification Mailers.......................................................................................................................................28-20
sheOutbound Notification Mailer Processing .....................................................................................................28-21
Ra Inbound Notification Mailer Processing........................................................................................................28-23
Notification Mailer Setup ..............................................................................................................................28-25
Connecting to Mail Servers Through SSL.....................................................................................................28-27
Notification Mailer Basic Configuration .......................................................................................................28-28
Notification Mailer Advanced Configuration................................................................................................28-30
Component Details for Notification Mailers .................................................................................................28-37
Notification Mailer Throughput ....................................................................................................................28-39
Handling Notification Mailer Errors..............................................................................................................28-40
Testing Mailer URL Access ..........................................................................................................................28-41
Summary........................................................................................................................................................28-44
Managing System Status and Throughput ....................................................................................................29-1
Managing System Status and Throughput .....................................................................................................29-3
Objectives ......................................................................................................................................................29-4
Workflow System Status ...............................................................................................................................29-5
Workflow Status in Oracle Applications Manager ........................................................................................29-7
Oracle Workflow Administration ..................................................................................................................29-9
Work Items ....................................................................................................................................................29-10
Purging Workflow Data.................................................................................................................................29-16

ix
Completed Work Items..................................................................................................................................29-21
Workflow Purge APIs ...................................................................................................................................29-24
Background Engines......................................................................................................................................29-26
Control Queue Cleanup .................................................................................................................................29-30
Queue Propagation ........................................................................................................................................29-33

Agent Activity ...............................................................................................................................................29-35
Searching Messages on an Agent ..................................................................................................................29-36
Summary........................................................................................................................................................29-37
Student Practices .............................................................................................................................................30-1
Student Practices ...........................................................................................................................................30-3
Lesson 1 - Introduction to Oracle Workflow.................................................................................................30-4
Guided Demonstration - Loading and Running a Workflow Process........................................................30-5
nse
Lesson 2 - Oracle Workflow Components ....................................................................................................30-7
Lesson 3 - Planning a Workflow Process ......................................................................................................30-8 li c e
Practice - Planning a Workflow Process....................................................................................................30-9 bl e
fe
Solution – Planning a Workflow Process ..................................................................................................30-10 r a
n s
Lesson 4 - Diagramming a Workflow Process ..............................................................................................30-11
a
no n-tr
Practice - Creating a Workflow Process ....................................................................................................30-12
Solution – Creating a Workflow Process...................................................................................................30-13
a
Lesson 5 - Defining Item Type Attributes and Lookup Types ......................................................................30-15
) h as deฺ
Practice - Defining Item Type Attributes...................................................................................................30-16
u ฺ sa t Gui
Solution – Defining Item Type Attributes ................................................................................................30-17
Lesson 6 - Defining Messages and Notification Activities............................................................................30-20
s t ฺed uden
Practice - Defining Messages ....................................................................................................................30-21
k ac is St
Solution – Defining Messages ..................................................................................................................30-22
Practice - Defining Notification Activities ................................................................................................30-25
j ri@ e th
Solution – Defining Notification Activities...............................................................................................30-26
a
r a lh o us
Lesson 7 - Testing and Monitoring Workflow Processes ..............................................................................30-28
j ri ( t
Practice - Running a Workflow Process ....................................................................................................30-29
Solution – Running a Workflow Process...................................................................................................30-30
lh a
Lesson 8 - Viewing and Responding to Notifications ...................................................................................30-31
d A
Practice - Responding to Notifications ......................................................................................................30-32
she Solution – Responding to Notifications.....................................................................................................30-33
Ra Practice - Modifying A Workflow Process................................................................................................30-34
Solution – Modifying a Workflow Process ...............................................................................................30-36
Lesson 9 - Worklist Flexfields.......................................................................................................................30-39
Practice - Defining a Specialized Worklist View Using Worklist Flexfields ............................................30-40
Solution – Defining a Specialized Worklist View Using Worklist Flexfields...........................................30-42
Lesson 10 - Oracle Workflow Directory Service ..........................................................................................30-46
Lesson 11 - Defining Function Activities......................................................................................................30-47
Practice - Defining a Function Activity .....................................................................................................30-48
Solution – Defining a Function Activity....................................................................................................30-50
Practice - Branching on a Function Activity Result ..................................................................................30-53
Solution – Branching on a Function Activity Result .................................................................................30-55
Practice - Using the Standard Assign Activity...........................................................................................30-58
Solution – Using the Standard Assign Activity .........................................................................................30-60
Lesson 12 - Post-Notification Functions .......................................................................................................30-66
Practice - Defining a Post-Notification Function.......................................................................................30-67
Solution – Defining a Post-Notification Function .....................................................................................30-68
Lesson 13 - Workflow Engine.......................................................................................................................30-71
Practice - Implementing Timeout Processing ............................................................................................30-72
Solution – Implementing Timeout Processing...........................................................................................30-73

x
Practice - Implementing Deferred Processing ...........................................................................................30-76
Solution – Implementing Deferred Processing ..........................................................................................30-77
Lesson 14 - Business Events..........................................................................................................................30-79
Practice - Defining an Event......................................................................................................................30-80
Solution – Defining an Event.....................................................................................................................30-81
Practice - Raising an Event........................................................................................................................30-83
Solution – Raising an Event ......................................................................................................................30-84
Lesson 15 - Event Subscriptions....................................................................................................................30-86

Practice - Defining a Subscription .............................................................................................................30-87
Solution – Defining a Subscription............................................................................................................30-89
Lesson 16 - Systems and Agents ...................................................................................................................30-94
Lesson 17 - Defining Event Activities...........................................................................................................30-95
Practice - Defining Event Activities ..........................................................................................................30-96
Solution – Defining Event Activities.........................................................................................................30-98
Lesson 18 - Business Event System APIs .....................................................................................................30-106
Lesson 19 - Error Handling ...........................................................................................................................30-107
Guided Demonstration - Error Handling ...................................................................................................30-108 nse
Lesson 20 - PL/SQL Documents ...................................................................................................................30-109
li c e
Practice - Using a PL/SQL Document Attribute........................................................................................30-110
bl e
Solution – Using a PL/SQL Document Attribute ......................................................................................30-112
fe r a
a n s
Lesson 21 - Forced Synchronous Processing.................................................................................................30-115
n-tr
Lesson 22 - Selector/Callback Functions.......................................................................................................30-116
Practice - Defining a Selector Function .....................................................................................................30-117
no
Solution – Defining a Selector Function....................................................................................................30-119
a
h as deฺ
Lesson 23 - Master/Detail Coordination Activities .......................................................................................30-122
Lesson 24 - Customizing Workflow Processes .............................................................................................30-123
)
u ฺ sa t Gui
Lesson 25 - Workflow Loaders .....................................................................................................................30-124
t ฺed uden
Lesson 26 - Specialized Workflow Monitoring.............................................................................................30-125
Guided Demonstration - Setting Up Specialized Workflow Monitoring...................................................30-126
s
ac is St
Lesson 27 - Setting Up Oracle Workflow .....................................................................................................30-129
k
a j ri@ e th
Guided Demonstration - Scheduling Agent Listeners and Propagation ....................................................30-130
Lesson 28 - Managing Service Components .................................................................................................30-132
a lh o us
Guided Demonstration - Service Components ..........................................................................................30-133
r
ri ( t
Lesson 29 - Managing System Status and Throughput..................................................................................30-135
j
lh a
Guided Demonstration - System Status and Throughput...........................................................................30-136
d A Solutions..............................................................................................................................................31-1
Sample
e
sh Sample Solutions ...........................................................................................................................................31-3
Ra Overview .......................................................................................................................................................31-4
Vacation Proposal Process Sketch.................................................................................................................31-5
wfvacxx.html .................................................................................................................................................31-6
wfvacxxc.sql..................................................................................................................................................31-7
wfvacxxs.sql ..................................................................................................................................................31-9
wfvacxxb.sql..................................................................................................................................................31-14
wfvacxxd.sql..................................................................................................................................................31-28
wfslctxx.sql....................................................................................................................................................31-30

xi
Ra
she
d
Alh aj ri ( r a
a j
t
k
lh o us
s
ri@ e th
t
ac is St
u ฺ
)
ฺed uden
h
sa t Gui
a
as deฺ
no
n-tr
a n s
fe r a
e bl
li c e
ens
Preface
Profile
Before You Begin This Course
• Thorough knowledge of Oracle Database and Oracle Application Server technology
• Thorough knowledge of Oracle E-Business Suite
Prerequisites
• Oracle Database: Introduction to SQL

nse
li c e
• Oracle Database: Program with PL/SQL
ble
fe r a
How This Course Is Organized
a n s
no
R12.x Implement Oracle Workflow is an instructor-led course featuring lecture and hands-on n-tr
a
exercises. Online demonstrations and written practice sessions reinforce the concepts and skills
introduced.
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

xiii
Related Publications
Oracle Publications
Title Part Number
Oracle Workflow Administrator's Guide E12903

Oracle Workflow Developer's Guide E12905
Oracle Workflow User's Guide E12906
Oracle Workflow API Reference E12904
Oracle Workflow Client Installation Guide E12779
Additional Publications nse

li c e
• System release bulletins ble
fe r a
Installation and user’s guides a n s
n-tr
•
• Read-me files a no
) h as deฺ
• International Oracle User’s Group (IOUG)aarticles ui
d u ฺs t G
• Oracle Magazine s t ฺe uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

xiv
Typographic Conventions
Typographic Conventions in Text
Convention Element Example
Bold italic Glossary term (if The algorithm inserts the new key.
there is a glossary)
Caps and Buttons, Click the Executable button.
lowercase check boxes, Select the Can’t Delete Card check box.
triggers, Assign a When-Validate-Item trigger to the ORD block.
windows Open the Master Schedule window.
Courier new, Code output, Code output: debug.set (‘I”, 300);
case sensitive directory names, Directory: bin (DOS), $FMHOME (UNIX)
nse
(default is filenames, Filename: Locate the init.ora file.
li c e
lowercase) passwords, e
pathnames,
Password: User tiger as your password.
Pathname: Open c:\my_docs\projects r a bl
URLs, URL: Go to http://www.oracle.com n sfe
a
n-tr
user input,
User input: Enter 300
usernames
Username: Log on as scott
a no
Initial cap Graphics labels
(unless the term is a as deฺ
Customer address (but Oracle Payables)
) h
proper noun)
u ฺ sa t Gui
Italic Emphasized words Do note
t d changes
ฺ save ento the database.
and phrases, s
For
c further u d
information,
t see Oracle7 Server SQL Language
titles of books and kaReference s SManual.
courses, jri@ t h
Enter
[email protected], where user_id is the
h a s e
Quotation i ( r al elements
variables
Interface t o u name of the user.
Select “Include a reusable module component” and click Finish.
r
marks haj with long names
A l that have only This subject is covered in Unit II, Lesson 3, “Working with
e d
sh initial caps; Objects.”
Ra lesson and chapter
titles in cross-
references
Uppercase SQL column Use the SELECT command to view information stored in the
names, commands, LAST_NAME
functions, schemas, column of the EMP table.
table names
Arrow Menu paths Select File > Save.
Brackets Key names Press [Enter].
Commas Key sequences Press and release keys one at a time:
[Alternate], [F], [D]
Plus signs Key combinations Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]

xv
Typographic Conventions in Code
Convention Element Example
Caps and Oracle Forms When-Validate-Item
lowercase triggers
Lowercase Column names, SELECT last_name
table names FROM s_emp;
Passwords DROP USER scott

IDENTIFIED BY tiger;
PL/SQL objects OG_ACTIVATE_LAYER
(OG_GET_LAYER (‘prod_pie_layer’))
Lowercase Syntax variables CREATE ROLE role

nse
italic
li c e
Uppercase SQL commands and SELECT userid
ble
functions FROM emp;
fe r a
a n s
Typographic Conventions in Oracle Application Navigation
o n -tr Paths
This course uses simplified navigation paths, such as the following a nexample, to direct you
through Oracle Applications. ) h as deฺ
u ฺ sa t Gui
(N) Invoice > Entry > Invoice Batches Summary
s t ฺed(M)uQuery
d en> Find (B) Approve
ac is St
This simplified path translates to thekfollowing:
a j ri@ e th
lh owindow,
1. (N) From the Navigator
a u s select Invoice then Entry then Invoice Batches
Summary. ri ( r t
a j
2.d A
lh
(M) From the menu, select Query then Find.
she
Ra 3. (B) Click the Approve button.
Notations:
(N) = Navigator
(M) = Menu
(T) = Tab
(B) = Button
(I) = Icon
(H) = Hyperlink
(ST) = Sub Tab

xvi
Typographical Conventions in Oracle Application Help System Paths
This course uses a “navigation path” convention to represent actions you perform to find
pertinent information in the Oracle Applications Help System.
The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals
—represents the following sequence of actions:
1. In the navigation frame of the help system window, expand the General Ledger entry.
2. Under the General Ledger entry, expand Journals.

nse
3. Under Journals, select Enter Journals. li c e
a b le
4. Review the Enter Journals topic that appears in the document frame of the helpf r
esystem
window. an s
- t r
n on
s a
) h a d e ฺ
ฺ sa t Gu i
u
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
a
d Alh
e
R ash

xvii
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

xviii
nse
li c e
ble
fe r a
a n s
o Oracle n-tr
Introduction
a nto
a) Guid has eฺ
Workflow
ฺ s
uChaptern1t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
A lha
d
she
Ra
Introduction to Oracle Workflow

Chapter 1 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 4
Enabling E-Business
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 5
Inter-Enterprise Business Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Inter-Enterprise Business Processes
e
sh In e-business, different enterprises need to communicate with each other over the Internet.
Ra Oracle Workflow with the Business Event System can be used as part of an integration hub,
modeling business processes that span all of the enterprises involved in an end-to-end process.

Chapter 1 - Page 6
Traditional Workflow
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Traditional Workflow
e
sh Traditional applications-based workflow processes are launched from a business application
Ra through APIs hard-coded within the application. These processes model the business rules in
the individual local application and are made up of activities executed by the Workflow Engine
only in that application’s system. For example, the modeling of an approval hierarchy is a
common use of Oracle Workflow in this scenario.

Chapter 1 - Page 7
Workflow-Driven Business Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Oracle Workflow can help save time by:
Ra • Reducing repetitive data entry tasks
• Automating approval hierarchies
• Automatically delivering notifications and reminders of work to be done
• Providing self-service monitoring capabilities

Chapter 1 - Page 8
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 9
Sample Workflow Process
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Process
Sample
d
e
sh A workflow process consists of a sequence of activities that together make up a business flow,
Ra expressing your organization’s policies and rules. The activities can include significant
business events, automated functions, notifications to users, or subprocesses.
This example shows a sample order processing workflow process that includes business events.

Chapter 1 - Page 10
Event-Based Workflow
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Event-Based Workflow
e
sh With the Business Event System, Oracle Workflow supports both traditional applications-
Ra based workflows and event-based integration workflows.
For e-business, there is a requirement to integrate with external systems, such as sending a
document to a business-to-business exchange, or other systems external to the local
application. Oracle Workflow supports e-business integration workflows by allowing business
analysts and developers to model business processes spanning different systems using a
graphical drag-and-drop designer - the Workflow Builder - and run those processes using the
Workflow Engine and the Business Event System. This support enables Oracle Workflow
customers to deal with business objects in comprehensive e-business integration flows with
minimal intrusion into the core application.
The Business Event System and the Workflow Engine can function independently of each
other. However, you can achieve the most powerful and flexible processing by using the
Business Event System and the Workflow Engine together to execute cross-system processes
for e-business integration.

Chapter 1 - Page 11
Subscription-Based Processing
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Subscription-Based Processing
e
sh The Business Event System provides increased flexibility through subscription-based
Ra processing: you raise a business event from an application, but specify the processing to
perform for that event as a subscription in Oracle Workflow. For example, you can launch a
workflow process when an event is raised by specifying that process in a subscription to the
event. You can also define multiple subscriptions to the same event to perform additional
processing for different purposes without intruding any further on the core application.

Chapter 1 - Page 12
System Integration with Oracle Workflow
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 13
Business Process-Based Integration
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Process-Based Integration
Business
d
e
sh Business process-based integration is model-driven.
Ra • Business rules are expressed in a process model.
• These rules define the policy for each end-to-end process.
• The process model can encompass applications both within and beyond the enterprise.
Business process-based integration provides:
• A global, enterprise-level view of business objects
• Business process automation
Oracle Workflow supports business process-based integration through the Business Event
System.

Chapter 1 - Page 14
Supported System Integration Types
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A System Integration Types
Supported
d
e
sh The types of system integration supported by Oracle Workflow are message-based. By
Ra supporting the communication of messages between systems, Oracle Workflow lets you define
processing across different systems encompassing both your own enterprise and your business
partners. The power of this cross-system processing, together with the flexibility provided by
subscription-based processing, enables you to use Oracle Workflow for e-business integration.

Chapter 1 - Page 15
Designing Applications for Change
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Applications for Change
Designing
d
e
sh The benefits of good design include:
Ra • Reduced cost of ownership through diminished development costs
• Ease of management and maintenance
• Visual documentation of business processes

Chapter 1 - Page 16
Designing Applications for Change
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Business Processes for Change
Designing
d
e
sh Complete process representation:
Ra • A workflow process can cross organizational and company boundaries to represent an
end-to-end flow.
• You can provide alternatives within a process to accommodate different situations.
• You can build management metrics and performance goals into a process.
Graphical development tool:
• The Oracle Workflow Builder separates business process definition and modeling from
code development.
• Workflow diagrams provide a visual overview of your processes.
• You can easily modify a process definition.
Ease of management and maintenance:
• Oracle Workflow lets you analyze time and costs for entire business processes.
• You can refine your process definitions according to your analysis to streamline them and
reduce time and costs.
• You can easily implement a modified process.

Chapter 1 - Page 17
• Oracle Workflow empowers process participants by giving them access to review the
progress and current status of their processes.
• Users can find the answers to many common questions themselves using these monitoring
capabilities.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 18
Designing Applications for Integration
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 19
Designing Applications for Integration
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Applications for Integration
Designing
d
e
sh Business events as integration points:
Ra • Applications can raise business events at any point where further processing or integration
might be required.
• You can define the processing to be triggered by an event immediately after defining the
event or at any later time.
Subscription-based processing:
• Use subscriptions to specify the processing you want to perform for a business event.
• You can define multiple subscriptions to the same event to perform additional processing
for different purposes.
Web-based business event and subscription management tool:
• The Event Manager separates event subscription definition from code development.
• You can use the Event Manager web pages to define, update, or delete event subscriptions
without intruding on the core application.

Chapter 1 - Page 20
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 21
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 1 - Page 22
nse
li c e
ble
fe r a
a n s
no n-tr
Oracle Workflow
a
has eฺ
Components
a) Guid
ฺ s
uChaptern2t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
Alha
d
she
Ra
Oracle Workflow Components

Chapter 2 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 4
Oracle Workflow Architecture
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Architecture
Oracle
d
e
sh Development Client
Ra The development client is a Windows PC. This tier is used to create and modify Oracle
Workflow process definitions, and to save and load flat files containing Oracle Workflow
process definitions and XML definitions for Business Event System objects.

Chapter 2 - Page 5
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Oracle
d
e
sh Oracle Database
Ra The server tier is the Oracle Database that hosts the business application integrated with Oracle
Workflow, the Workflow Engine, Business Event System, Notification System, and directory
service. The Business Event System leverages the Advanced Queuing feature within the Oracle
Database.

Chapter 2 - Page 6
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Oracle
d
e
sh Application Server
Ra The application server is the middle tier environment outside of the database. This environment
includes ancillary services such as Oracle HTTP Server as the Web server, and Oracle
Workflow service components that run in the middle tier, such as agent listeners and
notification mailers.

Chapter 2 - Page 7
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Oracle
d
e
sh End-User Client
Ra The end-user client is the workstation or PC that an end user uses to perform daily tasks. This
client includes browser support for accessing Oracle Workflow Web pages, as well as for
accessing the Oracle Workflow Manager component available through Oracle Applications
Manager (OAM). The end-user client also includes a mail client application for reviewing and
responding to notifications by e-mail.

Chapter 2 - Page 8
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 9
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 10
Workflow Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Processes
Workflow
d
e
sh A workflow process definition must be saved to the same database as the Workflow Engine. A
Ra process definition is composed of activities and the transitions between them.
• A completed application transaction or event can initiate a workflow process by raising an
event or by calling a series of Workflow Engine APIs.
• The Workflow Engine locates the “Start” activity in the process definition.
• The Workflow Engine drives through the process, performing all automated steps such as
function activities and Raise and Send event activities, until an asynchronous activity such
as a notification, Receive event activity, or blocking activity occurs.
- The Workflow Engine calls the Notification System to deliver a notification message
to an appropriate role. Once a user of that role completes the notification response,
the Workflow Engine continues to drive through the remaining activities in the
process.
- If a blocking activity is encountered, the Workflow Engine waits for an external
program to complete and call the appropriate Workflow Engine API before
proceeding to the next activity.

Chapter 2 - Page 11
- If a Receive event activity is encountered, the Workflow Engine waits to receive the
event from the Business Event System before proceeding to the next activity.
• The process completes when the Workflow Engine encounters an “End” activity.
Example: Order Processing
This example shows a workflow process that includes business events.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 12
Supported Process Constructs
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Process Constructs
Supported
d
e
sh The Workflow Engine supports sophisticated workflow rules to model your business logic.
Ra

Chapter 2 - Page 13
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 14
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 15
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 16
Oracle Workflow Builder
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Builder
Oracle
d
e
sh Saving workflow definitions as flat files on the local file system enables designers to back up
Ra their work and use source control.
Navigator Tree
The navigator provides a tree structure for the workflow definition, with the highest level being
the data store. Next is the item type, which is a grouping of workflow objects into a high-level
category. The lower levels are the workflow objects themselves, such as attributes, processes,
notifications, functions, events, messages, and lookup types. All these objects are organized
into their respective categories within the tree.
Process Diagram
The diagram is made up of icons representing workflow objects. A diagram is built by
dragging the objects from the navigator window and dropping them into the process diagram
window. This method is called bottom-up design. You can also create new objects as you
design the diagram and complete the definitions of those objects later. This method is called
top-down design.

Chapter 2 - Page 17
Business Event System Architecture
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Event System Architecture
Business
d
e
sh The Business Event System is an application service that communicates business events
Ra between systems. Oracle Workflow with the Business Event System can act as a system
integration messaging hub that relays business event messages among systems.
The Business Event System leverages Oracle Advanced Queuing to send messages from one
system to another.
For the greatest flexibility in routing and processing business events, you can model your
business process logic in powerful cross-system workflow processes that are executed by the
Workflow Engine. However, the Business Event System can also function independently of the
Workflow Engine.

Chapter 2 - Page 18
Business Event System Components
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 19
Advanced Queuing, an Enabling Technology
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Queuing, an Enabling Technology
Advanced
d
e
sh Oracle Advanced Queuing allows queue-to-queue propagation across machine boundaries.
Ra Oracle Advanced Queuing is a feature of the Oracle Database that provides database-integrated
message queuing functionality, leveraging the functions of the Oracle Database to store
messages persistently and transmit them using various transport protocols.
Java Message Service (JMS) is a messaging standard defined by Sun Microsystems, Oracle,
IBM, and other vendors. Oracle Java Message Service (OJMS) provides a Java API for Oracle
Advanced Queuing based on the JMS standard. Oracle Workflow supports communication of
JMS Text messages through Oracle Advanced Queuing in a format called
SYS.AQ$_JMS_TEXT_MESSAGE.
Oracle Workflow also supports business event messages in a standard Workflow format called
WF_EVENT_T. You can additionally define custom message formats.
For more information, refer to the Oracle Streams Advanced Queuing User’s Guide and
Reference.

Chapter 2 - Page 20
Oracle Database Communication Alternatives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Database Communication Alternatives
Oracle
d
e
sh You can use Oracle Advanced Queuing for communication by SQLNET, HTTP, and HTTPS
Ra protocols, and for integration with third-party messaging solutions.
You can use Oracle Net Services (formerly Net8) to propagate messages by the SQLNET
protocol. Oracle Workflow supports JMS Text messages for SQLNET propagation, as well as
business event messages in a standard Workflow format called WF_EVENT_T. You can also
define custom message formats.
The Oracle Streams Advanced Queuing Internet access functionality lets you perform Oracle
Advanced Queuing operations over the Internet by using the Oracle Advanced Queuing
Internet Data Access Presentation (IDAP) for messages and transmitting the messages over the
Internet using transport protocols such as HTTP or HTTPS.
Messaging Gateway is a feature of Oracle Advanced Queuing that enables communication
between applications based on non-Oracle messaging systems and Oracle Advanced Queuing.
Standard Oracle Advanced Queuing functionality provides propagation between two Oracle
Advanced Queuing queues; Messaging Gateway extends that propagation to legacy
applications based on non-Oracle messaging systems.

Chapter 2 - Page 21
For more information, refer to the Oracle Streams Advanced Queuing User’s Guide and
Reference.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 22
Accessing Oracle Workflow Web Pages
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 23
Oracle Workflow Home Pages
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Home Pages
Oracle
d
e
sh • Administrator home page: Lists your five highest priority notifications. Also provides tabs
Ra to the Developer Studio, Event Manager (Business Events), administrator Status Monitor,
Advanced Worklist, and Administration pages.
• Self-service home page: Lists your five highest priority notifications as well as the five
most recent workflows that you own that were started in the last two weeks. Also provides
tabs to the Advanced Worklist and self-service Status Monitor.

Chapter 2 - Page 24
Notification System
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Notification System
e
sh The Notification System:
Ra • Routes notifications to a role, which can be a single user or group of users
• Enables users to receive and respond to notifications using an e-mail application or Web
browser of choice
• Sends e-mail notifications and processes e-mail responses using the JavaMail API
• Allows any users with access to the Internet to be included in a workflow process
• Provides access to the Worklist from Oracle E-Business Suite through the Worklist web
pages
• Enables users to drill down from a notification in the Worklist web pages to any URL or
Oracle E-Business Suite form to respond to the notification

Chapter 2 - Page 25
Worklist Web Pages
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Web Pages
Worklist
d
e
sh Oracle Workflow includes two different versions of the Worklist:
Ra • Advanced Worklist: Provides full notification information as well as additional options for
displaying and administering notifications
• Personal Worklist: Provides additional search and filtering options for displaying
notifications

Chapter 2 - Page 26
E-Mail Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 27
Directory Services
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Services
Directory
d
e
sh Users can be associated with more than one role, and a role may contain more than one user.
Ra The Workflow Engine and Notification System use the directory service to determine who
should receive notifications and in what format. Notifications can be delivered to an individual
user or to all members of a particular role.
Note: Oracle Workflow uses a directory service model in which denormalized information is
maintained in the Workflow local tables for performance gain. You should maintain
synchronization between the user and role information stored in application tables by the
source modules and the information stored in the Workflow local tables.

Chapter 2 - Page 28
Status Monitor Web Pages
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Monitor
Workflow
d
e
sh Oracle Workflow includes both administrator and self-service versions of the Status Monitor in
Ra the Oracle Application Framework user interface format.

Chapter 2 - Page 29
Workflow Definitions Loader
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Definitions
Loading
d
e
sh The Workflow Definitions Loader is a utility program that lets you transfer process definitions
Ra between a database and a flat file. The Workflow Definitions Loader:
• Runs on the server machine.
• Lets you upgrade a database with new versions of process definitions or upload existing
process definitions after a database upgrade.
• Is also integrated into Oracle Workflow Builder.
• Allows process definitions to be source-controlled as flat files.

Chapter 2 - Page 30
Workflow XML Loader
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A XML Loader
Workflow
d
e
sh The Workflow XML Loader is a utility program that lets you transfer XML definitions for
Ra Business Event System objects between a database and a flat file.
• When you download Business Event System object definitions from a database, Oracle
Workflow saves the definitions as an XML file.
• When you upload object definitions to a database, Oracle Workflow loads the definitions
from the source XML file into the Business Event System tables in the database, creating
new definitions or updating existing definitions as necessary.

Chapter 2 - Page 31
Workflow Manager
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Manager
Workflow
d
e
sh Administrators can use Workflow Manager to perform the following tasks:
Ra • Run Workflow service components, such as notification mailers and agent listeners.
• Control other Workflow system services, including background engines, purging obsolete
Workflow data, and cleanup of the Workflow control queue.
• Monitor work item processing by viewing the distribution of all work items by status and
drilling down to additional information.
• Monitor event message processing for local Business Event System agents by viewing the
distribution of event messages by status and drilling down to additional agent information
and individual event messages, as well as by viewing queue propagation details.
With this ability to monitor work items and event messages, a system administrator can
identify possible bottlenecks easily.

Chapter 2 - Page 32
Service Components
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Components
Service
d
e
sh Oracle Workflow uses the Generic Service Component Framework (GSCF) to simplify and
Ra automate the management of background Java services. A service component is an instance of
a Java program that has been defined according to the GSCF standards so that it can be
managed through this framework.
Use Oracle Workflow Manager to configure and run service components.
Note: Oracle Workflow Manager also lets you manage Web services outbound components,
which process outbound Web service messages for Oracle XML Gateway. For more
information, see the Oracle XML Gateway User’s Guide.

Chapter 2 - Page 33
Oracle Workflow Documentation
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Documentation
Oracle
d
e
sh The main Oracle Workflow documentation set includes the following:
Ra • Oracle Workflow Administrator’s Guide: Explains how to complete the setup steps
necessary for any product that includes Workflow-enabled processes, as well as how to
monitor the progress of run-time workflow processes.
• Oracle Workflow Developer’s Guide: Explains how to define new workflow business
processes and customize existing Oracle E-Business Suite-embedded workflow processes.
It also describes how to define and customize business events and event subscriptions.
• Oracle Workflow User’s Guide: Describes how users can view and respond to workflow
notifications and monitor the progress of their workflow processes.
• Oracle Workflow API Reference: Describes the APIs provided for developers and
administrators to access Oracle Workflow.
• Oracle Workflow Client Installation Guide: Describes how to install the Oracle Workflow
Builder and Oracle XML Gateway Message Designer client components for Oracle E-
Business Suite.

Chapter 2 - Page 34
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 35
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 2 - Page 36
nse
li c e
ble
fe r a
a n s
no n-tr
Planning aaWorkflow Process
) h as deฺ
Chapter 3
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
Planning a Workflow Process

Chapter 3 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 4
Workflow Process Components
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Process Components
Workflow
d
e
sh • Data Store: A database connection or flat file that holds a workflow process definition.
Ra • Item Type: A grouping of workflow components into a high level category. All
components of a workflow process must be associated with a specific item type. An item
type can contain multiple processes.
• Item Type Attribute: A feature of the item type which stores information that can be
globally referenced by any activity in a process. Also referred to as an item attribute.
• Process Activity: A series of actions that need to be performed to accomplish a business
goal. A process is represented by a workflow diagram. A process can include function
activities, notification activities, event activities, and other process activities
(subprocesses), as well as the transitions between these activities.
• Event Activity: A business event modeled as an activity so that it can be included in a
workflow process.
• Notification Activity: A unit of work that requires human intervention. A notification
activity sends a message to a performer.
• Function Activity: An automated unit of work, usually defined as a PL/SQL stored
procedure. A function activity can also run an external function.

Chapter 3 - Page 5
• Message: The information sent by a notification activity. The message may request the
performer (the role receiving the message) to do some work or may simply provide
information.
• Lookup Type: A list of values that can be referenced by any activity in a workflow
process. The values in the list are called lookup codes.
• Transition: The relationship that defines the completion of one activity and the activation
of another activity within a process. In a process diagram, a transition is represented as an

arrow between two activities.
• Item: A specific business document or transaction.
• Process Instance: A unique item being managed by a process.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 6
Oracle Workflow Builder
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Builder
Oracle
d
e
sh In the navigator tree, each item type includes the following branches:
Ra • Attributes
• Processes (Subprocesses)
• Notifications
• Functions
• Events
• Messages
• Lookup Types

Chapter 3 - Page 7
Standard Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activities
Standard
d
e
sh The Standard item type is automatically installed on your Oracle Workflow server.You can
Ra also access the Standard item type from the file wfstd.wft located in your Oracle Workflow
Builder client installation in the \<ORACLE_HOME>\wf\DATA\<language>\ subdirectory.
The standard activities provided by Oracle Workflow include:
• And
• Or
• Compare Date
• Compare Number
• Compare Text
• Compare Execution Time
• Wait
• Block
• Defer Thread
• Launch Process

Chapter 3 - Page 8
• Noop
• Loop Counter
• Start
• End
• Role Resolution
• Notify
• Vote Yes/No
• Continue Flow
• Wait for Flow
• Assign
• Get Monitor URL
• Get Event Property nse
li c e
• Set Event Property e
• Compare Event Property r a bl
For a full explanation of these standard activities, see: Predefined Workflow Activities, Oraclen sfe
a
Workflow Developer’s Guide.
no n-tr
Note a
h as deฺ
If you are using Oracle XML Gateway, you can also use standard activities supporting XML
)
u ฺ sa t Gui
messaging that are provided in the XML Gateway Standard item type. For more information,
XML Gateway User’s Guide. s t ฺed uden

see: Integrating Oracle XML Gateway with Oracle Workflow Business Event System, Oracle
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 9
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Workflow Process
Planning
d
e
sh Consider modeling your process so that it can be customized and extended in the future.
Ra

Chapter 3 - Page 10
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Planning
d
e
sh If the process will begin with a Receive event activity, the calling application must raise an
Ra event, either with the WF_EVENT.Raise API or with a Raise event activity in another
workflow process. The event must trigger a subscription that sends the event message to the
workflow process that has the Receive event activity, which must be marked as a Start activity
node.
If the process will begin with a standard Start function activity, the activity must be marked as
a Start activity node, and the application must execute a procedure that calls the appropriate
Workflow Engine APIs, either WF_ENGINE.CreateProcess and WF_ENGINE.StartProcess,
or WF_ENGINE.LaunchProcess, which is a wrapper combining the CreateProcess and
StartProcess APIs. You can use WF_ENGINE.LaunchProcess if you do not need to set any
other values such as item attribute values in between creating and starting the process. If you
are starting several processes at once, your application can call
WF_ENGINE_BULK.CreateProcess and WF_ENGINE_BULK.StartProcess or
WF_ENGINE_BULK.FastForward to launch multiple processes in bulk.
Note: Using the standard Start function activity lets you visually represent the start of the
process in your diagram. Alternatively, you can choose to start the process with another

Chapter 3 - Page 11
function, notification, or process activity. In all cases, however, the activity must be marked as
a Start activity node.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 12
Activity Results and Lookup Types
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Results and Lookup Types
Activity
d
e
sh Process Activities
Ra The diagram for a process activity can include functions, notifications, events, and other
processes.
A process activity can be completed with a specific result that is defined in a lookup type. For
example, the sample process in the diagram above can be completed with a final result of
Accepted (A) or Declined (D), both of which would be codes defined in a lookup type.
Function Activities
The PL/SQL procedure for a function activity can return some result that determines the next
transition the Workflow Engine takes. That result should be defined as a code in a lookup type.
For example, the function activity in the diagram can be completed with a result of True (T) or
False (F), which are defined in the standard Boolean lookup type in the Standard item type.
Notification Activities
The message sent by a notification activity can simply convey information or it can require a
response.

Chapter 3 - Page 13
• If the message only provides information (such as a “For Your Information” (FYI)
message), then create and include “Send” message attributes in the message as necessary.
• If the message requires a response, then create “Send” message attributes that provide
enough information for the recipient to respond, and also create “Respond” message
attributes that prompt a response. For example, the response-required notification activity
in the diagram requests responses for two pieces of information called Resp 1 and Resp 2.
• If a particular response defines the actual result of the notification activity, then complete
the Result tab for the message. The information you enter creates a special “Respond”
message attribute that has an internal name of “RESULT”. The “RESULT” attribute has a
data type of lookup and must reference a lookup type that defines the possible result codes
and matches the result type for the notification activity. For example, the response-
required notification activity in the diagram requires a RESULT response which must be
either Yes (Y) or No (N). These codes are defined in the standard Yes/No lookup type in e
the Standard item type.
c e ns
Event Activities e li
An event activity can either receive, raise, or send a business event from the Business Event r a bl
System. An event activity does not have a result, but you can branch on the contents of an n sfe
a
event message using comparison activities provided in the Standard item type.
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 14
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 15
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 3 - Page 16
nse
li c e
ble
fe r a
a n s
noa Workflow n-tr
Diagramming
a
a) Guid has eฺ
Process
ฺ s
uChaptern4t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
Alha
d
she
Ra
Diagramming a Workflow Process

Chapter 4 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 4
Creating a New Workflow Process
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 5
Creating a New Process from Top Down
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 6
Creating a New Process from Bottom Up
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 7
Diagramming a Process
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 8
Quick Start Wizard
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Start Wizard
Quick
d
e
sh New Item Type Properties
Ra • Internal Name: Specify an all uppercase internal name with a maximum of eight
characters. Do not include colons or leading or trailing spaces.
• Display Name: Enter a translatable display name for the item type.
• Persistence Type: Specify Temporary or Permanent persistence for the status audit trail of
the item type. The persistence type controls when the run-time process status information
is eligible for purging after the process is complete. If the persistence type is Permanent,
the run-time status information is maintained indefinitely until it is specifically purged; if
it is Temporary, the run-time status information is maintained for a specified number of
days after the workflow completion date before it can be purged.
• Number of Days: If the persistence type is Temporary, specify the number of days from
the time an item type instance completes before its status audit trail can be purged.
New Process Properties
• Internal Name: Specify an all uppercase internal name. Do not include colons or leading
or trailing spaces.

Chapter 4 - Page 9
• Display Name: Enter a translatable display name for the process activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 10
Quick Start Wizard
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 11
Defining an Item Type
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A an Item Type
Defining
d
e
sh To define an item type:
Ra 1. Select a data store in the navigator tree, or create a new data store by choosing New from
the File menu.
2. Create a new item type by selecting New > Item Type from the Edit menu.
3. On the Item Type property page, enter an all uppercase internal name with a maximum of
eight characters. Do not include colons or leading or trailing spaces.
4. Enter a translatable display name for the item type.
5. Enter a description of the item type.
6. Specify Temporary or Permanent persistence for the status audit trail of the item type.
The persistence type controls when the run-time process status information is eligible for
purging after the process is complete.
7. If the persistence type is Temporary, specify the number of days from the time an item
type instance completes before its status audit trail can be purged.
8. Optionally enter the name of a selector/callback function for the item type.

Chapter 4 - Page 12
- The item type selector/callback function is a PL/SQL procedure that the Workflow
Engine can call to reset or test context information for an item type before executing
an activity.
- An item type can have multiple workflow processes associated with it. If it does, the
selector/callback function can also identify the appropriate process to run.
- Associating a selector/callback function with an item type makes the item type better
suited to future customizations.

9. Choose Apply to save your changes.
10. Optionally select the Access tab to set the access levels allowed to modify this item type.
Example
For an example workflow item type, see the Requisition demonstration workflow
(wfdemo.wft), located in the \<ORACLE_HOME>\wf\DATA\<language> directory in your
Oracle Workflow Builder installation. This workflow is described in detail in the Sample nse
Workflow Process chapter in the Oracle Workflow Developer’s Guide. li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 13
Defining a Process Activity
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Process Activity
Defining
d
e
sh To define a process activity:
Ra 1. In Oracle Workflow Builder, select the item type that you want in the navigator tree.
Then select New Process from the Edit menu.
2. In the Activity property page, enter an internal name for the activity. The internal name
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the activity.
4. Enter a description of the activity.
5. Choose an icon that identifies the activity.
6. Specify the result type that contains the possible results that the process can return.
7. Select the Runnable check box if this is a top-level workflow process that can be
initiated. If the Runnable check box is selected, the process will appear in the Process
Name list of values in the Initiate Workflow web page, and you can successfully pass this
process internal name in a call to the Workflow Engine API WF_Engine.CreateProcess.
Clear the Runnable check box if this process activity can only be executed as a
subprocess called by another higher-level process.

Chapter 4 - Page 14
8. Click Apply to save your changes.
9. Optionally select the Details tab to display and modify additional activity details.
10. Optionally select the Access tab to set the access levels allowed to modify this activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 15
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Each process diagram must have one or more Start activities and one or more End activities.
Ra Note: In the process window, you can display information about an activity by positioning
your mouse over the activity. The Instance Label, Internal Name, Display Name, Comment,
and Performer appear in a tool tip display.

Chapter 4 - Page 16
Top-Down Design
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Design
Top-Down
d
e
sh When you create a new activity in the process window, the property pages displayed for
Ra activities from the process diagram window include all tabs for the base activity definition as
well as for the usage of the individual activity node. You must enter at least an internal name
and a display name for the activity in order to use the activity in the diagram. You can also
enter the remaining details in the activity and activity node property pages immediately, or you
can save the activity and complete these details at a later time.
When you save a partially completed top-down process, Oracle Workflow Builder displays an
error window with a list of invalid or missing information. You can save the incomplete
process definition and correct the errors later.

Chapter 4 - Page 17
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh If the source activity has no result type associated with it, by default no label appears on the
Ra transition. You can choose to show a label for such a transition by selecting the transition,
holding down the right mouse button, and clearing the Hidden Label option. The label will
display as <Default>.
If the source activity has an associated result type, you can create transitions to follow:
• When a specific result is returned by the activity, labeled with the result display name
• When a result returned is not covered by other transitions, labeled <Default>
• Regardless of result returned, labeled <Any>
• When the activity times out, labeled <Timeout>
Note: The Timeout property for the node must be set to enable the <Timeout> option in the list
of results for the transition.
If the source activity is a voting activity, you can also create transitions to follow:
• When the vote results in a tie, labeled <Tie>
• When the vote doesn’t return a result, labeled <No Match>

Chapter 4 - Page 18
<Default> Transition
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Transition
<Default>
d
e
sh The Workflow Engine follows a <Default> transition if no other transition matching the
Ra completion result exists. This feature lets you simplify your process diagram modeling and
maintenance by only drawing transitions for unique results, allowing all other results to follow
the default transition.

Chapter 4 - Page 19
<Any> Transition
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Transition
<Any>
d
e
sh The Workflow Engine follows an <Any> transition regardless of what completion result the
Ra activity returns. This feature lets you include a generic activity in the process that the
Workflow Engine executes in parallel with any result-specific activity.

Chapter 4 - Page 20
Editing a Transition
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 21
Editing a Transition
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 22
Self-Looping Transitions
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Self-Looping Transitions
e
sh To draw a self-looping transition:
Ra 1. Select the activity node.
2. Hold down the right mouse button.
3. Drag the cursor away from and back to the same activity node.
4. Release the right mouse button and select the transition label from the list of results.
Alternatively, you can also use the following steps:
1. Draw a transition to some other activity.
2. Add a vertex point to the transition.
3. Select the arrowhead of the transition with the left mouse button and drag it back to the
originating activity.

Chapter 4 - Page 23
Customizing an Activity Node
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Customizing an Activity Node
e
sh To define node properties:
Ra 1. In Oracle Workflow Builder, double-click the activity node in the process window to
display the property pages for the node. Select the Node tab.
2. Specify a label for the node. By default, the label name is the activity name. If you use an
activity more than once in a process, -N is appended to the label name to identify each
node uniquely, where N represents the Nth instance of the activity in use.
3. Specify whether the activity is a Start, End, or Normal activity in the process.
For an End activity, if the process itself has a result type associated with it, you should
specify what the result of the process is when this End activity completes. Choose from
the possible results listed in the result type of the process activity.
4. Optionally enter a comment about this node.
5. For a notification activity, a process activity, or a Receive event activity, use the Timeout
region to specify whether the activity must be completed by some specified time.
6. For a notification activity or a Send event activity, optionally specify the message
priority.

Chapter 4 - Page 24
7. For a notification activity, specify a performer. A performer is a role that can consist of
one or more users.
- You can specify a static role. Specify Constant for the Performer Type, and select a
role name. Note that you must first load roles from your database.
- You can alternatively specify a dynamic role. Select Item Attribute for the Performer
Type, and select an item type attribute that returns a role name at runtime.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 25
Show Label in Designer Menu Options
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Show
d A Label in Designer Menu Options
e
sh • Instance Label: Uses the node label for each activity node
Ra • Internal Name: Uses the internal name of the activity as the label for each activity node
• Display Name: Uses the display name of the activity as the label for each activity node
• Performer: Uses the activity’s performer as the label for each activity node
• Comment: Uses the activity’s comment as the label for each activity node

Chapter 4 - Page 26
Display Modes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Modes
Display
d
e
sh In developer mode, Oracle Workflow Builder:
Ra • Provides visual distinctions between top-level processes and subprocesses in the navigator
tree
• Sets the icons for each activity and object to the default icon of its object type or subtype
in both the navigator tree and the process diagram window
• Identifies each object in the navigator tree by its internal name (developer name)
• Identifies each activity in the process diagram window by its activity label

Chapter 4 - Page 27
Verifying a Process Definition
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Process Definition
Verifying
d
e
sh You should always validate any new process definition you create, because validation helps
Ra you identify any potential problems with the definition that might prevent it from executing
successfully.
Note: The Verify option is enabled in the File menu only when the navigator tree is the current
window.

Chapter 4 - Page 28
Validation Performed by the Verify Command
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 29
Validation Performed by the Verify Command
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 30
Saving Process Definitions
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Process Definitions
Saving
d
e
sh If a non-unique display name is encountered when a process definition is being uploaded or
Ra upgraded in a database, the Workflow Definitions Loader automatically resolves the display
name conflict by adding a “@” character to the beginning of conflicting display names.

Chapter 4 - Page 31
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 4 - Page 32
nse
li c e
ble
fe r a
a n s
noType Attributes n-tr
Defining Item
a
a) Guid has eTypes
and Lookup ฺ
ฺ s
uChaptern5t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
A lha
d
she
Ra
Defining Item Type Attributes and Lookup Types

Chapter 5 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 4
Defining Item Type Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 5
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Item Type Attributes
Defining
d
e
sh Note: Do not use item type attributes as a denormalized data store. Always refer back to the
Ra base application to retrieve up-to-date values. There is a trade-off between the convenience of
storing global process data in item type attributes and the overhead incurred by loading item
type attributes when a process instance is created. Minimize the number of item type attributes
to improve the performance of your workflow process.
Examples
For example, the Requisition demonstration workflow includes item type attributes for the
following information: Forward From Username, Forward To Username, Requestor Username,
Requisition Amount, Requisition Number, Monitor URL, Requisition Description, Requisition
Process Owner, Reminder Requisition Document, Note, and Note for Reminder.

Chapter 5 - Page 6
Attribute Data Types
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Data Types
Attribute
d
e
sh • Text: A string of text of specified character length.
Ra • Number: A number with an optional format mask.
• Date: A date with an optional format mask.
• Lookup: A lookup code value from a specified lookup type.
• Role: A role name from the list of roles defined in the directory service.
• Attribute: The internal name of another existing item type attribute to which you want to
maintain references in a process.
• URL: A Universal Resource Locator (URL) to a network location.
• Form: The internal function name and any optional form parameters of an Oracle E-
Business Suite form function.
• Document: An attached document, as specified by the document type. PL/SQL, PL/SQL
CLOB, and PL/SQL BLOB documents are files representing data from the database as a
character string, a character large object (CLOB), or a binary large object (BLOB),
respectively. A document attribute can also be defined as a JSP call to an Oracle
Application Framework region for inclusion in a notification message.

Chapter 5 - Page 7
• Event: A Business Event System event message in the standard WF_EVENT_T structure.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 8
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Item Type Attributes
Defining
d
e
sh To define an item type attribute:
Ra 1. In the Oracle Workflow Builder, select the item type you want in the navigator tree. Then
select New Attribute from the Edit menu.
2. In the Attribute property page, enter an internal name for the attribute. The internal name
must be all uppercase without any leading or trailing spaces.
3. Enter a display name for the attribute.
4. Enter a description of the attribute.
5. In the Type field, select the data type for the attribute.
6. Depending on the data type, enter format information and a default value, if applicable.

Chapter 5 - Page 9
URL Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
URLAAttributes
e d
sh When you specify a frame target, you can select from the following options:
Ra • New Window: The URL loads in a new, unnamed browser window.
• Full Window: The URL loads into the full, original window.
Note: The Notification Details page no longer uses frames to display notifications.
Consequently, selecting Same Frame or Parent Frameset is equivalent to selecting Full
Window.
URL Attribute Values
The value of a URL attribute can be a text string or can be token substituted. A URL value is
specified in the format:
http://<location>

Chapter 5 - Page 10
URL Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
URLAAttributes
e d
sh When defining a URL attribute to point to such an image, you must provide the complete URL
Ra for the image, either as a constant or as a value returned from another item attribute. You
cannot token substitute any argument strings within the image URL.
Note: Oracle Workflow displays images only in the message body of a notification. If you
select Attach Content for a URL attribute that points to an image file, the URL attribute
appears as an attached link, just as other URLs do.

Chapter 5 - Page 11
URL Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
URLAAttributes
e d
sh In a plain text e-mail notification, the URL location value for an attached URL attribute is
Ra included as plain text.
In an HTML-formatted e-mail notification, a URL attribute appears as a hypertext link in the
message body. For attached URL attributes, an attachment called Notification References is
appended to the message. This attachment includes a link to each attached URL attribute for
the message. You can navigate to a URL by clicking its link.
If you define a URL attribute for an image, when the notification is viewed from the
Notification Details Web page or as an HTML-formatted e-mail, the image appears inline in
the message body.

Chapter 5 - Page 12
Form Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Form
d AAttributes
e
sh Form Attribute Values
Ra The value for an attribute of type form must be the internal function name of an Oracle E-
Business Suite form function, together with any optional form parameters that should be
prequeried with a value when the form is opened.
The default value for the form attribute must be entered using the following format:
function_name:parameter1=value1 parameter2=value2 ...parameterN=valueN
The value of a form parameter can be a text string enclosed in quotes (“ “) or can be token
substituted with another predefined item type attribute in either of the following ways:
• parameterN = “&item_type_attribute”
• parameterN = “Value &item_type_attribute”, where
&item_type_attribute represents the rest of the value
To find the internal function name for a form function, navigate to the form, select About
Oracle Applications from the Help menu, and locate the internal form name in the Current
Form section of the information displayed. Then log in to the Application Developer
responsibility and use the Forms window to query for the user form name based on the internal

Chapter 5 - Page 13
form name and the Form Functions windows to query for the form function name based on the
user form name.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 14
Form Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
NoteA
e d
sh Form attributes cannot be attached to e-mail notifications. To view form attachments, you must
Ra view the notification in the Notification Details Web page.

Chapter 5 - Page 15
Document Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Type Attributes
Document
d
e
sh PL/SQL, PL/SQL CLOB, and PL/SQL BLOB documents are useful when document content
Ra varies. For example, these documents can be used to represent purchase orders with variable
numbers of lines, or sales orders with variable lines, discounts, and shipping addresses.
Document Attribute Values
The value of a document attribute can be a text string or can be token substituted.
• A PL/SQL document value is specified in the format:
PLSQL:<procedure>/<document_identifier>
• A PL/SQL CLOB document value is specified in the format:
PLSQLCLOB:<procedure>/<document_identifier>
• A PL/SQL BLOB document value is specified in the format:
PLSQLBLOB:<procedure>/<document_identifier>
Replace <procedure> with the PL/SQL package and procedure name, separated by a period.
Replace <document_identifier>with the PL/SQL argument string that you want to pass directly
to the procedure. The argument string should identify the document.

Chapter 5 - Page 16
If you want to generate the document identifier for a PL/SQL, PL/SQL CLOB, or PL/SQL
BLOB document dynamically, you can token substitute the document identifier with other item
type attributes. The item attribute names must be in uppercase and must be separated by a
colon. For example:
PLSQL:PO_WF.SHOW_REQ/&REQ_TYPE:&REQ_NUMBER
Oracle Application Framework Regions
You can also use a document attribute to reference an Oracle Application Framework region
that you want to embed in a notification message. Specify the JSP call to reference the region
as the default value for the attribute.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 17
Document Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Type Attributes
Document
d
e
sh In a plain-text e-mail notification, PL/SQL, PL/SQL CLOB, and PL/SQL BLOB document
Ra attributes are attached as plain text to their parent notification. Note that this may render some
attachments unreadable if the attachment includes special formatting or your plain text e-mail
reader does not recognize attachments. To view these attachments, you should display your
notifications in the Notification Details Web page.
In an HTML-formatted e-mail notification with an attached PL/SQL, PL/SQL CLOB, or
PL/SQL BLOB document attribute, the fully generated PL/SQL document is fetched and
attached to the message.
An Oracle Application Framework region can only be displayed within the message body of a
notification. It cannot be included as an attachment to the notification.

Chapter 5 - Page 18
Deleting Item Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Item Attributes
Deleting
d
e
sh Deleting an item attribute from a workflow definition stored in a flat file and then uploading
Ra that flat file definition to a database will not delete the item attribute from the definition stored
in the database. To delete an item attribute completely, you must delete it from your flat file
definition and also delete it specifically from any databases in which that workflow item type is
loaded while connected to those databases.

Chapter 5 - Page 19
Defining Lookup Types
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Lookup Types
Defining
d
e
sh Although lookup types must be associated with a given item type and are defined in the
Ra navigator tree beneath the Lookup Types branch of that item type, lookup types can be
referenced by components in other item types.
To define a lookup type:
1. In the Oracle Workflow Builder, select the item type you want in the navigator tree. Then
select New Lookup Type from the Edit menu.
2. In the Lookup Type property page, enter an internal name for the lookup type. The
internal name must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the lookup type.
4. Enter a description of the lookup type.

Chapter 5 - Page 20
Defining Lookup Codes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Lookup Codes
Defining
d
e
sh To define a lookup code:
Ra 1. In the Oracle Workflow Builder, select the lookup type you want in the navigator tree.
Then select New Lookup Code from the Edit menu.
2. In the Lookup Code property page, enter an internal name for the lookup code. The
internal name must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the lookup code.
4. Enter a description of the lookup code.

Chapter 5 - Page 21
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 5 - Page 22
nse
li c e
ble
fe r a
a n s
no n-tr
Defining Messages
a and
ha s
eฺ
ฺ s a) Guid
e d uChaptern6t
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
A lha
d
she
Ra
Defining Messages and Notification Activities

Chapter 6 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 4
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 5
Defining a Message
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Message
Defining
d
e
sh To create a new message:
Ra 1. In the Oracle Workflow Builder, select the item type you want in the navigator tree. Then
select New Message from the Edit menu.
2. On the Message property page, enter an internal name for the message. The internal name
3. Enter a display name for the message.
4. Enter a description of the message.
5. Select the priority for the message (High, Normal, or Low). Message recipients can sort
their notifications based on the priority.

Chapter 6 - Page 6
Defining a Message
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Message
Defining
d
e
sh To define the body for a message:
Ra 1. In the message property pages, select the Body tab.
2. Enter the subject line for the message.
3. Enter the plain text message body in the Text Body tab.
4. Enter the HTML-formatted message body in the HTML Body tab.

Chapter 6 - Page 7
Defining a Message Attribute
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Message Attribute
Defining
d
e
sh To define a message attribute:
Ra 1. In the Oracle Workflow Builder, select the message you want in the navigator tree. Then
2. On the Attribute property page, enter an internal name for the attribute. The internal name
6. Depending on the data type, enter format information, if applicable.
7. Specify either Send or Respond in the Source field to indicate whether the attribute should
send information to the recipient or prompt the recipient for a response, respectively. You
should set the source to Send for any message attributes that you include in the message
subject and message body for token substitution.

Chapter 6 - Page 8
8. Set the default value of a Send attribute to reference either a constant or the run-time value
of an item type attribute. You can optionally set a default value for a Respond attribute as
well.
Note: To define a message attribute that references an existing item attribute, you can also
select the item attribute in the navigator tree and drag it onto the message you want in the
navigator tree. Then edit the property page that appears, making sure that the message attribute
has the appropriate source. The default type is automatically set to Item Attribute and the
default value references the originating item attribute.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 9
Defining a Respond Attribute
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Respond Attribute
Defining
d
e
sh The icon for a Respond attribute in the navigator tree includes a red question mark in its lower
Ra left corner to distinguish it from Send attributes.
The Notification System uses the Respond attributes defined for the message to generate the
response section of the notification sent to the recipient. The response section is composed
differently depending on whether the recipient receives the notification as a plain text e-mail
notification, as an HTML-formatted e-mail notification, or through the Notification Details
Web page. For plain text e-mail notifications, the response section is also composed differently
depending on whether your organization uses the direct response method or the templated
response method. (HTML e-mail notifications always use the templated response method.)

Chapter 6 - Page 10
Defining a Message Result
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Message
Defining
d
e
sh The icon for a message in the navigator tree includes a red question mark in its lower left
Ra corner when the message has a result defined for it.
To define the result for a message:
1. On the message property pages, select the Result tab.
2. Enter a display name for the result. Oracle Workflow uses the display name as the
response prompt in some notification formats, including e-mail notifications and the pull-
down menu that appears in the Notification Details page if there are more than four
possible result values.
3. Enter a description for the result.
4. Select a lookup type to provide the possible result values. The lookup type associated with
the message result should be the same as the result type of the notification activity that
sends the notification message.
5. Optionally, set the default value of the result to reference either a constant or the run-time
value of an item type attribute.

Chapter 6 - Page 11
Notification Details Web Page
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Notification Details Web Page
e
sh Images in an HTML message:
Ra If you define a “Send” message attribute of type URL that points to an image file with an
extension of gif, jpg, png, tif, bmp, or jpeg, and you embed the URL attribute in the HTML
body of the message, then Oracle Workflow displays the image inline in the Notification
Details page.

Chapter 6 - Page 12
HTML E-mail Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
HTML
d A E-mail Notifications
e
sh The response template consists of the required notification ID and access key that identify the
Ra notification the user is responding to and a response prompt edited with the result response that
the user selected.
Depending on the notification, the auto-generated e-mail response template may also prompt
the user for other information in addition to the selected result response. Any additional
prompts and values are generated by information drawn from the properties of each Respond
attribute, similarly to the response section for plain text templated response.
The user supplies responses by editing the response value text between the quotes following
each prompt.
Images in an HTML message:
If you define a “Send” message attribute of type URL that points to an image file with an
extension of gif, jpg, png, tif, bmp, or jpeg, and you embed the URL attribute in the HTML
body of the message, then Oracle Workflow displays the image inline in HTML-formatted e-
mail notifications.

Chapter 6 - Page 13
Plain Text E-mail Notifications Using Templated Response
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
AText E-mail Notifications Using Templated Response
Plain
d
e
sh • Description: The description of the Respond attribute; this description provides optional
Ra information on how to complete a response.
• Display Name: The display name of the Respond attribute; this name specifies the
response value that is expected.
• List of lookup codes: If the attribute is of type lookup, the lookup codes that are the
possible response values are listed.

Chapter 6 - Page 14
Plain Text E-mail Notifications Using Direct Response
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
AText E-mail Notifications Using Direct Response
Plain
d
e
sh • Display Name: The display name of the Respond attribute; this name specifies the
Ra response value that is expected.
• Sequence: The sequence position of this Respond attribute among all the Respond
attributes of the message, as listed in the navigator tree.
• Description: The description of the Respond attribute; this description provides optional
information on how to complete a response.
• Type Hint: A standard hint that is provided based on the attribute’s type:
Type Type Hint

Lookup Value must be one of the following:
<list of lookup codes>
Date Value must be a date in the form “<format>“.
Number Value must be a number in the form “<format>“.
Text Value must be <format> bytes or less.

Chapter 6 - Page 15
Defining a Notification Activity
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Notification Activity
Defining
d
e
sh To define a notification activity:
Then select New Notification from the Edit menu.
2. On the Activity property page, enter an internal name for the activity. The internal name
5. Select an icon that identifies the activity.
6. Optionally specify a PL/SQL stored procedure in the Function field. The procedure is
known as a post-notification function and can be used to couple processing logic to the
notification activity.
7. Specify the result type that contains the possible results that the notification can return. If
the message for the notification includes a result, then the result type of the notification
activity must be the same as the lookup type that the message result references.
8. Select the message that this notification sends.

Chapter 6 - Page 16
9. Select the Expand Roles check box if you want to send this notification to a multiuser
role and ensure that each user receives an individual copy of the notification. You should
always select the Expand Roles check box for FYI-type notifications.
11. Optionally select the Details tab to display and modify additional activity details.
12. Optionally select the Access tab to set the access levels allowed to modify this activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 17
Standard Voting Activity
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Voting Activity
Standard
d
e
sh The activity sends a message called “Default Voting Message Yes/No” that includes a message
Ra result. The message prompts the recipient to reply with “Yes” or “No.” The possible results of
this notification activity are stored in the lookup type called Yes/No.
Choose “Expand Roles” for the notification activity to ensure that all users in the role receive a
copy of the notification.
When the activity receives responses, it executes a PL/SQL procedure called
WF_STANDARD.VOTEFORRESULTTYPE to tally the Yes/No responses.
Vote Yes/No has three activity attributes associated with it:
• Voting Option: Specifies when and how to tally the votes
• Percent Yes: Specifies what percentage of Yes responses are required for a Yes result
• Percent No: Specifies what percentage of No responses are required for a No result

Chapter 6 - Page 18
Defining a Notification Activity Node
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 19
Defining a Timeout for a Notification
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Timeout for a Notification
Defining
d
e
sh • Choose “No Timeout” if the notification does not have to be completed by a certain time.
Ra • Choose “Relative Time” if you want the notification to be completed by some constant
relative time. You can enter any combination of days, hours, and minutes to specify when
the activity times out. The value you enter is interpreted as a relative offset from the begin
date of the activity, in the unit of minutes.
Note: A relative timeout value of zero means there is no timeout.
• Choose “Item Attribute” if you want the notification to be completed by some relative
time or date that is determined dynamically at run time. You must first create an item
attribute of type number or date to store the dynamic timeout value and then reference that
predefined item attribute here. The dynamic timeout value stored in this attribute is
interpreted as a relative offset from the begin date of the activity, in the unit of minutes.

Chapter 6 - Page 20
Defining a Dynamic Priority for a Notification
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Dynamic Priority for a Notification
Defining
d
e
sh You can set the override priority as a constant of High, Normal, or Low, or you can reference
Ra an item attribute. The item attribute must be of type number, and the following ranges apply:
• High: 1-33
• Normal: 34-66
• Low: 67-99

Chapter 6 - Page 21
Defining a Performer for a Notification
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 22
Special Message Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Message Attributes
Special
d
e
sh You can define special message attributes to specify how a notification is displayed or handled.
Ra When you define a special message attribute, you must usually enter its internal name
beginning with the # symbol as listed here, and assign the attribute a source of Send. You can
enter a display name and description of your own choosing. For information on additional
special message attributes, see the Oracle Workflow Developer’s Guide.
#HIDE_REASSIGN
Use #HIDE_REASSIGN to hide the Reassign button in the Notification Details Web page. The
response section in the Notification Details page includes the Reassign button by default. If
you want to restrict users from reassigning a notification, you can add the #HIDE_REASSIGN
attribute to control whether the Reassign button is displayed or hidden.
The #HIDE_REASSIGN attribute also controls whether a notification can be reassigned using
the Reassign button in the Advanced Worklist, Personal Worklist, or self-service home page.
The Reassign button in these pages will still be displayed, but an error message will appear if
users attempt to reassign notifications for which the #HIDE_REASSIGN attribute has been set.
Additionally, you can specify whether or not the notification can still be reassigned through
vacation rules. You can choose to both hide the Reassign button and prevent reassignment

Chapter 6 - Page 23
through vacation rules. In this case Oracle Workflow does not apply any vacation rules to
reassign those notifications, but simply delivers the notifications to the worklist of the original
recipient. You can also choose to hide the Reassign button but still allow reassignment through
vacation rules.
The #HIDE_REASSIGN attribute must be either of type text or lookup.
• To hide the Reassign button in the Notification Details page, and to prevent reassignment
from the Advanced Worklist, Personal Worklist, and self-service home page, as well as
through vacation rules, set the value of this attribute to Y.
• To hide the Reassign button in the Notification Details page, and to prevent reassignment
from the Advanced Worklist, Personal Worklist, and self-service home page, but still
allow reassignment through vacation rules, set the value of this attribute to B.
• To display the Reassign button in the Notification Details page, and to allow reassignment
from the Advanced Worklist, Personal Worklist, self-service home page, and vacation
nse
rules, set the value to N.
li c e
#FROM_ROLE ble
Use #FROM_ROLE to specify the role that is the source of a notification. For example, if you fe r a
have a notification that informs an approver that a requisition was submitted, you can set the a n s
requisition preparer as the From Role for the message.
no n-tr
a
The From Role for each notification is displayed in the Worklist Web page and in e-mail
) h as deฺ
notifications to give users additional information for reviewing and responding to the
u ฺ sa t Gui
notifications. Additionally, Oracle E-Business Suite Personal Worklist lets you search for
notifications based on the From Role.
s t ฺed uden
k ac is St
The #FROM_ROLE attribute must be of type role. You should specify an item type attribute as
the value for the #FROM_ROLE attribute and include logic in your workflow process that
j ri@ e th
dynamically sets that item type attribute to the role you want at run time.
a
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 24
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Special
d
e
sh #WF_SECURITY_POLICY
Ra Use #WF_SECURITY_POLICY to control whether notifications that include sensitive content
can be sent in e-mail. If you specify that a notification’s content must not be sent in e-mail,
users receive an e-mail message that only informs them that they must access the notification
through the Notification Details Web page instead to view its content and respond.
The #WF_SECURITY_POLICY attribute must be of type text. To prevent notification content
from being sent in e-mail, set the value of the #WF_SECURITY_POLICY attribute to
NO_EMAIL. If you set the value to EMAIL_OK or DEFAULT, leave the value blank, or if
you do not define a #WF_SECURITY_POLICY attribute for the message, Oracle Workflow
sends the full notification content in e-mail to users whose notification preference is set to
receive e-mail.
Notification Mailer Attributes
Use these attributes to control how a notification mailer generates the e-mail message for a
notification, if the recipient has a notification preference to receive e-mail notifications. For
example, if you want to customize notifications from a particular department, you can define
these attributes for those notifications. Values that you specify in these attributes for a

Chapter 6 - Page 25
particular notification override the default values for the notification mailer specified in the
mailer’s configuration parameters. Some of the most commonly used notification mailer
attributes are:
• #WFM_FROM: Lets you specify the value that appears in the From field of the message
header when the e-mail notification message is delivered to a user.
• #WFM_REPLYTO: Lets you specify the address of the e-mail account that receives
incoming messages, to the which e-mail notification response should be sent.

• #WFM_HTMLAGENT: Lets you specify the base URL that identifies the HTML Web
agent that handles HTML notification responses. This URL is required to support e-mail
notifications with HTML attachments. The default URL is derived from the Applications
Servlet Agent profile option. You can override this default by defining a different value
for this attribute.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 26
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Special
d
e
sh #WF_REASSIGN_LOV
Ra Use #WF_REASSIGN_LOV to specify the users to whom a message can be reassigned. Create
a role whose members are all the users that you want to allow as possible new recipients when
the notification is reassigned, and assign this role as the value for the #WF_REASSIGN_LOV
attribute. Then, when the notification recipient attempts to reassign the notification, only the
users that belong to that role will appear in the list of values for the Reassign field.
The #WF_REASSIGN_LOV attribute must be of type role and must have a source of Send. If
no existing role meets your needs, you can include logic in your process to create an ad hoc
role at run time and add the users you want to that role.
#HIDE_MOREINFO
When users view a notification that requires a response in the Notification Details page, the
response region includes the Request Information button by default. If you want to prevent
users from requesting more information about a notification, you can add the
#HIDE_MOREINFO attribute to control whether the Request Information button is displayed
or hidden.

Chapter 6 - Page 27
The #HIDE_MOREINFO attribute must be either of type text or lookup. To hide the Request
Information button, set the value of this attribute to Y. To display the Request Information
button, set the value to N. It is recommended that you define the #HIDE_MOREINFO attribute
with a type of lookup and assign it the predefined Yes/No lookup type that is provided in the
Standard item type.
#WF_SIG_POLICY
Use #WF_SIG_POLICY to require that a user’s response to a notification be signed

electronically. This electronic signature is analogous to a written signature. If you define a
notification to require an electronic signature, users must respond to the notification from the
Notification Details Web page and enter the appropriate type of signature. Otherwise, the
response will not be considered valid.
• If you define a notification to require a password-based signature, users must sign their
response by entering their Oracle E-Business Suite user name and password. e
• If you define a notification to require a certificate-based digital signature, users must sign c e ns
their response with a valid X.509 certificate issued by a certificate authority. e li
The signed response text for both types of signatures contains the notification header r a bl
information and the response values entered by the user. You can optionally require the signed n sfe
a
response text to include the notification message body as well.
no n-tr
Note: If the message body contains a link or an image, the signed response text includes the
a
) h as deฺ
HTML code used to reference the link or image, rather than the content of the referenced file
u ฺ sa t Gui
itself. The signed response text does not include notification attachments.
s t ฺed uden
The #WF_SIG_POLICY attribute must be either of type text or lookup.
k ac is St
• To require a password-based signature without including the message body in the signed
response text, set the value to PSIG_ONLY.
a j ri@ e th
• To require a password-based signature and include the message body in the signed
r a lh o us
response text, set the value to PSIG_BODY.
j ri ( t
a
• To require a certificate-based digital signature without including the message body in the
lh
d A signed response text, set the value to PKCS7X509_ONLY.
she • To require a certificate-based digital signature and include the message body in the signed
Ra response text, set the value to PKCS7X509_BODY.
• If you set the value to DEFAULT, leave the value blank, or if you do not define a
#WF_SIG_POLICY attribute for the message, Oracle Workflow performs the default
response processing that does not require a signature.
It is recommended that you define #WF_SIG_POLICY with a type of lookup and assign it the
predefined Signature Policy lookup type provided in the Standard item type.
Oracle Workflow records the status of requested and submitted signatures in the Signature
Evidence Store. You can search for signatures in the Signature Evidence Store to check the
status of a signature request and review details that provide evidence of the signature. If your
business logic requires a signature to be validated as a prerequisite for other activities, your
workflow can include a notification to an administrator to confirm the signature status before
continuing.
To preserve electronic signature evidence for future reference, the Purge Obsolete Workflow
Runtime Data concurrent program and the Oracle Workflow purging APIs by default do not
delete any notifications that required signatures or their associated signature information. If

Chapter 6 - Page 28
you anticipate needing access to signature evidence after the associated workflow processes are
complete, ensure that you choose to preserve signature data when purging. If you do not need
to maintain signature evidence, you can choose to delete signature-related information when
purging.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 29
Action History
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A History
Action
d
e
sh The action history table contains a row for each previous execution of the same notification
Ra activity node in a process, as well as a row for the initial submission of the process.
• For example, for a requisition approval notification activity that sends a certain
notification to several approvers in turn, the action history table would contain a row for
each approver to whom the notification was sent, as well as a row for the process owner.
• Additionally, if a notification is reassigned to another user in either delegate or transfer
mode, or if one user requests more information about the notification and another user
answers that request, the action history contains rows for those actions also.
Including the Action History Table
• If the notification requires a response, then Oracle Workflow automatically includes the
action history table in the notification.
• If the notification does not require a response, then Oracle Workflow only includes the
action history table automatically if the notification has been reassigned at least once or if
at least one recipient has requested more information about the notification. However, you
can manually include the action history table by calling the special message function
WF_NOTIFICATION(HISTORY) in the message body.

Chapter 6 - Page 30
Special Message Function
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Message Function
Special
d
e
sh Oracle Workflow creates the tables as Oracle Application Framework regions, unless the
Ra message body also includes any message attribute tokens that reference values other than
Oracle Application Framework regions. In this case, the tables are created in a standard Oracle
Workflow format.
Note: WF_NOTIFICATION() is not a PL/SQL function, but rather a special message function
that can only be called within an Oracle Workflow message body.
Message Attribute Table
To include a table of message attributes in a message body, call WF_NOTIFICATION() with
the ATTRS option followed by the internal names of the message attributes, separated by
commas. Use the following format:
WF_NOTIFICATION(ATTRS,<attribute1>,<attribute2>,<attribute3>,...)
Note: Do not include any spaces or carriage returns in the call to WF_NOTIFICATION(). You
only need to use a comma to delimit the parameters in the list.
The message attribute table contains a row for each message attribute listed in the
WF_NOTIFICATION() call, showing the display name and the value for each attribute.
Action History Table

Chapter 6 - Page 31
To include an action history table in a message body, call WF_NOTIFICATION() with the
HISTORY option in the following format:
WF_NOTIFICATION(HISTORY)
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 32
Embedding Oracle Application Framework Regions in
Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Embedding Oracle Application Framework Regions in Notifications
Ra For more information, see the Oracle Workflow Developer’s Guide and the Oracle Application
Framework Developer’s Guide, available from My Oracle Support Knowledge Document
744832.1.

Chapter 6 - Page 33
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 6 - Page 34
nse
li c e
ble
fe r a
a n s
o n-tr
Testing and
a nMonitoring
a) Guid has Processes
Workflow eฺ
ฺ s
uChaptern7t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
Alha
d
she
Ra
Testing and Monitoring Workflow Processes

Chapter 7 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 4
Testing Workflow Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 5
Testing Workflow Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Processes
Testing
d
e
sh Use a Web browser to navigate to the Developer Studio, using a responsibility and navigation
Ra path specified by your system administrator. Some possible navigation paths in the seeded
Workflow responsibilities are:
• Workflow Administrator Web Applications: Developer Studio
• Workflow Administrator Web (New): Developer Studio
• Workflow Administrator Event Manager: Developer Studio
You can navigate to the Developer Studio from other Oracle Workflow administrator Web
pages by selecting the Developer Studio tab or clicking the Developer Studio link at the end of
the page.
Note: You must have workflow administrator privileges to run a test workflow from the
Developer Studio.
In the Search region of the Developer Studio, enter search criteria to locate the workflow
process definitions you want to display. You can search by the workflow item type display
name and internal name. You can enter a partial value for the internal name to search for
workflow types whose internal names begin with that value. Select the Go button to perform
your search.

Chapter 7 - Page 6
Note: If a workflow process begins with a Receive event activity, you cannot use the
Developer Studio to test the process. Instead, you should raise a test event from the Event
Manager to trigger an event subscription that launches the process.
After you launch a process, you can review the progress of the process in the Status Monitor
and respond to any notifications using the Worklist.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 7
Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Administrator Monitor
e
sh The administrator version of the Status Monitor lets you view and administer runtime
Ra workflows. You can:
• Review the activities performed for a workflow.
• Check the status of the workflow by viewing the status diagram.
• Examine responses to notifications sent by the workflow.
• Review the workflow definition and attributes.
• If you have the appropriate workflow administrator privileges, you can also perform
control operations for a workflow or handle an error.
Workflow Administrator Privileges
Users have workflow administrator privileges if they belong to the Oracle Workflow
administration role, which is defined in the Workflow Configuration Web page.
Oracle Workflow also allows users to be assigned specialized workflow monitoring privileges
with restricted access to workflow data. If you have specialized workflow monitoring
privileges, you can only view workflows and perform administrative actions to which you have
been granted access. For example, you may only have access to monitor workflows belonging

Chapter 7 - Page 8
to particular item types, and you may be able to suspend and rewind workflows but not to skip
activities.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 9
Viewing Workflows in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflows in the Administrator Monitor
Viewing
d
e
sh Use a Web browser to navigate to the administrator Status Monitor, using a responsibility and
Ra navigation path specified by your system administrator. Some possible navigation paths in the
seeded Workflow responsibilities are:
• Workflow Administrator Web Applications: Status Monitor
• Workflow Administrator Web (New): Status Monitor
• Workflow Administrator Event Manager: Status Monitor
You can navigate to the administrator Status Monitor from other Oracle Workflow
administrator Web pages by selecting the Status Monitor tab or clicking the Status Monitor
link at the end of the page.
Searching for Workflows
In the Search region of the Workflows page, enter search criteria to locate the workflows you
want to display. The main search options are workflow item type display name, item type
internal name, owner, item key, user key, status, and start date.

Chapter 7 - Page 10
• Workflow Owned By: If you have workflow administrator privileges, select the user who
owns the workflows you want to review. If you do not have workflow administrator
privileges, you can only search for workflows that you own.
• Item Key and User Key: You can enter a partial value to search for workflows whose keys
begin with that value.
• Workflow Started: All the start date ranges include the current date; for example, Last 2
Weeks includes today as well as the previous thirteen days.

Note: You must enter at least one of the following criteria when you search in order to limit
the size of the results list.
• Workflow Type
• Type Internal Name
• Workflow Owned By
• Workflow Started: If you search only by this option, you must select a specific start date nse
range. You cannot use Workflow Started with the Any Time value as your only search li c e
option. ble
fe r a
You can also enter additional search criteria to search for workflows by activity characteristics.
a n s
The additional search criteria are activity status, activities waiting for a response from a
particular user, and days without progress. no n-tr
a
Click the Go button to perform your search.
) h as deฺ
Viewing Workflows
u ฺ sa t Gui
s t ฺed uden
• To send e-mail to the owner of a workflow, click the user link in the Owned By column.
• For an errored workflow, click the error icon or the error link in the Status column to view
error details. k ac is St
a j ri@ e th
• For a parent workflow, click the icon in the Child Workflows column to view its children.
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 11
Viewing Activity History in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activity History in the Administrator Monitor
Viewing
d
e
sh A hierarchical grid displays the process hierarchy formed by the selected workflow and any
Ra child workflows associated with it.
Searching for Activities
All activity types and statuses are selected by default. To search for specific activities, deselect
any activity types and statuses you do not want to view and click the Go button. At least one
activity type and one activity status must be selected for a search to be performed.
Viewing Activities
• To view details about the definition and current status of an activity, click the activity
name link in the Activity column.
• To send e-mail to the performer of a notification, click the user link in the Performer
column.

Chapter 7 - Page 12
Viewing a Status Diagram in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Status Diagram in the Administrator Monitor
Viewing
d
e
sh Above the process diagram, the process title displays the workflow process name, type, and
Ra user key, or item key if no user key has been set. If you drill down to a subprocess in the
process diagram, the process title displays the subprocess name.
Process Diagram
• An activity can be highlighted with a colored box to indicate a distinctive state:
- Red: The activity is in an error state.
- Green: The activity is active or in progress.
- Yellow: The activity is suspended.
• A transition arrow can have a thick green line to indicate that it has been traversed, or it
can have a thin black line to indicate that it has not been traversed.
• Click an activity icon to display information about it in the detail tab window.
• Click any empty space in the diagram to deselect a selected activity and display
information about the process as a whole in the detail tab window.

Chapter 7 - Page 13
• Double-click a subprocess activity icon to drill down and display the diagram of the
subprocess and its information in the detail tab window. You can also select the
subprocess activity icon and then choose Zoom In.
The process diagram is view-only. You cannot edit the diagram in the Status Monitor.
Detail Tab Window
• Definition: Displays the properties of the activity or process.

• Usage: Displays the properties for the activity as a node in the process.
• Status: Displays status and result information about the activity. Also shows error
information if the activity status is ERROR.
• Notification: Displays notification details for the selected notification activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 14
Viewing Responses in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Responses in the Administrator Monitor
Viewing
d
e
sh You can use the Monitor Responses page to drill down to responses to a particular notification.
Ra For example, you can use this page to view individual responses to a voting activity.
A hierarchical grid displays the process hierarchy formed by the selected workflow and any
child workflows associated with it.
To view and respond to a notification in the Notification Details page, click the subject link in
the Notification Subject column.
To send e-mail to the respondent for a notification, click the user link in the Respondent
column.
Notification Response Details
The Notification Response Details page displays the following:
• The subject line of the notification
• The user who responded to the notification
• The user to whom the notification was originally sent
• The date and time when the notification was sent
• The date and time when the response was received

Chapter 7 - Page 15
• The response value that is the result of the notification
• Whether the notification required an electronic signature
• Any further response values requested in the notification in addition to the result response
For a notification that required a signature, the page also displays further signature details.
To send e-mail to the respondent or original recipient for a notification, select the
corresponding user link.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 16
Viewing Workflow Details in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Details in the Administrator Monitor
Viewing
d
e
sh A hierarchical grid displays the process hierarchy formed by the selected workflow and any
Ra child workflows associated with it.
The Workflow Definition region displays the workflow type internal name, workflow type
description, the persistence type, number of persistence days, and the selector/callback function
that determines which process activity to run for the workflow type in a particular situation.
The Workflow Attributes region lists the names and values of the item attributes for the
workflow. For an attribute of type event, click the event message link to view the event
message details.
Updating Workflow Attribute Values
To change the values of any item attributes, click the Update Attributes button. In the Update
Workflow Attributes page, enter the new values you want and click Apply.
Note: You cannot update attributes of type event. However, you can click the event message
link to view the event message details.

Chapter 7 - Page 17
Viewing Error Information in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Error Information in the Administrator Monitor
Viewing
d
e
sh The Workflow Errors page displays the name of the activity that encountered an error, the
Ra activity type, the internal name of the error, the error message describing the error, and context
information to help you locate the source of the error.
Note: If you navigated to the Workflow Errors page from an error status link for a workflow,
the page shows details for each errored activity within the workflow. If you navigated to the
page from an error status link for a single errored activity, the page shows details for only that
activity.

Chapter 7 - Page 18
Viewing Child Workflows in the Administrator Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Child Workflows in the Administrator Monitor
Viewing
d
e
sh • To send e-mail to the owner of a workflow, click the user link in the Owned By column.
Ra • For an errored workflow, click the error icon or the error link in the Status column to view
error details.

Chapter 7 - Page 19
Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Self-Service Monitor
e
sh The self-service version of the Status Monitor lets you view and administer workflows that you
Ra own. You can:
• Review the notifications sent by a workflow
• Check the status of the workflow by viewing the status diagram
• Examine responses to notifications sent by the workflow
• If you have workflow administrator privileges, you can also perform certain control
operations for a workflow
Workflow Administrator Privileges
Users have workflow administrator privileges if they belong to the Oracle Workflow
administration role, which is defined in the Workflow Configuration Web page.

Chapter 7 - Page 20
Viewing Workflows in the Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflows in the Self-Service Monitor
Viewing
d
e
sh Use a Web browser to navigate to the self-service Status Monitor, using a responsibility and
• Workflow User Web Applications: Status Monitor
• Workflow User Web (New): Status Monitor
You can navigate to the self-service Status Monitor from other Oracle Workflow self-service
Web pages by selecting the Status Monitor tab or clicking the Status Monitor link at the end of
the page.
Searching for Workflows
In the Search region of the Workflows page, enter search criteria to locate the workflows you
want to display. The main search option is the workflow status.You can also search by the
workflow start date, workflow item type, and workflow identifier.
• All the start date ranges include the current date; for example, Last 2 Weeks includes
today as well as the previous thirteen days.

Chapter 7 - Page 21
• You can enter a partial value in the Workflow field to search for workflows whose
identifiers begin with that value.
Click the Go button to perform your search.
Viewing Workflows
For an errored workflow, click the error icon or the error link in the Status column to view
error details.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 22
Viewing Notification History in the Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Notification History in the Self-Service Monitor
Viewing
d
e
sh To send e-mail to the recipient of a notification, click the user link in the Notification Recipient
Ra column.

Chapter 7 - Page 23
Viewing a Status Diagram in the Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Status Diagram in the Self-Service Monitor
Viewing
d
e
sh Above the process diagram, the process title displays the workflow process name, type, and
Ra identifier. If you drill down to a subprocess in the process diagram, the process title displays
the subprocess name.
Process Diagram
• An activity can be highlighted with a colored box to indicate a distinctive state:
- Red: The activity is in an error state.
- Green: The activity is active or in progress.
- Yellow: The activity is suspended.
• A transition arrow can have a thick green line to indicate that it has been traversed, or it
can have a thin black line to indicate that it has not been traversed.
• Click an activity icon to display information about it in the detail tab window.
• Click any empty space in the diagram to deselect a selected activity and display
information about the process as a whole in the detail tab window.

Chapter 7 - Page 24
• Double-click a subprocess activity icon to drill down and display the diagram of the
subprocess and its information in the detail tab window. You can also click the subprocess
activity icon and then choose Zoom In.
The process diagram is view-only. You cannot edit the diagram in the Status Monitor.
Detail Tab Window
• Definition: Displays the properties of the activity or process.

• Usage: Displays the properties for the activity as a node in the process.
• Status: Displays status and result information about the activity. Also shows error
information if the activity status is ERROR.
• Notification: Displays notification details for the selected notification activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 25
Viewing Responses in the Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Responses in the Self-Service Monitor
Viewing
d
e
sh You can use the Monitor Responses page to drill down to responses to a particular notification.
Ra For example, you can use this page to view individual responses to a voting activity.
To send e-mail to the respondent for a notification, click the user link in the Respondent
column.
Notification Response Details
The Notification Response Details page displays the following:
• The subject line of the notification
• The user who responded to the notification
• The user to whom the notification was originally sent
• The date and time when the notification was sent
• The date and time when the response was received
• The response value that is the result of the notification
• Whether the notification required an electronic signature
• Any further response values requested in the notification in addition to the result response

Chapter 7 - Page 26
For a notification that required a signature, the page also displays further signature details.
To send e-mail to the respondent or original recipient for a notification, click the corresponding
user link.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 27
Viewing Error Information in the Self-Service Monitor
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Error Information in the Self-Service Monitor
Viewing
d
e
sh The Workflow Errors page displays the name of the activity that encountered an error, the
Ra activity type, the internal name of the error, and the error message describing the error.
Note: If you navigated to the Error Summary page from an error status link for a workflow, the
page shows details for each errored activity within the workflow. If you navigated to the page
from an error status link for a single errored notification activity, the page shows details for
only that activity.

Chapter 7 - Page 28
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 29
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 7 - Page 30
nse
li c e
ble
fe r a
a n s
o n-tr
Viewing anda nResponding to
ha s
Notifications eฺ
ฺ s a) Guid
e d uChaptern8t
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
A lha
d
she
Ra
Viewing and Responding to Notifications

Chapter 8 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 4
Viewing Notifications from a Web Browser
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 5
Worklist Pages
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Pages
Worklist
d
e
sh The Advanced Worklist is available by default from some of the seeded responsibilities in
Ra Oracle E-Business Suite. A system administrator can also add the Advanced Worklist to the
menu for another responsibility.
The Personal Worklist is not available on a seeded responsibility. Before you can access the
Personal Worklist, a system administrator must add it to the menu for an Oracle E-Business
Suite responsibility that is assigned to you.

Chapter 8 - Page 6
Advanced Worklist
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Worklist
Advanced
d
e
sh Use a Web browser to navigate to the Advanced Worklist, using a responsibility and
• Workflow User Web Applications: Advanced Worklist
• Workflow User Web Applications: Notifications
• Workflow User Web (New): Notifications
• Workflow Administrator Web Applications: Notifications
• Workflow Administrator Event Manager: Notifications
• Workflow Administrator Web (New): Notifications
You can also navigate to the Advanced Worklist from other Oracle Workflow Web pages by
selecting the Notifications tab or clicking the Notifications link at the end of the page, if you
are viewing the page in the context of an Oracle Workflow responsibility.
Accessing Notifications from the Advanced Worklist
• In the View pull-down menu, you can choose to view:
- Open Notifications

Chapter 8 - Page 7
- FYI Notifications
- To Do Notifications
- All Notifications
- Notifications From Me
• To define vacation rules, click the Vacation Rules link.
• To grant access to your worklist to another user, click the Worklist Access link.
• To view another user’s worklist, click the Switch User button. On the Switch User page,
select the user whose worklist you want to view. If a user granted you access only to
selected item types, then when you view that user's worklist, the page displays only
notifications that belong to those item types.
• To collectively reassign a group of notifications, select the notifications you want and
click the Reassign button. The Reassign button may be replaced by the Delegate button or e
the Transfer button, depending on the access you have been assigned in the WF:
c e ns
Notification Reassign Mode profile option. e li
- The Reassign button appears if you have access to reassign notifications to another r a bl
user either by delegating the notifications or by transferring complete ownership of n sfe
a
the notifications.
no
- The Delegate button appears if you only have access to delegate the notifications.
n-tr
a
) h as deฺ
- The Transfer button appears if you only have access to transfer ownership of the
notifications.
u ฺ sa t Gui
•
s t ฺed uden
To respond to a group of notifications collectively, select the notifications you want and
select the Respond button. The Respond button appears only if your workflow
k ac is St
administrator has enabled it. The notifications must all belong to the same workflow type
a j ri@ e th
and message definition so that the response values you provide will match all the
r a lh o us
notifications in the group.You can only use the Respond button to respond to notifications
ri ( t
that are open, require a response, do not require a digital signature, and do not contain a
j
lh a
request from another user for more information about another notification.
d •
A To collectively close a group of FYI notifications, select the notifications you want and
sh e select the Close button. In the confirmation page, choose Apply. You can only use the
Ra Close button to close notifications that are open and do not require a response.
• If you select more than one notification to open, only one notification is displayed at a
time. You can navigate among the open notifications by clicking the Next or Back buttons
on the Notification Details page.

Chapter 8 - Page 8
Notification Details
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Notification Details
e
sh • You can access the Notification Details page from the Advanced Worklist, from the
Ra Personal Worklist, or from e-mail notifications.
• In Oracle E-Business Suite, nonstructured data such as images, spreadsheets, or video can
be linked to structured application data, including Oracle Workflow notifications seeded
by other Oracle E-Business Suite applications. If a notification includes such Oracle E-
Business Suite attachments, the notification header displays an Attachment(s) heading
with links to the attachments. Click a link to view the attached data.
• The message body may include embedded links to additional information sources
pertinent to the notification. A reference URL link connects to a specified URL, either in
the same Web browser window or in a new window, depending on the notification.
• The Related Applications section may include attachment icons. These icons link to
additional information sources for the notification. There are three types of attachment
links:
- A reference URL link that connects to a specified URL.

Chapter 8 - Page 9
- A PL/SQL, PL/SQL CLOB, or PL/SQL BLOB document link that displays the
contents of a document generated from a PL/SQL function. Such documents can
contain text, HTML, images, or application files such as PDF or RTF documents.
- An Oracle E-Business Suite form link that drills down to an Oracle E-Business Suite
form or Oracle Application Framework page.
Note: You must use a responsibility with the appropriate security to open a linked
form or Oracle Application Framework page. If the form link or URL link is defined
to use a particular responsibility, you must have that responsibility assigned to you to
open the form or page. Otherwise, Oracle E-Business Suite displays a list from which
you can select the responsibility you want to use.
• If you want to view your next notification on the Notification Details page after
responding to this notification, select the Display Next Notification After My Response
check box. Otherwise, Oracle Workflow displays your worklist after you respond to a e
notification.
c e ns
• Use the Response section to act on the notification. e li
- If a notification requires a response, but none of the responses affect the result of the r a bl
notification activity, enter your response values and submit your response by clicking n sfe
a
Submit.
no n-tr
- If a notification requires a response with a result, enter your response values and click
a
) h as deฺ
the button for the result value you want, or if there are more than four result values,
u ฺ sa t Gui
enter your response values, select the result value you want from the pull-down menu,
and submit your response by clicking Submit.
s t ฺed uden
- The Response section can also display an attached form icon that lets you drill down
k ac is St
to an Oracle E-Business Suite form to complete your response.
j ri@ e th
- If a notification does not require a response, click the Close button when you have
a
a lh o us
finished reviewing it so that it does not appear in your worklist the next time you
r
j ri ( t
view your open notifications.
lh a
d A - If you want another user to respond to the notification instead of you, click the
she Reassign button. The Reassign button may be replaced by the Delegate button or the
Ra Transfer button, depending on the access you have been assigned in the WF:
Notification Reassign Mode profile option.
- To request more information about this notification from another user or role, click
the Request Information button.
- If another user sent you this notification with a request for more information, the
Response section displays the user who made the request and the request details.
Enter the information you want to provide and click Submit.
• If this notification requires a password-based electronic signature, a confirmation page
appears after you submit your response. This page displays notification header
information and the response values that you entered to let you review the response you
are signing. If the notification requires the signed response to include the message body,
then the confirmation page also displays the message body for you to review. To affix
your electronic signature to your response, enter your Oracle E-Business Suite user name
and password and click Submit.

Chapter 8 - Page 10
• If this notification requires a certificate-based digital signature, a confirmation page
appears after you submit your response. This page displays notification header
information and the response values that you entered to let you review the response that
you are signing. If the notification requires the signed response to include the message
body, then the confirmation page also displays the message body for you to review. Click
the Sign button and use your Web browser to enter your X.509 certificate as your
signature. For detailed instructions, please refer to the online help for your Web browser.
If you have multiple certificates installed, ensure that you enter a certificate that is
assigned to the Oracle E-Business Suite user name with which you logged in.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 11
Reassigning Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Reassigning Notifications
e
sh Navigate to the Reassign Notifications page by one of the following methods:
Ra • In the Advanced Worklist or Personal Worklist, select one or more notifications and
choose the Reassign button.
• On the Notification Details page for a single notification, click the Reassign button.
• Choose to reassign a notification from the Status Monitor.
The Reassign button may be replaced by the Delegate button or the Transfer button, depending
on the access you have been assigned in the WF: Notification Reassign Mode profile option.
The assignee types correspond to the originating system partitions in the Oracle Workflow
directory service.
If you have access either to delegate or transfer notifications, select one of these reassign
modes on the Reassign Notifications page to specify how you want to reassign the notification.
• “Delegate your response”: Select this option if you want to give the new user authority to
respond to the notification on your behalf, but you want to retain ownership of the
notification yourself. For example, a manager might delegate all vacation scheduling
approvals to an assistant.

Chapter 8 - Page 12
• “Transfer notification ownership”: Select this option if you want to give the new user
complete ownership of and responsibility for the notification. For example, use this option
if you should not have received the notification and you want to send it to the correct
recipient or to another recipient for resolution.
Note: If you only have access to one reassign mode, Oracle Workflow automatically uses that
mode (either delegate or transfer) when you reassign notifications.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 13
Responding to a Group of Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Responding to a Group of Notifications
e
sh Navigate to the Respond to Notifications as Group page by selecting one or more notifications
Ra in the Advanced Worklist or Personal Worklist and choosing the Respond button.
To view the full details of a notification and act on the notification individually, click the
subject link for the notification.
The Respond to Notifications as Group page does not display any default values for the
response prompts. You must enter the response values you want to submit. The response that
you enter is applied to all the selected notifications.
• If the notifications require a response, but none of the responses affect the result of the
notification activity, enter your response values and submit your response by clicking Go.
• If the notifications require a response with a result, enter your response values and click
the button for the result value you want, or if there are more than four result values, enter
your response values, select the result value you want from the pull-down menu, and
submit your response by clicking Go.

Chapter 8 - Page 14
Requesting More Information
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Requesting More Information
e
sh You can choose to request information from another user or role previously involved in this
Ra workflow process, or from any user listed in the Oracle Workflow directory service. When you
select the Any User option, you first select a type of user, and then select the user you want
within that type. The user types correspond to the originating system partitions in the Oracle
Workflow directory service.

Chapter 8 - Page 15
Certificate-Based Digital Signatures
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Certificate-Based Digital Signatures
e
sh To set up for certificate–based digital signatures:
Ra • Obtain an X.509 certificate and private key from a certificate authority. The certificate and
key should be provided in a PKCS 12 file with an extension of .p12 or .pfx .
• Obtain the certificate authority’s root certificate and any intermediate certificates required
for your type of certificate. Also, for each root and intermediate certificate, obtain a URL
specifying the location from which the corresponding Certificate Revocation List (CRL)
can be downloaded. If your system administrator has already obtained and installed the
root certificate for your certificate authority and the intermediate certificates for your type
of certificate, you can skip this step.
• Load the file containing your personal certificate and key onto the file system of your
client PC, and import the certificate into your browser. For detailed instructions, please
refer to the online Help for your browser.
• Use the certificate management functions in your browser or operating system to export
your personal certificate in the DER encoded binary X.509 format, as a file with an
extension of .cer.

Chapter 8 - Page 16
• Give your system administrator the exported file for your personal certificate, as well as
the root certificate for your certificate authority and the intermediate certificates for your
type of certificate, if necessary. The system administrator must load these certificates into
Oracle E-Business Suite.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 17
Granting Worklist Access
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Worklist Access
Granting
d
e
sh The worklist access feature lets you allow another user to handle your notifications without
Ra giving that user access to any other privileges or responsibilities that you have in Oracle E-
Business Suite. However, note that a user who has access to your worklist can view all the
details of your notifications and take most actions that you can take on the notifications. Ensure
that you take all necessary security considerations into account when you choose to grant
worklist access to another user.
If another user has granted you access to his or her worklist, you can switch the Advanced
Worklist or Personal Worklist to display that user’s notifications instead of your own.
• Your own assigned notification reassign mode still applies when you are viewing another
user’s worklist.
• If the other user has a notification marked as being sent from you, you can only view that
notification and cannot take any action on it. For example, you cannot respond to a
notification that you reassigned to the other user, nor to a notification marked as being
sent from you by the special #FROM_ROLE message attribute, such as an expense report
that is marked as having been submitted by you. (However, if you have workflow

Chapter 8 - Page 18
administrator privileges, those privileges override this restriction so that you can respond
to all notifications, even notifications from you.)
• You cannot define vacation rules for the user whose worklist you are viewing. You also
cannot grant access to that user’s worklist to anyone else.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 19
Granting Worklist Access
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Worklist Access
Granting
d
e
sh Navigate to the Worklist Access page by navigating to the Advanced Worklist or Personal
Ra Worklist and clicking the Worklist Access link.
• If a user has an e-mail address defined in Oracle E-Business Suite, you can click the link
in the User Name column to send e-mail to that user.
• The start and end dates for each user determine the access period when the user can view
and act on your worklist. The user’s active or inactive status depends on whether the
current date is within the access period. Leave the end date blank to grant access
indefinitely.
• If you are granting access only to selected item types, select the item types you want in the
Available Item Types list and move them to the Selected Item Types list. By default, the
Available Item Types list displays those item types for which you have previously
received at least one notification. Your workflow administrator can also add item types to
this list to let you grant a user access to handle other notifications that you may receive in
the future.

Chapter 8 - Page 20
• To update the description for a user, the start and end dates of the user's access period, or
the item types to which the user has access, click the Update icon for that user and enter
your changes.
• To revoke a user’s access, click the Delete icon for that user. The user will no longer have
access to your worklist, even if the user’s access status was previously Active.
Note: When you delete a user, the record of the user’s access no longer appears in your
Worklist Access page. If you want to keep this record for reference, you can simply set the end
date to end the user’s access, rather than deleting the user.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 21
Administrator Search for Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Administrator Search for Notifications
e
sh Navigate to the Notifications page by selecting the Administration tab on the Oracle Workflow
Ra administrator home page and selecting Notification Search in the horizontal navigation.
You must have workflow administrator privileges to access other users’ notifications on the
Notifications page. If you do not have administrator privileges, you can only search for and
access your own notifications. Workflow administrator privileges are assigned on the
Workflow Configuration page.
Searching for Notifications
The following search criteria are available only if you have workflow administrator privileges:
• Notification ID: If you specify a notification ID, all other search criteria are ignored.
• Owner
• To: Usually, the Owner role and the To role for a notification are the same. However, you
can specify different roles in the Owner field and the To field to search for notifications
that were reassigned in Delegate mode.
The following search criteria are always available:
• From

Chapter 8 - Page 22
•Status
•Workflow Type
•Type Internal Name
•Subject: This field is case-sensitive. You can use the percent sign (%) as a wildcard
character.
• Sent: All the sent date ranges include the current date. For example, Last 2 Weeks
includes today as well as the previous 13 days.
• Due Date: All the due date ranges include the current date.
• Priority
If you have workflow administrator privileges, you must enter at least one of the following
criteria when you search in order to limit the size of the results list.
• Notification ID
nse
• Owner
li c e
• To ble
• From fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 23
Reviewing Electronic Signature Details
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Electronic Signature Details
Reviewing
d
e
sh Navigate to the Electronic Signature page by selecting the Administration tab on the Oracle
Ra Workflow administrator home page and selecting Signature Evidence Store in the horizontal
navigation.
You can only review signatures for notifications that have not been purged.
Searching for Signatures
The following search criteria are available:
• Notification ID: If you specify a notification ID, all other search criteria are ignored.
• Signature Policy: The policy that identifies the type of signature and signed text required
by the notification.
• Requested Signer
• Status
• Creation Date: The date when the request for a signature was created.
• Signed Date: The date when the user submitted the signature.

Chapter 8 - Page 24
• Verified Date: The date when Oracle Workflow confirmed that the signature was well
formed, that it was created with a private key corresponding to the offered signing
certificate, and that it signed the plain text that it purported to sign.
• Last Validation Date: The most recent date when Oracle Workflow attempted to check
that the certificate used to create the signature was valid at the time the signature was
received.
• Validated Complete Date: The date when Oracle Workflow successfully validated the
signature against a certificate revocation list issued by the certificate authority after the
time the signature was received.
You must enter at least one of the following criteria when you search in order to limit the size
of the results list.
• Notification ID
• Requested Signer nse
• Creation Date li c e
• Signed Date ble
fe r a
• Verified Date
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 25
Personal Worklist
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Worklist
Personal
d
e
sh The Personal Worklist is not available on a seeded responsibility. Before you can access the
Ra Personal Worklist, a system administrator must add it to the menu for an Oracle E-Business
Suite responsibility that is assigned to you. Then you can use a Web browser to navigate to the
Personal Worklist in that responsibility.
• From the Simple Search page, you can also navigate to the Advanced Search page.
• In the View pull-down menu, you can choose from the preconfigured views, or you can
create your own personalized views to display notifications that match criteria that you
specify. The views that are available may depend on the responsibility through which you
access the Personal Worklist.
• To collectively reassign a group of notifications, select the notifications you want and
click the Reassign button. The Reassign button may be replaced by the Delegate button or
the Transfer button, depending on the access you have been assigned in the WF:
Notification Reassign Mode profile option.
• To respond to a group of notifications collectively, select the notifications you want and
select the Respond button.

Chapter 8 - Page 26
• To collectively close a group of FYI notifications, select the notifications you want and
select the Close button. In the confirmation page, choose Apply.
• To define vacation rules, click the Vacation Rules link.
• To grant access to your worklist to another user, click the Worklist Access link.
• To view another user’s worklist, click the Switch User button. On the Switch User page,
select the user whose worklist you want to view. If a user granted you access only to
selected item types, then when you view that user's worklist, the page displays only
notifications that belong to those item types.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 27
Simple Search for Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Search for Notifications
Simple
d
e
sh You can search for notifications by subject, from role, and sent date. You can enter a partial
Ra value for the subject or from role to search for notifications whose subjects or from roles
contain those values, respectively. The Subject and From fields are case-insensitive.
When you have displayed a set of notifications on the Simple Search page, you can open,
reassign, respond to, or close those notifications, define vacation rules, or grant access to your
worklist to another user, as in the Personal Worklist.
To navigate back to the Personal Worklist, click the Worklist Views button.

Chapter 8 - Page 28
Advanced Search for Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Search for Notifications
Advanced
d
e
sh The following search options are displayed by default: Subject, From, Message Attribute, and
Ra Sent. To display additional search options, select the notification property you want from the
Add Another pull-down menu and click Add.
For each search option, select a filter operator and then enter a filter value to specify the
notifications you want to display.
• For the is filter operator, you should enter a complete filter value that you want to match.
• For the other filter operators, you can enter a partial value, unless you are using the Sent,
Due, and Closed search options, which always require a complete date in the date format
you chose in your Oracle E-Business Suite general preferences.
• The filter value fields for all search options are case insensitive.
If you leave the filter operator and filter value blank for a search option, that option will not be
included in the search.
Note: The greater than, less than, after, and before filter operators are not
inclusive. For example, a search on the Sent option with the after operator displays only
notifications sent after the date you specify, not notifications sent on that date itself.

Chapter 8 - Page 29
• Subject: Enter the subject line of the notifications.
• From: Enter the role from which the notifications were sent.
• Message Attribute: Enter the value of a message attribute belonging to the notification.
Message attribute values can be numbers, dates, or text.
• Sent: Enter the date when the notifications were delivered.
• Type: Enter the display name of the item type to which the workflow process that sent the
notification belongs.
• Status: Enter open, closed, or canceled as the notification status.
• To: Enter the role to which the notifications were sent.
• Information Requested From: Enter the role to which notifications that are requests for
more information were sent.
• Due: Enter the date by which the notifications should be completed.
nse
• Closed: Enter the date when the notifications were closed or canceled. li c e
• Priority: Enter high, normal, or low as the notification priority. ble
fe r a
• Response Required: Enter yes or no to specify whether the notifications require a s
a n
n-tr
response from the recipient.
no
• FYI: Enter yes or no to specify whether the notifications are for your information (FYI)
a
only and do not require a response.
) h as deฺ
u ฺ sa t Gui
• Notification ID: Enter the numerical notification identifier.
• From Me: Enter yes or no to specify whether the notifications are sent from you.
s t ฺed uden
• Type Internal Name: Enter the internal name of the item type to which the workflow
k ac is St
process that sent the notification belongs.
a j ri@ e th
• Message Name: Enter the internal name of the message sent by the notification.
r a lh o us
When you have displayed a set of notifications on the Advanced Search page, you can open,
j ri ( t
a
reassign, respond to, or close those notifications, define vacation rules, or grant access to your
lh
A
worklist to another user, as in the Personal Worklist.
d
she To navigate back to the Personal Worklist, click the Worklist Views button.
Ra

Chapter 8 - Page 30
Creating a Personal Worklist View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Personal Worklist View
Creating
d
e
sh You can also navigate to the Create View page by clicking Save Search on the Simple Search
Ra or Advanced Search pages.
The Personalize Views page displays all existing views for the role you are logged in as,
including both preconfigured views provided by Oracle Workflow and your personalized
views.
• In the Display View column for a personalized view, select Yes to include the view in the
View menu in the Personal Worklist, or select No to exclude the view from the View
menu. Then click Apply.
Note: Preconfigured views always appear in the View menu. You cannot change this
setting for those views.
• To update a view, click the icon in the Update column for that view.
• To delete a view, click the icon in the Delete column for that view.
Note: You can update and delete only personalized views that you created. You cannot
update or delete preconfigured views.

Chapter 8 - Page 31
• To create a view that is a duplicate of an existing view, select the existing view that you
want to copy and click the Duplicate button.
Create View/Update View/Duplicate View
• Enter a display name to identify your personalized view.
• Select the number of notification rows you want to display in the view.
• If you want to make this view your default view, select the Set as Default check box. Only
one view can be set as the default at any time, so if you select Set as Default for the
current view, this option is automatically deselected for any view you previously set as the
default.
• Enter an optional description for the view.
• In the Column Properties region, specify the notification property columns you want to
display in the view and the order in which to display them.
- To add a column to the view, select the column in the Available Columns list and nse
click the Move button. You can also click the Move All button to add all available li c e
columns. ble
fe r a
- To remove a column from the view, select the column in the Columns Displayed list
a n s
and click the Remove button. You can also click the Remove All button to remove all
the columns. no n-tr
a
) h as deฺ
- To specify the order in which the columns are displayed, select a column in the
Columns Displayed list and use the top, up, down, or bottom arrow buttons to move
ฺ sa t Gui
the column to the position you want in the list.
u
t ฺed uden
• If you want to change the display names for the notification property columns in the view,
s
ac is St
click the Rename Columns/Totaling button. In the Rename Columns/Totaling page, enter
k
a j ri@ e th
the new name for each column and click Apply.
r a lh o us
• In the Sort Settings region, you can specify up to three levels of sorting for the
ri ( t
notifications in the view. For each level of sorting, select the notification property column
j
lh a
by which you want to sort and specify whether to sort in ascending or descending order.
d A
• Specify whether notifications must meet all or only one of your search criteria to be
she displayed.
Ra • The search criteria you can specify to locate notifications to display in the view are similar
to the search criteria in the Advanced Search page.

Chapter 8 - Page 32
Viewing Notifications Through E-mail
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Notifications through E-mail
Viewing
d
e
sh Set your notification preference in the Preferences page in Oracle E-Business Suite.
Ra • Plain text mail: The notification message appears as plain text, with no attachments. If the
message requires a response, you can respond by replying to the e-mail message. If the
notification message has “Content–Attached” URL or document message attributes
(meaning the Attach Content check box was selected when the attributes were defined in
the Workflow Builder), they are included as plain text. Note that this may render some
attachments unreadable if the attachment includes special formatting or your plain text e-
mail reader does not recognize attachments. To view these attachments, you should
display your notifications in the Notification Details page.
• HTML mail: The notification message appears as HTML-formatted text, with no standard
attachments. If the notification message has “Content–Attached” message attributes;
however, these attributes appear as attachments to the message. If the message requires a
response, you can respond by clicking one of the response links.
• Plain text mail with HTML attachments: The notification message appears as plain text,
with at least two other attachments. One attachment is an HTML–formatted version of the
message, and the other is a link to the notification in the Notification Details page. If the

Chapter 8 - Page 33
notification message has “Content–Attached” message attributes, these attributes appear
as additional attachments to the message. If the message requires a response, you can
respond by replying to the e-mail message or by opening the HTML-formatted version of
the message and clicking one of the response links, or you can navigate to the Notification
Details page and respond there.
• HTML mail with attachments: The notification message appears as HTML-formatted text,
with at least one other attachment that is a link to the notification in the Notification
Details page. If the notification message has “Content–Attached” message attributes, these
attributes appear as additional attachments to the message. If the message requires a
response, you can respond by clicking one of the response links, or you can navigate to the
Notification Details page and respond there.
Note
• If you view your notifications through e-mail, you can only reassign a notification by e
using the Forward function in your e-mail client, which performs similarly to the Delegate
c e ns
reassign mode. e li
• Oracle E-Business Suite form attributes cannot be attached to e-mail notifications. To r a bl
view form attachments, you must view the notification in the Notification Details page. n sfe
a
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 34
E-mail Response Methods
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Response Methods
E-mail
d
e
sh The Notification System interprets your response values in a case-sensitive manner.
Ra

Chapter 8 - Page 35
HTML-Formatted E-mail Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh The response template consists of the required notification ID and access key that identify the
Ra notification you are responding to and a response prompt edited with your selected result
response. Depending on the notification, the autogenerated e-mail response template may also
prompt you for other information in addition to your selected result response. Supply responses
by editing the response value text between the quotes following each response prompt.
If this notification includes sensitive content that cannot be sent in e-mail for security reasons,
the notification e-mail message directs you to access the online version of the notification
instead. Navigate to the Notification Details page to view the content of the notification and
submit your response.
• In addition to the response links, an HTML-formatted notification can also include a
Request Information link to request more information about the notification from another
user before you respond to the notification. The Request Information link automatically
generates a plain text e-mail reply. The reply contains the correct Reply To: e-mail address
as well as a request template in the message body. The request template contains the
required notification ID and access key that identify the notification you are responding to.
It also contains a prompt for you to enter the user from whom you want to request

Chapter 8 - Page 36
information, along with a list of users who have previously participated in the workflow
process, and a prompt for you to enter the question you want to ask that user.
• If another user sent you this notification with a request for more information, click the
response link and enter the information you want to provide between the quotes following
the response prompt.
• If this notification requires a password-based signature or a certificate-based digital
signature in your response, you cannot respond to the notification through e-mail. In this
case the notification informs you that an electronic signature is required and directs you to
access the online version of the notification instead. Navigate to the Notification Details
page to submit your response. Depending on the configuration of your Oracle Workflow
installation, the notification may include a "Click here to respond" link that you can click
to navigate to the Notification Details page. You must log in to Oracle E-Business Suite
before you can access the Notification Details page. e
c e ns
e li
r a bl
n sfe
a
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 37
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 38
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
AText E-mail Notifications Using Templated Response
Plain
d
e
sh If your mail application includes an editable copy of the original message when it generates the
Ra reply message, you can use that copy to enter your response values. Otherwise, copy and paste
from the original message to obtain a copy of the response template that you can edit.
• If another user sent you this notification with a request for more information, include the
response template in your reply and insert your response values between the quotes
following the response prompt.
• If this notification requires a password-based signature or a certificate-based digital
signature in your response, you cannot respond to the notification through e-mail. In this
case the notification informs you that an electronic signature is required and directs you to
access the online version of the notification instead. Navigate to the Notification Details
page to submit your response.

Chapter 8 - Page 39
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 40
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
AText E-mail Notifications Using Direct Response
Plain
d
e
sh If a response value requires more than one line, enclose the entire response value in double
Ra quotes. If a response prompt provides a default value, then you can accept the default value by
leaving the appropriate response line blank.
If this notification requires a password-based signature or a certificate-based digital signature
in your response, you cannot respond to the notification through e-mail. In this case the
notification informs you that an electronic signature is required and directs you to access the
online version of the notification instead. Navigate to the Notification Details page to submit
your response.

Chapter 8 - Page 41
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 42
Viewing an E-mail Summary of Notifications
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A an E-mail Summary of Notifications
Viewing
d
e
sh Your workflow administrator determines how frequently summary notifications are sent when
Ra setting up a notification mailer.
The plain text and HTML-formatted versions of the e-mail notification summary are based on
the Workflow Summary Mail (HTML) template defined in the System: Mailer item type. To
view the details of a notification or respond to or close the notification, you should use the
Worklist Web pages. In the HTML-formatted version of the summary, you can click a subject
link to navigate directly to the Notification Details page for that notification. The HTML-
formatted summary also includes a link to the Worklist page, from which you can access all
your notifications.

Chapter 8 - Page 43
Vacation Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Notification Processing
Automatic
d
e
sh Each time a notification is sent to you, Oracle Workflow tests the notification against your
Ra vacation rules.
• First, Oracle Workflow checks whether you have any active rules for that specific message
type.
• If not, it checks whether you have any active rules for that specific item type.
• Finally, it checks whether you have any active rules for messages of all item types.
As soon as it finds a match, Oracle Workflow applies the rule and discontinues any further rule
matching.
If a rule reassigns a notification, Oracle Workflow performs rule matching again against the
new recipient’s list of rules. Oracle Workflow maintains a count of the number of times it
forwards a notification to detect perpetual forwarding cycles. If a notification is automatically
forwarded more than ten times, Oracle Workflow assumes that a forwarding cycle has occurred
and ceases executing any further forwarding rules, marking the notification as being in error.

Chapter 8 - Page 44
Maintaining Vacation Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Maintaining Vacation Rules
e
sh The list of your vacation rules includes rules that you defined yourself as well as any rules
Ra defined for you by an administrator. A rule’s active or inactive status depends on whether the
current date falls within the rule’s effective dates.

Chapter 8 - Page 45
Defining Vacation Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Vacation Rules
Defining
d
e
sh Vacation Rule: Item Type
Ra • By default, the list of values for the Item Type field displays those item types for which
you have previously received at least one notification. Your workflow administrator can
also add item types to this list to let you create vacation rules to handle other notifications
you may receive in the future.
• If your workflow administrator has enabled creating generic vacation rules, you can select
the All option in the Item Type field. In this case the rule to applies to notifications
associated with any item type.
Vacation Rule: Notification
• Messages are listed by subject name.
• Select All if you want the rule to apply to all messages within the selected item type.
• Skip this step if you selected All as the item type.
Vacation Rule: Response
• The options in this page vary depending on the item types and messages to which each
rule applies.

Chapter 8 - Page 46
• If you leave the Start Date field blank, the rule is effective immediately. If you leave the
End Date field blank, the rule is effective indefinitely.
Note: Ensure that rules for the same notifications do not overlap in their effective dates. If
multiple rules are effective for the same notification, Oracle Workflow picks one rule at
random to apply.
• The comments you enter in the Message field appear in a special comments field when the
notification is reassigned or automatically responded to.

• You can choose the following actions:
- “Reassign”: Forward the notification to a designated user.
- “Respond”: Respond to the message with a set of predefined response values.
- “Deliver notifications to me regardless of any general rules”: Leave the notification in
your worklist with no automatic processing. You can define a rule with this action to
exclude a certain subset of notifications from a more encompassing rule. nse
• If your rule action is “Reassign,”, select the type of user to whom you want to reassign the li c e
notifications. Then select the user you want within that type. Finally, specify whether you ble
fe r a
want to delegate or transfer the notifications. s
a n
Note: The assignee types correspond to the originating system partitions in the Oracle
Workflow directory service. no n-tr
a
automatically respond. ) h as deฺ
• Then If your rule action is “Respond,” set the values with which you want to
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 47
Defining Vacation Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Vacation Rules
Defining
d
e
sh Navigate to the Vacation Rules page by selecting the Administration tab from the Oracle
Ra Workflow administrator home page and selecting Vacation Rules in the horizontal navigation.
You must have workflow administrator privileges to define vacation rules for other users in the
Vacation Rules page. Workflow administrator privileges are assigned in the Workflow
Configuration page.

Chapter 8 - Page 48
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 49
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 8 - Page 50
nse
li c e
ble
fe r a
a n s
o n-tr
Worklist Flexfields
an
) h as deฺ
Chapter 9
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 2
Worklist Flexfields
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 4
Worklist Flexfields
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Flexfields
Worklist
d
e
sh Note: Worklist flexfields are separate from the key flexfields and descriptive flexfields used in
Ra Oracle E-Business Suite. For information about key and descriptive flexfields, see the Oracle
Applications Flexfields Guide.
Worklist Flexfields
Chapter 9 - Page 5
Benefits of Worklist Flexfields
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A of Worklist Flexfields
Benefits
d
e
sh For example, if an expense notification includes message attributes for the expense total and
Ra purpose, you can map these message attributes to worklist flexfields. You can then define a
worklist view that includes only expense notifications and that displays the expense total and
purpose for each notification alongside the standard notification properties, such as the subject
line and sent date.
Worklist Flexfields
Chapter 9 - Page 6
Defining a Specialized Worklist View Using Worklist Flexfields
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Specialized Worklist View Using Worklist Flexfields
Defining
d
e
sh Users must have access to the Personal Worklist to take advantage of a specialized worklist
Ra view. Ensure that you have added the Personal Worklist to a responsibility and assigned that
responsibility to any users who need to access the specialized worklist view.
Worklist Flexfields
Chapter 9 - Page 7
Message Attributes in Worklist Flexfields Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Attributes in Worklist Flexfields Rules
Message
d
e
sh • If a respond message attribute has a default value, the corresponding worklist flexfield
Ra displays that value while the notification is open.
• When displayed in a Personal Worklist view, a form attribute appears as a form icon that
drills down to the specified Oracle E-Business Suite form or Oracle Self-Service Web
Applications page. Users must use a responsibility with the appropriate security to open a
linked form or Oracle Application Framework page.
• When displayed in a Personal Worklist view, a URL attribute appears as a URL icon that
links to the specified URL.
• A message attribute of type date must have the following format to be used in a worklist
flexfields rule: dd-mon-yyyy hh24:mi:ss
The Personal Worklist requires date attributes to be stored in this format to display them
properly according to each user's preference.
Worklist Flexfields
Chapter 9 - Page 8
How Worklist Flexfields Rules Operate
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 9
Phase Numbers
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Numbers
Phase
d
e
sh Do not assign the same phase number to more than one rule for the same item type. To ensure
Ra that the rules you want take effect, assign a different phase number to each rule for an item
type.
Worklist Flexfields
Chapter 9 - Page 10
Customization Levels
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 11
Core Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
CoreARules
e d
sh Although core rules cannot override or be overridden by limit and user rules, it is possible for a
Ra core rule with a higher phase number to override a core rule for the same item type with a
lower phase number.
Core rules can map the following worklist flexfields columns.
• Data type: Text
- PROTECTED_TEXT_ATTRIBUTE1
Worklist Flexfields
Chapter 9 - Page 12
• Data type: Number
- PROTECTED_NUMBER_ATTRIBUTE1
• Data type: Form
- PROTECTED_FORM_ATTRIBUTE1
- PROTECTED_FORM_ATTRIBUTE4 nse
li c e
- PROTECTED_FORM_ATTRIBUTE5 e
• Data type: URL r a bl
- PROTECTED_URL_ATTRIBUTE1 n sfe
a
- PROTECTED_URL_ATTRIBUTE2
no n-tr
- PROTECTED_URL_ATTRIBUTE3 a
- PROTECTED_URL_ATTRIBUTE4 ) h as deฺ
- PROTECTED_URL_ATTRIBUTE5 u ฺ sa t Gui
• Data type: Date s t ฺed uden
k ac is St
- PROTECTED_DATE_ATTRIBUTE1
j ri@ e th
a
a lh o us
r
j ri ( t
a
lh
d A - PROTECTED_DATE_ATTRIBUTE5
she
Ra
Worklist Flexfields
Chapter 9 - Page 13
Limit and User Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Aand User Rules
Limit
d
e
sh Limit rules and user rules can map the following worklist flexfields columns.
Ra • Data type: Text
- TEXT_ATTRIBUTE1
- TEXT_ATTRIBUTE2
- TEXT_ATTRIBUTE3
- TEXT_ATTRIBUTE4
- TEXT_ATTRIBUTE5
- TEXT_ATTRIBUTE6
- TEXT_ATTRIBUTE7
- TEXT_ATTRIBUTE8
- TEXT_ATTRIBUTE9
- TEXT_ATTRIBUTE10
• Data type: Number
- NUMBER_ATTRIBUTE1
Worklist Flexfields
Chapter 9 - Page 14
- NUMBER_ATTRIBUTE2
- NUMBER_ATTRIBUTE3
- NUMBER_ATTRIBUTE4
- NUMBER_ATTRIBUTE5
• Data type: Form
- FORM_ATTRIBUTE1
- FORM_ATTRIBUTE2
- FORM_ATTRIBUTE3
- FORM_ATTRIBUTE4
- FORM_ATTRIBUTE5
• Data type: URL
- URL_ATTRIBUTE1 nse
li c e
- URL_ATTRIBUTE2 e
- URL_ATTRIBUTE3 r a bl
- URL_ATTRIBUTE4 n sfe
a
- URL_ATTRIBUTE5
no n-tr
• Data type: Date a
- DATE_ATTRIBUTE1 ) h as deฺ
- DATE_ATTRIBUTE2 u ฺ sa t Gui
- DATE_ATTRIBUTE3 s t ฺed uden
- DATE_ATTRIBUTE4 k ac is St
- DATE_ATTRIBUTE5
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 15
Limit and User Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 16
Combining Core, Limit, and User Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Combining Core, Limit, and User Rules
e
sh • If a core rule does not meet your requirements, you can choose not to include its message
Ra attributes in your views. However, Oracle Workflow still stores the message attributes in
the mapped columns.
• If a limit rule does not meet your requirements and you want to override some of its
mappings while allowing others to take effect, define a user rule that maps the attributes
you want to the relevant columns in place of the attributes you do not need. If you no
longer want any mappings from a limit rule to take effect, disable that rule.
• While defining a user rule, you can check whether its column mappings conflict with any
existing rules for the same item type, and whether the new rule will override or be
overridden by the conflicting rules. Review each conflict to decide whether to accept the
current overrides or update the rule definitions to make a different rule take effect.
Worklist Flexfields
Chapter 9 - Page 17
Worklist Flexfields Rules Example
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Flexfields Rules Example
Worklist
d
e
sh This example uses the sample Requisition item type. For more details about this sample item
Ra type, see: The Requisition Item Type, Oracle Workflow Developer's Guide.
Suppose a core rule named EXC01 is seeded for the Requisition item type with a phase of 50
and the following column mapping:
• PROTECTED_TEXT_ATTRIBUTE1 column : Requisition Number attribute
Also, suppose a limit rule named EXL02 is seeded for the Requisition item type with a phase
of 60 and the following column mappings:
• TEXT_ATTRIBUTE1 column : Requisition Description attribute
• NUMBER_ATTRIBUTE1 column : Requisition Amount attribute
You prefer to display the Note attribute instead of the Requisition Description attribute, and
you also want to display the Monitor URL attribute. To do so, you define a user rule named
EXU03 for the Requisition item type with a phase of 110 and the following column mappings:
• TEXT_ATTRIBUTE1 column : Note attribute
• URL_ATTRIBUTE1 column : Monitor URL attribute
Worklist Flexfields
Chapter 9 - Page 18
These rules combine to produce a net set of four message attributes that you can display in a
Personal Worklist view for the Requisition item type.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 19
Defining a Worklist Flexfields Rule: Entering General Properties
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Worklist Flexfields Rule: Entering General Properties
Defining
d
e
sh Use a Web browser to navigate to the Worklist Flexfields Rules page, using a responsibility
Ra and navigation path specified by your system administrator. Some possible navigation paths in
the seeded Workflow responsibilities are:
• Workflow Administrator Web Applications: Worklist Flexfields Rules
• Workflow Administrator Web (New): Worklist Flexfields Rules
Entering General Properties
Review the customization level for the rule.
• Core: You cannot make any changes to the rule definition. This level is used only for rules
seeded by Oracle E-Business Suite.
• Limit: You can update the rule status to Enabled or Disabled, but you cannot make any
other changes to the rule definition. This level is used only for rules seeded by Oracle E-
Business Suite.
• User: You can update any property in the rule definition. This level is automatically set for
rules that you define.
Worklist Flexfields
Chapter 9 - Page 20
The phase number you enter for the rule specifies the order in which rules for the same
workflow item type take effect. Rules with a higher phase number override rules with a lower
phase number. Rules seeded by Oracle E-Business Suite use phase numbers from 1 to 99. You
can assign your rules phase numbers of 100 or higher.
Note: Do not assign the same phase number to more than one rule for the same item type. To
ensure that the rules you want take effect, assign a different phase number to each rule for an
item type.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 21
Defining a Worklist Flexfields Rule: Selecting Filter Criteria
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Worklist Flexfields Rule: Selecting Filter Criteria
Defining
d
e
sh • You can enter a partial value in the Workflow Type field to search for item types whose
Ra display names begin with that value. This field is case-sensitive.
• Select an item type in either list to view its description.
• If you perform a new search to show different item types in the Available Filter Criteria
list, Oracle Workflow still preserves the item types that you already added to the Selected
Filter Criteria list.
Worklist Flexfields
Chapter 9 - Page 22
Defining a Worklist Flexfields Rule: Selecting Message Attributes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Worklist Flexfields Rule: Selecting Message Attributes
Defining
d
e
sh • If you no longer want a previously selected workflow item type in the filter criteria for the
Ra rule, click the remove icon for that item type in the Selected Filter Criteria list. When you
remove an item type, Oracle Workflow removes any message attributes belonging to that
item type from the Available list and the Selected list.
• You can add to the Selected list a maximum of ten text attributes, five number attributes,
five form attributes, five URL attributes, and five date attributes.
• The Available and Selected lists show the display name and data type for each message
attribute. Select a message attribute in either list to view in the Description field the
display name and internal name of the message to which the attribute belongs.
- If multiple messages in the selected workflow item types have a message attribute
with the same internal name, display name, and data type, that message attribute
appears only once in the lists. In this case the Description field indicates that the
message attribute occurs in multiple messages
- Oracle Workflow treats all message attributes with the same internal name and data
type as the same attribute for purposes of worklist flexfields column mapping.
Although attributes with different display names appear separately in the Available
Worklist Flexfields
Chapter 9 - Page 23
and Selected lists, if you select at least one attribute with a particular internal name
and data type, all attributes that share that internal name and data type will be
included in the column mapping.
• If you display message attributes of a different data type in the Available list, Oracle
Workflow still preserves the message attributes that you already added to the Selected list.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 24
Defining a Worklist Flexfields Rule: Mapping Attributes to
Columns
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Defining a Worklist Flexfields Rule: Mapping Attributes to Columns
Ra • The Mapped Column field for each attribute displays only columns that match the
attribute data type.
• You can use each column only once in a rule.
• If multiple messages in the selected workflow item types have a message attribute with the
same internal name and data type, that message attribute appears only once. However, if
any of the repeated message attributes have different display names, the list shows all the
display names.
• To remove a message attribute from the column mappings for the rule, click the remove
icon for that attribute.
• On the Find Worklist Flexfields Rule Map Conflicts page, review the columns that other
rules map to different attributes for the same workflow item types. The Conflict field
indicates whether the current rule overrides or is overridden by the other rule, based on the
rule phase numbers.
- To return to your rule definition, click the Return to Pending Rule link.
Worklist Flexfields
Chapter 9 - Page 25
- If you need to resolve any conflicts, you can return to the previous pages to update
the definition of this rule before finishing it, or you can update other rule definitions
after finishing this rule.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 26
Resolving Conflicts Between Worklist Flexfields Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 27
Maintaining Worklist Flexfields Rules
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Maintaining Worklist Flexfields Rules
e
sh Searching for Rules
Ra You can search by the internal rule name, display name, phase, status, level, workflow item
type, message attribute, or worklist flexfields column name.
• You can enter partial values in the Rule Name and Display Name fields. These fields are
case-sensitive.
• If you specify a workflow type to search by, you can only select a message attribute
belonging to that workflow type. Otherwise, you can select a message attribute belonging
to any workflow type
You must enter at least one of the following criteria when you search to limit the size of the
results list.
• Rule Name
• Display Name
• Level
• Workflow Type
Worklist Flexfields
Chapter 9 - Page 28
If you search only by the Level option or the Workflow Type option, you must select a specific
value for that option. You cannot use one of these criteria with the Any value as your only
search option.
The Workflow Type, Message Attribute, and Column Name search options only list values for
which a rule exists.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 29
Storing Message Attribute Values in Worklist Flexfields Columns
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 30
Performing a Worklist Flexfields Rule Simulation
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh • Perform a Core Rules simulation to learn which message attributes are already available in
Ra worklist flexfields columns by default. Although you cannot change these rules, you can
use the simulation results to avoid duplicating the mapped attributes in user rules.
• Perform a Limit and User Rules simulation to verify that any other message attributes you
require are available in worklist flexfields columns. If necessary, you can adjust the rules'
effect by enabling or disabling limit rules and creating, updating, enabling, or disabling
user rules.
• After performing a simulation, update your rules with any changes you want to make and
then repeat the simulation, until you are satisfied with the net set of message attributes
available for the item type.
Worklist Flexfields
Chapter 9 - Page 31
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Use a Web browser to navigate to the Worklist Flexfields Rules Simulation page, using a
Ra responsibility and navigation path specified by your system administrator. Some possible
navigation paths in the seeded Workflow responsibilities are:
• Workflow Administrator Web Applications: Worklist Flexfields Rules Simulation
• Workflow Administrator Web (New): Worklist Flexfields Rules Simulation
Reviewing Simulation Results
The list of mapped attributes and columns shows the net effect of the enabled rules for the
selected item type and customization level. If you specified a message, the list shows only
mapped attributes belonging to that message.
The list displays only the rule that takes effect for each column. To view any overridden rules
that also map to that column, choose the overridden rules icon.
• On the Find Worklist Flexfields Rule Conflicts page, review the columns that overridden
rules map to different attributes than the effective rule. The Conflict field indicates that the
effective rule overrides the other rules, based on the rule phase numbers.
Worklist Flexfields
Chapter 9 - Page 32
• Check that no two rules for the same item type have the same phase number. To ensure
that the rules you want take effect, each rule for an item type must have a different phase
number.
• To return to the simulation results, click the Return to Worklist Flexfields Rule Simulation
link.
If necessary, you can take action to resolve any conflicts.
• To update a rule, click the update icon for that rule.

• To create a new rule, click the Create Rule button.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 33
Defining a Securing Function
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Securing Function
Defining
d
e
sh The navigation path to the Form Functions window in the seeded System Administrator
Ra responsibility is:
• System Administrator: Application > Function
If you follow these steps to secure your specialized worklist view, then it will appear in the list
of views only when users access the Personal Worklist from the responsibility on whose menu
you added your securing function.
If you do not secure your specialized worklist view, it will appear in the list of views whenever
any user accesses the Personal Worklist from any responsibility.
For more information about defining functions, menus, and responsibilities, see the Oracle
Applications System Administrator's Guide and Oracle Applications Developer's Guide.
Worklist Flexfields
Chapter 9 - Page 34
Creating a Personalized View for the Personal Worklist
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Personalized View for the Personal Worklist
Creating
d
e
sh You do not need to associate worklist flexfields rules directly with a Personal Worklist view.
Ra Rather, to display meaningful information in a view, limit the view to include only related item
types that are covered by worklist flexfields rules, and add only worklist flexfields columns
that are mapped by those rules.
Note: If you do not limit the item types included in the view, then the view may display
notifications from other item types with blank values or unrelated values in the worklist
flexfields columns.
For more information about creating personalizations, see the Oracle Application Framework
Personalization Guide.
Worklist Flexfields
Chapter 9 - Page 35
Creating a Personalized View for the Personal Worklist
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Personalized View for the Personal Worklist
Creating
d
e
sh Defining View Properties
Ra • If you defined a securing function for the view, specify the function in the view's general
properties.
• Select the columns to display in the view, including the worklist flexfields columns that
are mapped to message attributes. Rename the columns as appropriate to identify the
attributes stored in them.
• Specify the columns by which to sort the view, including worklist flexfields columns if
appropriate.
• To display only notifications from the relevant item types, add the Type parameter or the
Type Internal Name parameter to the search query for the view, and specify the item type
display name or internal name, respectively. You can add multiple instances of these
parameters to include multiple item types in the view. In this case, select the “Search
results where each may contain any value entered” option.
Worklist Flexfields
Chapter 9 - Page 36
Restarting Oracle HTTP Server
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 37
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Worklist Flexfields
Chapter 9 - Page 38
nse
li c e
ble
fe r a
a n s
no Directory n-tr
Oracle Workflow
a
a) Guid has eฺ
Service
ฺ s
uChaptern10t
e d
c s t ฺ
t u de
@ ka is S
h a jri se th
i ( r al to u
jr
A lha
d
she
Ra
Oracle Workflow Directory Service

Chapter 10 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 4
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Directory Service
Oracle
d
e
sh A role can contain only individual users as its members. It cannot contain another role.
Ra However, roles can be related to each other in a hierarchy so that users assigned to one role
automatically inherit membership in its superior roles as well.

Chapter 10 - Page 5
Predefined Directory Service
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Predefined Directory Service
e
sh If the predefined directory service provided by Oracle Workflow does not meet your needs,
Ra you can create your own directory service by defining custom views with the required
columns. However, note that only the Oracle Workflow predefined directory services are
supported by Oracle.

Chapter 10 - Page 6
Directory Service Views
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 7
WF_USERS View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 8
WF_USERS View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 9
WF_USERS View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 10 - Page 10
WF_ROLES View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

WF_ROLES View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
WF_ROLES View
e
sh If the e-mail address is null for a given role, notification mailers send an individual e-mail to
Ra each user within the role.

WF_USER_ROLES View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

WF_USER_ROLES View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
WF_USER_ROLES View
e
sh The Assignment_Type column indicates how a user was assigned to membership in a role:
Ra • D: The user was directly assigned to this role.
• I: The user inherited this role through membership in another role.
• B: The user has both direct and inherited assignments to this role.

WF_USER_ROLES View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

WF_USER_ROLE_ASSIGNMENTS_V View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

WF_USER_ROLE_ASSIGNMENTS_V View
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Local Directory Service Tables
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Directory Service Tables
Local
d
e
sh Oracle Workflow also includes the following directory service tables:
Ra • WF_LOCAL_ROLES_TL stores translated data for MLS support in the WF_USERS and
WF_ROLES views.
• WF_ROLE_HIERARCHIES stores information about hierarchical relationships between
roles.
• WF_USER_ROLE_ASSIGNMENTS stores information about how assignments of users
to roles are inherited through role hierarchy relationships.

Local Directory Service Tables
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Directory Service Tables
Local
d
e
sh In the Workflow local tables:
Ra • Only the following Oracle E-Business Suite entities are stored as users: Oracle E-Business
Suite users, which may or may not be linked to Oracle Human Resources employees;
Trading Community Architecture (TCA) person parties; and TCA contacts (relationship
parties).
• Several types of Oracle E-Business Suite entities are stored as roles, including: Oracle E-
Business Suite responsibilities, Oracle Human Resources positions, MarketView
approvals and channels, Engineering approval lists, TCA groups, Federal HR group boxes,
Position Control roles, and User Management roles.
For more information about entities owned by various Oracle E-Business Suite products, refer
to the documentation for those products.
You should periodically purge ad hoc users and roles from the Workflow local tables after they
have expired in order to improve performance. Run the Purge Obsolete Workflow Runtime
Data concurrent program through the Oracle Workflow Manager component of Oracle
Applications Manager to perform this purging.

Ad Hoc Users and Roles
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Users/Roles
Ad Hoc
d
e
sh The WF_DIRECTORY package contains the APIs supporting ad hoc users and roles,
Ra including:
• CreateAdHocUser()
• CreateAdHocRole()
• CreateAdHocRole2()
• AddUsersToAddHocRole()
• AddUsersToAddHocRole2()
• RemoveUsersFromAdHocRole()
• SetAdHocUserStatus()
• SetAdHocRoleStatus()
• SetAdHocUserExpiration()
• SetAdHocRoleExpiration()
• SetAdHocUserAttr()
• SetAdHocRoleAttr()

Validating a Directory Service Data Model
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Directory Service Data Model
Validating
d
e
sh Customizations to the predefined directory service provided by Oracle Workflow are not
Ra supported. However, if you do choose to create your own directory service or customize the
predefined directory service, you should run wfdirchk.sql afterwards to validate the directory
service data model.

Setting Workflow Preferences
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow Preferences
Setting
d
e
sh Set the global default notification preferences in the Workflow Configuration page and
Ra individual user preferences in the General Preferences page in Oracle E-Business Suite. The
General Preferences page also allows users to set their individual language and territory
preferences.
Note: The language, territory, and notification preference settings in the Workflow
Configuration and General Preferences pages are effective for Oracle Workflow only if your
directory service views map these columns to the Oracle Workflow preferences table.

Loading Roles
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Roles
Loading
d
e
sh To load roles:
Ra 1. In Oracle Workflow Builder, select Open from the File menu to connect to your database
and open the item type you want.
2. From the File menu, select Load Roles from Database.
3. Specify search criteria in the Find Roles field of the Role selection window and then click
Find.
4. Select the roles you want to load in the Query Results list, and click Add to add them to
the Loaded Roles list.
5. Click OK to load the roles and make them available to the objects in your open item type.
After you load roles from the database, you can expand the Directory Service branch in the
navigator tree to view information about the roles.

Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

nse
li c e
ble
fe r a
a n s
o Activities n-tr
Defining Function
an
) h as deฺ
Chapter 11
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
Defining Function Activities

Chapter 11 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 4
Function Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 5
Defining a Function Activity
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Function Activity
Defining
d
e
sh To define a function activity:
Then select New Function from the Edit menu.
2. On the Activity property page, enter an internal name for the activity. The internal name
5. Choose an icon that identifies the activity.
6. Enter a function name and function type for the activity.
- PL/SQL: Enter the name of the PL/SQL stored procedure that you want the
Workflow Engine to execute for this function activity. Use the following format:
<package_name>.<procedure_name>
- External: Enter the name of the external program you want the Workflow Engine
to enqueue on the Outbound queue. You must provide an external agent to dequeue
and consume the entry on the Outbound queue. The external agent can similarly

Chapter 11 - Page 6
enqueue an entry onto the Inbound queue for a Workflow background engine to
consume and process to complete the function activity.
7. Specify the result type that contains the possible results that the function can return.
8. Optionally, specify a relative cost, in seconds, that represents how long the procedure
takes to run. If the cost exceeds the Workflow Engine threshold, the activity will be
deferred for later processing by a background engine.

10. Optionally, select the Details tab to display and modify additional activity details.
11. Optionally, select the Access tab to set the access levels allowed to modify this activity.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 7
External Function Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Function Activities
External
d
e
sh The most flexible and powerful way to integrate external processing into a workflow process is
Ra by using business events and subscriptions. However, Oracle Workflow also supports
processing external to the database through external function activities. This capability
facilitates integration with external products and legacy systems.
The Workflow Engine leverages Oracle Advanced Queuing to support the execution of
external function activities.
• An ‘Outbound’ queue and an ‘Inbound’ queue are established in Oracle Workflow. When
the Workflow Engine encounters an external function activity, a message is written to the
Outbound queue. The payload of the message includes any activity attribute name and
value pairs.
• A message on the workflow outbound queue is read by an external agent. An external
execution agent can be any application that is external to the database. The external
system consumes and processes the message.
• The external agent enqueues a message in the workflow inbound queue for Oracle
Workflow to consume and process. The workflow inbound queue message can be
considered as the “reply” to the original workflow outbound queue message. The inbound

Chapter 11 - Page 8
queue message payload can include activity attribute name and value pairs with updated
values. The Workflow background engine consumes and processes the inbound message
and completes the original function activity.
Note: The ‘Outbound’ and ‘Inbound’ queues used for external function activities are separate
from the queues used for the Business Event System. Also, a message in this context is
different from the messages associated with notification activities.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Chapter 11 - Page 9
Assigning a Cost to a Function Activity
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A a Cost to a Function Activity
Assigning
d
e
sh Activity costs are entered in the Workflow Builder in seconds and stored in the database in
Ra hundredths of a second. For example, a function with an execution cost of 10 milliseconds
would be entered in the function properties Cost field as 0.01 and stored in the cost database
column as 1.
The default Workflow Engine threshold is 500 milliseconds. This value is equivalent to 0.5
when compared with function activity costs entered in the function properties in the Workflow
Builder and 50 when compared to function activity costs stored in the database.
The Workflow Engine executes one activity at a time. If possible, you should avoid placing
costly activities along the critical path of a process. Instead, place costly activities on parallel
branches in a process, where they can be deferred for a background engine to process later.

PL/SQL Procedures for Function Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Procedures for Function Activities
PL/SQL
d
e
sh Note: This functionality is most typically used by developers.
Ra

Standard API for PL/SQL Procedures Called by Function
Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Standard API for PL/SQL Procedures Called by Function Activities
Ra procedure <procedure name> (
itemtype in varchar2,
itemkey in varchar2,
actid in number,
funcmode in varchar2,
resultout out varchar2) is
<local declarations>
begin
if (funcmode=‘RUN’) then
<your RUN executable statements>
resultout:=‘COMPLETE:<result>‘;
return;
endif;

if (funcmode=‘CANCEL’) then
<your CANCEL executable statements>
resultout:=‘COMPLETE’;
return;
endif;
if (funcmode=‘SKIP’) then
<your SKIP executable statements>

return;
endif;
if (funcmode=‘RETRY’) then
<your RETRY executable statements>
return;
nse
endif;
li c e
...
ble
exception fe r a
a n s
n-tr
when others then
WF_CORE.CONTEXT(’<package name>’, ’<procedure name>’,
a no
<itemtype>, <itemkey>,
) h as deฺ
sa t Gui
to_char(<actid>), <funcmode>);
u ฺ
ฺed uden
raise;
s t
ac is St
end <procedure name>;
k
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Standard API Parameters
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Function Activity Execution Modes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activity Execution Modes
Function
d
e
sh Looping occurs when the completion of an activity causes a transition to another activity that
Ra has already been completed. The activity property called On Revisit determines how the
Workflow Engine handles this activity when it transitions to the activity more than once.
• Ignore: Ignores the activity after the activity has been executed once.
• Reset: Resets completed activities in a loop by executing activities in CANCEL mode
before re-executing them in RUN mode.
• Loop: Re-executes activities in the loop without resetting them; in this case no CANCEL
logic is executed.

Function Activity Execution Modes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activity Execution Modes
Function
d
e
sh Oracle Workflow records audit trail data for skip and retry operations.
Ra

Standard API Resultout Parameter
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A API Resultout Parameter
Standard
d
e
sh • COMPLETE:<result_code> The activity completes with the specified result code. The
Ra result code must match one of the result codes defined in the result type of the activity.
• WAITING The activity is pending, waiting for another activity to complete before it
completes. An example is the Standard 'AND' activity.
• DEFERRED:<date> The activity is deferred to a background engine for execution until
a given date. <date> must be of the format:
to_char(<date_string>, wf_engine.date_format)
• NOTIFIED:<notification_id>:<assigned_user> An external entity has been notified
that an action must be performed. A notification ID and an assigned user can optionally be
returned with this result. Note that the external entity must call CompleteActivity() to
inform the Workflow Engine when the action completes.
• ERROR:<error_code> The activity encounters an error and returns the indicated error
code.

Exception Handling
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Handling
Exception
d
e
sh If an activity encounters an error, information about the error is stored in the following
Ra columns in the WF_ITEM_ACTIVITY_STATUSES table, which are viewable from the Status
Monitor.
• ERROR_NAME
• ERROR_MESSAGE
• ERROR_STACK

Exception Handling Example
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Handling Example
Exception
d
e
sh • WF_CORE.CONTEXT adds an entry to the error stack to provide context information
Ra that helps locate the source of an error.
• Use this example exception handler construct in your PL/SQL procedures to facilitate
debugging workflow function activities.
• If a call to ‘procedure name’ fails with an unhandled exception, the column
ERROR_STACK in the WF_ITEM_ACTIVITY_STATUSES table records the call to
‘procedure name’ and its arguments.

Defining Activity Details
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activity Details
Defining
d
e
sh To define activity details:
Ra 1. Open the property pages for the activity you want in the Oracle Workflow Builder and
select the Details tab.
2. Specify the internal name of the item type that owns the error process that you want to
execute if an error occurs in the current activity.
3. Specify the internal name of the error process.
4. Specify the On Revisit value to determine how the Workflow Engine handles this activity
when it transitions to the activity more than once.
- Ignore: Ignores the activity after the activity has been executed once; used for OR-
type operations where the rest of the branch is ignored.
- Reset: Resets completed activities in a loop by executing activities in CANCEL mode
before re-executing them in RUN mode.
- Loop: Re-executes activities in the loop without resetting them.

Note: The Details tab also displays the effective date and version of the activity. You set the
effective date when you save your changes using the Save As option in the File menu. All your
activity modifications share the same effective date when you save. The version number of the
activity is maintained by Oracle Workflow.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

Error Handling
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
AHandling
Error
d
e
sh Oracle Workflow provides an item type called System: Error which contains processes that you
Ra can use for generic error handling.
• Default Error Process
• Retry-only Process

Looping
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A
Looping
d
e
sh To handle a revisited activity, the Workflow Engine can:
Ra • Ignore the activity and stop further processing of the thread, so that in effect, the activity
can only run once.
• Reset the loop to the loop point before re-executing by first running cancel logic to undo
the activities within the loop.
• Loop through the activities to the loop point, re-executing each one without running
cancel logic to undo any previous logic. The Loop option results in faster performance
than Reset, so the Loop option is recommended if the activities within the loop can be re-
executed without first having their status reset by cancel logic.

Defining an Activity Attribute
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A an Activity Attribute
Defining
d
e
sh • Activity attributes can be only be associated with function activities or Raise event
Ra activities.
• You can change the definition of an activity attribute at any time in Oracle Workflow
Builder.
To define an activity attribute:
1. In the Oracle Workflow Builder, select the activity you want in the navigator tree. Then
2. On the Attribute property page, enter an internal name for the attribute. The internal name
6. Depending on the data type, enter format information and a default value, if applicable.

Setting Activity Attribute Values
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Activity Attribute Values
Setting
d
e
sh To set activity attribute values:
Ra 1. In the Oracle Workflow Builder, display the property pages of an activity node, and select
the Node Attributes tab.
2. Select an attribute.
3. Enter a value for the attribute. The value can be either constant or dynamic.
- For a constant value, select Constant and enter a value.
- For a dynamic value, select Item Attribute and then select the name of an item type
attribute that returns a value of the appropriate data type during runtime.
You can use the WF_ENGINE.GetActivityAttribute APIs to retrieve the value of an activity
attribute within a PL/SQL function. The following example shows a variable being set to the
value of an activity attribute of type text:
aname := wf_engine.GetActivityAttrText(itemtype, itemkey,
actid, ‘VALUE1');

Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra

nse
li c e
ble
fe r a
a n s
o Functions n-tr
Post-Notification
an
) h as deฺ
Chapter 12
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
Post-Notification Functions
Chapter 12 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Chapter 12 - Page 2
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Chapter 12 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Chapter 12 - Page 4
PL/SQL Procedures for Notification Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Chapter 12 - Page 5
Standard API for PL/SQL Procedures Called by Notification
Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Standard API for PL/SQL Procedures Called by Notification Activities
Ra procedure <procedure name> (
itemtype in varchar2,
itemkey in varchar2,
actid in number,
funcmode in varchar2,
resultout out varchar2) is
<local declarations>
begin
if (funcmode=‘VALIDATE’) then
<your VALIDATE executable statements>
return;
endif;
Chapter 12 - Page 6
if (funcmode=‘RESPOND’) then
<your RESPOND executable statements>
return;
endif;
if (funcmode=‘FORWARD’) then
<your FORWARD executable statements>

return;
endif;
if (funcmode=‘TRANSFER’) then
<your TRANSFER executable statements>
return;
nse
endif;
li c e
if (funcmode=‘QUESTION’) then ble
<your QUESTION executable statements> fe r a
resultout:=‘COMPLETE’; a n s
return;
no n-tr
endif;
a
if (funcmode=‘ANSWER’) then
) h as deฺ
<your ANSWER executable statements>
resultout:=‘COMPLETE’; u ฺ sa t Gui
return;
s t ฺed uden
endif;
k ac is St
if (funcmode=‘RUN’) then
a j ri@ e th
r a lh o us
<your RUN executable statements>
ri ( t
j
lh a
return;
d A
endif;
she if (funcmode=‘TIMEOUT’) then
Ra <your TIMEOUT executable statements>
if (<condition_ok_to_proceed>) then
else
resultout := wf_engine.eng_timedout;
end if;
return;
endif;
...
exception
when others then
WF_CORE.CONTEXT(’<package name>’, ’<procedure name>’,
<itemtype>,
<itemkey>, to_char(<actid>), <funcmode>);
Chapter 12 - Page 7
raise;
end <procedure name>;
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Chapter 12 - Page 8
Post-Notification Function Execution Modes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Post-Notification Function Modes
e
sh • VALIDATE: Called when a performer submits a response before RESPOND mode. The
Ra post-notification function can validate the response values before accepting and recording
the response. For example, if the notification requires an electronic signature, the post-
notification function can run in VALIDATE mode to verify the response values and
inform the user of any errors before requiring the user to enter a signature.
• RESPOND: The performer responded to the notification. The post-notification function
can interpret the result and perform post-response processing. The function can reject the
response with an error.
• FORWARD: The performer delegates the notification to another user. The function can
audit or reject the delegation request with an error. This state corresponds to the Delegate
Authority option on the Reassign Notifications page.
• TRANSFER: The performer transfers the notification to another user. The function can
audit or reject the transfer request with an error. This state corresponds to the Transfer
Ownership option on the Reassign Notifications page.
Chapter 12 - Page 9
• QUESTION: The performer submitted a request for more information about the
notification from another user. The function can verify that the request is directed to a role
that has appropriate authority to view the notification, for example.
• ANSWER: The performer responded to a request with answering information. The
function can interpret the answer and validate or reject it.
• RUN: Called after RESPOND mode. The post-notification function in RUN mode can
perform additional processing associated with the notification.

• TIMEOUT: If a notification activity does not complete within a certain period of time,
then Oracle Workflow marks that activity as timed out and then cancels any notification
associated with the timed-out activity. The post-notification function in TIMEOUT mode
can perform processing to determine an alternative result for the notification. For
example, if the notification is a vote, and some responses are received before the timeout
event, the post-notification function can determine whether there are enough votes
nse
received to determine the vote result.
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Standard API Resultout Parameter for a Post-Notification
Function
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
e
sh Standard API Resultout Parameter for a Post-Notification Function
Ra If, based on the results of your post-notification function, you do not want the Validate,
Respond, Forward, Transfer, Question, or Answer operation to occur, you can do one of two
things:
• Return ERROR:<errcode> in the resultout parameter. In this case, Oracle Workflow
converts the result to a generic exception and includes the specified error code in the
generic error message that appears to the user.
• Raise an exception directly in your procedure with a more informative error message to
appear to the user.
Post-Notification Function Context Information
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Post-Notification Function Context Information
e
sh In some cases, the values of the context variables depends on the function mode in which the
Ra post-notification function is being executed and on the notification interface that the recipient
uses to respond.
For more information, see Post-Notification Functions, Oracle Workflow API Reference.
Exception Handling
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
nse
li c e
ble
fe r a
a n s
no n-tr
Workflow a
Engine
) h as deฺ
Chapter 13
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
lh s
j ri (ra to u
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 1
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 2
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 3
Objectives
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 4
Overview of the Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A of the Workflow Engine
Overview
d
e
sh The Notification System is also implemented in server-side PL/SQL and can interface with the
Ra Workflow Web agent or the Java-based notification mailer program to deliver notifications to
end users.
The Workflow Engine and the Business Event System can function independently of each
other. However, you can now achieve the most powerful and flexible processing by using the
Workflow Engine and the Business Event System together to execute cross-system processes
for e-business integration.
Oracle Workflow additionally provides Java wrappers for many Workflow Engine APIs to let
you call the Workflow Engine from Java code.
For more information, see: Workflow Engine APIs, Oracle Workflow API Reference.
Workflow Engine
Chapter 13 - Page 5
Overview of the Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 6
Initiating a Workflow Process
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
Initiating
d
e
sh • If you use an event to initiate a workflow process, you must define a subscription that
Ra sends the event message to the workflow process when the event is raised. You can also
define a subscription to send an event to start a workflow process when the event message
is received from an external source. In both cases, the process must begin with a Receive
event activity that is marked as a Start activity node to receive the event.
• If you call the Workflow Engine APIs to initiate a workflow process, use the
CreateProcess and StartProcess APIs if you want to perform additional tasks, such as
setting item attributes, after creating and before starting the process. If you do not need to
perform any additional tasks, you can use the LaunchProcess API, which is a wrapper
combining the CreateProcess and StartProcess APIs.
• The procedure that executes the Workflow Engine APIs to initiate a process must identify
the item type and item key of the process for these APIs. The item type and item key
passed to these APIs uniquely identify an item and must be passed to subsequent API calls
for each specific process. The process must begin with the standard Start activity or with
another function, notification, or process activity, marked as a Start activity node.
Workflow Engine
Chapter 13 - Page 7
• You can also use the Workflow Engine bulk APIs to initiate several instances of the same
workflow process at once. Call WF_ENGINE_BULK.CreateProcess and
WF_ENGINE_BULK.StartProcess if you want to set item attributes after creating and
before starting the processes, or call WF_ENGINE_BULK.FastForward to create multiple
new processes and begin executing them at a specified activity stage.
• Oracle Workflow also includes the Developer Studio to let you manually initiate a
workflow process. The Developer Studio is intended for use by a workflow developer or
administrator to test workflow processes in a development environment.
Example
The following example shows how to initiate a process using the CreateProcess,
SetItemUserKey, SetItemAttribute, SetItemOwner, and StartProcess APIs.
wf_engine.CreateProcess( ItemType => ItemType,

nse
ItemKey => ItemKey,
li c e
process => WorkflowProcess );
ble
--
fe r a
wf_engine.SetItemUserKey ( ItemType => ItemType,
a n s
n-tr
ItemKey => ItemKey,
UserKey => ItemUserKey);
a no
--
) h as deฺ
sa t Gui
wf_engine.SetItemOwner ( itemtype => itemtype,
u ฺ
itemkey => itemkey,
owner
t ฺed uden
=> ProcessOwner );
s
--
k ac is St
--
a j ri@ e th
r a lh o us
-- Initialize workflow item attributes
--
j ri ( t
lh a
wf_engine.SetItemAttrText ( itemtype => itemtype,
d A itemkey => itemkey,
she aname => 'REQUISITION_NUMBER',

Ra avalue => RequisitionNumber);
--
wf_engine.SetItemAttrNumber ( itemtype => itemtype,
itemkey => itemkey,
aname => 'REQUISITION_AMOUNT',
avalue => RequisitionAmount );
--
...
--
wf_engine.StartProcess( itemtype => itemtype,
itemkey => itemkey );
Workflow Engine
Chapter 13 - Page 8
Workflow Engine Processing
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Chapter 13 - Page 9
Workflow Engine Processing
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine Processing
Workflow
d
e
sh The Workflow Engine sets a savepoint for each completed function activity, and saves all
Ra consecutively completed function activities as part of one commit cycle. If an error occurs
during a commit, the database can roll back to an appropriate savepoint.
The Workflow Engine never issues a commit, as it is the responsibility of the calling
application to commit. When the Workflow Engine encounters a blocking activity such as a
response-required notification, it sets the activity to the appropriate status, such as NOTIFIED,
and returns control to the calling application. That application can then issue a commit.
Similarly, when the Workflow Engine reaches the end of a process, it returns control to the
calling application, which can then issue a commit.
Note:
• A notification activity that sends an FYI notification message will be automatically
completed by the Workflow Engine. Only notifications that prompt for a response will
cause the Workflow Engine to pause and wait for a response from the notification
recipient.
Workflow Engine
• If a background engine resumes the processing for a process that was deferred or timed
out, the background engine issues a commit after completing its processing. In this case,
the background engine is acting on behalf of the calling application.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Activity Statuses
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Statuses
Activity
d
e
sh • Active: The activity is currently being executed. The topmost process will be active until
Ra the entire process completes.
• Complete: The activity executed successfully.
• Waiting: The activity is waiting for dependencies to complete. An example is the AND
activity, where one incoming transition is complete but the activity is still waiting for
another required incoming transition to complete before it can be marked as complete.
• Notified: The activity is waiting for a response from a notification, for an event message,
or for an external program to complete and call the Workflow Engine.
• Deferred: The activity is deferred to a background engine for execution.
• Error: The activity has encountered an error during execution.
• Suspend: The activity is suspended from further execution.
Workflow Engine
Calling the Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A the Workflow Engine
Calling
d
e
sh You can add a standard Block activity after any function activity that calls an external
Ra program. The Block activity will pause the process until the external program completes and
makes a call to WF_ENGINE.CompleteActivity().
Workflow Engine
Background Engines
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
Background Engines
e
sh Use the Workflow Manager component in Oracle Applications Manager to run background
Ra engines by submitting the Workflow Background Process concurrent program.
Workflow Engine
Stuck Processes
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Processes
Stuck
d
e
sh For example, a process could become stuck when:
Ra • A thread within a process leads to an activity that is not defined as an End activity but has
no other activity modeled after it, and no other activity is active.
• A process with only one thread loops back, but the pivot activity of the loop has the On
Revisit property set to Ignore.
• An activity returns a result for which no eligible transition exists. For instance, if the
function for a function activity returns an unexpected result value, and no default
transition is modeled after that activity, the process cannot continue.
Generally, you should run a separate background engine to check for stuck processes at less
frequent intervals than the background engine that you run for deferred or timed out activities,
normally not more often than once a day. Run the background engine to check for stuck
processes when the load on the system is low.
Workflow Engine
Timed Out Activities
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Out Activities
Timed
d
e
sh You can fix the due date of an activity at design time by setting the timeout value to a relative
Ra time in days, hours, and minutes. You can also set the timeout value to an item attribute and
specify it when you initiate an instance of the process.
If you are using an item attribute to set the timeout value, then the item attribute must be set to
type number or type date. If the item attribute is of type number, the value entered must be in
the unit of minutes. If the item attribute is of type date, the value entered must be a date in the
format DD-MON-RR HH24:MI:SS.
Note: If a timed out activity does not have a <Timeout> transition modeled, the Workflow
Engine will try to find an error process to execute.
Workflow Engine
Deferred Processing
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Processing
Deferred
d
e
sh The Workflow Engine integrates with Oracle Advanced Queuing to carry out deferred
Ra processing. When the Workflow Engine encounters an activity for deferred processing, a
message is written to a separate “deferred” queue. The Background Engine consumes and
processes the deferred queue messages, executing and completing the deferred activity.
The Workflow Engine threshold is an externalized constant. You can force a process to be
deferred as soon as it is launched by lowering the Workflow Engine threshold level. For
example, if you want to launch a workflow process using the Workflow Engine APIs from a
database trigger, you must defer the process immediately in order to avoid issuing savepoints,
which are not allowed in a database trigger.
The following example shows how to defer a process immediately upon launching it.
-- Set engine to defer everything to the background engine for this session
-- This provides faster user response time, at the expense of
-- delaying workflow progress until the background engine runs.
save_threshold := wf_engine.threshold;
wf_engine.threshold := -1;
Workflow Engine
-- Launch the process
wf_engine.CreateProcess(...);
wf_engine.SetItemAttr...(...);
wf_engine.StartProcess(...);
-- Reset the threshold

wf_engine.threshold:=save_threshold;
exception
-- Ensure threshold is reset
wf_engine.threshold := save_threshold;
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Oracle Workflow APIs
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
Oracle Workflow APIs
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Workflow APIs
Oracle
d
e
sh The public views are installed in the APPS account.
Ra For more information, refer to the Oracle Workflow API Reference.
Workflow Engine
Workflow Engine APIs
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine APIs
Workflow
d
e
sh • WF_ENGINE.CreateProcess creates a new run-time process for a work item.
Ra • WF_ENGINE.StartProcess begins execution of the specified process.
• WF_ENGINE.LaunchProcess launches a specified process by creating the new run-time
process and beginning its execution.
• WF_ENGINE.SetItemOwner sets the owner of an existing item.
• WF_ENGINE.SetItemUserKey sets a user-friendly identifier for an item.
• WF_ENGINE.GetItemUserKey returns the user-friendly identifier assigned to an item.
• WF_ENGINE.SetItemParent defines the parent/child relationship for master/detail
processes.
• WF_ENGINE.Event receives an event from the Business Event System into a workflow
process.
• WF_ENGINE.Background runs a background engine to process deferred and timed out
activities and stuck processes.
• WF_ENGINE.CreateForkProcess forks a run-time process by creating a new process that
is a copy of the original.
Workflow Engine
• WF_ENGINE.StartForkProcess begins execution of the specified new forked process.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine APIs
Workflow
d
e
sh • WF_ENGINE.SetItemAttrText, WF_ENGINE.SetItemAttrNumber,
Ra WF_ENGINE.SetItemAttrDate, and WF_ENGINE.SetItemAttrEvent set the value of an
item type attribute in a process.
• WF_ENGINE.SetItemAttrDocument sets the value of an item attribute of type document
to a document identifier.
• WF_ENGINE.SetItemAttrTextArray, WF_ENGINE.SetItemAttrNumberArray, and
WF_ENGINE.SetItemAttrDateArray set the values of an array of item type attributes in a
process.
• WF_ENGINE.GetItemAttrText, WF_ENGINE.GetItemAttrNumber,
WF_ENGINE.GetItemAttrDate, and WF_ENGINE.GetItemAttrEvent return the value of
an item type attribute in a process.
• WF_ENGINE.GetItemAttrDocument returns the document identifier of an item attribute
of type document.
• WF_ENGINE.GetItemAttrClob returns the value of an item type attribute in a process as a
character large object (CLOB).
Workflow Engine
• WF_ENGINE.GetItemAttrInfo returns information about an item attribute, such as its
type and format.
Example
• If an event subscription sends a business event to a workflow process, the subscription's
globally unique identifier (GUID) is set as a dynamic item attribute of type text named
SUB_GUID so that the workflow process can reference other information in the
subscription definition. You can call the WF_ENGINE.GetItemAttrText() API to retrieve

the subscription GUID value from the SUB_GUID item attribute, and then use the GUID
to select other values from the WF_EVENT_SUBSCRIPTIONS table.
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine APIs
Workflow
d
e
sh • WF_ENGINE.AddItemAttr adds a new item attribute to the run-time process.
Ra • WF_ENGINE.AddItemAttrTextArray, WF_ENGINE.AddItemAttrNumberArray, and
WF_ENGINE.AddItemAttrDateArray add an array of new item type attributes to the run-
time process.
• WF_ENGINE.GetActivityAttrText, WF_ENGINE.GetActivityAttrNumber,
WF_ENGINE.GetActivityAttrDate, and WF_ENGINE.GetActivityAttrEvent return the
value of an activity attribute in a process.
• WF_ENGINE.GetActivityAttrClob returns the value of an activity attribute in a process as
a character large object (CLOB).
• WF_ENGINE.GetActivityAttrInfo returns information about an activity attribute, such as
its type and format.
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine APIs
Workflow
d
e
sh • WF_ENGINE.CompleteActivity notifies the engine that the specified activity has been
Ra completed for the item, identifying the activity by the activity node label name.
• WF_ENGINE.CompleteActivityInternalName notifies the engine that the specified
activity has been completed for the item, identifying the activity by its internal name.
• WF_ENGINE.BeginActivity determines if the specified activity can currently be
performed and raises an exception if it cannot.
• WF_ENGINE.AssignActivity assigns an activity to another performer.
• WF_ENGINE.GetActivityLabel returns the instance label of an activity, given the internal
activity instance identification.
• WF_ENGINE.AbortProcess aborts process execution and cancels outstanding
notifications.
• WF_ENGINE.SuspendProcess suspends process execution so that users cannot transition
items to new activities.
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine APIs
Workflow
d
e
sh • WF_ENGINE.ResumeProcess returns a suspended process to normal execution status.
Ra • WF_ENGINE.HandleError handles any activity that has encountered an error. This API
can also be called for any arbitrary activity in a process to roll back part of the process to
that activity.
• WF_ENGINE.ItemStatus returns the status and results for the root process of the specified
item instance.
Workflow Engine
Workflow Engine Bulk APIs
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
A Engine Bulk APIs
Workflow
d
e
sh • WF_ENGINE_BULK.CreateProcess creates multiple new run-time process instances of
Ra the specified item type at once, based on the specified array of workflow item keys.
• WF_ENGINE_BULK.StartProcess begins execution of multiple new run-time process
instances at once, identified by the specified item type and array of workflow item keys.
• WF_ENGINE_BULK.FastForward creates multiple new run-time process instances of the
specified item type at once, based on the specified array of workflow item keys, and
begins execution of the new work items at the specified activity.
• WF_ENGINE_BULK.SetItemAttrText, WF_ENGINE_BULK.SetItemAttrNumber, and
WF_ENGINE_BULK.SetItemAttrDate set the values of an array of item type attributes in
multiple work items, identified by the specified item type and array of item keys.
Workflow Engine
Summary
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine
nse
li c e
ble
fe r a
a n s
no n-tr
a
) h as deฺ
u ฺ sa t Gui
s t ฺed uden
k ac is St
a j ri@ e th
r a lh o us
j ri ( t
lh a
d A
she
Ra
Workflow Engine

Implement

Uploaded by

Copyright:

Available Formats

Implement

Uploaded by

Document Information

Original Title

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

Implement

Uploaded by

Copyright:

Available Formats

Unauthorized reproduction or distribution prohibitedฺ Copyright© 2016, Oracle and/or its affiliatesฺ

U.S. GOVERNMENT RIGHTS

Introduction to Oracle Workflow ..................................................................................................................1-1

Ra Worklist Web Pages ......................................................................................................................................2-26

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Quick Start Wizard ........................................................................................................................................4-9

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Testing Workflow Processes .........................................................................................................................7-5

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Limit and User Rules.....................................................................................................................................9-14

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Post-Notification Function Execution Modes................................................................................................12-9

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

PL/SQL and Java Subscription Processing....................................................................................................15-31

shedEvent Activities .............................................................................................................................................17-5

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Event Data Generate Functions .....................................................................................................................18-21

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Standard API for a Selector/Callback Function.............................................................................................22-7

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Step 4: Synchronizing License Statuses ........................................................................................................27-28

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Queue Propagation ........................................................................................................................................29-33

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Lesson 15 - Event Subscriptions....................................................................................................................30-86

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

• Thorough knowledge of Oracle Database and Oracle Application Server technology

• Thorough knowledge of Oracle E-Business Suite

• Oracle Database: Introduction to SQL

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Oracle Workflow Administrator's Guide E12903

Additional Publications nse

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

table names FROM s_emp;

Passwords DROP USER scott

Lowercase Syntax variables CREATE ROLE role

(ST) = Sub Tab

Copyright © Oracle Corporation, 2009. All rights reserved.

R12.x Implement Oracle Workflow Table of Contents

The following help navigation path, for example—

(Help) General Ledger > Journals > Enter Journals

—represents the following sequence of actions:

2. Under the General Ledger entry, expand Journals.

Copyright © Oracle Corporation, 2009. All rights reserved.