Business Anchor Mapping 

Use

At design time, you create business anchors for each interaction component. Business anchor mapping establishes a data flow between two interaction components in a parent-child relationship in the user interface framework. Only one business anchor is created for a business component. All other business anchors created for tiles and tile sets refer to this business anchor through business anchor mapping.

Prerequisites

You have created the business anchor hierarchy for an interaction component.

Features

This function maps the business anchor of one interaction component to the business anchor of other interaction components. It is always defined with the lower level interaction components. In this way, you create dependencies between interaction components.

Activities

Mapping is performed from the child to the parent. This creates a business anchor in the parent to associate it with the child business anchor and establishes a data flow from child to parent for the associated data source. Mobile Application Studio creates the mapping between business anchors of various interaction components when you create the business anchor hierarchy.

We recommend you to use the drag and drop method to create business anchor hierarchy, so that the Mobile Application Studio can take care of mapping the business anchors.

If the parent already has a business anchor associated with the data source of the child anchor, you can map another business anchor manually.

·        You can map the child’s anchor to the existing anchor in the parent.

Doing this adds the child to an existing data flow and creates or extends a data pool.

·        You can map the child’s anchor to the parent independent of the existing anchor, creating a second business anchor in the parent associated with the same data source.

Doing this creates a second data flow and establishes a second data collection which is maintained in the runtime application. The result is that the two child interaction components are independent of each other, such that a context selected in one interaction component is not reflected in the other interaction component.