Forums » Interstage BPM Server
Group WorkItem
-
What would be the impact if I set SupportGroupWorkItem=false vs SupportGroupWorkItem=true in ibpmproperties table
And I create process definition with tasks as group workitem.
It does creates group workitem with false,
do we provide option to set a task as group task (like studio) in console process designer
Author: Nanda Subramani
Attachment: -
Hi Nanda,
You should be able to set a task a a group task from the system properties using SupportGroupWorkItem=true.
However, I've tested this and it doesn't look it like it is working properly. Let me look into this with development and get back to you.Author: Marc Bui
Attachment: -
SupportGroupWorkItem
Initial value: falseThis parameter specifies support for the Group Work Item feature of Interstage BPM. If this parameter
is set to true, you can specify work items as group work items. This means that anyone in the specified group can work on them.
Note: • Note the following when setting the parameter to true:
• The functionality and filtering of work items is restricted. Refer to the API Javadoc for details.
• The parameter has no effect on work items associated with Voting Activity Nodes and when a Role Java Action is used. A group work item is not generated; instead,
work items for each user in the group are generated.
• In the Directory Service, don't use the same name for a user and a group. A user having the same name as a group can work on a group work item even if the user doesn't belong to that group.
• If you specify any other value than true, TRUE, false or FALSE, the Interstage BPM Server uses the initial value false.
Regards,
RajeevAuthor: Rajeev Kumar Singh
Attachment: -
Thanks Rajeev,
I also wanted to add that the Interstage BPM server gives precedence to the property set at the node level (ExpandGroups) over the system level property (SupportGroupWorkItem).
According to the developer's guide, the SupportGroupWorkItem parameter was created as a global parameter to support process definitions that have no setting for "ExpandGroups". These type process definitions were created by very old versions of the product.
Detail of this parameter can be found from the developer's guide under the following section, "Changing the Work Item Mode".Author: Marc Bui
Attachment: -
Thanks,
even with SupportGroupWorkItem=false, filtering is restricted, it gives you the tasks only when you select All Tasks.
----------
when we set as group workitem for group "XYZ", just using Expand Groups in studio.
and user who is non admin and belongs to that group "XYZ".
will that user be able to see his group workitem? i dont think
because non admin user will be able to see only MyTasks not All Tasks.
Here admin user has to assign that task specifically to that user or use action to assign it.
so how to make non admin user to see the group workitems by themselves
is this something to do with SupportGroupWorkItem=trueAuthor: Nanda Subramani
Attachment: -
Nanda,
The SupportGroupWorkItem=true will not change the filtering restriction to solve the problem you are facing.
The scenario you described is an issue. The non-admin user should be able to view and work on the work item from "All Tasks" since it was set as a group work item. We've verfied that the "All Tasks" filter was available for non-admin users on an older build (7.4) and seems to be gone from the newer builds. We will log this issue as a bug to development.
Can you confirm the build you are seeing this issue in?
Thanks,
MarcAuthor: Marc Bui
Attachment: -