This topic applies only to the IBM Business Automation Workflow Advanced configuration.

Support for null business objects

Edit online
Draft comment:
This topic only applies to BAW, and is located in the BAW repository. Last updated on 2025-03-13 12:15
This scenario involves an outside system communicating with IBM® Business Automation Workflow through XML wrapped inside of a SOAP message. When the enclosed element is nillible and has xsi:nil="true", then the resulting DataObject which is created in IBM Business Automation Workflow is null.

Here is an example which illustrates an XML message with a nillible element.

<?xml version="1.0"?>
<soap:Envelope xmlns:soap="http://www.w3.org/2001/12/soap-envelope">
	<soap:Body>
		<p:Employee xmlns:p="http://www.mycompany.com" xmlns:xsi="http://www.w3.org" 
			xsi:nil="true"/>
	</soap:Body>
</soap:Envelope>
Where Employee is defined as:
<element name="Employee" nillable="true">
...
</element>
The business object that is generated and sent from the export is null in this case. For example, if any downstream components have operations invoked on them, the input to that operation is null.
Note: These objects cannot be passed into business object maps because business object maps are unable to map fields from a null object.