Page History

Requirements:
# The mobile solution needneeds to have the mobile solution type
# If the data shown in mobile app is user specific the mustAuthenticate property has to be enabled
# The mobile plugin has to be installed

Once the solution type is set to mobile the:
# solution explorer view will filter to show only the capabilites possible in mobile. (API wise)
# form designer/palette will change to place mobile interface elements only utilizing a different layout manager.
# each form shown in the mobile client without passing a (related) foundset (like first form) will need a offlineDataDescription.addFoundSet call in the mobile service solution

Limitations:
# dataproviders are not accessable without a scope, which means first a record object needs to be retreived before the dataproviders from such a record can be accessed.
example:
{code}
var rec = foundset.getSelectedRecord();
if (rec.phone_direct) plugins.mobile.call(rec.phone_direct);
{code}
# new records pks always become UUID's values, while UUID are not required for pks for any data delivered by the server, the service solution would need to translate UUID's to local ids upon retrieval of new records.
# only single pk are supported on entities. (no compound pk support)
# no SQL support, everything has to happen via relations/foundset navigation from the provided root foundset by the service solution.
# no calculation support. (yet, is planned)
# only custom valuelists are supported, but application.setValueListItems is present

Within these limitations at form design and API level all business logic should work.

Supported plugins:
# Mobile plugin (especially designed for using mobile device capabilities, like GPS and making calls)
# Dialog plugin .showWarningDialog function

h5. Other pages

{list-siblings}
{children} 

\\