Feb 5, 2010

Predefined Oracle workflow activities:

Predefined Oracle workflow activities:

And/Or Activities: In cases where multiple parallel branches transition to a single node, you can decide whether that node should transition forward when any of those parallel branches complete or when all of the parallel branches complete. Use the And activity as the node for several converging branches to ensure that all branches complete before continuing. Use the Or activity as the node for several converging branches to allow the process to continue whenever any one of the branches completes.

And: Completes when the activities from all converging branches complete. Calls a PL/SQL procedure named WF_STANDARD.ANDJOIN.

Or:Completes when the activities from at least one converging branch complete. Calls a PL/SQL procedure named WF_STANDARD.ORJOIN.

Comparison Activities
The comparison activities provide a standard way to compare two numbers, dates, or text strings.
Compare Date: Use to compare the value of an item type attribute of type Date with a constant date.
Compare Number: Use to compare the value of an item type attribute of type Number with a constant number.
Compare Text: Use to compare the value of two item type attributes of type Text.

All the Comparison activities call a PL/SQL procedure named WF_STANDARD.COMPARE.

Compare Execution Time Activity
The Compare Execution Time activity provides a standard way to compare the elapsed execution time of a process with a constant test time. The Compare Execution Time activity calls a PL/SQL procedure named WF_STANDARD.COMPAREEXECUTIONTIME.

Wait Activity
The Wait activity pauses the process for the time you specify. You can either wait until:
1. a specific date
2. a given day of the month
3. a given day of the week
4. a period of time after this activity is encountered

This activity calls the PL/SQL procedure named WF_STANDARD.WAIT.

Block Activity
The Block activity lets you pause a process until some external program or manual step completes and makes a call to the CompleteActivity Workflow Engine API. Use the Block activity to delay a process until
some condition is met, such as the completion of a concurrent program. Make sure your program issues a CompleteActivity call when it completes to resume the process at the Block activity. This activity calls the PL/SQL procedure named WF_STANDARD.BLOCK.

Defer Thread Activity
The Defer Thread activity defers the subsequent process thread to the background queue without requiring you to change the cost of each activity in that thread to a value above the Workflow Engine threshold. This activity always interrupts the process thread by causing a disconnect to occur in the current database session, even if the thread is already deferred. This activity calls the PL/SQL procedure named WF_STANDARD.DEFER.

Launch Process Activity
The Launch Process activity lets you launch another workflow process from the current process. This activity calls the PL/SQL procedure named WF_STANDARD.LAUNCHPROCESS.

Noop Activity
The Noop activity acts as a place holder activity that performs no action. You can use this activity anywhere you want to place a node without performing an action. You can change the display name of this
activity to something meaningful when you include it in a process, so that it reminds you of what you want this activity to do in the future. This activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

Loop Counter Activity
Use the Loop Counter activity to limit the number of times the Workflow Engine transitions through a particular path in a process. The Loop Counter activity can have a result of Loop or Exit. This Loop Counter activity calls the PL/SQL procedure named WF_STANDARD.LOOPCOUNTER.

Start Activity
The Start activity marks the start of a process and does not perform any action. Although it is not necessary you may include it in your process diagram to visually mark the start of a process as a separate node. This
activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

End Activity
The End activity marks the end of a process and does not perform any action. You can use it to return a result for a completed process by specifying a Result Type for the activity. Although it is not necessary,
you may include it in your process diagram to visually mark the end of your process as a separate node. This activity calls the PL/SQL procedure named WF_STANDARD.NOOP.

Role Resolution Activity
The Role Resolution activity lets you identify a single user from a role comprised of multiple users. In a process diagram, place the Role Resolution activity in front of a notification activity and specify the
performer of that notification activity to be a role consisting of several users. The Role Resolution activity selects a single user from that role and assigns the notification activity to that user. This activity calls the PL/SQL procedure named WF_STANDARD.ROLERESOLUTION.

Notify Activity
The Notify function activity lets you send a notification, where the message being sent is determined dynamically at runtime by a prior function activity. To use the Notify activity, you must model a prerequisite function activity into the process that selects one of several predefined messages for the Notify activity to send.

Vote Yes/No Activity
The Vote Yes/No activity lets you send a notification to a group of users in a role and tally the Yes/No responses from those users. The results of the tally determine the activity that the process transitions to
next. The Vote Yes/No activity, classified as a notification activity, first sends a notification message to a group of users and then performs a PL/SQL post–notification function to tally the users' responses (votes).

Master/Detail Coordination Activities
The Master/Detail coordination activities let you coordinate the flow of master and detail processes. For example, a master process may spawn detail processes that need to be coordinated such that the master
process continues only when each detail process reaches a certain point in its flow or vice versa.

Wait for Flow Activity
Place this activity in a master or detail process to pause the flow until the other corresponding detail or master process completes a specified activity. This activity calls a PL/SQL procedure named
WF_STANDARD.WAITFORFLOW.

Continue Flow Activity Use this activity to mark the position in the corresponding detail or master process where, upon completion, you want the halted process to continue. This activity calls a PL/SQL procedure named WF_STANDARD.CONTINUEFLOW.

Assign Activity
The Assign activity lets you assign a value to an item attribute. This activity calls the PL/SQL procedure named WF_STANDARD.ASSIGN.

Get Monitor URL Activity
The Get Monitor URL activity generates the URL for the Workflow Monitor diagram window and stores it in an item attribute that you specify. This activity calls the PL/SQL procedure named F_STANDARD.GETURL.



AND/OR Activities :


In cases where multiple parallel branches transition to a single node, you can decide whether that node should transition forward when
Any of those parallel branches complete (OR) => Uses the WF_STANDARD.AndJoin procedure
When all of the parallel branches complete. (AND) => Uses the WF_STANDARD.OrJoin procedure

COMPARISON Activity :
The comparison activities provide a standard way to compare two numbers, dates, or text strings.
Compare Date compares a date-type item with a constant date
Compare Number compares a number-type item with a constant number
Compare Text compares two text-type item types.
All of these use the procedure :
WF_STANDARD.Compare.

WAIT Activity :
The Wait activity pauses the process for the time you specify. One can wait until -
A specific date
A given day of the month
A given day of the week
A period of time after this activity is encountered
This activity calls the PL/SQL procedure named WF_STANDARD.WAIT.

No comments:

OraApps Search

Custom Search

Search This Blog