Filter
Top Products
If there is some front end program that uses FlowMark API calls to create and
start process instances, have it divide the work in a round robin way: one for
team A, then team B, then team C, then back to A. You can use the system
fields in the data container to limit the “range” by department, or have separate
roles whose members have the same job. For instance, instead of a role
“Clerk” for billing, you may have roles CLERKA, CLERKB, and CLERKC.
Again, you can use the data container (or use a separate but “the same”
process template).
7.1 Performance and Capacity Considerations
For every user who is assigned an activity, there is a commitment of work efforts
for FlowMark, including the actual assignment, updating the database, notifying the
user of the activity and when it changes state, and database space to maintain the
extra data. Each of these work efforts is small. However, when multiplied by many
users for many activities in many instances, the impact is significant. Weigh that
against the benefit you expect from assigning an activity to multiple users. Finally,
consider that only one user will really process the work item. Each person
assigned beyond that one adds overhead to the operation of your system.
14 FlowMark V2.3 Design Guidelines