Skip Headers
Oracle Workflow Developer's Guide
Release 2.6.3.5
Part Number B12161-02
|
|
 |
 |
|
 |
 |
 |
| |
Previous |
Next |
|
Contents |
Index |
Glossary |
Workflow Objects That Support Versioning
The following Workflow objects support versioning:
- Processes and subprocesses
- Process activities (nodes)
- Activity attribute values
When you modify any of these objects in the Workflow Builder and save them to the database, the Workflow Loader does not update the existing definition of the object. Instead, a new version of the object or owning object is created.
As a result, you can modify any of these objects without affecting active work items that were initiated before the change.
For example:
- If you update a notification activity to reference a new message, the notification will be versioned.
- If you update a function activity to reference a new lookup type, the function will be versioned.
- If you update a function activity to reference a new API, the function will be versioned.
- If you remove a process activity, or node, from a process diagram, the owning process will be versioned, as well as all the process activities that exist within the process.
- If you add an activity attribute to an activity, the owning activity will be versioned.
The modifications in all of these examples will affect only work items that are initiated after the changes are made.
Copyright © 2003, 2004, Oracle. All rights reserved.