Multiple Instances in Sequences and Groups

BDS supports the use of multiplicity on a sequence, choice, or group in an imported schema or WSDL.

Note: This support is only available on imported data. You cannot define multiplicity on a sequence, choice, or group in a user-defined BOM.

For example, an imported sequence might be defined in an XML schema as follows:

<xs:complexType name="PlaneOptionalElms">

<xs:sequence minOccurs="0" maxOccurs="unbounded">

<xs:element name="freightDetails" type="xs:string" minOccurs="0" maxOccurs="unbounded"/>

<xs:element name="passengers" type="xs:int" minOccurs="0" maxOccurs="unbounded"/>

</xs:sequence>

</xs:complexType>

<xs:element name="PlaneOptionalElmsElement" type="PlaneOptionalElms"/>

The support for multiplicity on imported data means that, for example, important data passed in to your process over a web service, and defined with multiplicity on a sequence or a choice, will maintain the order in the content of the original message. However, you can retrieve the data only by requesting all occurrences of a given element within the sequence or choice. This applies when data is passed to scripts, mapping screens, or forms.

Note: Note that if you use a script to populate or to add to a sequence or a choice with a multiplicity greater than one, the order in which the data is added in the script will be maintained in the order of the BOM class instance containing the data. So if you add data in a particular order, that same order will appear in the XML if the data is later passed over a web service.