Role resolution narrows down the
list of possible agents for a work item.
Before you begin to define roles,
you have to start the workflow process:
- Decide what you want to do with the workflow and break it down
into the smallest useful units of work. These will become your
- Select the objects you need, by either creating a business
object or using one of the existing ones. You should find a useful
object in the Business Object Repository.
- Each task calls a method of an object. Ensure that the methods
you need already exist.
- Create the tasks or use existing ones. Define the possible
agents of the task in the task definition.
- Group tasks together in the workflow.
- Assign agents to the work items in the workflow definition.
These must be a subset of the possible agents of the task. If not,
then the work item will not be executed.
This you can do manually, as a one-on-one assignment, or you can
use role resolution.
If you choose to use role resolution
to narrow down the list of possible agents for a work item in a
workflow, you must:
- Select the standard role transaction.
- Decide how you wish to determine the agent, that is, via
function modules, organization data or responsibilities.
- Create a container definition (you do not need to do this for
- Workflow will automatically propose a binding where you confirm
that the fields in the role container match the fields in the
- Run the workflow.
At runtime, role resolution returns a table with the set of
possible agents. This set of agents is determined at runtime via
the values assigned to the elements of the role container.
The work item then appears in the
integrated inbox of the selected agents. For the standard role
transaction we are concerned with steps 1 to 3 of the role