Tile Bindings

The binding section describes the business objects that feed data to the tile’s UI. You must provide the binding definitions at the beginning of the layout XML.

To define a binding in the layout XML, use:

<Binding bindingId="LeaveRequests">
      <P pid= "boType" value="LeaveRequestCollection" />
      <!— Add further binding parameters here -->
 </Binding>

The binding definition has a unique ID. Each binding can have several parameters, which are documented in the XSD schema. Some of the most frequently used parameters include:

boType – represents the type of business objects, or a collection name (OData).
sourceBo – is a business object for which related data is queried.
relationId – identifies the related collection or entry.
orderby – orders returned entries by the specified criteria.
top – limits the number of entries to be returned simultaneously.
skip – indicates the number of items to be skipped before a fetch; used for paging.
filter – represents an OData filtering string.

For additional parameters, see the extensive documentation in the XSD file. This tile definition contains a reference to the binding previously defined:

<Tile tileId="LeaveRequestList">
     <P pid=”title” value= "{$_i18n.leaverequestlist}"/>
     <BindingRef ref="LeaveRequests" />
<!— further details skipped for brevity -->
</Tile>

By default, bindings are resolved at runtime by the framework, but you can add custom control logic to manage the model for specific tiles.