JR45351: REASSIGNING A TASK BACK TO THE SAME SET OF USERS AS DEFINED FAILS, LEAVING THE TASK NOT OPERABLE
Fixes are available
Closed as program error.
Reassigning a task back to the same set of users as defined (as potential owners of the task) before the task was claimed fails, leaving the task not operable, i.e. unclaimable.
Problem Description: When defining task assignment (aka task routing) in terms of a custom user list, the sequence of claiming the task and assigning it back to the initial custom user list will result in the task not being assigned to any user or role, thus rendering the task not operable. Problem Summary: Custom user lists are internally mapped onto ad-hoc groups. In order to keep the number of ad-hoc group low, such groups are deleted internally after claiming a task. Such deletion concerns DB entries, but not the group entries maintained in a memory cache. When reassigning the task back to the initial custom user list, the initial ad-hoc group is found in the memory cache, but has no entry in the database. Problem Conclusion: The deletion of the ad-hoc group is removed, so that cach and database entries fr the ad-hoc group never get out of sync. Removal of unnecessary ad-hoc groups is covered by a separate mechanism.
Problem will be fixed with V8011
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
Fixed component ID
Applicable component levels