Specify all of the output variables that you want this service to return to the calling program or client.

Make sure the names of output variables match the names used by the services that produce them. Like input variables, if you do not specify names that match the ones produced by the flow’s constituent services, you must use the Pipeline view to manually link them to one another.

Avoid using multiple outputs that have the same name. Although Designer permits you to declare multiple output parameters with the same name, the fields may not be processed correctly within the service or by services that invoke this service.

Make sure the variables match the data types of the variables they represent in the service. For example, if a service produces a String called AuthorizationCode, make sure you define that variable as a String. Or, if a service produces a Long object called EmployeeID, define that output variable as an Object and apply the java.lang.Long object constraint to it. For a complete description of the data types supported by a service, see Data Types

Declared output variables appear automatically as outputs in the pipeline.When you select the last service or MAP step in a flow, the declared output variables appear under Pipeline Out.

Object and Object list variables must be a serializable data type. If it cannot be serialized, the pipeline cannot be exchanged with a remote Integration Server. Further, the class names for the data type must be included in the Integration Server whitelist classes file or a package whitelist classes file for the pipeline to be deserialized at the destination Integration Server. Classes defined by Integration Server are already included in the whitelist class file. This requirement applies to all Object and Object list variables, including those contained in a Document or Document list.