Manual:Extension/Workflows/Activity/GroupVote: Difference between revisions

No edit summary
No edit summary
Line 1: Line 1:
==Description==
==Description==
The activity ''GroupVot''e is responsible for collecting necessary data about the voting of a group on a special topic. Unlike the UserVote it is not possbile to delegate the task. A user that is part of a group can accept or decline a vote and also leave a comment, which justifies their decision. The voting result is determined by whatever threshold has been reached first and ends the activity.  
The activity ''GroupVot''e is responsible for collecting necessary data about the voting of a group on a special topic. Unlike the [[Manual:Extension/Workflows/Activity/UserVote|UserVote]], it is not possbile to delegate the task. A user that is part of a group can accept or decline a vote and also leave a comment that justifies their decision. The voting result is determined by whatever threshold has been reached first and ends the activity.  
{| class="wikitable"
{| class="wikitable"
! colspan="2" |'''Short profile'''
! colspan="2" |'''Short profile'''

Revision as of 15:13, 21 December 2021

Description

The activity GroupVote is responsible for collecting necessary data about the voting of a group on a special topic. Unlike the UserVote, it is not possbile to delegate the task. A user that is part of a group can accept or decline a vote and also leave a comment that justifies their decision. The voting result is determined by whatever threshold has been reached first and ends the activity.

Short profile
Name GroupVote
Async No
BPMN type bpmn:userTask
BPMN Extension Element "wf:type" group_vote

Extension elements

Name of extension element Description Type
threshold Multiple thresholds can be defined element
threshold/type Arbitraty identifier, to be used in the connected gateway string
threshold/value Either absolute or relative number of users. Depends on unit. int
threshold/unit Either user or percent. string

Example

<bpmn:extensionElements>
   <wf:type>group_vote</wf:type>
   <wf:threshold>
   		<wf:type>yes</wf:type>
<wf:value>3</wf:value>
<wf:unit>user</wf:unit>
    </wf:threshold>
    <wf:threshold>
   		<wf:type>no</wf:type>
<wf:value>10</wf:value>
<wf:unit>percent</wf:unit>
    </wf:threshold>
</bpmn:extensionElements>

<bpmn:outgoing>FromGroupVoteToGatewayGroupVote</bpmn:outgoing>

Once one of the thresholds is reached, the activity will be completed and a <bpmn:exclusiveGateway> (referenced by <bpmn:outgoing>) will be called. It will choose its outgoing <bpmn:sequenceFlow> by mapping its name to the "type" of the threshold that has been reached.

<bpmn:exclusiveGateway id="GatewayGroupVote">
  <bpmn:incoming>FromGroupVoteToGatewayGroupVote</bpmn:incoming>
  <bpmn:outgoing>FromGatewayUserVoteToApproveRevision</bpmn:outgoing>
  <bpmn:outgoing>FromGatewayUserVoteToSendMail</bpmn:outgoing>
</bpmn:exclusiveGateway>
<bpmn:sequenceFlow
    name="yes"
    id="FromGatewayGroupVoteToApproveRevision"
    sourceRef="GatewayGroupVote" 
    targetRef="ApproveRevision"
/>
<bpmn:sequenceFlow
    name="no"
    id="FromGatewayGroupVoteToSendMail"
    sourceRef="GatewayGroupVote"
    targetRef="SendMail"
/>

Properties

Name of property Source Description Type
due_date UIActivity Due date for task completion date/timestamp
assigned_group - Name of the user group that should vote; can be plain grouname as used in the DB (e.g. "sysop") string
instructions - Text that is shown to the group of user, so they know what to vote about string
users_voted - Not to be set in the workflow definition. Used to store data during the activities life cycle. E.g.
[
    { "userName": "UserA", "vote": "yes", "comment": "Good" },
    { "userName": "UserB", "vote": "no",  "comment": "Not good" }
]
Can be accessed by follow up activitites by e.g.

{{<GroupVoteActivityID>.0.userName}}

string




To submit feedback about this documentation, visit our community forum.

No categories assignedEdit

Discussions