Task release does not work correctly when task is assigned to a group
kbt167164
PRODUCTIssue
When a workflow task is assigned to a manually typed in group with the task result rule set to "First Response" and "Resolve group to individuals" options unchecked, the task does not become available to all group users after a user who opened the task releases it.Symptoms
When a workflow task is assigned to a manually typed in group with the following configuration:
Task result rule = "First Response"
"Resolve groups to individuals" = Unchecked
"How many responses are available" = "Only one response"
When one of the group users opens the task and then releases it, the task remains allocated for all other users in the group, whereas expectation is that it should be available for all users of the group after release.
Resolution
This issue has been addressed in 5.3 and you have to upgrade to this version to get a fix for this issue. There is no fix for previous releases as the fix for this problem infers a K2 database schema change. It cannot be shipped in the form of a fix pack for any previous versions as this will break the 5.3 upgrade process for every client who applies this fix for a previous version. The 5.3 installer does not account for this column in previous versions of the product. There is no way of implementing such a fix without introducing excessive support/testing overhead and complexity.
This specific fix relies on presence in K2 database new column in Server.WorklistSlot table named OriginalActionerID, which allows to track when task has been assigned to a group. Changes to K2 database schema are shipped with major releases, or, in special cases, in Fix Packs for current major release, but they never shipped for previous major releases.
On the screenshot above you can see Server.WorklistSlot table columns in 5.2 (on the left) and 5.3 (on the right) versions of K2 database schema.
