| Oracle Workflow Guide Release 2.6.2 Part Number A95265-03 |
|
|
|
| |
|
|
||
| Contents | Index | Glossary | Master Index | Feedback |
procedure TRANSFER
(nid in number,
new_role in varchar2,
forward_comment in varchar2 default null);
Java Syntax
public static boolean transfer
(WFContext wCtx,
BigDecimal nid,
String newRole
String comment)
Description
This procedure forwards a notification to a new role and transfers ownership of the notification to the new role. It also implicitly calls the Callback function specified in the Send or SendGroup function with TRANSFER mode. A comment can be supplied to explain why the forward is taking place. The Transfer feature in the Notification System calls this procedure. Note that when you transfer a notification, the transfer is recorded in the USER_COMMENT field of the notification.
Attention: Existing notification attributes (including due date) are not refreshed or otherwise changed except for ORIGINAL_RECIPIENT, which identifies the owner of the notification.
Arguments (input)
| wCtx | Workflow context information. Required for the Java method only. See: Oracle Workflow Context. |
| nid | The notification id. |
| new_role or newRole | The role name of the person the note is transferred to. |
| forward_comment or comment | An optional comment to append to notification. |
The following code excerpt shows an example of how to call transfer() in a Java program. The example code is from the WFTest.java program.
// transfer to MBEECH
System.out.println("Transfer Test");
System.out.println("Transfer nid " + myNid +
" from BLEWIS to MBEECH");
WFNotificationAPI.transfer(ctx, myNid, "MBEECH",
"Matt, You own it now.");
count = WFNotificationAPI.workCount(ctx, "MBEECH");
System.out.println("There are " + count +
" open notification(s) for" +
p" MBEECH after Transfer.");
| Previous | Next | Contents | Index | Glossary |
