Mapping Resources

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

There is a default out-of-the-box user defined that can log in before other users are set up — for information, see Authentication.

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, etc.).

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 can be hierarchical, i.e., you can have parent groups with sub groups. For example, you can have a CustomerServiceRepresentative group with subgroups of MotorInsuranceSpecialist, TravelInsuranceSpecialist, and HomeInsuranceSpecialist. Typically, sub-groups are specializations of the parent group. Groups can be nested several layers deep.

    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 MotorInsuranceSpecialist group will also receive work items offered to the CustomerServiceRepresentative 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. For example, you can have a TravelInsurance organization unit with positions of OfficeManagerTravel and TravelInsuranceCSR. Positions cannot be nested, although organization units can.

    Resources can be mapped to positions, but not 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.

The Organization Browser allows you to map the desired resources to the groups and/or positions that have been defined in your organization model. You can use one of two methods:

  • Using the “drag and drop” method - This method works fine if you have only a few mappings to do — for information, see Mapping Resources From the Resource List.
  • Using the Resource Editor - This method is better suited to bulk editing. It allows you to also edit resource information (capabilities, push destinations, etc.), as well as mapping resources — for information, see Viewing Editing Resource Information.