Scribd
Upload
33 views9 pages

BPM11gFoundation-03-2-Organization & Roles

This document provides an overview of Oracle BPM Suite 11g project organization and roles. It describes how organizational units, roles, participants, and calendar/holiday rules can be defined and organized within a BPM Studio project to model department hierarchies, responsibilities, and time constraints. These project-level definitions are not deployed but rather used to test processes internally before deployment, at which point mappings are made to backend LDAP groups and users. Screenshots illustrate examples of organizational units, roles, and rule mappings.

Uploaded by

Zakia Sadou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
33 views9 pages

BPM11gFoundation-03-2-Organization & Roles

This document provides an overview of Oracle BPM Suite 11g project organization and roles. It describes how organizational units, roles, participants, and calendar/holiday rules can be defined and organized within a BPM Studio project to model department hierarchies, responsibilities, and time constraints. These project-level definitions are not deployed but rather used to test processes internally before deployment, at which point mappings are made to backend LDAP groups and users. Screenshots illustrate examples of organizational units, roles, and rule mappings.

Uploaded by

Zakia Sadou
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

<Insert Picture Here>

Oracle BPM Suite 11g Training


Organization & Roles
Oracle BPM Training

• Objectives
• Oracle BPM Studio Project Organization
• Organizational Units
• Roles
• Mapping Roles & Organization Units to LDAP
• Holiday and Calendar Rules
Oracle Studio Project Organization
• Each Project in addition to having a Processes folder also has an
Organization folder. This node is used to define the:
• Organizational Units to create department hierarchies and help segregate process
deployment
• Roles (Abstract) to be used in the process
• Participants to sand box test the process
• Holiday and Calendar Rules to embed declarative time sensitive constraints
• The Project Organization created in Oracle BPM Studio IS NOT
copied and moved over when a project is deployed to the BPM run-
time environment. It is used to sandbox test the project in the Oracle
BPM Studio runtime environment

The following screenshot shows the


different type of assets that can be created
in the Project Organization node
Organizational Units
• Each Project can define different
Organizational Units
• Organizational Units are useful
when the project contains several
processes and these may spawn
multiple departments within an
Organization
• Organizational Units can be
defined in hierarchies to mimic
hierarchies in the Enterprise.
• Organizational Units in BPM
Project are abstract and can be
mapped to 1 or more LDAP The following screenshot shows a
hierarchical organizational unit Logistics
Groups. with sub organizational unit and 3 other
organizational units for different
departments in the organization
Roles
• Roles are created to create areas of responsibilities for human
persons in an Organization.
• Each Project if using human centric activities will need to create an
Role and use it in the modeled processes. There is no limit as to the
amount of roles that can be created, but the general practice is to
think about responsibilities in the Organization where the process is
deployed

The following screenshot shows a set of abstract roles to be used in the business processes
Mapping BPM Roles to LDAP Users

Roles are abstract and help


define and mimic
responsibilities of an
individual in the Enterprise.
They need to be mapped to
Participants.

The following screenshot shows mapping between BPM Roles & LDAP Users.
Holiday and Calendar Rules
• Each Project can have multiple Holiday and
Calendar Rules
• Holiday Rules are used to define non
working days
• Calendar Rules are used to define Working
Hours for individuals in an Organization
• Calendar Rules can be assigned Holiday
Rules Calendar Rule with working hours and
timezone associated to it.
• Calendar Rules can be assigned to
Organizational Units to drive time constraints
to all the processes deployed to it
• Calendar Rules can be assigned to roles to
drive time constraints for given roles in the
process (more granular than assigning to Org
Units)
Day 1

• Lab 1

You might also like