A BPM lane has a descriptive name that should indicate who is responsible for the flow contained in the lane. To push work to specific roles, you have to map this lane name to an actual role in the application. You do this in the Configure tab in the Properties tab in the Performers section by simply opening the element properties and selecting the desired role.
The other properties you can configure here come from the user tasks. They are:
- Assignment Option: This determines how the activity is assigned. Options are:
- By Load: This means the application checks everyone who's eligible for the activity and assigns each individual activity to whoever has the least work.
- Everyone: This means anyone can go into the pool and pull the activity.
- Sequential: This means the application assigns each individual activity, in order, to whoever is next on the list of eligible users.
- Follow Assignment: This determines whether a rejected activity routes back to the specific user who submitted the rejected data.
- Conditions: These determine who is eligible to receive the activity given the Assignment Option parameter. You can enter any number of properties that come from the user table in the framework: role, skill, location, etc. Each row acts as an OR condition and each column within the row acts as an AND condition. For example: you have a row with a role of Demographic Processor and a position of Senior; and you also have a row with a role of Address Processor and an authority level of Full. In such a case, a Demographic process with a position of Senior OR an Address Processor with an authority level of Full can receive the activity.
This post is part of the BPM topic. Click here to open the BPM Overview.