Input mappings for list structure parameters may now also be specified. In this instance, the metadata is similar to that described above for aggregate formal parameters (see Input mappings for aggregated struct parameters). The type of the struct specified in the metadata for a list struct parameter is the name of the list structure. The name of the first field specifies the name of the role contained in the association between the specified list struct and the child struct it aggregates. Typically, this field then resolves down to another struct (the child struct contained within the list struct). The workflow data object specified in such a mapping is a list workflow data object. The following metadata snippet provides an example of such input mappings. The metadata elements have been previously described above in the struct input mappings section.
<automatic-activity id="1" category="AC1">
...
<bpo-mapping
interface-name="curam.sample.facade.intf.SampleBenefit"
method-name="processClaimantDependents">
<formal-parameters>
<formal-parameter index="0">
<struct type="curam.sample.struct.
ClaimantDependentDetailsList">
<field name="dtls">
<struct type="curam.sample.struct.
ClaimantDependentDetails">
<field name="identifier">
<base-type type="INT64">
<wdo-attribute wdo-name="ClaimantDependent"
name="identifier"/>
</base-type>
</field>
<field name="firstName">
<base-type type="STRING">
<wdo-attribute wdo-name="ClaimantDependent"
name="firstName"/>
</base-type>
</field>
<field name="surname">
<base-type type="STRING">
<wdo-attribute wdo-name="ClaimantDependent"
name="surname"/>
</base-type>
</field>
</struct>
</field>
</struct>
</formal-parameter>
</formal-parameters>
</bpo-mapping>
</automatic-activity>