Actions that you can take on human tasks depend on your authorization role. This role can be a J2EE role or an instance-based role.
A role is a set of employees who share the same level of authority. Java™ 2 Platform, Enterprise Edition (J2EE) roles are set up when the human task container is configured. Instance-based roles are assigned to human tasks and escalations when the task is modeled. Role-based authorization requires that global security is enabled in WebSphere® Application Server.
You can use the administrative console to change the assignment of users and groups to these roles.
A task instance or an escalation instance is not assigned directly to a staff member in the task model, instead it is assigned to one of the available roles. Any staff member that is assigned to an instance-based role can perform the actions for that role. The association of users to instance-based roles is determined at runtime using staff resolution.
The following instance-based roles are supported:
These roles are authorized to perform the following actions:
Role | Authorized actions |
---|---|
Potential instance creator | Members of this role can create an instance of the task. If no potential instance creator is defined for the task template or the application components, then all users are considered to be a member of this role. |
Originator | Members of this role have administrative rights until the task starts. When the task starts, the originator has the authority of a reader and can perform some administrative actions, such as suspending and resuming tasks, and transferring work items. |
Potential starter | Members of this role can start an existing task instance. If a potential starter is not specified, the originator becomes the potential starter. For inline tasks without a potential starter, the default is everybody. |
Starter | Members of this role have the authority of a reader and can perform some administrative actions, such as transferring work items. |
Potential owner | Members of this role can claim a task. If no potential owner is defined for the task template or the application components, then all users are considered to be a member of this role. If staff resolution fails for this role, then the administrators are assigned as the potential owners. |
Owner | Work on and complete a task. |
Reader | View the properties of all of the task objects, but cannot work on them. |
Editor | Members of this role can work with the content of a task, but cannot claim or complete it |
Administrator | Members of this role can administer tasks, task templates, and escalations. |
Escalation receiver | Members of this role have the authority of a reader for the escalation and the escalated task. |
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)