Documente Academic
Documente Profesional
Documente Cultură
Workflow
Volume 1 - Student Guide
m y
d e
c a
e A
c l
r a
O ly
l & On
D49191GC10
Edition 1.0
n a e
June 2007
t e r U s
D50533
I n
c l e
r a
O
Copyright © 2007, 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:
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.
Authors
Leta Davis, Donna Johnson, Gary Lemmons, Michael Morrison, Georgia Price, Robert
Wunderlich
oracletutor m y
This book was published using:
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Table of Contents
c a
Oracle Workflow Builder ..............................................................................................................................2-17
Business Event System Architecture .............................................................................................................2-18
A
Business Event System Components.............................................................................................................2-19
Advanced Queuing, an Enabling Technology ...............................................................................................2-20
e
c l
Oracle Database Communication Alternatives..............................................................................................2-21
Accessing Oracle Workflow Web Pages .......................................................................................................2-23
Oracle Workflow Home Pages ......................................................................................................................2-24
r a
Notification System .......................................................................................................................................2-25
Worklist Web Pages ......................................................................................................................................2-26
O ly
E-Mail Notifications ......................................................................................................................................2-27
Directory Services .........................................................................................................................................2-28
l & On
Status Monitor Web Pages.............................................................................................................................2-29
Workflow Definitions Loader........................................................................................................................2-30
n a e
Workflow XML Loader.................................................................................................................................2-31
Workflow Manager........................................................................................................................................2-32
t e r U s
Service Components ......................................................................................................................................2-33
Oracle Workflow Documentation..................................................................................................................2-34
I n
Review Questions ..........................................................................................................................................2-36
Summary........................................................................................................................................................2-37
c l e
Planning a Workflow Process.........................................................................................................................3-1
Planning a Workflow Process........................................................................................................................3-3
Objectives ......................................................................................................................................................3-4
r a
Workflow Process Components ....................................................................................................................3-5
Oracle Workflow Builder ..............................................................................................................................3-7
c
Defining Item Type Attributes and Lookup Types.......................................................................................5-1 a
Summary........................................................................................................................................................4-35
A
Defining Item Type Attributes and Lookup Types........................................................................................5-3
Objectives ......................................................................................................................................................5-4
e
c l
Defining Item Type Attributes.......................................................................................................................5-5
Attribute Data Types .....................................................................................................................................5-7
r a
Defining Item Type Attributes.......................................................................................................................5-9
URL Attributes ..............................................................................................................................................5-10
Form Attributes .............................................................................................................................................5-13
O ly
Document Attributes......................................................................................................................................5-16
l & On
Deleting Item Attributes ................................................................................................................................5-19
Defining Lookup Types.................................................................................................................................5-20
Defining Lookup Codes.................................................................................................................................5-21
a e
Practice - Defining Item Type Attributes...................................................................................................5-22
n
e r
Solution – Defining Item Type Attributes ................................................................................................5-23
s
Summary........................................................................................................................................................5-26
t U
Defining Messages and Notification Activities ..............................................................................................6-1
I n
Defining Messages and Notification Activities .............................................................................................6-3
Objectives ......................................................................................................................................................6-4
l e
Notification Activities ...................................................................................................................................6-5
c
Defining a Message .......................................................................................................................................6-6
r a
Defining a Message Attribute........................................................................................................................6-8
Defining a Respond Attribute........................................................................................................................6-10
Defining a Message Result ............................................................................................................................6-11
O Notification Details Web Page ......................................................................................................................6-12
e A
Viewing a Status Diagram in the Self-Service Monitor ................................................................................7-24
Viewing Responses in the Self-Service Monitor ...........................................................................................7-26
c l
Viewing Error Information in the Self-Service Monitor ...............................................................................7-28
Practice - Running a Workflow Process ....................................................................................................7-29
r a
Solution – Running a Workflow Process...................................................................................................7-30
Summary........................................................................................................................................................7-31
O ly
Viewing and Responding to Notifications......................................................................................................8-1
l & On
Viewing and Responding to Notifications.....................................................................................................8-3
Objectives ......................................................................................................................................................8-4
Viewing Notifications from a Web Browser .................................................................................................8-5
a e
Worklist Pages...............................................................................................................................................8-6
n
e r
Advanced Worklist ........................................................................................................................................8-7
s
Notification Details........................................................................................................................................8-9
t U
Reassigning Notifications..............................................................................................................................8-12
I n
Requesting More Information........................................................................................................................8-14
Certificate-Based Digital Signatures .............................................................................................................8-15
e
Granting Worklist Access..............................................................................................................................8-17
l
Administrator Search for Notifications..........................................................................................................8-21
c
Reviewing Electronic Signature Details ........................................................................................................8-23
r a
Personal Worklist ..........................................................................................................................................8-25
Simple Search for Notifications.....................................................................................................................8-27
c l
Performing a Worklist Flexfields Rule Simulation .......................................................................................9-31
Defining a Securing Function........................................................................................................................9-34
r a
Creating a Personalized View for the Personal Worklist...............................................................................9-35
Restarting Oracle HTTP Server.....................................................................................................................9-37
O ly
Practice - Defining a Specialized Worklist View Using Worklist Flexfields ............................................9-38
Solution – Defining a Specialized Worklist View Using Worklist Flexfields...........................................9-41
l & On
Summary........................................................................................................................................................9-45
Oracle Workflow Directory Service...............................................................................................................10-1
a e
Oracle Workflow Directory Service ..............................................................................................................10-3
n
e r
Objectives ......................................................................................................................................................10-4
s
Oracle Workflow Directory Service ..............................................................................................................10-5
t U
Predefined Directory Service.........................................................................................................................10-6
I n
Directory Service Views................................................................................................................................10-7
WF_USERS View .........................................................................................................................................10-8
e
WF_ROLES View.........................................................................................................................................10-11
l
WF_USER_ROLES View.............................................................................................................................10-13
c
WF_USER_ROLE_ASSIGNMENTS_V View ............................................................................................10-16
r a
Local Directory Service Tables .....................................................................................................................10-18
Ad Hoc Users and Roles................................................................................................................................10-20
m y
Summary........................................................................................................................................................11-44
d e
Workflow Engine.............................................................................................................................................12-1
Workflow Engine ..........................................................................................................................................12-3
c a
Objectives ......................................................................................................................................................12-4
Overview of the Workflow Engine................................................................................................................12-5
A
Initiating a Workflow Process .......................................................................................................................12-7
Workflow Engine Processing ........................................................................................................................12-9
e
c l
Activity Statuses ............................................................................................................................................12-12
Calling the Workflow Engine........................................................................................................................12-13
r a
Background Engines......................................................................................................................................12-14
Stuck Processes .............................................................................................................................................12-15
Timed Out Activities .....................................................................................................................................12-16
O ly
Deferred Processing.......................................................................................................................................12-17
l & On
Oracle Workflow APIs ..................................................................................................................................12-19
Workflow Engine APIs .................................................................................................................................12-21
Workflow Engine Bulk APIs.........................................................................................................................12-28
a e
Practice - Implementing Timeout Processing ............................................................................................12-29
n
e r
Solution – Implementing Timeout Processing...........................................................................................12-30
s
Practice - Implementing Deferred Processing ...........................................................................................12-33
t U
Solution – Implementing Deferred Processing ..........................................................................................12-34
I n
Summary........................................................................................................................................................12-36
Business Events ................................................................................................................................................13-1
l e
Business Events .............................................................................................................................................13-3
c
Objectives ......................................................................................................................................................13-4
r a
Business Events .............................................................................................................................................13-5
Event Properties.............................................................................................................................................13-6
Generate Functions ........................................................................................................................................13-8
O License Status for Events ..............................................................................................................................13-10
c a
PL/SQL and Java Subscription Processing....................................................................................................14-31
Defining a Subscription .................................................................................................................................14-33
Maintaining Subscriptions .............................................................................................................................14-35
e A
Predefined Subscriptions ...............................................................................................................................14-36
Practice - Defining a Subscription .............................................................................................................14-37
c l
Solution – Defining a Subscription............................................................................................................14-39
Summary........................................................................................................................................................14-44
r a
Systems and Agents .........................................................................................................................................15-1
Systems and Agents.......................................................................................................................................15-3
O ly
Objectives ......................................................................................................................................................15-4
l & On
Systems..........................................................................................................................................................15-5
System Properties ..........................................................................................................................................15-6
Local System .................................................................................................................................................15-7
a e
External Systems ...........................................................................................................................................15-8
n
e r
Defining a System .........................................................................................................................................15-9
s
Maintaining Systems .....................................................................................................................................15-10
t U
Agents............................................................................................................................................................15-12
I n
Standard Agents.............................................................................................................................................15-14
Agent Properties ............................................................................................................................................15-16
e
Custom Queue Handlers ................................................................................................................................15-21
l
Agents on External Systems ..........................................................................................................................15-22
c
Defining an Agent .........................................................................................................................................15-24
r a
Agent Groups.................................................................................................................................................15-26
Defining an Agent Group ..............................................................................................................................15-27
c a
Business Event System datatypes ..................................................................................................................17-5
Event Message Structure ...............................................................................................................................17-6
A
Agent Structure..............................................................................................................................................17-10
Parameter List Structure ................................................................................................................................17-12
e
c l
Parameter Structure .......................................................................................................................................17-13
Raising Events Programmatically..................................................................................................................17-15
r a
Event Data Generate Functions .....................................................................................................................17-22
Standard API for PL/SQL Event Data Generate Functions...........................................................................17-23
Standard API for Java Event Data Generate Functions .................................................................................17-24
O ly
Queue Handlers .............................................................................................................................................17-27
l & On
Standard APIs for PL/SQL Queue Handlers .................................................................................................17-28
Standard APIs for Java Queue Handlers........................................................................................................17-29
Subscription Rule Functions..........................................................................................................................17-31
a e
Standard API for PL/SQL Subscription Rule Functions ...............................................................................17-32
n
e r
Standard API for Java Subscription Rule Functions......................................................................................17-34
s
Predefined Subscription Rule Functions........................................................................................................17-36
t U
Event APIs.....................................................................................................................................................17-38
I n
Event Function APIs......................................................................................................................................17-40
Adding a Correlation ID to an Event Message ..............................................................................................17-41
l e
Business Event System Cleanup API ............................................................................................................17-43
Summary........................................................................................................................................................17-44
c
r a
Error Handling ................................................................................................................................................18-1
Error Handling...............................................................................................................................................18-3
Objectives ......................................................................................................................................................18-4
O Error Handling for Workflow Processes .......................................................................................................18-5
A
Post-Notification Function Execution Modes................................................................................................20-9
Standard API Resultout Parameter for a Post-Notification Function ............................................................20-11
e
c l
Post-Notification Function Context Information ...........................................................................................20-12
Practice - Defining a Post-Notification Function.......................................................................................20-13
r a
Solution – Defining a Post-Notification Function .....................................................................................20-15
Exception Handling .......................................................................................................................................20-19
Summary........................................................................................................................................................20-20
O ly
Forced Synchronous Processing .....................................................................................................................21-1
l & On
Forced Synchronous Processing ....................................................................................................................21-3
Objectives ......................................................................................................................................................21-4
n a e
Forced Synchronous Processes......................................................................................................................21-5
Process Definition Restrictions......................................................................................................................21-6
t e r U s
Summary........................................................................................................................................................21-9
Selector/Callback Functions ...........................................................................................................................22-1
I n
Selector/Callback Functions ..........................................................................................................................22-3
Objectives ......................................................................................................................................................22-4
e
Item Type Selector/Callback Functions.........................................................................................................22-5
l
Defining a Selector/Callback Function for an Item Type ..............................................................................22-6
c
Standard API for a Selector/Callback Function.............................................................................................22-7
r a
Standard API Parameters...............................................................................................................................22-9
Selector/Callback Function Commands.........................................................................................................22-11
m y
Objectives ......................................................................................................................................................25-4
d e
Workflow Definitions Loader........................................................................................................................25-5
Workflow XML Loader.................................................................................................................................25-7
c a
Summary........................................................................................................................................................25-11
Specialized Workflow Monitoring .................................................................................................................26-1
A
Specialized Workflow Monitoring ................................................................................................................26-3
Objectives ......................................................................................................................................................26-4
e
c l
Assigning Specialized Workflow Monitoring Privileges ..............................................................................26-5
Granting Restricted Access to Workflow Monitoring Data...........................................................................26-7
r a
Granting Restricted Access Based on Item Types .........................................................................................26-8
Granting Restricted Access Based on Functional Criteria.............................................................................26-9
Granting Permissions for Administrative Actions.........................................................................................26-11
O ly
Guided Demonstration - Setting Up Specialized Workflow Monitoring...................................................26-12
l & On
Summary........................................................................................................................................................26-15
Setting Up Oracle Workflow ..........................................................................................................................27-1
n a e
Setting Up Oracle Workflow .........................................................................................................................27-3
Objectives ......................................................................................................................................................27-4
t r s
Required Setup Steps.....................................................................................................................................27-5
e
Step 1 Setting Global Workflow Preferences ................................................................................................27-6
U
Step 2 Setting Up an Oracle Workflow Directory Service ............................................................................27-9
I n
Step 3 Running Background Engines ............................................................................................................27-13
Step 4 Configuring the Business Event System.............................................................................................27-16
l e
Step 4 Event Message Communication .........................................................................................................27-17
c
Step 4 Setting Up Database Links and Queues..............................................................................................27-18
r a
Step 4 Checking Database Parameters...........................................................................................................27-19
Step 4 Scheduling Agent Listeners................................................................................................................27-20
Step 4 Scheduling Propagation......................................................................................................................27-23
O Guided Demonstration - Scheduling Agent Listeners and Propagation ....................................................27-27
c a
Agent Listener Configuration Wizards..........................................................................................................28-17
Notification Mailers.......................................................................................................................................28-20
Outbound Notification Mailer Processing .....................................................................................................28-21
e A
Inbound Notification Mailer Processing........................................................................................................28-23
Notification Mailer Setup ..............................................................................................................................28-25
c l
Connecting to Mail Servers Through SSL.....................................................................................................28-27
Notification Mailer Basic Configuration .......................................................................................................28-28
r a
Notification Mailer Advanced Configuration................................................................................................28-30
Component Details for Notification Mailers .................................................................................................28-37
O ly
Notification Mailer Throughput ....................................................................................................................28-39
Guided Demonstration - Service Components ..........................................................................................28-40
l & On
Handling Notification Mailer Errors..............................................................................................................28-42
Summary........................................................................................................................................................28-43
a e
Managing System Status and Throughput ....................................................................................................29-1
n
e r
Managing System Status and Throughput .....................................................................................................29-3
s
Objectives ......................................................................................................................................................29-4
t U
Workflow System Status ...............................................................................................................................29-5
I n
Workflow Status in Oracle Applications Manager ........................................................................................29-7
Oracle Workflow Administration ..................................................................................................................29-9
e
Work Items ....................................................................................................................................................29-10
l
Oracle Workflow Administration ..................................................................................................................29-15
c
Purging Workflow Data.................................................................................................................................29-16
r a
Completed Work Items..................................................................................................................................29-21
Workflow Purge APIs ...................................................................................................................................29-24
m y
d e
c a
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle Corporation, 2007. All rights reserved.
Prerequisites
R12 Implement Oracle Workflow is an instructor-led course featuring lecture and hands-on
exercises. Online demonstrations and written practice sessions reinforce the concepts and skills
introduced.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle Corporation, 2007. All rights reserved.
Additional Publications
• Read-me files
Italic
proper noun)
Emphasized words Do not save changes to the database.
m y
and phrases,
titles of books and
For further information, see Oracle7 Server SQL Language
Reference Manual.
d e
courses,
variables
Enter user_id@us.oracle.com, where user_id is the
name of the user.
ca
Quotation
marks
Interface elements
with long names A
Select “Include a reusable module component” and click Finish.
e
that have only
initial caps;
c l
This subject is covered in Unit II, Lesson 3, “Working with
Objects.”
lesson and chapter
titles in cross-
r a
Uppercase
references
SQL column O ly Use the SELECT command to view information stored in the
names, commands,
l
functions, schemas,& On LAST_NAME
column of the EMP table.
table names
n a e
Arrow
Brackets
Commas
Menu paths
Key names
t e r
Key sequences
U s Select File > Save.
Press [Enter].
Press and release keys one at a time:
Plus signs I n
Key combinations
[Alternate], [F], [D]
Press and hold these keys simultaneously: [Ctrl]+[Alt]+[Del]
c l e
r a
O
Copyright © Oracle Corporation, 2007. All rights reserved.
(N) Invoice > Entry > Invoice Batches Summary (M) Query > Find (B) Approve
m y
This simplified path translates to the following:
d e
1. (N) From the Navigator window, select Invoice then Entry then Invoice Batches
Summary. ca
e A
2.
c l
(M) From the menu, select Query then Find.
c
r a (H) = Hyperlink
1. In the navigation frame of the help system window, expand the General Ledger entry.
4. Review the Enter Journals topic that appears in the document frame of the help system
window.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle Corporation, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Inter-Enterprise Business Processes
e A
c l
In e-business, different enterprises need to communicate with each other over the Internet.
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Traditional Workflow
e A
c l
Traditional applications-based workflow processes are launched from a business application
r a
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
O ly
only in that application’s system. For example, the modeling of an approval hierarchy is a
& On
common use of Oracle Workflow in this scenario.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow-Driven Business Processes
e A
Oracle Workflow can help save time by:
c l
• Reducing repetitive data entry tasks
r a
• Automating approval hierarchies
O ly
• Automatically delivering notifications and reminders of work to be done
l & On
• Providing self-service monitoring capabilities
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Sample Workflow Process
e A
c l
A workflow process consists of a sequence of activities that together make up a business flow,
r a
expressing your organization’s policies and rules. The activities can include significant
business events, automated functions, notifications to users, or subprocesses.
O ly
This example shows a sample order processing workflow process that includes business events.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Event-Based Workflow
e A
c l
With the Business Event System, Oracle Workflow supports both traditional applications-
r a
based workflows and event-based integration workflows.
For e-business, there is a requirement to integrate with external systems, such as sending a
O ly
document to a business-to-business exchange, or other systems external to the local
l & On
application. Oracle Workflow supports e-business integration workflows by allowing business
analysts and developers to model business processes spanning different systems using a
n a e
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
e r s
customers to deal with business objects in comprehensive e-business integration flows with
t U
minimal intrusion into the core application.
I n
The Business Event System and the Workflow Engine can function independently of each
e
other. However, you can achieve the most powerful and flexible processing by using the
l
Business Event System and the Workflow Engine together to execute cross-system processes
c
for e-business integration.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Subscription-Based Processing
e A
c l
The Business Event System provides increased flexibility through subscription-based
r a
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
O ly
workflow process when an event is raised by specifying that process in a subscription to the
l & On
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.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Business Process-Based Integration
e A
c l
Business process-based integration is model-driven.
r a
• Business rules are expressed in a process model.
O ly
• These rules define the policy for each end-to-end process.
• The process model can encompass applications both within and beyond the enterprise.
l & On
Business process-based integration provides:
a e
• A global, enterprise-level view of business objects
n
t e r
• Business process automation
s
Oracle Workflow supports business process-based integration through the Business Event
U
System.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Supported System Integration Types
e A
c l
The types of system integration supported by Oracle Workflow are message-based. By
r a
supporting the communication of messages between systems, Oracle Workflow lets you define
processing across different systems encompassing both your own enterprise and your business
O ly
partners. The power of this cross-system processing, together with the flexibility provided by
& On
subscription-based processing, enables you to use Oracle Workflow for e-business integration.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Designing Applications for Change
e A
The benefits of good design include:
c l
r a
• Reduced cost of ownership through diminished development costs
• Ease of management and maintenance
O ly
• Visual documentation of business processes
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Designing Business Processes for Change
e A
Complete process representation:
c l
r a
• A workflow process can cross organizational and company boundaries to represent an
end-to-end flow.
O ly
• You can provide alternatives within a process to accommodate different situations.
& On
• You can build management metrics and performance goals into a process.
l
Graphical development tool:
n a e
• The Oracle Workflow Builder separates business process definition and modeling from
code development.
t e r U s
• Workflow diagrams provide a visual overview of your processes.
I n
• You can easily modify a process definition.
c l e
Ease of management and maintenance:
• Oracle Workflow lets you analyze time and costs for entire business processes.
r a
• You can refine your process definitions according to your analysis to streamline them and
reduce time and costs.
O • You can easily implement a modified process.
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Designing Applications for Integration
e A
Business events as integration points:
c l
r a
• Applications can raise business events at any point where further processing or integration
might be required.
O ly
• You can define the processing to be triggered by an event immediately after defining the
event or at any later time.
Subscription-based processing: l & On
n a e
• Use subscriptions to specify the processing you want to perform for a business event.
t
for different purposes.e r U s
• You can define multiple subscriptions to the same event to perform additional processing
I n
Web-based business event and subscription management tool:
c l e
• 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
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow in Oracle E-Business Suite
e A
c l
In Oracle E-Business Suite, Oracle Workflow is incorporated in applications including
r a
Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and Human
Resources Management Systems (HRMS). Oracle Workflow is leveraged by both professional
O ly
applications, which are typically Forms-based applications for power users, and self-service
& On
applications, which are typically HTML-based applications for more casual users.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the sample solution file named wfvacXX_062.wft
from the file system.
4. Save the workflow definition to the class database using File > Save As. Then close the data
store.
6. Click the Developer Studio link. In the Search region of the Developer Studio page, enter
the name of the XX Vacation Proposal workflow item type and click Go. Then, in the
Results region, click the Run icon for the XX Vacation Proposal item type.
7. Enter a process owner, item key, user key, requestor, approver, from date, and to date. The
requestor and approver should have Workflow administrator and user responsibilities
assigned to them.
m y
8. Click the Submit button. A confirmation message appears. Click OK.
d e
9.
ca
Select the Status Monitor tab to review the process status in the Status Monitor Web pages.
•
e A
In the Search region, enter the XX Vacation Proposal item type and the item key you
chose, and click Go.
c l
•
r a
In the Results region, select your process and click the Activity History button to review
the process activities.
O ly
•
process.
l & On
Click the Status Diagram button to review the graphical diagram of the status of the
n a e
10. Log off and log in again as the approver. You can use either a Workflow administrator
t e r U s
responsibility or Workflow user responsibility.
n
11. Click the Notifications link.
I
c l e
12. In the Worklist, select the subject line for the Vacation Proposal notification sent by your
process to open the notification message.
r a
13. On the Notification Details page, approve or reject the proposal.
O
Copyright © Oracle, 2007. All rights reserved.
15. Open the Workflow Builder again and make a change to the process diagram, such as
adding a function activity by dragging and dropping the Noop function from the Standard
item type into the process. Then save the definition to the class database again.
16. Repeat steps 5 through 9 to show the new version of the workflow definition in use.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Architecture
e A
Development Client
c l
r a
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
O ly
process definitions and XML definitions for Business Event System objects.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Architecture
e A
Oracle Database
c l
r a
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
O ly
service. The Business Event System leverages the Advanced Queuing feature within the Oracle
Database.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Architecture
e A
Application Server
c l
r a
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
O ly
Workflow service components that run in the middle tier, such as agent listeners and
notification mailers.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Architecture
e A
End-User Client
c l
r a
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
O ly
accessing the Oracle Workflow Manager component available through Oracle Applications
l & On
Manager (OAM). The end-user client also includes a mail client application for reviewing and
responding to notifications by e-mail.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow Processes
e A
c l
A workflow process definition must be saved to the same database as the Workflow Engine. A
r a
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
O ly
event or by calling a series of Workflow Engine APIs.
l & On
• The Workflow Engine locates the “Start” activity in the process definition.
• The Workflow Engine drives through the process, performing all automated steps such as
a e
function activities and Raise and Send event activities, until an asynchronous activity such
n
t e r U s
as a notification, Receive event activity, or blocking activity occurs.
- The Workflow Engine calls the Notification System to deliver a notification message
I n
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
c l e
process.
- If a blocking activity is encountered, the Workflow Engine waits for an external
r a program to complete and call the appropriate Workflow Engine API before
proceeding to the next activity.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Supported Process Constructs
e A
c l
The Workflow Engine supports sophisticated workflow rules to model your business logic.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Builder
e A
c l
Saving workflow definitions as flat files on the local file system enables designers to back up
their work and use source control.
Navigator Tree r a
O ly
The navigator provides a tree structure for the workflow definition, with the highest level being
l & On
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,
a e
notifications, functions, events, messages, and lookup types. All these objects are organized
n
Process Diagram
t e r
into their respective categories within the tree.
U s
I n
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
l e
window. This method is called bottom-up design. You can also create new objects as you
c
design the diagram and complete the definitions of those objects later. This method is called
a
top-down design.
r
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Business Event System Architecture
e A
c l
The Business Event System is an application service that communicates business events
r a
between systems. Oracle Workflow with the Business Event System can act as a system
integration messaging hub that relays business event messages among systems.
O ly
The Business Event System leverages Oracle Advanced Queuing to send messages from one
system to another.
l & On
For the greatest flexibility in routing and processing business events, you can model your
a e
business process logic in powerful cross-system workflow processes that are executed by the
n
Workflow Engine.
t e r
Workflow Engine. However, the Business Event System can also function independently of the
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Advanced Queuing, an Enabling Technology
e A
c l
Oracle Advanced Queuing allows queue-to-queue propagation across machine boundaries.
r a
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
O ly
messages persistently and transmit them using various transport protocols.
l & On
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
n a e
Advanced Queuing based on the JMS standard. Oracle Workflow supports communication of
JMS Text messages through Oracle Advanced Queuing in a format called
e
SYS.AQ$_JMS_TEXT_MESSAGE.
t r U s
Oracle Workflow also supports business event messages in a standard Workflow format called
I n
WF_EVENT_T. You can additionally define custom message formats.
c l
Reference. e
For more information, refer to the Oracle Streams Advanced Queuing User’s Guide and
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Database Communication Alternatives
e A
c l
You can use Oracle Advanced Queuing for communication by SQLNET, HTTP, and HTTPS
r a
protocols, and for integration with third-party messaging solutions.
You can use Oracle Net Services (formerly Net8) to propagate messages by the SQLNET
O ly
protocol. Oracle Workflow supports JMS Text messages for SQLNET propagation, as well as
a e
The Oracle Streams Advanced Queuing Internet access functionality lets you perform Oracle
n
e r
Advanced Queuing operations over the Internet by using the Oracle Advanced Queuing
s
Internet Data Access Presentation (IDAP) for messages and transmitting the messages over the
t U
Internet using transport protocols such as HTTP or HTTPS.
I n
Messaging Gateway is a feature of Oracle Advanced Queuing that enables communication
c l e
between applications based on non-Oracle messaging systems and Oracle Advanced Queuing.
Standard Oracle Advanced Queuing functionality provides propagation between two Oracle
r a
Advanced Queuing queues; Messaging Gateway extends that propagation to legacy
applications based on non-Oracle messaging systems.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Home Pages
e A
c l
• Administrator home page: Lists your five highest priority notifications. Also provides tabs
r a
to the Developer Studio, Event Manager (Business Events), administrator Status Monitor,
Advanced Worklist, and Administration pages.
O ly
• Self-service home page: Lists your five highest priority notifications as well as the five
l & On
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.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Notification System
e A
The Notification System:
c l
r a
• Routes notifications to a role, which can be a single user or group of users
O ly
• Enables users to receive and respond to notifications using an e-mail application or Web
browser of choice
& On
• Sends e-mail notifications and processes e-mail responses using the JavaMail API
l
n a e
• 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
t e r U s
• Enables users to drill down from a notification in the Worklist web pages to any URL or
I n
Oracle E-Business Suite form to respond to the notification
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Worklist Web Pages
e A
c l
Oracle Workflow includes two different versions of the Worklist in the Oracle Application
Framework user interface format:
r a
• Advanced Worklist: Provides full notification information as well as additional options for
O ly
displaying and administering notifications
notifications
l & On
• Personal Worklist: Provides additional search and filtering options for displaying
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Directory Services
e A
c l
Users can be associated with more than one role, and a role may contain more than one user.
r a
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
O ly
user or to all members of a particular role.
l & On
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
n a e
synchronization between the user and role information stored in application tables by the
source modules and the information stored in the Workflow local tables.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow Monitor
e A
c l
Oracle Workflow includes both administrator and self-service versions of the Status Monitor in
a
the Oracle Application Framework user interface format.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Loading Workflow Definitions
e A
c l
The Workflow Definitions Loader is a utility program that lets you transfer process definitions
O ly
• Lets you upgrade a database with new versions of process definitions or upload existing
l & On
process definitions after a database upgrade.
• Is also integrated into Oracle Workflow Builder.
n a e
• Allows process definitions to be source-controlled as flat files.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow XML Loader
e A
c l
The Workflow XML Loader is a utility program that lets you transfer XML definitions for
r a
Business Event System objects between a database and a flat file.
• When you download Business Event System object definitions from a database, Oracle
O ly
Workflow saves the definitions as an XML file.
l & On
• 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
a e
new definitions or updating existing definitions as necessary.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow Manager
e A
c l
Administrators can use Workflow Manager to perform the following tasks:
r a
• Run Workflow service components, such as notification mailers and agent listeners.
O ly
• Control other Workflow system services, including background engines, purging obsolete
Workflow data, and cleanup of the Workflow control queue.
l & On
• Monitor work item processing by viewing the distribution of all work items by status and
drilling down to additional information.
n a e
• Monitor event message processing for local Business Event System agents by viewing the
t e r U s
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.
I n
With this ability to monitor work items and event messages, a system administrator can
identify possible bottlenecks easily.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Service Components
e A
c l
Oracle Workflow uses the Generic Service Component Framework (GSCF) to simplify and
r a
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.
O ly
l & On
Use Oracle Workflow Manager to configure and run service components.
Note: Oracle Workflow Manager also lets you manage Web services outbound components,
a e
which process outbound Web service messages for Oracle XML Gateway. For more
n
t e r
information, see the Oracle XML Gateway User’s Guide.
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Documentation
e A
c l
The main Oracle Workflow documentation set includes the following:
r a
• 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
O ly
monitor the progress of run-time workflow processes.
l & On
• Oracle Workflow Developer’s Guide: Explains how to define new workflow business
processes and customize existing Oracle E-Business Suite-embedded workflow processes.
a e
It also describes how to define and customize business events and event subscriptions.
n
t e r U s
• Oracle Workflow User’s Guide: Describes how users can view and respond to workflow
notifications and monitor the progress of their workflow processes.
I n
• Oracle Workflow API Reference: Describes the APIs provided for developers and
administrators to access Oracle Workflow.
l e
You can also consult the following:
c
• Installation documentation for your release and platform, usually available within the
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Review Questions and Solutions
e A
Which component of Oracle Workflow:
c l
r a
• Communicates business events among systems? Business Event System
O ly
• Executes workflow processes? Workflow Engine
• Lets you develop workflow process definitions? Oracle Workflow Builder
l & On
• Delivers process-related messages to users? Notification System
a e
• Lets you review and administer a run-time process? Status Monitor
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Workflow Process Components
e A
c l
• Data Store: A database connection or flat file that holds a workflow process definition.
r a
• 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
O ly
type can contain multiple processes.
l & On
• 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.
a e
• Process Activity: A series of actions that need to be performed to accomplish a business
n
t e r U s
goal. A process is represented by a workflow diagram. A process can include function
activities, notification activities, event activities, and other process activities
I n
(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
l e
workflow process.
c
• Notification Activity: A unit of work that requires human intervention. A notification
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Builder
e A
c l
In the navigator tree, each item type includes the following branches:
• Attributes
r a
• Processes (Subprocesses)
• Notifications O ly
• Functions
l & On
• Events
n a e
• Messages
• Lookup Types
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Standard Activities
e A
c l
The Standard item type is automatically installed on your Oracle Workflow server.You can
r a
also access the Standard item type from the file wfstd.wft located on your PC in the
\<ORACLE_HOME>\Wf\data\<language>\ subdirectory.
O ly
The standard activities provided by Oracle Workflow include:
• And
• Or l & On
• Compare Date
n a e
• Compare Number
• Compare Text
t e r U s
I n
• Compare Execution Time
• Wait
c
• Block l e
r a
• Defer Thread
O • Launch Process
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Planning a Workflow Process
e A
c l
Consider modeling your process so that it can be customized and extended in the future.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Planning a Workflow Process
e A
c l
If the process will begin with a Receive event activity, the calling application must raise an
r a
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
O ly
workflow process that has the Receive event activity, which must be marked as a Start activity
node.
l & On
If the process will begin with a standard Start function activity, the activity must be marked as
n a e
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,
e r s
or WF_ENGINE.LaunchProcess, which is a wrapper combining the CreateProcess and
t U
StartProcess APIs. You can use WF_ENGINE.LaunchProcess if you do not need to set any
I n
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
l e
WF_ENGINE_BULK.CreateProcess and WF_ENGINE_BULK.StartProcess or
c
WF_ENGINE_BULK.FastForward to launch multiple processes in bulk.
r a
Note: Using the standard Start function activity lets you visually represent the start of the
O process in your diagram. Alternatively, you can choose to start the process with another
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Activity Results and Lookup Types
e A
Process Activities
c l
r a
The diagram for a process activity can include functions, notifications, events, and other
processes.
O ly
A process activity can be completed with a specific result that is defined in a lookup type. For
l & On
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
n a e
t e r U s
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.
I n
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.
l e
Notification Activities
c
The message sent by a notification activity can simply convey information or it can require a
r a
response.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Tasks
Planning a Workflow Process
On paper, sketch a diagram of a vacation proposal process. The business process is as follows:
• If the approver approves the proposal, the requestor receives a notification reporting
that the vacation is approved.
• If the approver rejects the proposal, the requestor receives a notification reporting that
the vacation is rejected.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. Make a sketch of a diagram on paper, placing the activities in the approximate order in
which they will occur.
Hint: The process should include only start, end, and notification activities.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Quick Start Wizard
e A
New Item Type Properties
c l
r a
• Internal Name: Specify an all uppercase internal name with a maximum of eight
characters. Do not include colons or leading or trailing spaces.
O ly
• Display Name: Enter a translatable display name for the item type.
l & On
• 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
a e
is eligible for purging after the process is complete. If the persistence type is Permanent,
n
t e r U s
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
I n
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
l e
the time an item type instance completes before its status audit trail can be purged.
c
New Process Properties
r a
• Internal Name: Specify an all uppercase internal name. Do not include colons or leading
or trailing spaces.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining an Item Type
e A
To define an item type:
c l
r a
1. Select a data store in the navigator tree, or create a new data store by choosing New from
the File menu.
O ly
2. Create a new item type by selecting New > Item Type from the Edit menu.
l & On
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.
n a e
4. Enter a translatable display name for the item type.
t e r U s
5. Enter a description of the item type.
6. Specify Temporary or Permanent persistence for the status audit trail of the item type.
I n
The persistence type controls when the run-time process status information is eligible for
purging after the process is complete.
l e
7. If the persistence type is Temporary, specify the number of days from the time an item
c
r a 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.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Process Activity
e A
To define a process activity:
c l
r a
1. In Oracle Workflow Builder, select the item type that you want in the navigator tree.
Then select New Process from the Edit menu.
O ly
2. In the Activity property page, enter an internal name for the activity. The internal name
l & On
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the activity.
n a e
4. Enter a description of the activity.
t e r U s
5. Choose an icon that identifies the activity.
6. Specify the result type that contains the possible results that the process can return.
I n
7. Select the Runnable check box if this is a top-level workflow process that can be
l e
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
c
r a 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
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Diagramming a Process
e A
c l
Each process diagram must have one or more Start activities and one or more End activities.
r a
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,
O ly
and Performer appear in a tool tip display.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Top-Down Design
e A
c l
When you create a new activity in the process window, the property pages displayed for
r a
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
O ly
and a display name for the activity in order to use the activity in the diagram. You can also
l & On
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.
n a e
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
e r s
process definition and correct the errors later.
t U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Diagramming a Process
e A
c l
If the source activity has no result type associated with it, by default no label appears on the
r a
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>.
O ly
l & On
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
a e
• When a result returned is not covered by other transitions, labeled <Default>
n
t e r U s
• Regardless of result returned, labeled <Any>
• When the activity times out, labeled <Timeout>
I n
Note: The Timeout property for the node must be set to enable the <Timeout> option in the list
of results for the transition.
l e
If the source activity is a voting activity, you can also create transitions to follow:
c
r a
• When the vote results in a tie, labeled <Tie>
• When the vote doesn’t return a result, labeled <No Match>
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
<Default> Transition
e A
c l
The Workflow Engine follows a <Default> transition if no other transition matching the
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
<Any> Transition
e A
c l
The Workflow Engine follows an <Any> transition regardless of what completion result the
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Self-Looping Transitions
e A
To draw a self-looping transition:
c l
1. Select the activity node.
r a
O ly
2. Hold down the right mouse button.
3. Drag the cursor away from and back to the same activity node.
l & On
4. Release the right mouse button and select the transition label from the list of results.
a e
Alternatively, you can also use the following steps:
n
t e r
1. Draw a transition to some other activity.
s
2. Add a vertex point to the transition.
U
I n
3. Select the arrowhead of the transition with the left mouse button and drag it back to the
originating activity.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Customizing an Activity Node
e A
To define node properties:
c l
r a
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.
O ly
2. Specify a label for the node. By default, the label name is the activity name. If you use an
l & On
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.
a e
3. Specify whether the activity is a Start, End, or Normal activity in the process.
n
t e r U s
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
I n
the possible results listed in the result type of the process activity.
4. Optionally enter a comment about this node.
l e
5. For a notification activity, a process activity, or a Receive event activity, use the Timeout
c
region to specify whether the activity must be completed by some specified time.
r a
6. For a notification activity or a Send event activity, optionally specify the message
priority.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Show Label in Designer Menu Options
e A
c l
• Instance Label: Uses the node label for each activity node
r a
• Internal Name: Uses the internal name of the activity as the label for each activity node
O ly
• 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
l & On
• Comment: Uses the activity’s comment as the label for each activity node
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Display Modes
e A
c
In developer mode, Oracle Workflow Builder:l
r a
• Provides visual distinctions between top-level processes and subprocesses in the navigator
tree
O ly
• Sets the icons for each activity and object to the default icon of its object type or subtype
l & On
in both the navigator tree and the process diagram window
• Identifies each object in the navigator tree by its internal name (developer name)
n a e
• Identifies each activity in the process diagram window by its activity label
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Verifying a Process Definition
e A
c l
You should always validate any new process definition you create, because validation helps
successfully. r a
you identify any potential problems with the definition that might prevent it from executing
O ly
Note: The Verify option is enabled in the File menu only when the navigator tree is the current
window.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Saving Process Definitions
e A
c l
If a non-unique display name is encountered when a process definition is being uploaded or
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Tasks
Creating a Workflow Process
Create a workflow process in the Oracle Workflow Builder using the Quick Start Wizard. Your
m y
a Workflow Process practice.
d e
workflow process should model the vacation proposal process that you sketched in the Planning
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
• Click OK. The XX Vacation Proposal Process window appears, populated with the Start
and End nodes.
4. Create notification activity nodes for Vacation Proposal, Vacation Rejected FYI, and
Vacation Approved FYI notification activities.
m y
•
d e
For each notification, click the New Notification button in the process diagram window
a
toolbar, and then click an open spot in the diagram between the Start and End nodes
c
•
e A
In the node properties window for each notification, enter an internal name and display
name and click an icon on the Notification tab. For the Vacation Proposal notification,
c l
select the Approval lookup type that is provided in the Standard item type as the Result
Type for the activity. Then click OK.
r a
5.
O ly
Create a new End node by dragging the End function from the Standard item type in the
navigator tree into the process diagram window. Double-click the new End node and select
& On
the Node tab. In the Start/End field, select End and then click OK.
l
6.
a e
In the process diagram, draw transitions between the nodes in the process to indicate the
n
e r
process flow. To draw a transition, right-click the source activity, hold down the right
s
mouse button, drag the cursor to the destination activity, and release the right mouse button.
t U
For transitions from the Vacation Proposal node, select the appropriate result from the
I n
results menu that appears. Select Approve for the Vacation Approved FYI notification
activity and Reject for the Vacation Rejected FYI notification activity.
7.
c l e
Select the XX Vacation Proposal Process in the navigator tree, right-click the process
r a activity, and select Properties to open the property pages for the process.
O8. Select the Activity tab and select Approval as the result type for the process. Then click OK.
10. Double-click the End node that follows the Vacation Approved FYI node and select the
Node tab. Select Approve in the Result field and then click OK.
11. In the Navigator window, click the Verify button to verify your workflow. Because you
have not yet defined the underlying components for your process, the Workflow Error
window displays warnings for validation checks that the process does not yet satisfy.
Review the error messages to learn about the errors. In later practices, you will add
additional functionality to your workflow to eliminate these errors. Click Cancel to exit the
Workflow Error window.
12. From the File menu, select Save As and save your new data store and item type to a
workflow definition file named wfvacXX.wft. The Oracle Workflow Builder will verify your
workflow again. Click Save in the Workflow Error window to finish saving the workflow
definition.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Item Type Attributes
e A
c l
Note: Do not use item type attributes as a denormalized data store. Always refer back to the
r a
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
O ly
type attributes when a process instance is created. Minimize the number of item type attributes
Examples
l & On
to improve the performance of your workflow process.
a e
For example, the Requisition demonstration workflow includes item type attributes for the
n
e r
following information: Forward From Username, Forward To Username, Requestor Username,
s
Requisition Amount, Requisition Number, Monitor URL, Requisition Description, Requisition
t U
Process Owner, Reminder Requisition Document, Note, and Note for Reminder.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Attribute Data Types
e A
c l
• Text: A string of text of specified character length.
r a
• Number: A number with an optional format mask.
O ly
• Date: A date with an optional format mask.
• Lookup: A lookup code value from a specified lookup type.
l & On
• Role: A role name from the list of roles defined in the directory service.
n a e
• Attribute: The internal name of another existing item type attribute to which you want to
maintain references in a process.
e r s
• URL: A Universal Resource Locator (URL) to a network location.
t U
• Form: The internal function name and any optional form parameters of an Oracle E-
I n
Business Suite form function.
c l e
• 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
r 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
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Item Type Attributes
e A
To define an item type attribute:
c l
r a
1. In the Oracle Workflow Builder, select the item type you want in the navigator tree. Then
select New Attribute from the Edit menu.
O ly
2. In the Attribute property page, enter an internal name for the attribute. The internal name
l & On
must be all uppercase without any leading or trailing spaces.
3. Enter a display name for the attribute.
n a e
4. Enter a description of the attribute.
t e r U s
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.
I n
7. Click Apply to save your changes.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
URL Attributes
e A
c l
When you specify a frame target, you can select from the following options:
r a
• New Window: The URL loads in a new, unnamed browser window.
O ly
• Full Window: The URL loads into the full, original window.
Note: The Notification Details page no longer uses frames to display notifications.
Window. l & On
Consequently, selecting Same Frame or Parent Frameset is equivalent to selecting Full
http://<location>
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
URL Attributes
e A
c l
When defining a URL attribute to point to such an image, you must provide the complete URL
r a
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.
O ly
Note: Oracle Workflow displays images only in the message body of a notification. If you
l & On
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.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
URL Attributes
e A
c l
In a plain text e-mail notification, the URL location value for an attached URL attribute is
included as plain text.
r a
In an HTML-formatted e-mail notification, a URL attribute appears as a hypertext link in the
O ly
message body. For attached URL attributes, an attachment called Notification References is
l & On
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.
a e
If you define a URL attribute for an image, when the notification is viewed from the
n
the message body.
t e r
Notification Details Web page or as an HTML-formatted e-mail, the image appears inline in
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Form Attributes
e A
Form Attribute Values
c l
r a
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
O ly
prequeried with a value when the form is opened.
& On
The default value for the form attribute must be entered using the following format:
l
a e
function_name:parameter1=value1 parameter2=value2 ...parameterN=valueN
r n
The value of a form parameter can be a text string enclosed in quotes (“ “) or can be token
s
substituted with another predefined item type attribute in either of the following ways:
t e U
• parameterN = “&item_type_attribute”
n
I
• parameterN = “Value &item_type_attribute”, where
&item_type_attribute represents the rest of the value
e
l
To find the internal function name for a form function, navigate to the form, select About
c
r a
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
O responsibility and use the Forms window to query for the user form name based on the internal
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Note
e A
c l
Form attributes cannot be attached to e-mail notifications. To view form attachments, you must
a
view the notification in the Notification Details Web page.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Document Type Attributes
e A
c l
PL/SQL, PL/SQL CLOB, and PL/SQL BLOB documents are useful when document content
r a
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 O ly
l & On
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:
n a e
PLSQL:<procedure>/<document_identifier>
t e r U s
• A PL/SQL CLOB document value is specified in the format:
n
PLSQLCLOB:<procedure>/<document_identifier>
I
• A PL/SQL BLOB document value is specified in the format:
e
c l
PLSQLBLOB:<procedure>/<document_identifier>
Replace <procedure> with the PL/SQL package and procedure name, separated by a period.
r a
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.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Document Type Attributes
e A
c l
In a plain-text e-mail notification, PL/SQL, PL/SQL CLOB, and PL/SQL BLOB document
r a
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
O ly
reader does not recognize attachments. To view these attachments, you should display your
l & On
notifications in the Notification Details Web page.
In an HTML-formatted e-mail notification with an attached PL/SQL, PL/SQL CLOB, or
e r s
An Oracle Application Framework region can only be displayed within the message body of a
t U
notification. It cannot be included as an attachment to the notification.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Deleting Item Attributes
e A
c l
Deleting an item attribute from a workflow definition stored in a flat file and then uploading
r a
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
O ly
definition and also delete it specifically from any databases in which that workflow item type is
& On
loaded while connected to those databases.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Lookup Types
e A
c l
Although lookup types must be associated with a given item type and are defined in the
r a
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: O ly
l & On
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.
a e
2. In the Lookup Type property page, enter an internal name for the lookup type. The
n
t e r U s
internal name must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the lookup type.
I n
4. Enter a description of the lookup type.
5. Click Apply to save your changes.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Lookup Codes
e A
To define a lookup code:
c l
r a
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.
O ly
2. In the Lookup Code property page, enter an internal name for the lookup code. The
l & On
internal name must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the lookup code.
n a e
4. Enter a description of the lookup code.
t e r U s
5. Choose Apply to save your changes.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Tasks
Defining Item Type Attributes
Define item type attributes for the Vacation Proposal item type that you created in the Creating a
Workflow Process practice.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
• Click OK.
ca
• Click OK.
e A
8.
l
From the Edit menu, select New > Attribute.
c
9.
a
Define the following properties for the item attribute:
− Internal Name: FROM_DATE r
− Display Name: From Date
O ly
− Type: Date
− Format: DD-MON-RRRR
l & On
n a e
• Click OK.
t e r U s
10. From the Edit menu, select New > Attribute.
I n
11. Define the following properties for the item attribute:
l e
− Internal Name: TO_DATE
c
− Display Name: To Date
r a − Type: Date
− Format: DD-MON-RRRR
O
Copyright © Oracle, 2007. All rights reserved.
• Click OK.
14. You can optionally create a URL item attribute to test how Oracle Workflow includes URL
links in notifications. From the Edit menu, select New > Attribute.
• Click OK.
16. 16. You can optionally create a form item attribute to test how Oracle Workflow attaches
m y
Oracle E-Business Suite forms to notifications. From the Edit menu, select New > Attribute.
d e
17. Define the following properties for the item attribute:
− Internal Name: FORM_EXAMPLE
ca
− Display Name: Form Example
− Type: Form
e A
− Default Value: FND_FNDSCAUS
c l
• Click OK.
r a
O ly
18. From the File menu, select Save. The Oracle Workflow Builder will verify your workflow.
& On
Click Save in the Workflow Error window to finish saving the workflow definition.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Message
e A
To create a new message:
c l
r a
1. In the Oracle Workflow Builder, select the item type you want in the navigator tree. Then
select New Message from the Edit menu.
O ly
2. On the Message property page, enter an internal name for the message. The internal name
l & On
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the message.
n a e
4. Enter a description of the message.
t e r U s
5. Select the priority for the message (High, Normal, or Low). Message recipients can sort
their notifications based on the priority.
I n
6. Click Apply to save your changes.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Message
e A
To define the body for a message:
c l
r a
1. In the message property pages, select the Body tab.
O ly
2. Enter the subject line for the message.
3. Enter the plain text message body in the Text Body tab.
l & On
4. Enter the HTML-formatted message body in the HTML Body tab.
a e
5. Choose Apply to save your changes.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Message Attribute
e A
To define a message attribute:
c l
r a
1. In the Oracle Workflow Builder, select the message you want in the navigator tree. Then
select New Attribute from the Edit menu.
O ly
2. On the Attribute property page, enter an internal name for the attribute. The internal name
l & On
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the attribute.
n a e
4. Enter a description of the attribute.
t e r U s
5. In the Type field, select the data type for the attribute.
6. Depending on the data type, enter format information, if applicable.
I n
7. Specify either Send or Respond in the Source field to indicate whether the attribute should
l e
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
c
r a subject and message body for token substitution.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Respond Attribute
e A
c l
The icon for a Respond attribute in the navigator tree includes a red question mark in its lower
r a
left corner to distinguish it from Send attributes.
The Notification System uses the Respond attributes defined for the message to generate the
O ly
response section of the notification sent to the recipient. The response section is composed
l & On
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
n a e
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
e r s
response method. (HTML e-mail notifications always use the templated response method.)
t U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Message
e A
c l
The icon for a message in the navigator tree includes a red question mark in its lower left
O ly
1. On the message property pages, select the Result tab.
l & On
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-
a e
down menu that appears in the Notification Details page if there are more than four
n
possible result values.
t e r U s
3. Enter a description for the result.
I n
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
l e
sends the notification message.
c
5. Optionally, set the default value of the result to reference either a constant or the run-time
m y
d e
ca
Notification Details Web Page
e A
Images in an HTML message:
c l
r a
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
O ly
body of the message, then Oracle Workflow displays the image inline in the Notification
Details page.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
HTML E-mail Notifications
e A
c l
The response template consists of the required notification ID and access key that identify the
O ly
Depending on the notification, the auto-generated e-mail response template may also prompt
l & On
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
a e
attribute, similarly to the response section for plain text templated response.
n
each prompt.
t e r
The user supplies responses by editing the response value text between the quotes following
U s
I n
Images in an HTML message:
If you define a “Send” message attribute of type URL that points to an image file with an
l e
extension of gif, jpg, png, tif, bmp, or jpeg, and you embed the URL attribute in the HTML
c
body of the message, then Oracle Workflow displays the image inline in HTML-formatted e-
a
mail notifications.
r
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Plain Text E-mail Notifications Using Templated Response
A
c l
• Description: The description of the Respond attribute; this description provides optional
r a
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. O ly
l & On
• List of lookup codes: If the attribute is of type lookup, the lookup codes that are the
possible response values are listed.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Plain Text E-mail Notifications Using Direct Response
A
c l
• Display Name: The display name of the Respond attribute; this name specifies the
response value that is expected.
r a
• Sequence: The sequence position of this Respond attribute among all the Respond
O ly
attributes of the message, as listed in the navigator tree.
l & On
• Description: The description of the Respond attribute; this description provides optional
information on how to complete a response.
a e
• Type Hint: A standard hint that is provided based on the attribute’s type:
n
Type
t e r
Type Hint
U s
Lookup
I n
Value must be one of the following:
Date
c l e <list of lookup codes>
Value must be a date in the form “<format>“.
r a Number
Text
Value must be a number in the form “<format>“.
Value must be <format> bytes or less.
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Tasks
Defining Messages
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
5. Define a Vacation Proposal message that informs the approver of the vacation proposal.
• On the Body tab, enter the following message text body including the message attribute
tokens for the requestor, approver, and the start and end dates of the proposed vacation:
Requestor: &REQUESTOR
m y
Approver: &APPROVER
d e
From Date: &FROM_DATE
ca
To Date: &TO_DATE
e A
•
c l
On the Result tab, enter Approve as the display name, enter “Please approve or reject
this proposal” as the description, and select the Approval lookup type.
6. r a
In the Navigator window, drag and drop the Requestor, Approver, From Date, To Date, and
O ly
Comments item attributes onto the message to create the corresponding message attributes
l & On
with those item attributes as their default values. If you created URL Example and Form
Example attributes, drag and drop those attributes onto the message as well. For the
a e
Comments attribute, set the Source field to Respond. For the URL Example attribute, select
n
7.
t e r
the Attach Content check box.
U s
From the Edit menu, select New > Message.
8. I n
Define a Vacation Rejected that informs the requestor that the vacation proposal was
l
rejected.
c e
O ra
• On the Message tab, set the message priority to Low.
Requestor: &REQUESTOR
Approver: &APPROVER
To Date: &TO_DATE
Comments: &COMMENTS
• Drag and drop the appropriate item attributes onto the message to create the
corresponding message attributes with those item attributes as their default values.
10. Define a Vacation Approved message that informs the requestor that the vacation proposal
was approved.
e
The following vacation proposal was approved. A
Requestor: &REQUESTOR
c l
Approver: &APPROVER r a
O ly
From Date: &FROM_DATE
l & On
To Date: &TO_DATE
n a e
Comments: &COMMENTS
t e r U s
•
I n
Drag and drop the appropriate item attributes onto the message to create the
corresponding message attributes with those item attributes as their default values.
l e
11. From the File menu, select Save. The Oracle Workflow Builder will verify your workflow.
c
Click Save in the Workflow Error window to finish saving the workflow definition.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Notification Activity
e A
To define a notification activity:
c l
r a
1. In Oracle Workflow Builder, select the item type that you want in the navigator tree.
Then select New Notification from the Edit menu.
O ly
2. On the Activity property page, enter an internal name for the activity. The internal name
l & On
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the activity.
n a e
4. Enter a description of the activity.
t e r U s
5. Select an icon that identifies the activity.
6. Optionally specify a PL/SQL stored procedure in the Function field. The procedure is
I n
known as a post-notification function and can be used to couple processing logic to the
notification activity.
l e
7. Specify the result type that contains the possible results that the notification can return. If
c
r a 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Standard Voting Activity
e A
c l
The activity sends a message called “Default Voting Message Yes/No” that includes a message
r a
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.
O ly
Choose “Expand Roles” for the notification activity to ensure that all users in the role receive a
copy of the notification.
l & On
When the activity receives responses, it executes a PL/SQL procedure called
a e
WF_STANDARD.VOTEFORRESULTTYPE to tally the Yes/No responses.
n
t e r U s
Vote Yes/No has three activity attributes associated with it:
• Voting Option: Specifies when and how to tally the votes
I n
• 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
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Timeout for a Notification
e A
c l
• Choose “No Timeout” if the notification does not have to be completed by a certain time.
r a
• 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
O ly
the activity times out. The value you enter is interpreted as a relative offset from the begin
l & On
date of the activity, in the unit of minutes.
Note: A relative timeout value of zero means there is no timeout.
n a e
• Choose “Item Attribute” if you want the notification to be completed by some relative
t e r U s
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
I n
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.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Dynamic Priority for a Notification
e A
c l
You can set the override priority as a constant of High, Normal, or Low, or you can reference
• High: 1-33 r a
an item attribute. The item attribute must be of type number, and the following ranges apply:
• Normal: 34-66 O ly
• Low: 67-99
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Special Message Attributes
e A
c l
You can define special message attributes to specify how a notification is displayed or handled.
r a
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
O ly
enter a display name and description of your own choosing. For information on additional
#HIDE_REASSIGN
l & On
special message attributes, see the Oracle Workflow Developer’s Guide.
a e
Use #HIDE_REASSIGN to hide the Reassign button in the Notification Details Web page. The
n
e r
response section in the Notification Details page includes the Reassign button by default. If
s
you want to restrict users from reassigning a notification, you can add the #HIDE_REASSIGN
t U
attribute to control whether the Reassign button is displayed or hidden.
I n
The #HIDE_REASSIGN attribute also controls whether a notification can be reassigned using
c l e
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
r a
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
O vacation rules. You can choose to both hide the Reassign button and prevent reassignment
m y
d e
ca
Special Message Attributes
e A
#WF_SECURITY_POLICY
c l
r a
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,
O ly
users receive an e-mail message that only informs them that they must access the notification
l & On
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
a e
from being sent in e-mail, set the value of the #WF_SECURITY_POLICY attribute to
n
e r
NO_EMAIL. If you set the value to EMAIL_OK or DEFAULT, leave the value blank, or if
s
you do not define a #WF_SECURITY_POLICY attribute for the message, Oracle Workflow
t U
sends the full notification content in e-mail to users whose notification preference is set to
receive e-mail.
I n
c l e
Notification Mailer Attributes
Use these attributes to control how a notification mailer generates the e-mail message for a
r 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
O these attributes for those notifications. Values that you specify in these attributes for a
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Special Message Attributes
e A
#WF_REASSIGN_LOV
c l
r a
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
O ly
the notification is reassigned, and assign this role as the value for the #WF_REASSIGN_LOV
l & On
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.
a e
The #WF_REASSIGN_LOV attribute must be of type role and must have a source of Send. If
n
t e r
no existing role meets your needs, you can include logic in your process to create an ad hoc
s
role at run time and add the users you want to that role.
U
#HIDE_MOREINFO
I n
When users view a notification that requires a response in the Notification Details page, the
l e
response region includes the Request Information button by default. If you want to prevent
c
users from requesting more information about a notification, you can add the
r a
#HIDE_MOREINFO attribute to control whether the Request Information button is displayed
or hidden.
O
Copyright © Oracle, 2007. All rights reserved.
r a
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
O ly
#WF_SIG_POLICY attribute for the message, Oracle Workflow performs the default
l & On
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
a e
predefined Signature Policy lookup type provided in the Standard item type.
n
t e r U s
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
I n
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
l e
workflow can include a notification to an administrator to confirm the signature status before
c
continuing.
r a
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
O delete any notifications that required signatures or their associated signature information. If
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Action History
e A
c l
The action history table contains a row for each previous execution of the same notification
r a
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
O ly
notification to several approvers in turn, the action history table would contain a row for
l & On
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
a e
mode, or if one user requests more information about the notification and another user
n
t e r
answers that request, the action history contains rows for those actions also.
Including the Action History Table
U s
I n
• If the notification requires a response, then Oracle Workflow automatically includes the
action history table in the notification.
l e
• If the notification does not require a response, then Oracle Workflow only includes the
c
action history table automatically if the notification has been reassigned at least once or if
r a 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
O WF_NOTIFICATION(HISTORY) in the message body.
m y
d e
ca
Special Message Function
e A
c l
Oracle Workflow creates the tables as Oracle Application Framework regions, unless the
r a
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.
O ly
l & On
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
n a e
t e r U s
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
I n
commas. Use the following format:
WF_NOTIFICATION(ATTRS,<attribute1>,<attribute2>,<attribute3>,...)
l e
Note: Do not include any spaces or carriage returns in the call to WF_NOTIFICATION(). You
c
only need to use a comma to delimit the parameters in the list.
r a
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.
O Action History Table
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
Embedding Oracle Applications Framework Regions in Notifications
r a
For more information, see the Oracle Workflow Developer’s Guide and the Oracle Application
Framework Developer’s Guide, available from OracleMetaLink note 391554.1.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the connect string for the class database and the
user name and password of the Oracle Workflow database account.
Tasks
m y
Defining a Special Message Attribute
d e
ca
Define a special message attribute to hide the Reassign button in the Notification Details page
for one of the messages that you created in the Defining Messages practice.
e A
Defining Notification Activities
c l
r a
Use the messages that you created in the Defining Messages practice to complete the notification
activity definitions for the item type.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
3. In the Navigator window, select the Vacation Proposal message. Then, from the Edit menu,
select New > Attribute.
• Click OK. Defining the special #HIDE_REASSIGN message attribute and setting its
value to Yes (internal value Y) will hide the Reassign button in the Notification Details
m y
from reassigning the notification in a mass reassignment from the Advanced Worklist,
d e
page for the notification that sends this message. This attribute will also prevent users
e A
5.
c l
In the Navigator window, expand your XX Vacation Proposal item type and then drag and
r a
drop each message onto the corresponding notification activity to assign that message to the
activity. To verify that each notification activity has an appropriate message, double-click
O ly
each notification activity to open the property window and then verify the value in the
Message field. For example, the Vacation Approved message should appear in the Message
& On
field for the Vacation Approved FYI notification activity.
l
6.
a e
Open the process diagram window for the process.
n
7.
e r s
Double-click the Vacation Proposal node and select the Node tab. Set the performer for the
t U
node to the Approver item attribute.
8. I n
Double-click the Vacation Rejected FYI node and select the Node tab. Set the performer for
l e
node to the Requestor item attribute.
c
9.
r a Double-click the Vacation Approved FYI node and select the Node tab. Set the performer
for node to the Requestor item attribute.
O
Copyright © Oracle, 2007. All rights reserved.
11. From the File menu, select Save to save your work to your workflow definition file.
m y
d e
ca
12. From the File menu, select Save As and save your item type to the class database, using the
database user name, password, and connect string provided by the instructor.
e A
13. Close the data store.
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Testing Workflow Processes
e A
c l
Use a Web browser to navigate to the Developer Studio, using a responsibility and navigation
O ly
• Workflow Administrator Web Applications: Developer Studio
l & On
• Workflow Administrator Web (New): Developer Studio
• Workflow Administrator Event Manager: Developer Studio
n a e
You can navigate to the Developer Studio from other Oracle Workflow administrator Web
the page.
t e r U s
pages by selecting the Developer Studio tab or clicking the Developer Studio link at the end of
I n
Note: You must have workflow administrator privileges to run a test workflow from the
Developer Studio.
l e
In the Search region of the Developer Studio, enter search criteria to locate the workflow
c
process definitions you want to display. You can search by the workflow item type display
r a
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
O your search.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Administrator Monitor
e A
c l
The administrator version of the Status Monitor lets you view and administer runtime
workflows. You can:
r a
• Review the activities performed for a workflow.
O ly
• Check the status of the workflow by viewing the status diagram.
& On
• Examine responses to notifications sent by the workflow.
l
n a e
• Review the workflow definition and attributes.
• If you have the appropriate workflow administrator privileges, you can also perform
t e r
Workflow Administrator Privileges
U s
control operations for a workflow or handle an error.
I n
Users have workflow administrator privileges if they belong to the Oracle Workflow
c l e
administration role, which is defined in the Workflow Configuration Web page.
Oracle Workflow also allows users to be assigned specialized workflow monitoring privileges
r a
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
O been granted access. For example, you may only have access to monitor workflows belonging
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing Workflows in the Administrator Monitor
e A
c l
Use a Web browser to navigate to the administrator Status Monitor, using a responsibility and
O ly
• Workflow Administrator Web Applications: Status Monitor
l & On
• Workflow Administrator Web (New): Status Monitor
• Workflow Administrator Event Manager: Status Monitor
n a e
You can navigate to the administrator Status Monitor from other Oracle Workflow
t e
link at the end of the page.
r U s
administrator Web pages by selecting the Status Monitor tab or clicking the Status Monitor
I n
Searching for Workflows
In the Search region of the Workflows page, enter search criteria to locate the workflows you
l e
want to display. The main search options are workflow item type display name, item type
c
internal name, owner, item key, user key, status, and start date.
r a
O
Copyright © Oracle, 2007. All rights reserved.
a
• For a parent workflow, click the icon in the Child Workflows column to view its children.
c
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Activity History in the Administrator Monitor
A
c l
A hierarchical grid displays the process hierarchy formed by the selected workflow and any
child workflows associated with it.
Searching for Activities r a
O ly
All activity types and statuses are selected by default. To search for specific activities, deselect
l & On
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
n a e
t e r U s
• To view details about the definition and current status of an activity, click the activity
name link in the Activity column.
I n
• To send e-mail to the performer of a notification, click the user link in the Performer
column.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing a Status Diagram in the Administrator Monitor
A
c l
Above the process diagram, the process title displays the workflow process name, type, and
r a
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 O ly
l & On
• An activity can be highlighted with a colored box to indicate a distinctive state:
- Red: The activity is in an error state.
n a e
- Green: The activity is active or in progress.
t e r U s
- Yellow: The activity is suspended.
• A transition arrow can have a thick green line to indicate that it has been traversed, or it
I n
can have a thin black line to indicate that it has not been traversed.
c l e
• 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
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing Responses in the Administrator Monitor
e A
c l
You can use the Monitor Responses page to drill down to responses to a particular notification.
r a
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. O ly
the Notification Subject column.
l & On
To view and respond to a notification in the Notification Details page, click the subject link in
a e
To send e-mail to the respondent for a notification, click the user link in the Respondent
n
column.
t e r
Notification Response Details
U s
I n
The Notification Response Details page displays the following:
• The subject line of the notification
l e
• The user who responded to the notification
c
r a
• The user to whom the notification was originally sent
• The date and time when the notification was sent
O • The date and time when the response was received
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Workflow Details in the Administrator Monitor
A
c l
A hierarchical grid displays the process hierarchy formed by the selected workflow and any
child workflows associated with it.
r a
The Workflow Definition region displays the workflow type internal name, workflow type
O ly
description, the persistence type, number of persistence days, and the selector/callback function
l & On
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
a e
workflow. For an attribute of type event, click the event message link to view the event
n
message details.
t e r
Updating Workflow Attribute Values
U s
I n
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.
l e
Note: You cannot update attributes of type event. However, you can click the event message
c
link to view the event message details.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Error Information in the Administrator Monitor
A
c l
The Workflow Errors page displays the name of the activity that encountered an error, the
r a
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.
O ly
Note: If you navigated to the Workflow Errors page from an error status link for a workflow,
l & On
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.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Child Workflows in the Administrator Monitor
A
c l
• To send e-mail to the owner of a workflow, click the user link in the Owned By column.
r a
• For an errored workflow, click the error icon or the error link in the Status column to view
error details.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Self-Service Monitor
e A
c l
The self-service version of the Status Monitor lets you view and administer workflows that you
own. You can:
r a
• Review the notifications sent by a workflow
O ly
• Check the status of the workflow by viewing the status diagram
& On
• Examine responses to notifications sent by the workflow
l
operations for a workflow
n a e
• If you have workflow administrator privileges, you can also perform certain control
t e r
Workflow Administrator Privileges
U s
Users have workflow administrator privileges if they belong to the Oracle Workflow
I n
administration role, which is defined in the Workflow Configuration Web page.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing Workflows in the Self-Service Monitor
e A
c l
Use a Web browser to navigate to the self-service Status Monitor, using a responsibility and
O ly
• Workflow User Web Applications: Status Monitor
l & On
• Workflow User Web (New): Status Monitor
You can navigate to the self-service Status Monitor from other Oracle Workflow self-service
a e
Web pages by selecting the Status Monitor tab or clicking the Status Monitor link at the end of
n
the page.
Searching for Workflows
t e r U s
I n
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
l e
workflow start date, workflow item type, and workflow identifier.
c
• All the start date ranges include the current date; for example, Last 2 Weeks includes
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Notification History in the Self-Service Monitor
A
c l
To send e-mail to the recipient of a notification, click the user link in the Notification Recipient
column.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing a Status Diagram in the Self-Service Monitor
A
c l
Above the process diagram, the process title displays the workflow process name, type, and
Process Diagram O ly
l & On
• An activity can be highlighted with a colored box to indicate a distinctive state:
- Red: The activity is in an error state.
n a e
- Green: The activity is active or in progress.
t e r U s
- Yellow: The activity is suspended.
• A transition arrow can have a thick green line to indicate that it has been traversed, or it
I n
can have a thin black line to indicate that it has not been traversed.
c l e
• 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
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing Responses in the Self-Service Monitor
e A
c l
You can use the Monitor Responses page to drill down to responses to a particular notification.
r a
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. O ly
Notification Response Details
l & On
The Notification Response Details page displays the following:
n a e
• The subject line of the notification
t e r U s
• The user who responded to the notification
• The user to whom the notification was originally sent
I n
• The date and time when the notification was sent
c l e
• The date and time when the response was received
• The response value that is the result of the notification
r a
• Whether the notification required an electronic signature
O • Any further response values requested in the notification in addition to the result response
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Viewing Error Information in the Self-Service Monitor
A
c l
The Workflow Errors page displays the name of the activity that encountered an error, the
r a
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
O ly
page shows details for each errored activity within the workflow. If you navigated to the page
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the username and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
Workflow Configuration page.
m y
• The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
d e
have this responsibility assigned to it.
ca
•
e A
The instructor will provide you with the names of users that you can assign as the
requestor and approver in the Vacation Proposal process. These user names should have
c l
Workflow administrator and user responsibilities assigned to them. Additionally, if you
r a
attached the Form Example attribute to the Vacation Proposal message, the user name
for the approver should have the System Administrator responsibility assigned to it to
O ly
be able to view the attached form.
Tasks
l & On
Running a Workflow Process
n a e
e r s
Run the workflow process using the Developer Studio.
t U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
1. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
2. Click the Developer Studio link. In the Search region of the Developer Studio page, select
the name of your XX Vacation Proposal item type and click Go. Then, in the Results region,
click the run icon for the XX Vacation Proposal item type.
3. In the Workflow Owner field, select the role that you want to use as the requestor for the
vacation proposal.
4. Enter a unique item key such as XX071 in the Item Key field.
5. Ensure that your XX Vacation Proposal Process is displayed in the Process field.
6. Next, enter starting values for the necessary item attributes. In the Requestor field, select the
role that you want to use as the requestor for the vacation proposal.
7. In the Approver field, select the role that you want to use as the approver for the vacation
proposal.
m y
8. In the From Date field, enter the vacation from date.
d e
9. In the To Date field, enter the vacation to date.
ca
10. Leave the Comments field blank.
e A
c l
11. Click the Submit button to run the workflow. Oracle Workflow launches the workflow
process with the values that you entered. A confirmation message appears. Click OK.
r a
O ly
12. To review the process status in the Status Monitor Web pages, select the Status Monitor tab.
•
chose, and click Go.
l & On
In the Search region, enter your XX Vacation Proposal item type and the item key you
n a e
•
t e r
In the Results region, select your process and click the Activity History button to review
the process activities.
U s
•
I n
Then click the Status Diagram button to review the graphical diagram of the status of the
process.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Worklist Pages
e A
c l
The Advanced Worklist is available by default from some of the seeded responsibilities in
O ly
The Personal Worklist is not available on a seeded responsibility. Before you can access the
l & On
Personal Worklist, a system administrator must add it to the menu for an Oracle E-Business
Suite responsibility that is assigned to you.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Advanced Worklist
e A
c l
Use a Web browser to navigate to the Advanced Worklist, using a responsibility and
O ly
• Workflow User Web Applications: Advanced Worklist
l & On
• Workflow User Web Applications: Notifications
• Workflow User Web (New): Notifications
n a e
• Workflow Administrator Web Applications: Notifications
t e r U s
• Workflow Administrator Event Manager: Notifications
• Workflow Administrator Web (New): Notifications
I n
You can also navigate to the Advanced Worklist from other Oracle Workflow Web pages by
l e
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.
c
r a
Accessing Notifications from the Advanced Worklist
• In the View pull-down menu, you can choose to view:
O - Open Notifications
m y
d e
ca
Notification Details
e A
c l
• You can access the Notification Details page from the Advanced Worklist, from the
r a
Personal Worklist, or from e-mail notifications.
• In Oracle E-Business Suite, nonstructured data such as images, spreadsheets, or video can
O ly
be linked to structured application data, including Oracle Workflow notifications seeded
l & On
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
a e
with links to the attachments. Click a link to view the attached data.
n
e r
• The message body may include embedded links to additional information sources
s
pertinent to the notification. A reference URL link connects to a specified URL, either in
t U
the same Web browser window or in a new window, depending on the notification.
I n
• The Related Applications section may include attachment icons. These icons link to
c l
links: e
additional information sources for the notification. There are three types of attachment
O
Copyright © Oracle, 2007. All rights reserved.
e
- If you want another user to respond to the notification instead of you, click the
A
c l
Reassign button. The Reassign button may be replaced by the Delegate button or the
r a
Transfer button, depending on the access you have been assigned in the WF:
Notification Reassign Mode profile option.
O ly
- To request more information about this notification from another user or role, click
l & On
the Request Information button.
- If another user sent you this notification with a request for more information, the
n a e
Response section displays the user who made the request and the request details.
Enter the information you want to provide and click Submit.
e r s
• If this notification requires a password-based electronic signature, a confirmation page
t U
appears after you submit your response. This page displays notification header
I n
information and the response values that you entered to let you review the response you
e
are signing. If the notification requires the signed response to include the message body,
l
then the confirmation page also displays the message body for you to review. To affix
c
your electronic signature to your response, enter your Oracle E-Business Suite user name
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Reassigning Notifications
e A
c l
Navigate to the Reassign Notifications page by one of the following methods:
r a
• In the Advanced Worklist or Personal Worklist, select one or more notifications and
choose the Reassign button.
O ly
• On the Notification Details page for a single notification, click the Reassign button.
& On
• Choose to reassign a notification from the Status Monitor.
l
n a e
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.
directory service.
t e r U s
The assignee types correspond to the originating system partitions in the Oracle Workflow
I n
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.
l e
• “Delegate your response”: Select this option if you want to give the new user authority to
c
r a 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
O approvals to an assistant.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Requesting More Information
e A
c l
You can choose to request information from another user or role previously involved in this
r a
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
O ly
within that type. The user types correspond to the originating system partitions in the Oracle
Workflow directory service.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Certificate-Based Digital Signatures
e A
c l
To set up for certificate–based digital signatures:
r a
• 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 .
O ly
• Obtain the certificate authority’s root certificate and any intermediate certificates required
l & On
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)
a e
can be downloaded. If your system administrator has already obtained and installed the
n
t e r
root certificate for your certificate authority and the intermediate certificates for your type
s
of certificate, you can skip this step.
U
I n
• 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
c l e
refer to the online Help for your browser.
• Use the certificate management functions in your browser or operating system to export
r a your personal certificate in the DER encoded binary X.509 format, as a file with an
extension of .cer.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Granting Worklist Access
e A
c l
The worklist access feature lets you allow another user to handle your notifications without
r a
giving that user access to any other privileges or responsibilities that you have in Oracle
Applications. However, note that a user who has access to your worklist can view all the
O ly
details of your notifications and take most actions that you can take on the notifications. Ensure
n a e
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.
e r s
• Your own assigned notification reassign mode still applies when you are viewing another
user’s worklist. t U
I n
• If the other user has a notification marked as being sent from you, you can only view that
c l e
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
r a 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
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Granting Worklist Access
e A
c l
Navigate to the Worklist Access page by navigating to the Advanced Worklist or Personal
r a
Worklist and clicking the Worklist Access link.
• If a user has an e-mail address defined in Oracle Applications, you can click the link in the
O ly
User Name column to send e-mail to that user.
l & On
• 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
a e
current date is within the access period. Leave the end date blank to grant access
n
indefinitely.
t e r U s
• If you are granting access only to selected item types, select the item types you want in the
I n
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
c l e
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
r a the future.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Administrator Search for Notifications
e A
c l
Navigate to the Notifications page by selecting the Administration tab on the Oracle Workflow
r a
administrator home page and selecting Notification Search in the horizontal navigation.
You must have workflow administrator privileges to access other users’ notifications on the
O ly
Notifications page. If you do not have administrator privileges, you can only search for and
r a
The following search criteria are always available:
O • From
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Reviewing Electronic Signature Details
e A
c l
Navigate to the Electronic Signature page by selecting the Administration tab on the Oracle
navigation. r a
Workflow administrator home page and selecting Signature Evidence Store in the horizontal
O ly
You can only review signatures for notifications that have not been purged.
Searching for Signatures
l & On
The following search criteria are available:
n a e
• Notification ID: If you specify a notification ID, all other search criteria are ignored.
by the notification.
t e r U s
• Signature Policy: The policy that identifies the type of signature and signed text required
• Requested Signer
I n
• Status
c l e
• Creation Date: The date when the request for a signature was created.
r a
• Signed Date: The date when the user submitted the signature.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Personal Worklist
e A
c l
The Personal Worklist is not available on a seeded responsibility. Before you can access the
r a
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
O ly
Personal Worklist in that responsibility.
l & On
• 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
a e
create your own personalized views to display notifications that match criteria that you
n
t e r
specify. The views that are available may depend on the responsibility through which you
access the Personal Worklist.
U s
I n
• 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
c l e
the Transfer button, depending on the access you have been assigned in the WF:
Notification Reassign Mode profile option.
r a
• To define vacation rules, click the Vacation Rules link.
• To grant access to your worklist to another user, click the Worklist Access link.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Simple Search for Notifications
e A
c l
You can search for notifications by subject, from role, and sent date. You can enter a partial
r a
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.
O ly
When you have displayed a set of notifications on the Simple Search page, you can reassign or
a e
To navigate back to the Personal Worklist, click the Worklist Views button.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Advanced Search for Notifications
e A
c l
The following search options are displayed by default: Subject, From, Message Attribute, and
r
Add Another pull-down menu and click Add.a
Sent. To display additional search options, select the notification property you want from the
O ly
For each search option, select a filter operator and then enter a filter value to specify the
notifications you want to display.
l & On
• For the is filter operator, you should enter a complete filter value that you want to match.
n a e
• For the other filter operators, you can enter a partial value, unless you are using the Sent,
t e r U s
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.
I n
• 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
l e
included in the search.
c
Note: The greater than, less than, after, and before filter operators are not
r a
inclusive. For example, a search on the Sent option with the after operator displays only
O notifications sent after the date you specify, not notifications sent on that date itself.
c l
To navigate back to the Personal Worklist, click the Worklist Views button.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Creating a Personal Worklist View
e A
c l
You can also navigate to the Create View page by clicking Save Search on the Simple Search
or Advanced Search pages.
r a
The Personalize Views page displays all existing views for the role you are logged in as,
O ly
including both preconfigured views provided by Oracle Workflow and your personalized
views.
l & On
• In the Display View column for a personalized view, select Yes to include the view in the
a e
View menu in the Personal Worklist, or select No to exclude the view from the View
n
menu. Then click Apply.
t e r s
Note: Preconfigured views always appear in the View menu. You cannot change this
U
I n
setting for those views.
• To update a view, click the icon in the Update column for that view.
l e
• To delete a view, click the icon in the Delete column for that view.
c
Note: You can update and delete only personalized views that you created. You cannot
O
Copyright © Oracle, 2007. All rights reserved.
r a
• The search criteria you can specify to locate notifications to display in the view are similar
O ly
to the search criteria in the Advanced Search page.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
Workflow Configuration page.
m y
• The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
d e
have this responsibility assigned to it.
ca
• The instructor will provide you with the names of users that you can use as the
e A
requestor and approver in the Vacation Proposal process. These user names should have
c l
Workflow administrator and user responsibilities assigned to them. Additionally, if you
r a
attached the Form Example attribute to the Vacation Proposal message, the user name
for the approver should have the System Administrator responsibility assigned to it to
O ly
be able to view the attached form.
Tasks
l & On
Responding to Notifications
n a e
e r s
Use the Worklist Web pages to view and respond to notifications.
t U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
1. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor.
2. Log in as the approver that you assigned for the vacation proposal in the previous practice.
You can use either a Workflow administrator or user responsibility.
4. In the Worklist, select the subject line for the Vacation Proposal notification sent by your
process to open and review the notification message.
• Because you defined the special #HIDE_REASSIGN attribute for the Vacation Proposal
message, the Reassign button should not appear in the Notification Details page.
• If you attached the URL Example attribute to the Vacation Proposal message, Oracle
Workflow displays the URL link at the end of the notification.
• If you attached the Form Example attribute to the Vacation Proposal message, and you
are logged in as a user who has a responsibility that has access to that form, Oracle
Workflow displays an attached form icon at the end of the notification. You can click the m y
d
form icon to drill down to the form. If you have multiple responsibilities with access toe
ca
the form, a list of your responsibilities appears to let you select the one with which you
want to navigate to the form. If you do not have responsibility access to the form, the
attached form icon is not displayed.
e A
5.
l
Navigate back to the Notification Details page.
c
6.
a
Enter comments if you want and select Approve or Reject to respond to the notification.
r
7.
O ly
Log off and log in as the requestor. You can use either a Workflow administrator or user
responsibility.
t e r s
Open the Vacation Approved or Vacation Rejected notification sent by your process and
review the notification message. Click OK to return to the Worklist.
U
I n
10. To review the updated status of the process in the Status Monitor Web pages, select the
l e
Status Monitor tab. Then search for the process with the XX Vacation Proposal item type
and your item key, and view the status diagram again by clicking the Status Diagram button.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing Notifications through E-mail
e A
c l
Set your notification preference in the Preferences page in Oracle E-Business Suite.
r a
• 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
O ly
notification message has “Content–Attached” URL or document message attributes
l & On
(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
n a e
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
e r s
display your notifications in the Notification Details page.
t U
• HTML mail: The notification message appears as HTML-formatted text, with no standard
I n
attachments. If the notification message has “Content–Attached” message attributes;
l e
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.
c
r a
• 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
O message, and the other is a link to the notification in the Notification Details page. If the
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
E-mail Response Methods
e A
c l
The Notification System interprets your response values in a case-sensitive manner.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
HTML-Formatted E-mail Notifications
e A
c l
The response template consists of the required notification ID and access key that identify the
r a
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
O ly
prompt you for other information in addition to your selected result response. Supply responses
l & On
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,
n a e
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.
t e r U s
• In addition to the response links, an HTML-formatted notification can also include a
I n
Request Information link to request more information about the notification from another
e
user before you respond to the notification. The Request Information link automatically
l
generates a plain text e-mail reply. The reply contains the correct Reply To: e-mail address
c
as well as a request template in the message body. The request template contains the
r a required notification ID and access key that identify the notification you are responding to.
O It also contains a prompt for you to enter the user from whom you want to request
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Plain Text E-mail Notifications Using Templated Response
A
c l
If your mail application includes an editable copy of the original message when it generates the
r a
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.
O ly
If this notification includes sensitive content that cannot be sent in e-mail for security reasons,
l & On
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.
n a e
e r
• If another user sent you this notification with a request for more information, include the
s
response template in your reply and insert your response values between the quotes
t U
following the response prompt.
I n
• If this notification requires a password-based signature or a certificate-based digital
c l e
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
r a access the online version of the notification instead. Navigate to the Notification Details
page to submit your response.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e
Plain Text E-mail Notifications Using Direct Response
A
c l
If a response value requires more than one line, enclose the entire response value in double
r a
quotes. If a response prompt provides a default value, then you can accept the default value by
leaving the appropriate response line blank.
O ly
If this notification includes sensitive content that cannot be sent in e-mail for security reasons,
l & On
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.
n a e
e r
If this notification requires a password-based signature or a certificate-based digital signature
s
in your response, you cannot respond to the notification through e-mail. In this case the
t U
notification informs you that an electronic signature is required and directs you to access the
I n
online version of the notification instead. Navigate to the Notification Details page to submit
c l e
your response.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Viewing an E-mail Summary of Notifications
e A
c l
Your workflow administrator determines how frequently summary notifications are sent when
setting up a notification mailer.
r a
In Oracle Applications, the plain text and HTML-formatted versions of the e-mail notification
O ly
summary are based on the Workflow Summary Mail (HTML) template defined in the System:
l & On
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
n a e
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
e r
access all your notifications.
t U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Automatic Notification Processing
e A
c l
Each time a notification is sent to you, Oracle Workflow tests the notification against your
vacation rules.
r a
• First Oracle Workflow checks whether you have any active rules for that specific message
type. O ly
l & On
• 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.
n a e
As soon as it finds a match, Oracle Workflow applies the rule and discontinues any further rule
matching.
t e r U s
If a rule reassigns a notification, Oracle Workflow performs rule matching again against the
I n
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
l e
forwarded more than ten times, Oracle Workflow assumes that a forwarding cycle has occurred
c
and ceases executing any further forwarding rules, marking the notification as being in error.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Maintaining Vacation Rules
e A
c l
The list of your vacation rules includes rules that you defined yourself as well as any rules
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Vacation Rules
e A
Vacation Rule: Item Type
c l
r a
• 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
O ly
also add item types to this list to let you create vacation rules to handle other notifications
you may receive in the future.
l & On
• If your workflow administrator has enabled creating generic vacation rules, you can select
a e
the All option in the Item Type field. In this case the rule to applies to notifications
n
t
Vacation Rule: Notification
e r
associated with any item type.
U s
I n
• Messages are listed by subject name.
• Select All if you want the rule to apply to all messages within the selected item type.
l e
• Skip this step if you selected All as the item type.
c
r a
Vacation Rule: Response
• The options in this page vary depending on the item types and messages to which each
O rule applies.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Vacation Rules
e A
c l
Navigate to the Vacation Rules page by selecting the Administration tab from the Oracle
r a
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
O ly
Vacation Rules page. Workflow administrator privileges are assigned in the Workflow
Configuration page.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the connect string for the class database and the
m y
user name and password of the Oracle Workflow database account.
d e
• The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
ca
Workflow Configuration page.
e A
•
c l
The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
r a
have this responsibility assigned to it.
• O ly
The instructor will provide you with the names of users that you can assign as the
l & On
requestor and approver in the Vacation Proposal process. These user names should have
Workflow administrator and user responsibilities assigned to them.
n a e
Tasks
t e r
Creating an HTML Body for a Message
U s
I n
Modify the Vacation Proposal workflow process that you created in the Creating a Workflow
l e
Process practice. First, create an HTML body for the Vacation Proposal message.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Next, modify the process to allow the approver to respond to the Vacation Proposal message
with alternate vacation dates.
Finally, modify the process to define a loop that enables the requester to resubmit another
proposal to the same approver if the first proposal is rejected.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
3. In the navigator tree, open your XX Vacation Proposal item type and select the Vacation
Proposal message.
4. Open the property pages for the Vacation Proposal message and select the Body tab. Within
the Body tab, select the HTML Body tab.
5. Enter an HTML-formatted version of your message. You can use the Import button to
import a sample HTML body from the wfvacxx.html sample solution file on your file
system. Click OK.
6. In the Navigator window, click the Verify button to verify your workflow.
U s
− Display Name: Alternate To Date
− Type: Date
I n
− Format: DD-MON-RRRR
•
c l e
Click OK.
r a
O
Copyright © Oracle, 2007. All rights reserved.
13. Open the property pages for the Vacation Rejected message. Select the Body tab:
• Add the following message attribute tokens for the alternate from and to dates into the
message body before the comments token:
14. Drag and drop the Alternate From Date and Alternate To Date item attributes onto the
Vacation Rejected message to create the corresponding message attributes. The Source field
for both alternate date attributes should be set to Send.
15. On the property pages for the Vacation Rejected message, select the Body tab and add the
text “Do you want to resubmit your proposal?” at the end of the message body. Then select
the Result tab. In the Display Name field for the result, enter "Resubmit Vacation
Proposal?". In the Lookup Type field, select Yes/No.
m y
16. Ensure that the Vacation Rejected message has From Date and To Date message attributes.
d e
Set the Source field to Respond for these attributes.
ca
17. Open the process diagram window.
e A
c l
18. Double-click the Vacation Rejected FYI notification activity node. Change the display name
for the activity to "Vacation Rejected - Resubmit?". Change the result type for the activity to
Yes/No to match the message result.
r a
O ly
19. Select the transition that connects the Vacation Proposal notification and the Vacation
l & On
Rejected - Resubmit? notification and drag the transition to create a vertex point. Select the
transition again and right-click it. Select the Locked option from the menu that appears. In
a e
this way, you can avoid drawing a new transition on top of this one.
n
e r s
20. Delete the existing transition between the Vacation Rejected - Resubmit? node and the End
t U
node. Draw a new transition from the Vacation Rejected - Resubmit? node to the End node
I n
and select No from the transition results menu.
l e
21. Draw a new transition from the Vacation Rejected - Resubmit? node to the Vacation
c
Proposal node and select Yes from the transition results menu.
r a
O
Copyright © Oracle, 2007. All rights reserved.
23. From the File menu, select Save to save your work to your workflow definition file.
m y
d e
ca
24. From the File menu, select Save As and save your item type to the class database, using the
database username, password, and connect string provided by the instructor.
e A
25. Close the data store.
c l
r a
26. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
O ly
l & On
27. Use the Developer Studio to launch your workflow process and test your work. You can use
the Worklist Web pages to view the notifications sent by the process and use the Status
a e
Monitor Web pages to review the status of the process.
n
•
t e r U s
As the approver, reject the initial vacation proposal.
•
I n
Then, as the requestor, respond to the Vacation Rejected – Resubmit? notification by
submitting new vacation dates.
•
c l e
As the approver, view and respond to the new proposal.
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 1
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 2
Worklist Flexfields
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 3
Objectives
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 4
Worklist Flexfields
m y
d e
ca
Worklist Flexfields
e A
c l
Note: Worklist flexfields are separate from the key flexfields and descriptive flexfields used in
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 5
Benefits of Worklist Flexfields
m y
d e
ca
Benefits of Worklist Flexfields
e A
c l
For example, if an expense notification includes message attributes for the expense total and
r a
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
O ly
purpose for each notification alongside the standard notification properties, such as the subject
line and sent date.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 6
Defining a Specialized Worklist View Using Worklist Flexfields
m y
d e
ca
e
Defining a Specialized Worklist View Using Worklist Flexfields
A
c l
Users must have access to the Personal Worklist to take advantage of a specialized worklist
r a
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.
O ly
Some Oracle Applications products also provide seeded worklist flexfields rules and Personal
& On
Worklist views. For more information, consult your product-specific documentation.
l
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 7
Message Attributes in Worklist Flexfields Rules
m y
d e
ca
Message Attributes in Worklist Flexfields Rules
e A
c l
• If a respond message attribute has a default value, the corresponding worklist flexfield
r a
displays that value while the notification is open.
• When displayed in a Personal Worklist view, a form attribute appears as a form icon that
O ly
drills down to the specified Oracle Applications form or Oracle Self-Service Web
l & On
Applications page. Users must use a responsibility with the appropriate security to open a
linked form or Oracle Application Framework page.
a e
• When displayed in a Personal Worklist view, a URL attribute appears as a URL icon that
n
t e r
links to the specified URL.
U s
• A message attribute of type date must have the following format to be used in a worklist
I n
flexfields rule: dd-mon-yyyy hh24:mi:ss
The Personal Worklist requires date attributes to be stored in this format to display them
l e
properly according to each user's preference.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 8
How Worklist Flexfields Rules Operate
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 9
Phase Numbers
m y
d e
ca
Phase Numbers
e A
c l
Do not assign the same phase number to more than one rule for the same item type. To ensure
type. r a
that the rules you want take effect, assign a different phase number to each rule for an item
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 10
Customization Levels
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 11
Core Rules
m y
d e
ca
Core Rules
e A
c l
Although core rules cannot override or be overridden by limit and user rules, it is possible for a
O ly
Core rules can map the following worklist flexfields columns.
• Data type: Text
- PROTECTED_TEXT_ATTRIBUTE1l & On
n a e
- PROTECTED_TEXT_ATTRIBUTE2
t e r
- PROTECTED_TEXT_ATTRIBUTE3
- PROTECTED_TEXT_ATTRIBUTE4
U s
I n
- PROTECTED_TEXT_ATTRIBUTE5
c l e
- PROTECTED_TEXT_ATTRIBUTE6
- PROTECTED_TEXT_ATTRIBUTE7
r a - PROTECTED_TEXT_ATTRIBUTE8
O - PROTECTED_TEXT_ATTRIBUTE9
Worklist Flexfields
Chapter 9 - Page 12
- PROTECTED_TEXT_ATTRIBUTE10
• Data type: Number
- PROTECTED_NUMBER_ATTRIBUTE1
- PROTECTED_NUMBER_ATTRIBUTE2
- PROTECTED_NUMBER_ATTRIBUTE3
- PROTECTED_NUMBER_ATTRIBUTE4
- PROTECTED_NUMBER_ATTRIBUTE5
• Data type: Form
- PROTECTED_FORM_ATTRIBUTE1
- PROTECTED_FORM_ATTRIBUTE2
- PROTECTED_FORM_ATTRIBUTE3
- PROTECTED_FORM_ATTRIBUTE4
- PROTECTED_FORM_ATTRIBUTE5
• Data type: URL
- PROTECTED_URL_ATTRIBUTE1
- PROTECTED_URL_ATTRIBUTE2
- PROTECTED_URL_ATTRIBUTE3
- PROTECTED_URL_ATTRIBUTE4
•
- PROTECTED_URL_ATTRIBUTE5
Data type: Date
m y
- PROTECTED_DATE_ATTRIBUTE1
d e
- PROTECTED_DATE_ATTRIBUTE2
- PROTECTED_DATE_ATTRIBUTE3
ca
- PROTECTED_DATE_ATTRIBUTE4
e A
- PROTECTED_DATE_ATTRIBUTE5
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 13
Limit and User Rules
m y
d e
ca
Limit and User Rules
e A
c l
Limit rules and user rules can map the following worklist flexfields columns.
• Data type: Text
r a
- TEXT_ATTRIBUTE1
- TEXT_ATTRIBUTE2 O ly
- TEXT_ATTRIBUTE3
l & On
- TEXT_ATTRIBUTE4
n a e
- TEXT_ATTRIBUTE5
- TEXT_ATTRIBUTE6
t e r U s
I n
- TEXT_ATTRIBUTE7
- TEXT_ATTRIBUTE8
l e
- TEXT_ATTRIBUTE9
c
- TEXT_ATTRIBUTE10
r a
• Data type: Number
O - 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
- URL_ATTRIBUTE2
- URL_ATTRIBUTE3
- URL_ATTRIBUTE4
- URL_ATTRIBUTE5
• Data type: Date
- DATE_ATTRIBUTE1
- DATE_ATTRIBUTE2
- DATE_ATTRIBUTE3
m y
- DATE_ATTRIBUTE4
d e
- DATE_ATTRIBUTE5
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 15
Limit and User Rules
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 16
Combining Core, Limit, and User Rules
m y
d e
ca
Combining Core, Limit, and User Rules
e A
c l
• If a core rule does not meet your requirements, you can choose not to include its message
O ly
• If a limit rule does not meet your requirements and you want to override some of its
l & On
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
a e
longer want any mappings from a limit rule to take effect, disable that rule.
n
e r
• While defining a user rule, you can check whether its column mappings conflict with any
s
existing rules for the same item type, and whether the new rule will override or be
t U
overridden by the conflicting rules. Review each conflict to decide whether to accept the
I n
current overrides or update the rule definitions to make a different rule take effect.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 17
Worklist Flexfields Rules Example
m y
d e
ca
Worklist Flexfields Rules Example
e A
c l
This example uses the sample Requisition item type. For more details about this sample item
r a
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: O ly
l & On
• PROTECTED_TEXT_ATTRIBUTE1 column : Requisition Number attribute
Also, suppose a limit rule named EXL02 is seeded for the Requisition item type with a phase
a e
of 60 and the following column mappings:
n
t e r U s
• TEXT_ATTRIBUTE1 column : Requisition Description attribute
• NUMBER_ATTRIBUTE1 column : Requisition Amount attribute
I n
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
l e
EXU03 for the Requisition item type with a phase of 110 and the following column mappings:
c
r a
• TEXT_ATTRIBUTE1 column : Note attribute
• URL_ATTRIBUTE1 column : Monitor URL attribute
O
Copyright © Oracle, 2007. All rights reserved.
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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 19
Defining a Worklist Flexfields Rule: Entering General Properties
m y
d e
ca
Defining a Worklist Flexfields Rule
e A
c l
Use a Web browser to navigate to the Worklist Flexfields Rules page, using a responsibility
r
the seeded Workflow responsibilities are:a
and navigation path specified by your system administrator. Some possible navigation paths in
O ly
• Workflow Administrator Web Applications: Worklist Flexfields Rules
n a e
Review the customization level for the rule.
t e r U
seeded by Oracle Applications. s
• Core: You cannot make any changes to the rule definition. This level is used only for rules
I n
• 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
l e
Applications.
c
r a
• User: You can update any property in the rule definition. This level is automatically set for
rules that you define.
O
Copyright © Oracle, 2007. All rights reserved.
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 Applications 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 21
Defining a Worklist Flexfields Rule: Selecting Filter Criteria
m y
d e
ca
e
Defining a Worklist Flexfields Rule: Selecting Filter Criteria
A
c l
• You can enter a partial value in the Workflow Type field to search for item types whose
r a
display names begin with that value. This field is case-sensitive.
• Select an item type in either list to view its description.
O ly
• If you perform a new search to show different item types in the Available Filter Criteria
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 22
Defining a Worklist Flexfields Rule: Selecting Message Attributes
m y
d e
ca
e
Defining a Worklist Flexfields Rule: Selecting Message Attributes
A
c l
• If you no longer want a previously selected workflow item type in the filter criteria for the
r a
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
O ly
item type from the Available list and the Selected list.
l & On
• 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.
a e
• The Available and Selected lists show the display name and data type for each message
n
t e r
attribute. Select a message attribute in either list to view in the Description field the
s
display name and internal name of the message to which the attribute belongs.
U
I n
- 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
c l e
appears only once in the lists. In this case the Description field indicates that the
message attribute occurs in multiple messages
r a - 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.
O 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 24
Defining a Worklist Flexfields Rule: Mapping Attributes to
Columns
m y
d e
ca
e A
c l
Defining a Worklist Flexfields Rule: Selecting Message Attributes
r a
• The Mapped Column field for each attribute displays only columns that match the
attribute data type.
O ly
• You can use each column only once in a rule.
& On
• If multiple messages in the selected workflow item types have a message attribute with the
l
n a e
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.
t e r U s
• To remove a message attribute from the column mappings for the rule, click the remove
I n
icon for that attribute.
• On the Find Worklist Flexfields Rule Map Conflicts page, review the columns that other
l e
rules map to different attributes for the same workflow item types. The Conflict field
c
indicates whether the current rule overrides or is overridden by the other rule, based on the
O - 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 26
Resolving Conflicts Between Worklist Flexfields Rules
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 27
Maintaining Worklist Flexfields Rules
m y
d e
ca
Maintaining Worklist Flexfields Rules
e A
Searching for Rules
c l
r a
You can search by the internal rule name, display name, phase, status, level, workflow item
type, message attribute, or worklist flexfields column name.
O ly
• You can enter partial values in the Rule Name and Display Name fields. These fields are
case-sensitive.
l & On
• If you specify a workflow type to search by, you can only select a message attribute
a e
belonging to that workflow type. Otherwise, you can select a message attribute belonging
n
to any workflow type
t e r U s
You must enter at least one of the following criteria when you search to limit the size of the
results list.
• Rule Name I n
l e
• Display Name
c
r a
• Level
• Workflow Type
O
Copyright © Oracle, 2007. All rights reserved.
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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 29
Storing Message Attribute Values in Worklist Flexfields Columns
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 30
Performing a Worklist Flexfields Rule Simulation
m y
d e
ca
Performing a Worklist Flexfields Rule Simulation
e A
c l
• Perform a Core Rules simulation to learn which message attributes are already available in
r a
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.
O ly
• Perform a Limit and User Rules simulation to verify that any other message attributes you
l & On
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.
n a e
e r
• After performing a simulation, update your rules with any changes you want to make and
s
then repeat the simulation, until you are satisfied with the net set of message attributes
t
available for the item type. U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 31
Performing a Worklist Flexfields Rule Simulation
m y
d e
ca
Performing a Worklist Flexfields Rule Simulation
e A
c l
Use a Web browser to navigate to the Worklist Flexfields Rules Simulation page, using a
r a
responsibility and navigation path specified by your system administrator. Some possible
navigation paths in the seeded Workflow responsibilities are:
O ly
• Workflow Administrator Web Applications: Worklist Flexfields Rules Simulation
n a e
The list of mapped attributes and columns shows the net effect of the enabled rules for the
t e r U s
selected item type and customization level. If you specified a message, the list shows only
mapped attributes belonging to that message.
I n
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.
l e
• On the Find Worklist Flexfields Rule Conflicts page, review the columns that overridden
c
rules map to different attributes than the effective rule. The Conflict field indicates that the
r a effective rule overrides the other rules, based on the rule phase numbers.
O
Copyright © Oracle, 2007. All rights reserved.
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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 33
Defining a Securing Function
m y
d e
ca
Defining a Securing Function
e A
c l
The navigation path to the Form Functions window in the seeded System Administrator
responsibility is:
r a
• System Administrator: Application > Function
O ly
If you follow these steps to secure your specialized worklist view, then it will appear in the list
a e
If you do not secure your specialized worklist view, it will appear in the list of views whenever
n
t e r U s
any user accesses the Personal Worklist from any responsibility.
For more information about defining functions, menus, and responsibilities, see the Oracle
n
Applications System Administrator's Guide and Oracle Applications Developer's Guide.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 34
Creating a Personalized View for the Personal Worklist
m y
d e
ca
e
Creating a Personalized View for the Personal Worklist
A
c l
You do not need to associate worklist flexfields rules directly with a Personal Worklist view.
r a
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.
O ly
l & On
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.
n a e
Personalization Guide.
t e r
For more information about creating personalizations, see the Oracle Application Framework
U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 35
Creating a Personalized View for the Personal Worklist
m y
d e
ca
e
Creating a Personalized View for the Personal Worklist
A
Defining View Properties
c l
r a
• If you defined a securing function for the view, specify the function in the view's general
properties.
O ly
• Select the columns to display in the view, including the worklist flexfields columns that
a e
• Specify the columns by which to sort the view, including worklist flexfields columns if
n
appropriate.
t e r U s
• To display only notifications from the relevant item types, add the Type parameter or the
I n
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
l e
parameters to include multiple item types in the view. In this case, select the “Search
c
results where each may contain any value entered” option.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 36
Restarting Oracle HTTP Server
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 37
Practice - Defining a Specialized Worklist View Using Worklist
Flexfields
Overview
In this practice, you will define a worklist flexfields rule based on the vacation item type that you
created in the Creating a Workflow Process practice. Then you will create a specialized worklist
view that includes the columns mapped by the worklist flexfields rule.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
Workflow Configuration page. m y
• d
The instructor will provide you with the URL for the login page and the name of a
e
ca
Workflow administrator responsibility and a Workflow user responsibility. The user
A
name that you use to log in should have these responsibilities assigned to it.
e
•
c l
The instructor will perform the necessary setup steps to provide the Personal Worklist
as a menu option on a Workflow user responsibility and to enable you to define
r a
personalized worklist views. These setup steps include adding the Personal Worklist
function to the application menu for the responsibility, assigning the responsibility to a
O ly
user, and setting the Personalize Self-Service Defn profile option to Yes for that user.
•
l & On
Adding the Personal Worklist Function to a Menu
•
n a e
Assigning a Responsibility to a User
•
t e r U s
Setting the Personalize Self-Service Defn Profile Option
I n
Adding the Personal Worklist Function to a Menu
1. l e
Use a Web browser to connect to a System Administrator responsibility.
c
r
2. a Select Application > Menu to open the Menus window.
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 38
3. Query the menu for the Workflow User Web Applications responsibility by selecting View
> Query by Example > Enter. Enter FND_WFUSER as the menu name and then execute the
query by selecting View > Query by Example > Run to display the menu details.
4. Scroll down to the last record and click the New record icon from the application toolbar. In
the new record, add the Personal Worklist function to the menu:
− Seq: <Enter an appropriate sequence number>
− Prompt: Personal Worklist
− Submenu: <Leave this field blank>
− Function: Personal Worklist (WF_WORKLIST_CUSTOM)
− Grant: Checked
Note: There are two spaces between “Personal” and “Worklist” in the function name. If you
search by the function display name, ensure that you enter both spaces.
6. In the navigator, select Security: User > Define to open the Users window.
7. Query a user name by selecting View > Query by Example > Enter. Enter the user name and
then execute the query by selecting View > Query by Example > Run to display the user
details.
m y
8. e
Click the New record icon from the application toolbar and select the Workflow User Web
d
9.
Applications responsibility.
c
a
10. In the navigator, select Profile > System to open the Find System Profile Values window.
r
O ly
11. Select the User check box and enter the user name to which you assigned the Workflow
User Web Applications responsibility.
l & On
12. Enter Personalize Self-Service Defn as the Profile and click Find.
n a e
t e r
13. Select Yes as the Personalize Self-Service Defn profile value in the User field.
U s
14. Save your work and close the window.
Tasks I n
c l e
Defining a Worklist Flexfields Rule
r a
Define a worklist flexfields rule based on the vacation item type that you created in the Creating
Oa Workflow Process practice.
Worklist Flexfields
Chapter 9 - Page 39
Simulating the Effects of a Worklist Flexfields Rule
Perform a worklist flexfields rule simulation to review and verify which attributes are available
in which worklist flexfields columns for your item type.
Create a personalized worklist view that includes the columns mapped by your worklist
flexfields rule and displays notifications from your vacation item. You can also specify your
desired column settings and sort order for the personalized view.
Use the personalized view that you created to view the vacation message attributes mapped by
your rule in the Personal Worklist with your desired settings and sort order.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 40
Solution – Defining a Specialized Worklist View Using Worklist
Flexfields
Defining a Worklist Flexfields Rule
1. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
3. On the Worklist Flexfields Rules page, click the Create Rule button.
4. Enter the following values in the Create Worklist Flexfields Rule: Enter General Properties
page:
− Rule Name: XXWFVACRULE
− Display Name: XX Vacation Worklist Flexfields Rule
− Status: Enabled
− Phase: 110
− Owner Name: XX Practices
− Owner Tag: FND
• Click Next.
m y
5.
Proposal item type that you created in the Creating a Workflow Process practice. d e
In the Create Worklist Flexfields Rule: Set Filter Criteria page, search for the XX Vacation
6. ca
Select the XX Vacation Proposal item type from the Available Filter Criteria list and move it
to the Selected Filter Criteria list. Click Next.
e A
7.
c l
In the Create Worklist Flexfields Rule: Select Message Attributes page, select the following
− Alternate To Date
− From_Date O ly
− To_Date
l & On
− Comments
n a e
• Click Next.
t e r U s
8.
n
In the Create Worklist Flexfields Rule: Map Attributes to Columns page, ensure the message
I
attributes are mapped to the following columns:
l e
− Alternate From Date: DATE_ATTRIBUTE1
c
− Alternate To Date: DATE_ATTRIBUTE2
r a − From_Date: DATE_ATTRIBUTE3
− To_Date: DATE_ATTRIBUTE4
O − Comments: TEXT_ATTRIBUTE1
Worklist Flexfields
Chapter 9 - Page 41
• Click Finish.
9. Click the Home global link to return to the Oracle E-Business Suite home page.
10. Click the Worklist Flexfields Rules Simulation link in a Workflow administrator
responsibility.
11. Enter the following values in the Criteria region of the Worklist Flexfields Rules Simulation
page:
− Workflow Type: XX Vacation Proposal
− Customization Level: Limit and User Rules checked
• Click Go.
12. Review and verify which attributes are available in which worklist flexfields columns for
your item type based on your worklist flexfields rule.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
l e
Creating a Personalized View
c
r a
13. Return to the Oracle E-Business Suite home page and select the Workflow user
responsibility provided by the instructor.
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 42
14. Click the Personal Worklist link.
16. In the Personalization Structure region, click the Seeded User Views icon for the “Table:
Customizable and …” item.
17. On the Personalize Views page, click the Create View button.
18. On the Create View page, enter the following values to define your view:
− View Name: XXWFVACVIEW
− Number of Rows Displayed: 25 Rows
− Securing Function: (Leave this field blank)
− Description: XX Worklist Personal View
19. Click the Rename Columns/Totaling button and enter the following column names:
− DATE_ATTRIBUTE1: Alternate From Date
− DATE_ATTRIBUTE2: Alternate To Date
− DATE_ATTRIBUTE3: From_Date
− DATE_ATTRIBUTE4: To_Date
− TEXT_ATTRIBUTE1: Comments
• Click Apply.
m y
20. Define the following properties in the Column Properties region for your view:
d e
•
list:
ca
Move the following columns from the Available Columns list to the Columns Displayed
I n
− First Sort: Sent (descending order)
− Second Sort: From Date (ascending order)
l e
− Third Sort: Subject (ascending order)
c
a
21. Define the following values in the Search Query to Filter Data in your Table region:
r
O • Select the “Show table data when any condition is met” option.
Worklist Flexfields
Chapter 9 - Page 43
• Select Type in the Add Another pull-down menu and click the Add button. For the Type
filter, select the “contains” filter operator and then enter “XX Vacation Proposal” as the
workflow type filter value.
23. Return to the Oracle E-Business Suite home page, and click the Personal Worklist link.
24. In the Personal Worklist, select the XXWFVACVIEW view from the View pull-down menu
and click Go. Verify that the notifications sent from your XX Vacation Proposal item type
are displayed in the worklist with the attribute columns that you specified and your desired
settings and sort order.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 44
Summary
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 45
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Worklist Flexfields
Chapter 9 - Page 46
Oracle Workflow Directory
Service
Chapter 10
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Oracle Workflow Directory Service
e A
c l
A role can contain only individual users as its members. It cannot contain another role.
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Predefined Directory Service
e A
c l
If the predefined directory service provided by Oracle Workflow does not meet your needs,
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
WF_ROLES View
e A
c l
If the e-mail address is null for a given role, notification mailers send an individual e-mail to
each user within the role.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
WF_USER_ROLES View
e A
c l
The Assignment_Type column indicates how a user was assigned to membership in a role:
r a
• D: The user was directly assigned to this role.
O ly
• I: The user inherited this role through membership in another role.
• B: The user has both direct and inherited assignments to this role.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Local Directory Service Tables
e A
c l
Oracle Workflow also includes the following directory service tables:
r a
• WF_LOCAL_ROLES_TL stores translated data for MLS support in the WF_USERS and
WF_ROLES views.
O ly
• WF_ROLE_HIERARCHIES stores information about hierarchical relationships between
roles.
l & On
• WF_USER_ROLE_ASSIGNMENTS stores information about how assignments of users
a e
to roles are inherited through role hierarchy relationships.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Local Directory Service Tables
e A
In the Workflow local tables:
c l
r a
• 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;
O ly
Trading Community Architecture (TCA) person parties; and TCA contacts (relationship
parties).
l & On
• Several types of Oracle E-Business Suite entities are stored as roles, including: Oracle E-
a e
Business Suite responsibilities, Oracle Human Resources positions, MarketView
n
t e r
approvals and channels, Engineering approval lists, TCA groups, Federal HR group boxes,
s
Position Control roles, and User Management roles.
U
I n
For more information about entities owned by various Oracle E-Business Suite products, refer
to the documentation for those products.
l e
You should periodically purge ad hoc users and roles from the Workflow local tables after they
c
have expired in order to improve performance. Run the Purge Obsolete Workflow Runtime
r a
Data concurrent program through the Oracle Workflow Manager component of Oracle
Applications Manager to perform this purging.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Ad Hoc Users/Roles
e A
c l
The WF_DIRECTORY package contains the APIs supporting ad hoc users and roles,
including:
• CreateAdHocUser() r a
• CreateAdHocRole() O ly
• CreateAdHocRole2()
l & On
• AddUsersToAddHocRole()
• AddUsersToAddHocRole2()
n a e
e r
• RemoveUsersFromAdHocRole()
• SetAdHocUserStatus()t U s
I n
• SetAdHocRoleStatus()
l e
• SetAdHocUserExpiration()
c
• SetAdHocRoleExpiration()
r a
• SetAdHocUserAttr()
O • SetAdHocRoleAttr()
m y
d e
ca
Validating a Directory Service Data Model
e A
c l
Customizations to the predefined directory service provided by Oracle Workflow are not
r a
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.
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Setting Workflow Preferences
e A
c l
Set the global default notification preferences in the Workflow Configuration page and
r a
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.
O ly
l & On
Note: The language, territory, and notification preference settings in the Workflow
Configuration and General Preferences pages are effective for Oracle Workflow only if your
a e
directory service views map these columns to the Oracle Workflow preferences table.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Loading Roles
e A
To load roles:
c l
r a
1. In Oracle Workflow Builder, select Open from the File menu to connect to your database
and open the item type you want.
O ly
2. From the File menu, select Load Roles from Database.
Find. l & On
3. Specify search criteria in the Find Roles field of the Role selection window and then click
n a e
4. Select the roles you want to load in the Query Results list, and click Add to add them to
the Loaded Roles list.
t e r U s
5. Click OK to load the roles and make them available to the objects in your open item type.
I n
After you load roles from the database, you can expand the Directory Service branch in the
navigator tree to view information about the roles.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining a Function Activity
e A
To define a function activity:
c l
r a
1. In Oracle Workflow Builder, select the item type that you want in the navigator tree.
Then select New Function from the Edit menu.
O ly
2. On the Activity property page, enter an internal name for the activity. The internal name
l & On
must be all uppercase without any colons or leading or trailing spaces.
3. Enter a display name for the activity.
n a e
4. Enter a description of the activity.
t e r U s
5. Choose an icon that identifies the activity.
6. Enter a function name and function type for the activity.
I n
- PL/SQL: Enter the name of the PL/SQL stored procedure that you want the
c l e
Workflow Engine to execute for this function activity. Use the following format:
<package_name>.<procedure_name>
r a - 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
O and consume the entry on the Outbound queue. The external agent can similarly
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
•
m y
The instructor will provide you with the connect string for the class database and the
user name and password of the Oracle Workflow database account.
d e
•
ca
The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
Workflow Configuration page.
e A
•
c l
The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
r a
have this responsibility assigned to it.
• O ly
The instructor will provide you with the names of users that you can assign as the
l & On
requestor and approver in the Vacation Proposal process. These user names should have
Workflow administrator and user responsibilities assigned to them.
n a e
Tasks
t
Defining a Function Activity e r U s
I n
In the Vacation Proposal item type that you created in the Creating a Workflow Process practice,
l e
add a function activity that updates a schedule of planned vacations.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Load the PL/SQL package containing the predefined PL/SQL procedure that the function activity
calls.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
3. In the navigator tree, open your XX Vacation Proposal item type and open the process
diagram window for the Vacation Proposal process.
4. Delete the transition between the Vacation Approved FYI node and the End (Approve)
node.
5. Click the New Function button, position the cross-hair cursor between the Vacation
Approved FYI node and the End node, and click again to create a new function activity node
there and open the property pages for the node.
Note: As a workflow development standard, where possible, you should use the procedure m y
d e
name of the function called by the activity as the internal name of the activity. For example,
the activity that calls the function WFVACXX.SCHEDULE_UPDATE should have the
internal name SCHEDULE_UPDATE.
ca
7. Select the icon DB_UPD.ICO for the activity.
e A
8.
c l
Enter the package and procedure name WFVACXX.SCHEDULE_UPDATE in the Function
a
Name field for the activity. This function will have no result. Click OK.
r
O ly
Note: If you are defining a function activity during the process design phase and you do not
yet know the package and procedure name for the PL/SQL procedure you want the activity
l & On
to call, you can enter WF_STANDARD.NOOP as a placeholder in the Function Name field.
n a e
WF_STANDARD.NOOP is a standard Workflow PL/SQL procedure that sets the resultout
parameter to wf_engine.eng_completed and returns.
9.
t e r U s
Draw transitions from the Vacation Approved FYI node to the Update Vacation Schedule
n
node, and from the Update Vacation Schedule node to the End (Approve) node.
I
c l e
10. To verify error handling information for the Vacation Proposal process, open the property
pages for the Vacation Proposal process and select the Details tab. Ensure that the error item
O11. In the Navigator window, click the Verify button to verify your workflow.
13. From the File menu, select Save As and save your item type to the class database, using the
database user name, password, and connect string provided by the instructor.
c l
This script creates a vacation schedule table named
− REQUESTOR - varchar2(30) r a
WFVACXX_VACATION_SCHEDULE. The table includes the following columns:
− APPROVER - varchar2(30) O ly
− FROM_DATE - date
− TO_DATE - date
l & On
n a e
16. Copy and edit the sample package specification and body scripts. The sample scripts are
e r s
named wfvacxxs.sql and wfvacxxb.sql, respectively. They create a package named
t U
WFVACXX that contains all the sample PL/SQL procedures for all practices in this course.
I n
The procedure specific to this practice is WFVACXX.SCHEDULE_UPDATE. Open a copy
of each sample file and replace all instances of XX with your own terminal number. Save
l e
the files and rename them by replacing xx with your terminal number.
c
r a The WFVACXX.SCHEDULE_UPDATE procedure records an approved vacation proposal
in the WFVACXX_VACATION_SCHEDULE table.
O
Copyright © Oracle, 2007. All rights reserved.
@wfvacxxc
@wfvacxxs
@wfvacxxb
Alternatively, you can run the scripts from the default prompt if you include the directory
path for the scripts in the commands. For example, if your scripts are located in the E:\Labs
folder, then enter the following commands:
@E:\Labs\wfvacxxc
@E:\Labs\wfvacxxs
@E:\Labs\wfvacxxb
Note: You can ignore the “table or view does not exist” error in the output from the first
script, wfvacxxc. The script follows programming standards that require attempting to
drop the table before attempting to create it, to remove any preexisting table of that name.
After this error message, you should see messages indicating that the table and index have
been successfully created.
m y
18. Use a Web browser to connect to a Workflow administrator responsibility with the URL
d e
a
provided by the instructor. Log in as a user with workflow administrator privileges.
c
e A
19. Use the Developer Studio to launch your workflow process and test your work. You can use
the Worklist Web pages to view the notifications sent by the process and approve the
l
vacation proposal, and use the Status Monitor Web pages to review the status of the process.
c
•
r a
Run the process and approve the vacation proposal.
• O ly
Use SQL*Plus to verify that the appropriate row was inserted into your
& On
WFVACXX_VACATION_SCHEDULE table. Enter the following command:
l
a e
select * from WFVACXX_VACATION_SCHEDULE;
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
External Function Activities
e A
c l
The most flexible and powerful way to integrate external processing into a workflow process is
r a
by using business events and subscriptions. However, Oracle Workflow also supports
processing external to the database through external function activities. This capability
O ly
facilitates integration with external products and legacy systems.
a e
• An ‘Outbound’ queue and an ‘Inbound’ queue are established in Oracle Workflow. When
n
e r
the Workflow Engine encounters an external function activity, a message is written to the
s
Outbound queue. The payload of the message includes any activity attribute name and
value pairs. t U
I n
• A message on the workflow outbound queue is read by an external agent. An external
c l e
execution agent can be any application that is external to the database. The external
system consumes and processes the message.
r a
• 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
O considered as the “reply” to the original workflow outbound queue message. The inbound
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Assigning a Cost to a Function Activity
e A
c l
Activity costs are entered in the Workflow Builder in seconds and stored in the database in
r a
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.
O ly
l & On
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
a e
Builder and 50 when compared to function activity costs stored in the database.
n
e r
The Workflow Engine executes one activity at a time. If possible, you should avoid placing
s
costly activities along the critical path of a process. Instead, place costly activities on parallel
t U
branches in a process, where they can be deferred for a background engine to process later.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
m y
•
user name and password of the Oracle Workflow database account.
d e
The instructor will provide you with the connect string for the class database and the
•
ca
The instructor will provide you with the user name and password of a user with
c l
The instructor will provide you with the URL for the login page and the name of a
•
r a
Workflow administrator responsibility. The user name that you use to log in should
O ly
have this responsibility assigned to it.
•
l & On
The instructor will provide you with the names of users that you can assign as the
requestor and approver in the Vacation Proposal process. These user names should have
a e
Workflow administrator and user responsibilities assigned to them.
n
Tasks
t e r U s
I
Loading a PL/SQL Package n
l e
Load the PL/SQL package containing the predefined PL/SQL procedure for the function activity
to call.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Add a function activity to check whether the approver is the same as the requestor in the
Vacation Proposal item type that you created in the Creating a Workflow Process practice. The
function activity should have a result type of Yes/No.
Model different branches in the process based on the function activity result.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
1. If you have not already done so, copy and edit the sample package specification and body
scripts. The sample scripts are named wfvacxxs.sql and wfvacxxb.sql, respectively. They
create a package named WFVACXX that contains all the sample PL/SQL procedures for all
practices in this course. The procedure specific to this practice is
WFVACXX.CHECK_APPROVER. Open a copy of each sample file and replace all
instances of XX with your own terminal number. Save the files and rename them by
replacing xx with your terminal number.
Note: If you have already copied, edited, and run the complete sample package specification
and body scripts containing all the sample procedures for all practices, you do not need to
repeat these steps.
2. If you have not already done so, log in to SQL*Plus using the database user name,
password, and connect string provided by the instructor. Run the package specification and
package body scripts in that order by entering the following commands from the directory
where the scripts are located:
m y
@wfvacxxs
d e
@wfvacxxb
ca
A
Alternatively, you can run the scripts from the default prompt if you include the directory
e
c
folder, then enter the following commands:l
path for the scripts in the commands. For example, if your scripts are located in the E:\Labs
@E:\Labs\wfvacxxs
r a
O ly
& On
@E:\Labs\wfvacxxb
l
Defining a Function Activity with a Result Type
a e
3.
r n s
Start the Oracle Workflow Builder.
4.
t e U
From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
n
I
Creating a Workflow Process practice.
e
5.
l
Open the process diagram window for the Vacation Proposal process.
c
r
6.
a Delete the transition between the Start node and the Vacation Proposal node.
O
Copyright © Oracle, 2007. All rights reserved.
Note: As a workflow development standard, where possible, you should use the procedure
name of the function called by the activity as the internal name of the activity. For example,
the activity that calls the function WFVACXX.CHECK_APPROVER should have the
internal name CHECK_APPROVER.
10. Enter the package and procedure name WFVACXX.CHECK_APPROVER as the function
name for the activity.
13. Draw a transition from the Start node to the Approver Same as Requestor? node.
m y
14. Draw a transition from the Approver Same as Requestor? node to the Vacation Proposal
d e
node and select No from the transition results menu.
ca
e A
15. Create a new End node by dragging the End function from the Standard item type in the
navigator tree into the process diagram. Open the property pages for the node, and select the
l
Node tab. In the Start/End field, select End. In the Result field, select Reject.
c
r a
Using multiple End nodes can help simplify your diagram and uniquely identify which End
O ly
activity is executed when different paths through a process can terminate with the same
result. For example, the Vacation Proposal can now end with a result of Reject for two
unique reasons:
l & On
− A vacation proposal is submitted with the approval equal to the requestor.
a e
− A vacation proposal is rejected by the approver.
n
e r s
16. Draw a transition from the Approver Same as Requestor? node to the new End node and
t U
select either Yes or <Default> from the transition results menu.
I n
17. In the Navigator window, click the Verify button to verify your workflow.
c l e
18. From the File menu, select Save to save your work to your workflow definition file.
r a
O
Copyright © Oracle, 2007. All rights reserved.
21. Use a Web browser to connect to a Workflow administrator responsibility with the URL
m y
provided by the instructor. Log in as a user with workflow administrator privileges.
d e
ca
22. Use the Developer Studio to launch your workflow process and test your work. You can use
the Worklist Web pages to view the notifications sent by the process, and use the Status
Monitor Web pages to review the status of the process.
e A
•
c l
First, run the process and enter the same role for the requestor and the approver. The
process should end with a result of Reject, and no notification should be sent.
r a
Then, run the process again and enter different roles for the requestor and the approver.
•
O ly
The process should proceed to send the Vacation Proposal notification to the approver.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
Standard API for PL/SQL Procedures Called by Function Activities
procedure <procedure name> (
r a
itemtype in varchar2,
O ly
& On
itemkey in varchar2,
actid in number,
funcmode in varchar2, l
a e
r
resultout out varchar2) is
n s
<local declarations>
n t e U
begin
e I
c l
if (funcmode=‘RUN’) then
<your RUN executable statements>
r a resultout:=‘COMPLETE:<result>‘;
return;
O endif;
raise;
to_char(<actid>), <funcmode>);
m y
end <procedure name>;
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Function Activity Execution Modes
e A
c l
Looping occurs when the completion of an activity causes a transition to another activity that
r a
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.
O ly
• Ignore: Ignores the activity after the activity has been executed once.
l & On
• Reset: Resets completed activities in a loop by executing activities in CANCEL mode
before re-executing them in RUN mode.
a e
• Loop: Re-executes activities in the loop without resetting them; in this case no CANCEL
n
logic is executed.
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Function Activity Execution Modes
e A
c l
Oracle Workflow records audit trail data for skip operations.
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Standard API Resultout Parameter
e A
c l
• COMPLETE:<result_code> The activity completes with the specified result code. The
r a
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
O ly
completes. An example is the Standard 'AND' activity.
l & On
• DEFERRED:<date> The activity is deferred to a background engine for execution until
a given date. <date> must be of the format:
n a e
to_char(<date_string>, wf_engine.date_format)
t e r U s
• 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
I n
returned with this result. Note that the external entity must call CompleteActivity() to
inform the Workflow Engine when the action completes.
l e
• ERROR:<error_code> The activity encounters an error and returns the indicated error
code.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Exception Handling
e A
c l
If an activity encounters an error, information about the error is stored in the following
Monitor. r a
columns in the WF_ITEM_ACTIVITY_STATUSES table, which are viewable from the Status
• ERROR_NAME O ly
• ERROR_MESSAGE
• ERROR_STACK l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Exception Handling Example
e A
c l
• WF_CORE.CONTEXT adds an entry to the error stack to provide context information
r a
that helps locate the source of an error.
• Use this example exception handler construct in your PL/SQL procedures to facilitate
O ly
debugging workflow function activities.
l & On
• 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
a e
‘procedure name’ and its arguments.
n
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining Activity Details
e A
To define activity details:
c l
r a
1. Open the property pages for the activity you want in the Oracle Workflow Builder and
select the Details tab.
O ly
2. Specify the internal name of the item type that owns the error process that you want to
l & On
execute if an error occurs in the current activity.
3. Specify the internal name of the error process.
n a e
4. Specify the On Revisit value to determine how the Workflow Engine handles this activity
t e r U s
when it transitions to the activity more than once.
- Ignore: Ignores the activity after the activity has been executed once; used for OR-
I n
type operations where the rest of the branch is ignored.
- Reset: Resets completed activities in a loop by executing activities in CANCEL mode
c l e
before re-executing them in RUN mode.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Error Handling
e A
c l
Oracle Workflow provides an item type called System: Error which contains processes that you
can use for generic error handling.
• Default Error Process r a
• Retry-only Process O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Looping
e A
c l
To handle a revisited activity, the Workflow Engine can:
r a
• Ignore the activity and stop further processing of the thread, so that in effect, the activity
can only run once.
O ly
• Reset the loop to the loop point before re-executing by first running cancel logic to undo
the activities within the loop.
l & On
• Loop through the activities to the loop point, re-executing each one without running
n a e
cancel logic to undo any previous logic. The Loop option results in faster performance
t e r U s
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.
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Defining an Activity Attribute
e A
c l
• Activity attributes can be only be associated with function activities or Raise event
activities.
r a
• You can change the definition of an activity attribute at any time in Oracle Workflow
Builder. O ly
To define an activity attribute:
l & On
1. In the Oracle Workflow Builder, select the activity you want in the navigator tree. Then
a e
select New Attribute from the Edit menu.
n
t e r U s
2. On the Attribute property page, enter an internal name for the attribute. The internal name
must be all uppercase without any colons or leading or trailing spaces.
I n
3. Enter a display name for the attribute.
4. Enter a description of the attribute.
l e
5. In the Type field, select the data type for the attribute.
c
r a
6. Depending on the data type, enter format information and a default value, if applicable.
7. Click Apply to save your changes.
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
Setting Activity Attribute Values
e A
To set activity attribute values:
c l
r a
1. In the Oracle Workflow Builder, display the property pages of an activity node, and select
the Node Attributes tab.
2. Select an attribute. O ly
& On
3. Enter a value for the attribute. The value can be either constant or dynamic.
l
n a e
- 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
t e r U s
attribute that returns a value of the appropriate data type during runtime.
4. Click Apply to save your changes.
I n
You can use the WF_ENGINE.GetActivityAttribute APIs to retrieve the value of an activity
l e
attribute within a PL/SQL function. The following example shows a variable being set to the
value of an activity attribute of type text:
c
r a
aname := wf_engine.GetActivityAttrText(itemtype, itemkey,
actid, ‘VALUE1');
O
Copyright © Oracle, 2007. All rights reserved.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Note: In order to use the sample solution scripts provided for these practices, you must enter the
internal names for all objects that you define exactly as shown in the instructions. Otherwise, you
must modify the sample code to reference the object names that you define.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
•
m y
The instructor will provide you with the connect string for the class database and the
user name and password of the Oracle Workflow database account.
d e
•
ca
The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
Workflow Configuration page.
e A
•
c l
The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
r a
have this responsibility assigned to it.
• O ly
The instructor will provide you with the names of users that you can assign as the
l & On
requestor and approver in the Vacation Proposal process. These user names should have
Workflow administrator and user responsibilities assigned to them.
n a e
Tasks
t e r U s
Creating a Subprocess to Reset Item Attribute Values
I n
Create a subprocess within the Vacation Proposal workflow process that you created in the
l e
Creating a Workflow Process practice. The subprocess should use the standard Start, Assign,
c
And, and End activities from the Standard item type.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Complete the definitions of the Assign activity nodes to prepare the necessary item type
attributes to submit a fresh vacation proposal. Use the Assign activity nodes to automatically
reset the From Date and To Date attributes to the alternate values provided by the approver when
the initial vacation proposal was rejected, and to clear the Alternate From Date, Alternate To
Date, and Comments attributes.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
4. Open the property pages for the From Date message attribute associated with the Vacation
Rejected message and set the Source field to Send. The requestor will now no longer
respond to this message with a new from date; instead, the From Date attribute will be
automatically set to the alternate from date suggested by the approver.
5. Open the property pages for the To Date message attribute associated with the Vacation
Rejected message and set the Source field to Send. The requestor will now no longer
respond to this message with a new to date; instead, the To Date attribute will be
automatically set to the alternate to date suggested by the approver.
6.
7.
From the Edit menu, select New > Process.
t e r U s
Vacation Rejected - Resubmit? node and the Vacation Proposal node.
I n
11. Draw a transition from the Vacation Rejected - Resubmit? node to the Reset Dates and
Comments node and select Yes from the transition results menu.
c l e
12. Draw a transition from the Reset Dates and Comments node to the Vacation Proposal node.
r a
13. Double-click the Reset Dates and Comments node to display the process diagram window.
O
Copyright © Oracle, 2007. All rights reserved.
15. Create five Assign nodes by dragging the Assign function from the Standard item type in the
navigator tree into the process diagram window five times.
16. Create an And node by dragging the And function from the Standard item type in the
navigator tree into the process diagram window.
17. Create an End node by dragging the End function from the Standard item type in the
navigator tree into the process diagram window. Double-click the new End node and select
the Node tab. In the Start/End field, select End.
18. Draw a transition from the Start node to the first Assign node.
19. Draw a transition from the first Assign node to the second Assign node.
20. Draw transitions from the second Assign node to the third, fourth, and fifth Assign nodes.
This design specifies that the last three Assign nodes can be processed in parallel.
21. Draw transitions from the third, fourth, and fifth Assign nodes to the And node. This design
specifies that the process should not continue until all three of these Assign nodes have been
completed.
m y
22. Draw a transition from the And node to the End node.
d e
Defining Assign Activity Nodes
ca
e A
23. Double-click the first Assign node and select the Node tab. Enter “Assign value from
Alternate From Date attribute to From Date” as the comment for the node and click Apply.
c l
24. Select the Node Attributes tab. In the Attribute region, define the following properties for
r
the Item Attribute activity attribute: a
− Name: Item Attribute
− Type: Constant O ly
− Value: From Date
l & On
• Click Apply.
n a e
e r s
25. Next, in the Attribute region, define the following properties for the Date Value activity
attribute:
t U
I n
− Name: Date Value
l e
− Type: Item Attribute
− Value: Alternate From Date
c
r a • Click OK.
O
Copyright © Oracle, 2007. All rights reserved.
27. Select the Node Attributes tab. In the Attribute region, define the following properties for
the Item Attribute activity attribute:
− Name: Item Attribute
− Type: Constant
− Value: To Date
• Click Apply.
28. Next, in the Attribute region, define the following properties for the Date Value activity
attribute:
− Name: Date Value
− Type: Item Attribute
− Value: Alternate To Date
• Click OK.
29. Double-click the third Assign node and select the Node tab. Enter “Clear value provided by
approver from Alternate From Date” as the comment for the node and click Apply.
e A
attribute: c l
31. Next, in the Attribute region, define the following properties for the Date Value activity
O • Click Apply.
Copyright © Oracle, 2007. All rights reserved.
• Click OK.
35. Double-click the fifth Assign node and select the Node tab. Enter “Clear value provided by
approver from Comments” as the comment for the node and click Apply.
36. Select the Node Attributes tab. In the Attribute region, define the following properties for
the Item Attribute activity attribute:
− Name: Item Attribute
− Type: Constant
− Value: Comments
• Click Apply.
37. Next, in the Attribute region, define the following properties for the Date Value activity
attribute:
− Name: Text Value
− Type: Constant
− Value: (Leave this field blank)
m y
• Click OK.
d e
38. In the Navigator window, click the Verify button to verify your workflow.
ca
e A
39. From the File menu, select Save to save your work to your workflow definition file.
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
c l e
dates and comments.
r a •
specifying that you want to resubmit the vacation proposal. You should not need to enter
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 1
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 2
Workflow Engine
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 3
Objectives
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 4
Overview of the Workflow Engine
m y
d e
ca
Overview of the Workflow Engine
e A
c l
The Notification System is also implemented in server-side PL/SQL and can interface with the
end users. r a
Workflow Web agent or the Java-based notification mailer program to deliver notifications to
O ly
The Workflow Engine and the Business Event System can function independently of each
l & On
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.
n a e
t e r
Oracle Workflow additionally provides Java wrappers for many Workflow Engine APIs to let
s
you call the Workflow Engine from Java code.
U
API Reference.
I n
For more information, refer to the “Workflow Engine APIs” chapter in the Oracle Workflow
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 5
Overview of the Workflow Engine
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 6
Initiating a Workflow Process
m y
d e
ca
Initiating a Workflow Process
e A
c l
• If you use an event to initiate a workflow process, you must define a subscription that
r a
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
O ly
is received from an external source. In both cases, the process must begin with a Receive
l & On
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
n a e
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
e r s
perform any additional tasks, you can use the LaunchProcess API, which is a wrapper
t U
combining the CreateProcess and StartProcess APIs.
I n
• The procedure that executes the Workflow Engine APIs to initiate a process must identify
e
the item type and item key of the process for these APIs. The item type and item key
l
passed to these APIs uniquely identify an item and must be passed to subsequent API calls
c
for each specific process. The process must begin with the standard Start activity or with
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - 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.
ca
A
--
wf_engine.SetItemAttrText ( itemtype => itemtype,
aname
c l e
itemkey => itemkey,
=> 'REQUISITION_NUMBER',
--
avalue
r a=> RequisitionNumber);
O ly
wf_engine.SetItemAttrNumber ( itemtype => itemtype,
l & On
itemkey => itemkey,
aname => 'REQUISITION_AMOUNT',
n a e
avalue => RequisitionAmount );
--
t e r U s
n
...
--
e I
c l
wf_engine.StartProcess( itemtype => itemtype,
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 8
Workflow Engine Processing
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 9
Workflow Engine Processing
m y
d e
ca
Workflow Engine Processing
e A
c l
The Workflow Engine sets a savepoint for each completed function activity, and saves all
r a
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.
O ly
The Workflow Engine never issues a commit, as it is the responsibility of the calling
l & On
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,
n a e
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
e r s
calling application, which can then issue a commit.
Note: t U
I n
• A notification activity that sends an FYI notification message will be automatically
c l e
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
r a recipient.
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 10
• 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 11
Activity Statuses
m y
d e
ca
Activity Statuses
e A
c l
• Active: The activity is currently being executed. The topmost process will be active until
the entire process completes.
r a
• Complete: The activity executed successfully.
O ly
• Waiting: The activity is waiting for dependencies to complete. An example is the AND
l & On
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.
n a e
• Notified: The activity is waiting for a response from a notification, for an event message,
t e r U s
or for an external program to complete and call the Workflow Engine.
• Deferred: The activity is deferred to a background engine for execution.
I n
• Error: The activity has encountered an error during execution.
• Suspend: The activity is suspended from further execution.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 12
Calling the Workflow Engine
m y
d e
ca
Calling the Workflow Engine
e A
c l
You can add a standard Block activity after any function activity that calls an external
r a
program. The Block activity will pause the process until the external program completes and
makes a call to WF_ENGINE.CompleteActivity().
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 13
Background Engines
m y
d e
ca
Background Engines
e A
c l
Use the Workflow Manager component in Oracle Applications Manager to run background
a
engines by submitting the Workflow Background Process concurrent program.
r
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 14
Stuck Processes
m y
d e
ca
Stuck Processes
e A
c l
For example, a process could become stuck when:
r a
• 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.
O ly
• A process with only one thread loops back, but the pivot activity of the loop has the On
l & On
Revisit property set to Ignore.
• An activity returns a result for which no eligible transition exists. For instance, if the
a e
function for a function activity returns an unexpected result value, and no default
n
t e r U s
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
I n
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
l e
processes when the load on the system is low.
c
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 15
Timed Out Activities
m y
d e
ca
Timed Out Activities
e A
c l
You can fix the due date of an activity at design time by setting the timeout value to a relative
r a
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.
O ly
If you are using an item attribute to set the timeout value, then the item attribute must be set to
l & On
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.
n a e
t e r
Note: If a timed out activity does not have a <Timeout> transition modeled, the Workflow
s
Engine will try to find an error process to execute.
U
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 16
Deferred Processing
m y
d e
ca
Deferred Processing
e A
c l
The Workflow Engine integrates with Oracle Advanced Queuing to carry out deferred
r a
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
O ly
processes the deferred queue messages, executing and completing the deferred activity.
l & On
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
n a e
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,
e r s
which are not allowed in a database trigger.
t U
The following example shows how to defer a process immediately upon launching it.
I n
e
-- Set engine to defer everything to the background engine for this session
l
-- This provides faster user response time, at the expense of
c
a
-- delaying workflow progress until the background engine runs.
O rsave_threshold := wf_engine.threshold;
wf_engine.threshold := -1;
Workflow Engine
Chapter 12 - Page 17
-- Launch the process
wf_engine.CreateProcess(...);
wf_engine.SetItemAttr...(...);
wf_engine.StartProcess(...);
exception
-- Ensure threshold is reset
wf_engine.threshold := save_threshold;
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 18
Oracle Workflow APIs
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 19
Oracle Workflow APIs
m y
d e
ca
Oracle Workflow APIs
e A
c l
The public views are installed in the APPS account.
r a
Note: Additionally, Oracle Workflow includes APIs to handle Release 2.5 workflow Advanced
Queuing processing. Although these APIs will continue to be supported for backward
O ly
compatibility, customers using Oracle Workflow Release 2.6 and higher should use the
l & On
Business Event System rather than the queue APIs to integrate with Oracle Advanced Queuing.
For more information, refer to the Oracle Workflow API Reference.
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 20
Workflow Engine APIs
m y
d e
ca
Workflow Engine APIs
e A
c l
• WF_ENGINE.CreateProcess creates a new run-time process for a work item.
r a
• WF_ENGINE.StartProcess begins execution of the specified process.
O ly
• WF_ENGINE.LaunchProcess launches a specified process by creating the new run-time
process and beginning its execution.
& On
• WF_ENGINE.SetItemOwner sets the owner of an existing item.
l
n a e
• WF_ENGINE.SetItemUserKey sets a user-friendly identifier for an item.
• WF_ENGINE.GetItemUserKey returns the user-friendly identifier assigned to an item.
e r s
• WF_ENGINE.SetItemParent defines the parent/child relationship for master/detail
processes.
t U
I n
• WF_ENGINE.Event receives an event from the Business Event System into a workflow
process.
c l e
• WF_ENGINE.Background runs a background engine to process deferred and timed out
Workflow Engine
Chapter 12 - Page 21
• WF_ENGINE.StartForkProcess begins execution of the specified new forked process.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 22
Workflow Engine APIs
m y
d e
ca
Workflow Engine APIs
e A
c l
• WF_ENGINE.SetItemAttrText, WF_ENGINE.SetItemAttrNumber,
r
item type attribute in a process. a
WF_ENGINE.SetItemAttrDate, and WF_ENGINE.SetItemAttrEvent set the value of an
O ly
• WF_ENGINE.SetItemAttrDocument sets the value of an item attribute of type document
to a document identifier.
l & On
• WF_ENGINE.SetItemAttrTextArray, WF_ENGINE.SetItemAttrNumberArray, and
a e
WF_ENGINE.SetItemAttrDateArray set the values of an array of item type attributes in a
n
process.
t e r U s
• WF_ENGINE.GetItemAttrText, WF_ENGINE.GetItemAttrNumber,
I n
WF_ENGINE.GetItemAttrDate, and WF_ENGINE.GetItemAttrEvent return the value of
an item type attribute in a process.
l e
• WF_ENGINE.GetItemAttrDocument returns the document identifier of an item attribute
c
of type document.
r a
• WF_ENGINE.GetItemAttrClob returns the value of an item type attribute in a process as a
character large object (CLOB).
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 23
• 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.
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 24
Workflow Engine APIs
m y
d e
ca
Workflow Engine APIs
e A
c l
• WF_ENGINE.AddItemAttr adds a new item attribute to the run-time process.
r a
• WF_ENGINE.AddItemAttrTextArray, WF_ENGINE.AddItemAttrNumberArray, and
WF_ENGINE.AddItemAttrDateArray add an array of new item type attributes to the run-
time process. O ly
l & On
• WF_ENGINE.GetActivityAttrText, WF_ENGINE.GetActivityAttrNumber,
WF_ENGINE.GetActivityAttrDate, and WF_ENGINE.GetActivityAttrEvent return the
a e
value of an activity attribute in a process.
n
t e r U s
• WF_ENGINE.GetActivityAttrClob returns the value of an activity attribute in a process as
a character large object (CLOB).
I n
• WF_ENGINE.GetActivityAttrInfo returns information about an activity attribute, such as
its type and format.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 25
Workflow Engine APIs
m y
d e
ca
Workflow Engine APIs
e A
c l
• WF_ENGINE.CompleteActivity notifies the engine that the specified activity has been
r a
completed for the item, identifying the activity by the activity node label name.
• WF_ENGINE.CompleteActivityInternalName notifies the engine that the specified
O ly
activity has been completed for the item, identifying the activity by its internal name.
l & On
• WF_ENGINE.BeginActivity determines if the specified activity can currently be
performed and raises an exception if it cannot.
n a e
• WF_ENGINE.AssignActivity assigns an activity to another performer.
t e r U s
• WF_ENGINE.GetActivityLabel returns the instance label of an activity, given the internal
activity instance identification.
I n
• WF_ENGINE.AbortProcess aborts process execution and cancels outstanding
notifications.
l e
• WF_ENGINE.SuspendProcess suspends process execution so that users cannot transition
c
items to new activities.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 26
Workflow Engine APIs
m y
d e
ca
Workflow Engine APIs
e A
c l
• WF_ENGINE.ResumeProcess returns a suspended process to normal execution status.
r a
• 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. O ly
item instance.
l & On
• WF_ENGINE.ItemStatus returns the status and results for the root process of the specified
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 27
Workflow Engine Bulk APIs
m y
d e
ca
Workflow Engine Bulk APIs
e A
c l
• WF_ENGINE_BULK.CreateProcess creates multiple new run-time process instances of
r a
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
O ly
instances at once, identified by the specified item type and array of workflow item keys.
l & On
• 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
a e
begins execution of the new work items at the specified activity.
n
t e r U s
• WF_ENGINE_BULK.SetItemAttrText, WF_ENGINE_BULK.SetItemAttrNumber, and
WF_ENGINE_BULK.SetItemAttrDate set the values of an array of item type attributes in
n
multiple work items, identified by the specified item type and array of item keys.
I
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 28
Practice - Implementing Timeout Processing
Overview
In this practice, you will implement one type of timeout processing in the Vacation Proposal
workflow process that you created in the Creating a Workflow Process practice.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the connect string for the class database and the
user name and password of the Oracle Workflow database account.
• The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
m y
Workflow Configuration page.
d e
•
ca
The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
have this responsibility assigned to it.
e A
•
c l
The instructor will provide you with the names of users that you can assign as the
r a
requestor and approver in the Vacation Proposal process. These user names should have
Workflow administrator and user responsibilities assigned to them.
Tasks O ly
l & On
Defining Timeout Processing with a Loop Counter
n a e
e r
Modify the Vacation Proposal workflow process that you created in the Creating a Workflow
s
Process practice by defining timeout processing to transition to a loop counter, and on the third
t U
loop, exit to approve the proposal automatically.
I n
Running a Background Engine
c l e
Run a background engine to process timed out activities.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 29
Solution – Implementing Timeout Processing
Defining Timeout Processing with a Loop Counter
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
3. Open the process diagram window for the Vacation Proposal process and open the property
pages for the Vacation Proposal notification activity node.
4. Select the Node tab. In the Timeout region, select Relative Time as the type. For the value,
enter a short duration such as 1 minute for testing purposes. Click OK.
5. Select the Loop Counter function activity in the Standard item type. To locate the Loop
Counter activity, you can choose Find from the Edit menu or press Ctrl+F. Enter “Loop
Counter” in the Search Text field, select the Display Name and Function check boxes, and
click the Search button. The Loop Counter activity will be automatically selected. Close the
Find window.
6. Drag and drop the Loop Counter activity into the Vacation Proposal process diagram,
positioning it above the Vacation Proposal notification node.
m y
7. e
Open the property pages for the Loop Counter node and select the Node Attributes tab to set
d
the number of times the Workflow Engine should execute the loop. Select the Loop Limit
ca
attribute. Select the type Constant and enter the value 2 for the attribute. Click OK.
8. A
Draw a transition from the Vacation Proposal node to the Loop Counter node and select
e
l
<Timeout> from the transition results menu.
c
9.
a
Create a vertex point in the transition between the Vacation Proposal node and the Loop
Counter node.
r
O ly
10. Draw a transition from the Loop Counter node back to the Vacation Proposal node and
& On
select Loop from the transition results menu.
l
a e
11. Draw a transition from the Loop Counter node to the Vacation Approved FYI node and
n
t e r U s
select Exit from the transition results menu.
12. In the Navigator window, click the Verify button to verify your workflow.
I n
13. From the File menu, select Save to save your work to your workflow definition file.
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 30
14. From the File menu, select Save As and save your item type to the class database, using the
database user name, password, and connect string provided by the instructor.
16. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges. m y
d e
17. Use the Developer Studio to launch your workflow process and test your work. You can use
ca
the Worklist Web pages to view the notifications sent by the process, and use the Status
Monitor Web pages to review the status of the process.
e A
•
c l
Verify your work by reviewing the Vacation Proposal notification on the Notification
Details Web page. The message header should now display both a sent date and a due
r a
date. The interval between these times should be equal to the relative time value you
entered for the notification timeout. Write down the times for the sent date and due date.
O ly
•
l & On
To test your work, do not respond to the Vacation Proposal notification, but allow the
notification activity to time out instead by waiting for the timeout interval you specified
to elapse.
n a e
Running a Background Engine
t e r U s
I n
18. Run a background engine for your item type to process the timed out activity and allow the
process to continue. Run the background engine repeatedly to process timed out activities
c l e
for each execution of the loop. You can run a background engine through the Oracle
Workflow Manager component of Oracle Applications Manager. You can also run a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 31
19. To run a background engine through Oracle Applications Manager to process timed out
activities:
• Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
• On the Workflow System page, select Background Engines from the Submit Request For
menu and click Go to submit the concurrent request through Oracle Self-Service Web
Applications.
• Click Next in each remaining page of the wizard until the Summary page, and then click
Submit.
20. To run the WF_ENGINE.Background API to process timed out activities, open SQL*Plus
and enter the following command:
m y
Exec WF_ENGINE.Background('WFVACXX', NULL, NULL, FALSE, TRUE,
FALSE);
d e
ca
21. Log in to Oracle Workflow as the requestor and use the Status Monitor Web pages to review
c l
22. Allow the Vacation Proposal notification activity to time out again. Then run a background
r a
engine again to process the timed out activity.
O ly
23. Use the Status Monitor Web pages to review the status of the process and verify that the
& On
process followed the timeout transition to execute the Loop Counter activity a second time.
l
n a e
24. Allow the Vacation Proposal notification activity to time out again. Then run a background
engine again to process the timed out activity.
t e r U s
25. Use the Status Monitor Web pages to review the status of the process and verify that the
I n
process followed the timeout transition to execute the Loop Counter activity a third time and
then followed the exit transition to execute the Vacation Approved FYI activity and the rest
l e
of the process. Use the Worklist Web pages to review the notification sent by the Vacation
c
Approved FYI activity.
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 32
Practice - Implementing Deferred Processing
Overview
In this practice, you will implement deferred processing for a function activity in the Vacation
Proposal workflow process that you created in the Creating a Workflow Process practice.
Note: Because many students access the system and create objects during this course, you need a
way to distinguish between the objects created by you and by your classmates. Therefore, you
will be assigned a terminal number by your instructor. Use this number as a prefix wherever you
see XX included in the name of something that you are defining. In this way, you can ensure that
the definitions you create are unique.
Assumptions
• You must have access to an Oracle Applications Vision database, or a comparable
training or test instance at your site on which to complete this practice.
• The instructor will provide you with the connect string for the class database and the
user name and password of the Oracle Workflow database account.
• The instructor will provide you with the user name and password of a user with
workflow administrator privileges. The workflow administrator is defined on the
m y
Workflow Configuration page.
d e
•
ca
The instructor will provide you with the URL for the login page and the name of a
Workflow administrator responsibility. The user name that you use to log in should
have this responsibility assigned to it.
e A
•
c l
The instructor will provide you with the names of users that you can assign as the
r a
requestor and approver in the Vacation Proposal process. These user names should have
Workflow administrator and user responsibilities assigned to them.
Tasks O ly
Defining Deferred Processing
l & On
n a e
e r
Modify the Vacation Proposal workflow process that you created in the Creating a Workflow
s
Process practice by implementing deferred processing for a function activity in the process. To
t U
do so, set the function activity cost above the engine threshold to defer the activity when the
I
process is executed. n
l e
Running a Background Engine
c
r a
Run a background engine to process deferred activities.
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 33
Solution – Implementing Deferred Processing
Defining Deferred Processing
2. From the File menu, select Open to open the wfvacXX.wft data store that you defined in the
Creating a Workflow Process practice.
3. Open the property pages for the Update Vacation Schedule function activity. Change the
cost for the activity to 100. Because this cost is above the default engine threshold of 50, the
activity will be deferred when the process is executed. Click OK.
4. In the Navigator window, click the Verify button to verify your workflow.
5. From the File menu, select Save to save your work to your workflow definition file.
6. From the File menu, select Save As and save your item type to the class database, using the
database user name, password, and connect string provided by the instructor.
8. Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
m y
9.
d e
Use the Developer Studio to launch your workflow process and test your work. You can use
•
e A
To test your work, log in as the approver and approve the Vacation Proposal notification.
c l
•
r a
Log in as the requestor and use the Status Monitor Web pages to review the status of the
process. The process should be stopped at the Update Vacation Schedule function
activity.
O ly
Running a Background Engine
l & On
a e
10. Run a background engine for your item type to process the deferred activity and allow the
n
e r
process to continue. You can run a background engine through the Oracle Workflow
s
Manager component of Oracle Applications Manager. You can also run a background
t U
engine using the WF_ENGINE.Background API.
I n
11. To run a background engine through Oracle Applications Manager to process deferred
l e
activities:
c
O ra
• Use a Web browser to connect to a Workflow administrator responsibility with the URL
provided by the instructor. Log in as a user with workflow administrator privileges.
Workflow Engine
Chapter 12 - Page 34
• Click the Workflow Manager link.
• On the Workflow System page, select Background Engines from the Submit Request For
menu and click Go to submit the concurrent request through Oracle Self-Service Web
Applications.
• Click Next in each remaining page of the wizard until the Summary page, and then click
Submit.
12. To run the WF_ENGINE.Background API to process deferred activities, open SQL*Plus
and enter the following command:
13. Log in to Oracle Workflow as the requestor and use the Status Monitor Web pages to view
the diagram for the process. The process should now have completed.
m y
d e
14. To remove the deferred processing so that you will not need to run the background engine in
later practices, start the Oracle Workflow Builder, open the wfvacXX.wft data store, open
15. In the Navigator window, click the Verify button to verify your workflow.
e A
c l
16. From the File menu, select Save to save your work to your workflow definition file.
r a
17. From the File menu, select Save As and save your item type to the class database, using the
O ly
database user name, password, and connect string provided by the instructor.
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 35
Summary
m y
d e
ca
e A
c l
r a
O ly
l & On
n a e
t e r U s
I n
c l e
r a
O
Copyright © Oracle, 2007. All rights reserved.
Workflow Engine
Chapter 12 - Page 36