Within Oracle BPM an organization defines a hierarchical structure that reflects the real-world organization of your business. An Oracle BPM organization defines the way people are grouped and defines the roles or each group and individual.
The following table lists the elements of an Oracle BPM organization.
| Element | Icon | Description |
|---|---|---|
| Organizational Units |
|
Organizational Units are used to represent departments or divisions within the organization. Organizational Units can be defined hierarchically so that, for example, you can represent divisions within an organization, departments within a division, areas within a department, and so on. You can assign Participants, Calendars, and Business Parameters to an Organizational Unit. You can also deploy processes under an organizational unit. |
| Roles |
|
Roles are used to represent functions performed by people related to the organization. Roles are assigned to participants or groups, and these assignments define the permissions the participants have when executing Oracle BPM tasks through WorkSpace. |
| Groups |
|
Groups are collections of roles. In this way, it is possible assign multiple roles to participants in a single step. Groups may also contain other groups. |
| Participants |
|
Participants are the actual people who participate in the organization, usually as end users of the BPM implementation. |
| Holidays |
|
Holidays Define the organization’s non-working days. These rules inform the Process Execution Engine that there is an exception to the normal calendar rules on certain days of the year. |
| Calendars |
|
Calendars define the organization’s work week and work schedule. Calendar rules can be assigned to organizational units. |
| Business Parameters |
|
Business Parameters are used to maintain constant values defined either for the entire organization, or at the Organizational Unit level. These parameters are visible to all instances and all processes across the Organization. Although business parameters may be changed every once in a while, they are not meant to be used as variables. Rather, they provide a way of storing long-lived values, such as a sales tax rate, without having to hard-code them into Process Business Language methods. |