Outbound object structure processing performs the serialization
of business object (mbo) data into an XML message. During this processing,
an automation script can insert custom processing logic to change
the default processing behavior of the object structure. The script
can be used instead of the Java™ definition
class or can be used with it.
Functions, such as skipMbo(ctx), are used in serialization. In the function name, ctx is the object in the function that is prepared by the integration framework and communicates data between the integration framework and the automation script. An automation script can affect the processing of the data and communicate those changes back to the integration framework.
Serialization includes the following functions that can be used
by automation scripts to insert customized logic into the processing
of the data:
- skipMbo(ctx)
- Filters object data from the XML message. APIs are available to filter data from the XML message, continue processing for data that you want in the XML message, and complete processing of the object structure after data is filtered out. For example, if the object structure is constructing an XML message for a purchase order, an automation script can insert logic that filters out purchase order line data where the line type is for service lines.
- skipCols(ctx)
- Filters a column or multiple columns from the object structure. For example, if the object structure is constructing an XML message for an asset, an automation script can insert logic that filters out a number of columns that are not needed by the system that will receive the XML message.
- overrideValues(ctx)
- Sets the value of an object structure field in the XML message. For example, if the object structure is constructing an XML message for an asset, an automation script CAN insert logic that might filter out a number of columns that are not needed by the system that will receive the XML message that is created.