Table of Contents


  1. Preface
  2. Understanding Data Types and Field Properties
  3. Designing Processes
  4. Using and Displaying Data
  5. Designing Guides
  6. Designing Process Objects
  7. Designing Service Connectors
  8. Using Connectors
  9. System Services, Listeners and Connectors

2. Design

2. Design

Service Step

Service Step

When you add a Service step, you set some properties.
The following sections describes the Service step properties:


Step Type
The Service step.
A descriptive name for the service.


Service Type
The connection, process, or system service you add to the process. Select from a list of existing tasks.
You must have an existing item to add to a process. You cannot create a task in when you create a process.
When you add a service to a Service step, corresponding Input Fields are created.

Input Fields

Input Fields section shows the names of input fields that are most often used when using this kind of step. For Service steps that create objects, the input fields shown are the fields that are most frequently needed when the object is created. (If you do not need a field and it is optional, you can delete it.) You can choose additional (optional) input fields from the list.
Use the delete icon to remove a field. This removes input fields that you do not want to pass to the Service step. Some fields are required and cannot be deleted.

Fault Handling

Fault handling in Process Designer is based on the Business Process Model and Notation (BPMN) 2.0 specification, which defines the concept of a boundary event. The boundary events catch faults associated with specific steps, rather than the overall process scope. This means you can handle faults at the step level, not the process level. (Developers can also use Process Developer to define a fault handler on the process scope.)
Visibility of Faults in
Application Integration Console
When fault handling is enabled in a process, you can view the error marker on the step and some basic fault information in the
Application Integration Console
Processes list.

Timer Events

Use Timer Events to perform an action based on a schedule. You can specify whether you want the event to run
At specific time
After a delay
The following image shows a configured timer event:
You can view the timer set for Service 2 to run 45 minutes after Service 1.
if you want the timer to interrupt the Service step. When you set an interrupting timer, the Service Step task is interrupted and the process only runs the task on the timer set

Message Events

Specify messages for use with message providers and correlation