Reassignment List On Vacation Rules Page Not Restricted By Attribute WF_REASSIGN_LOV
(Doc ID 1492500.1)
Last updated on FEBRUARY 17, 2023
Applies to:
Oracle Workflow - Version 12.1.3 to 12.1.3 [Release 12.1]Information in this document applies to any platform.
Symptoms
Developing a custom workflow and one of the requirements in workflow is to restrict the user list for reassignment on vacation rule page based on a ROLE.
Configred WF_REASSIGN_LOV attribute as specified in:
Oracle Workflow Developer's Guide - Release 12.1 - Part No. E12905-04 - page 3-33,
but the list of users is not getting restricted to the users assigned to the role.
Steps to Reproduce
1. Create a custom workflow and configure the WF_REASSIGN_LOV attribute as described in the Workflow Developer's guide.
2. Create a role and assign it to WF_REASSIGN_LOV.
3. Run the custom workflow so that notification which is configured with the WF_REASSIGN_LOV gets triggered.
4. Create a vacation rule on the notification and check if a list of users is restricted to the users assigned to role created in step#2.
Documentation from Oracle Workflow Developer's Guide - Release 12.1 - Part No. E12905-04 - page 3-33 reads:
You can use a special message attribute with the internal name #WF_REASSIGN_LOV to specify the users to whom a message can be reassigned. Create a role whose members are all the users that you want to allow as possible new recipients when the notification is reassigned, and assign this role as the value for the #WF_REASSIGN_LOV attribute.
Then, when the notification recipient attempts to reassign the notification, only the users that belong to that role will appear in the list of values for the Assignee field. See:
To Reassign a Notification to Another User, Oracle Workflow User's Guide.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |