Implementation and Coding

Once you have appropriately set up the environment, you can start coding apps.

Extensibility Framework initialization is signaled in the completion block of the MAFCore loadWithWindow: andCompletionBlock: API. A non-nil NSError pointer passed to the completion block by the framework indicates one or more issues during initialization, which you must correct before you can continue.

The Extensibility Framework internally fetches and converts data based on the data bindings defined in the configuration.

You can develop applications that rely purely on configuration. You can develop a fully metadata-driven app by describing the UIs, data bindings, screen transitions, and actions in the layout XML.

With the Extensibility Framework, you can freely combine metadata-driven tiles and native iOS view controllers (also views and controls).

You can add a manually coded view or control to a tile.

You can retrieve a configuration-based tile using the MAFUIManager tileByIdentifier: API.

You can provision the data for the metadata-driven tile.

Similarly to adding a custom subview to a metadata-driven tile, you can embed a custom UIControl element in a tile.

You can set a delegate to intercept messages sent by the UI controls after a user interaction, for example, after tapping a button.

You can provide custom data for specific tiles, that is, you can feed the tile with custom data from a database of your choice.

To intercept UI element creation notifications, use MAFUIElementCreatorDelegate, which lets you create custom subviews or decorate the ones created by the framework.

Data is fetched, validated, and transformed into generic business objects. The extensibility layer displays the data on its views and subviews.

When customers upload a new Application Configuration Profile to the SAP Mobile Platform server, the application has to fetch the new configuration as soon as possible.