Task Workflow Being Sent to All Members of Group Even if They are End Dated
Last updated on DECEMBER 14, 2017
Applies to:Oracle Common Applications - Version 12.1.3 and later
Information in this document applies to any platform.
On : 12.1.3 version, Common MES
When tasks are assigned to a group resource, it sends notifications to all members (even end-dated members of the group) regardless of what value has been put in the profile option 'Task Manager: Send notifications to Group and Team members'.
If the profile option is set to 'No', notifications should not go out to the group.
If the profile option is set to 'Yes', it should only send notifications to active members of the group and not to end-dated group members or users who have been end-dated.
The issue can be reproduced at will with the following steps:
1. End dating resource (i.e Employee ) from the group.
-> End dated the resource from a resource group, and then created a task related that resource group(Owner in TASK form).
-> Task Workflow notification are coming to end dated resource above.
2. End dating resource (i.e Employee ) from the group + end dating the User (I.e FND_USER)
-> End dated the resource from a resource group, and end dated the user, then created a task related that resource group(Owner in TASK form).
-> Task Workflow went into error.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms