# Collection-handler Handler

<span class="notranslate">This handler is applicable when the persistence of this object is managed by the parent dataNode. The allowed attributes are:</span>

<div id="bkmrk-attribute-usage-coll"><table class="confluenceTable tablesorter tablesorter-default stickyTableHeaders" role="grid"><thead class="tableFloatingHeaderOriginal"><tr class="tablesorter-headerRow" role="row"><th aria-disabled="false" aria-label="Attribute: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="0" role="columnheader" scope="col" tabindex="0"><div><div>**Attribute**</div></div></th><th aria-disabled="false" aria-label="Usage: No sort applied, activate to apply an ascending sort" aria-sort="none" class="confluenceTh tablesorter-header sortableHeader tablesorter-headerUnSorted" data-column="1" role="columnheader" scope="col" tabindex="0"><div><div>**Usage**</div></div></th></tr></thead><tbody aria-live="polite" aria-relevant="all"><tr role="row"><td class="confluenceTd">collection

</td><td class="confluenceTd">EL expression that identifies the collection onto which the business object must be added or removed

</td></tr><tr role="row"><td class="confluenceTd">if

</td><td class="confluenceTd">EL expression that must be evaluated to true prior to handler action

</td></tr><tr role="row"><td class="confluenceTd">unless

</td><td class="confluenceTd">EL expression that must be evaluated to false prior to handler action</td></tr></tbody></table>

</div><span class="notranslate">The following example shows how you could manage objects City as a collection of objects within the object Country, which in turn is saved on a disk arhivo:</span>

```
<datanode name="city">
    <collection-handler collection="${parent.instance.cities}">
</datanode>
```