|
Oracle Workflow Developer's Guide Release 2.6.3 Part Number B10284-02 |
|
|
|
|
|
||
| Previous | Next | Contents | Index | Glossary |
Note: If you are using the Oracle Applications Framework-based version of the Worklist pages available with Oracle Workflow embedded in Oracle Applications, the Reassign page may include the Delegate field or the Transfer field instead of the Reassign field, depending on the setting of the FND: Notification Reassign Mode profile option. The #HIDE_REASSIGN attribute controls the Delegate field and the Transfer field in the same way as the Reassign field. See: Setting the FND: Notification Reassign Mode Profile Option, Oracle Workflow Administrator's Guide.
The #WF_REASSIGN_LOV attribute must be of type role and must have a source of Send. You can either specify a particular role as a constant value for the #WF_REASSIGN_LOV attribute, or specify an item type attribute as the value and include logic in your workflow process that dynamically sets that item type attribute to the role you want at runtime. If no existing role meets your needs, you can include logic in your process to create an ad hoc role at runtime and add the users you want to that role. See: CreateAdHocRole, Oracle Workflow API Reference and AddUsersToAdHocRole, Oracle Workflow API Reference.
Note: The Oracle Workflow web pages are being converted to the Oracle Applications Framework user interface format. Depending on your version of Oracle Workflow and which patches you have applied, you may see Oracle Workflow web pages in the new format or in the previous format. The new Worklist pages that support the #WF_REASSIGN_LOV attribute are currently available for the version of Oracle Workflow embedded in Oracle Applications.
To Reassign a Notification to Another User (for Oracle Applications), Oracle Workflow User's Guide
| Previous | Next | Contents | Index | Glossary |
