One take on a streamlined and simple voting app using javascript. Designed to be easy to implement in an existing workflow as well as being a standalone, able to transition items in the originating workflow using an action based on active/inactive.

On submit, users who are to vote are entered in a field. On the form submit they are copied to another field for use in driving the process.

In the voting state there is a vote button only if you are on the "not yet voted" list, a user field containing those left to vote.

In the vote transition, some fields are hidden until a decision is made, yes, no, or other, and on form submit the user is subtracted from the "not yet voted" field so that they cannot vote again. The vote count is also increased by one or reduced by one (or left alone in the case of "other" to count the votes.

Once a user has voted they will not see the vote button. If everyone on the list has voted then the item will move on to the next state.

Another transition is present that skips the "Last Voter?" decision so that a delayed notification can be added to transition the item once the due date is hit. This allows for everyone to vote only if done so within a timeframe. This transition does not show on any form.

As the "voters" field is left intact with all the original users invited to vote, this field can be used to send notifications on results, and drive visibility of the item through secondary ownership as desired.

A decision then routes the item to a passed the vote or rejected state based on the yes or no vote winning out. A Vote Count of more than 0 indicates a yes vote.

Current counts are hidden as they may affect an individual's vote if shown. To show these simply change the hide fields to "make read only" and the show fields to "make not read only".

For statistical purposes a count of yes, no, and "other" are kept. The "other" option can be removed from the "vote" single selection field without any changes needed to the form actions or javascript. The "other" option is for options such as "declined to vote" or "no opinion" and can be renamed accordingly.

The outcome decision can be removed to simply view the item rather than branching based on the vote.

User role set to both voters fields as starting point.

Very simple graphs were added to the closed states for analysis of the vote. These use javascript, the jquery plugin, and html5 features and so may not function with older browsers. Mainly a quick demo of how simple custom functionality can be added with a few minutes of coding.

Process app type: Design Example

Required SBM Version: Other

Complexity: Advanced

SBM 10.1.4