Previous | Next | Contents | Index | Glossary | Library |
In general, an activity can either send a notification message or perform a PL/SQL function. The special Voting activity, classified as a notification activity, does both by first sending a notification message to a group of users and then performing a PL/SQL function to tally the users' responses (votes).
The following four fields in the Activity properties page of the Voting activity determine how the Voting activity behaves:
You can edit the Default Voting Message or use your own custom message as long as you associate a Respond message attribute called RESULT with the message. Similarly, you can customize or use a different lookup type associated with RESULT to offer other possible responses to the recipient.
Attention: The Expand Roles Check Box should also be checked when sending FYI Notifications.
WF_STANDARD.VOTEFORRESULTTYPE is a generic tallying function. The Result Type that you specify for the activity defines the possible responses for the function to tally and the activity attributes you define determine how the function tallies the responses.
The value of the activity attribute can either be blank or a number that represents the percentage of votes required for a particular result. If you provide a percentage, then the result is matched if the actual tallied percentage for that response is greater than your specified percentage. If you leave an activity attribute value blank, then the Workflow Engine treats the response for that activity attribute as a default. In other words, if no particular percentage is satisfied after the votes are tallied, then the response that received the highest number of votes among those associated with a blank activity attribute becomes the result.
Note: If the tallied votes do not satisfy any response percentages and there are no default responses (blank activity attributes) specified, the result is #NOMATCH. If a <Default> transition from the Voting activity exists, then the Workflow Engine will take this transition, otherwise, it will raise an error that no transition for the result is available (ERROR:#NOTRANSITION).
Note: If the tallied votes satisfy more than one response percentage or if no response percentage is satisfied, but a tie occurs among the default responses, the result is #TIE. If a <Default> transition from the Voting activity exists, then the Workflow Engine will take this transition, otherwise, it will raise an error that no transition for the result is available (ERROR:#NOTRANSITION).
Note: If you have something specific in mind that you would like to happen if a tie or no match occurs in a Voting activity, you can model that into a custom activity and create a <Default> transition from the Voting activity to that custom activity.
In addition to defining your set of custom activity attributes, you must also set an activity attribute called Voting Option, whose internal name must be VOTING_OPTION, to specify how the votes are tallied. You can set Voting Option to one of three values:
Response | Custom Response Activity Attribute Value |
---|---|
A | 50 |
B | 50 |
C | 50 |
Table 1 - 6. (Page 1 of 1) |
Response | Custom Response Activity Attribute Value |
---|---|
A | 50 |
B | 50 |
C | blank |
Table 1 - 7. (Page 1 of 1) |
Response | Custom Response Activity Attribute Value |
---|---|
A | 50 |
B | blank |
C | blank |
Table 1 - 8. (Page 1 of 1) |
Response | Custom Response Activity Attribute Value |
---|---|
A | blank |
B | blank |
C | blank |
Table 1 - 9. (Page 1 of 1) |
Response | Custom Response Activity Attribute Value |
---|---|
YES | 100 |
NO | blank |
Table 1 - 10. (Page 1 of 1) |
Response | Custom Response Activity Attribute Value |
---|---|
GUILTY | 100 |
NOT_GUILTY | 100 |
Table 1 - 11. (Page 1 of 1) |
Previous | Next | Contents | Index | Glossary | Library |