Oracle BPM Activities.

BPM studio can contains  total of 47 objects, swimlanes  and user/roles. The responsibility for each of the user/roles are defined in each of the swimlanes. The roles defined are logical and has to be mapped to LDAP  while development and implementation BPM Studio also enables you to create more robust organizational models using organizational units, calendars, and holidays.

Each of the activity has been explained in detail


Reference : Oracle® Fusion Middleware Modeling and Implementation Guide for Oracle 
                       Business Process Management 



  Activity 

The generic activity is used as a place holder within a business process and 

 generally used to designate a part of the process that needs to be added later. 

Name 
Enter a name or accept the default. This becomes the name of the flow object within your process.

Description 
Enter an optional description of this task. Adding a description can make your process more readable.

The below is available only in project templates

Permissions
Sets the edit policy for this flow object. This option is only available in project templates.

Project templates also allow you to define edit policies for processes and flow objects within a process. Edit policies determine what parts of a process can be changed or edited when creating a new project based on a project template. Edit policies are defined for the entire process. However, you can also define edit policies for individual flow objects. More

Select from the following values:

Sealed: The flow object cannot be modified. Can Modify Implementation: The user may redefine this component if necessary. Must implement: The user is required to implement this component for it to function correctly. Use process permission: Uses the default edit policy defined by the process.

Sampling Point 

Expand to configure sampling points for this flow object. Sampling points allow you to generate information about the performance of a flow object in a running process. The data generated according to this configuration is stored in the Process Analytics Database. You can configure sampling point generation at the following levels:

Project: Defined in the project preferences
Process: Defined in the process preferences
Flow Object: Defined in the properties of each flow object.

Sampling point generation specified at the project level is applied to all of the processes within the project. However, you can override project-level settings within a process. Likewise, sampling point generation specified at the process level is applied to all of the flow objects within the process. You can also override process-level settings within each flow object. By default, the project sampling configuration is set to generate sampling points only for interactive activities.  Overriding sampling point generation at the project or process level is usually done to improve performance. For example, if your project contains a process that contains a great number of activities and you are not interested in obtaining process metrics for this process, you might choose to set its sampling point configuration so that the process does not generate sampling points. Likewise, if you are interested in measuring only one process within your project, you might choose to set the project not to generate sampling points and configure that particular process to generate sampling points. By default, the process is set to use the project sampling point configuration. You can also configure one or more of the activities in your process to use a sampling point setting different from the one used in your process. For example, you might choose to set all the gateway activities in your process to not generate sampling points because you consider these metrics do not provide relevant information.

Inherit Process Default

Select to use the default sampling configuration defined at the process level.

Generate 

Select to generate sampling point data for this activity. This will override the default configuration defined at the process or project level.

Do not generate 

Select to not generate sampling point data. This is primarily used for performance reasons.

The activity can be configured as below

1. Default activity
2. User task
3. Service task
4. Send task
5. Recieve task
6. Business rule task
7. Script task
8. Manual task
9. Call activity
10. Notification task.
11. Update task.