Skip Headers
Oracle Workflow Developer's Guide
Release 2.6.3.5
Part Number B12161-02
|
|
 |
 |
|
 |
 |
 |
|
Previous |
Next |
|
Contents |
Index |
Glossary |
Example Function Activities
In general, a function activity must have the following information specified in its Activity property page:
- Internal name for the activity.
- Display name for the activity.
- Result type for the activity, which can be none or the name of a predefined lookup type.
- Name of the PL/SQL stored procedure that the activity calls.
Also, the PL/SQL stored procedure that a function activity calls must comply with a specific API. See: Standard API for PL/SQL Procedures Called by Function Activities.
You can view the scripts that create the WF_REQDEMO stored procedure package used by the Requisition process in the demo subdirectory of the Oracle Workflow directory structure on your server.
See Also
Example: Select Approver
Example: Verify Authority
Copyright © 2003, 2004, Oracle. All rights reserved.