Understanding Mobile Application Platform Classes
Implement your own custom application classes to initialize, add business logic, and dynamically change layouts for your Mobile Application Platform (MAP) applications.
The Mobile Application Platform framework completely separates the business logic from the presentation layer. All Mobile Application Platform metadata is available in your application class PeopleCode and is not tied to application pages or other metadata, allowing you to override the defaults defined on the actual layout. This means that you have complete control of the presentation layer for any transaction within the application class PeopleCode.
To manipulate pages, elements, and other aspects of your applications through PeopleCode, import the PS_PT:Integration:IDocLayoutHandler interface class and implement its two abstract methods. See Examples: Mobile Application Platform PeopleCode for an example.
Three built-in classes are delivered for the Mobile Application Platform framework. Additional operations can be performed by importing and using selected methods from the PT_MAP_ADMIN:MapFluid application class:
Field or Control
A Map object represents the MAP application (or layout); it is the highest level object in a MAP application. From the Map object, you can get the Document object (which defines the data structure for the MAP application), the URI document object, MapPage objects, and MapElement objects.
Each page in a MAP application is represented as a MapPage object which can be retrieved from a Map object.
Each element on a page is represented as a MapElement object. A MapElement object can be retrieved from a Map object or from MapPage object.
Import and use selected methods from the PT_MAP_ADMIN:MapFluid application class to perform certain operations on the fluid page header.
In addition, the IntBroker class includes several methods to support the Mobile Application Platform framework.