Service Task Properties Dialog - Basic Page

Oracle BPM Editorthen chooseComponent Palettethen chooseService Taskthen choosedialog for the Service Task

Use to edit the basic properties of the service task.

The service task enables you to communicate with other processes and services. Process analysts can add the service task when they know that a process needs to invoke an external service or process.

Process developers can then implement the necessary services. You can use the service task to invoke the following:

The service task has similar behavior to the send and receive task pair and the message throw and catch event pair. The primary difference is that the send task is used to invoke processes and service synchronously. This means that when the service task invokes a process or service, the token waits at the service task until a response is returned. After the response is received, the token continues to the next sequence flow in the process.

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.

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:

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:

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. More

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.


Modeling and Implementation Guide, "Introduction to the Service Task"