The following sections describes the Service step properties:

Property	Description
Step Type	The Service step.
Name	A descriptive name for the service. The name can contain only alphanumeric characters, underscores (_), spaces, and Unicode characters.

Property

Description

Service Type

The connection, process, or system service options that you add to the process. When you select the Process or the Connection option as the service type, a Select button appears. Click Select to browse and select from a list of processes or connections. When you select the System Service option for the service type, you can select an action from a list of system service actions. You must have an existing item to add to a process. You cannot create a task when you create a process.

For more information about the list of supported actions for system service, see System Service Actions.

When you add a service to a Service step, corresponding Input Fields are created.

The

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 input fields from the list.

Based on the service type configured in the

Service

step, you can also map the fields automatically with the fields configured in the input fields or temporary fields. You can also map the complex process objects configured in the process.

To map the fields automatically, on the

Input Fields

tab, click

AutoMap

.

You must ensure that you have meaningful field names to find the most accurate field matches. If the field name that you want to match contains some random text, Application Integration does not recognize the field name and the mapping field remains empty.

Application Integration matches the best possible fields based on the field name and data type that are configured in the process. Informatica does not guarantee exact field matches. After the fields are mapped, you must manually verify if the mappings are correct and update as needed.

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

Use Timer Events to perform an action based on a schedule. You can specify whether you want the event to run

At specific time

or

After a delay

.

The following image shows a configured timer event:

Select

Interrupting

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

Specify messages for use with message providers and correlation. You can add multiple instances of the same message event to the Service step.