Mapping Resources

Mapping resources is an administrative task that will typically be performed before users start using BPM applications.

Mapping resources can then be performed on an ongoing basis as resources are added or removed from the system, or if the organization model is revised (new positions, groups, and so on).

Mapping resources involves assigning resources to specific groups and/or positions in an organization model, which results in the resources receiving work items that are sent to the groups/positions to which the resources have been mapped.

Resources can be mapped to groups and/or positions:

  • A group represents a job type within the organization. It allows resources to be grouped by their job characteristics.

    Groups are hierarchical, that is, you can have parent groups with sub groups. Typically, sub-groups are specializations of the parent group. For example:

  • If a group has sub-groups, you can assign resources to either the parent group or the sub-group. Resources that belong to sub-groups receive work items that are offered to their parent groups, as well as to the sub-group to which they belong. Using the example above, resources in the WorkItemManagement and ResourceManagement groups will also receive work items offered to the GlobalWorkManagement group.

    For information about the inheritance of privileges and capabilities assigned to groups, see Privileges and Capabilities.

  • A position represents a set of responsibilities for a job within an organization unit. It allows resources to be grouped by job responsibility.

    Positions are subordinate to an organization unit in the organization model. An organization unit can have many positions. Positions cannot be nested, although organization units can. In the following example, ReardenManagement and ReardenSales are organization units under the ReardenSteel organization. Each of the organization units have three positions.

    Resources can be mapped to positions, but not organizations or organization units.

    Resources that belong to a position receive work items offered to the position, as well as work items offered to the organization unit that is the immediate parent of the position.

    For information about the inheritance of privileges and capabilities assigned to positions, see Privileges and Capabilities.

Procedure

  1. Select the LDAP container that contains the candidate resources you want to map.
  2. In the right pane, click either ORGANIZATIONS or GROUPS, depending on whether you want to map resources to a position or group.
  3. Expand the organization or group structure to expose the position or group to which you want to map a resource.
  4. Map resources to the position or map in one of the following ways:
    • Drag a resource into the desired position or group.
    • Select one or more resources by clicking the box to the left of the resource, then click Add Selected in the position or group.
    • Select one or more resources by clicking the box to the left of the resource, then choose any of the selections from the Actions menu in the upper-right part of the screen:
      • May to all positions and groups
      • Map to all positions
      • Remove from all positions and groups
      • Remove from all positions
    If one or more of the resources had not yet been added to the system, or mapped to a position or group, the Add and map resources dialog is displayed.
  5. If the Add and map resources dialog is displayed, optionally change the resource's resource name or label, then click Add and map resources.
    If the group or position to which you are mapping the resource has capabilities defined, and the resource does not have those capabilities, a message is displayed indicating that. This is only informational; capabilities are not enforced.
    For information about resource names and labels, see Renaming a Resource.

Result

If you had dragged the resource into a position or group, the resource is now shown as a "member" of the position or group: