/mobileapps/config/index.htmlAperio Mobile App definition consists of the following elements: app.json - configuration of the general app properties menu.json - menu structure (optional) livesearch.json - definition of livesearch capable fields (optional) /mods - container for app modules /locales - folder with localizations /cfg/table.json - form table settings Here is en example of app: mwhs_dc1-11. Mobile Warehouse appHugoen-usMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/appjson/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/appjson/index.htmlThe app file contains a set of properties that defines the mobile app. Here is the list of available properties. Property Description Example title The main title of the app. It will be displayed e.g. on the sign-in form. “Mobile Warehouse” subtitle The second title of the app. It will be shown as smaller text below the title. “DC1” link The URL path to the app relative to the web server context where the app is published. Example: server.company.com:8090/myapp “/myapp” modules A list of modules with forms for the app. The order of the list determines the search order for the forms. See more in Modules section. [“custom”,“base”] menu The root menu id. This is an optional property. When specified, the app menu will be provided by the API method: applicationMenu.get. This way, the menu structure may be backend-system driven. If the property is not specified, the client will load the menu from the app’s menu.json file. “MWHS” version The version of the app. It will be displaed e.g. on the sign-in form “1.0.0.2” browserReload When set to false the browser’s page reload function will be disabled (F5). This option may be helpful in some situations when accidental reloads occur often on some devices. Optional, default is true - reload enabled. false onSessionClose API method name that will be run when signing off from the app. May be useful for e.g. automatic release of resources. Optional. “resourceRF.release” css Custom client theme. Currently creating own style sheets is not supported yet. “mytheme.css” Example of Mobile Warehouse app file/mobileapps/config/menujson/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/menujson/index.htmlThe menu file provides the menu content for your app (if not API driven - see menu property of app.json file). The top level element is an array with menu items. An item may represent a form to launch or a sub menu. Example of menu item to launch form myForm: { "title": "Form 1", "form": "myForm" } title is the label of the item form is the destination form to open when item is selected To make an item a submenu, specify items property that will have an array of nested items. You may define multiple nested levels of submenus./mobileapps/config/livesearch/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/livesearch/index.htmlWhen the Live Search configuration file (livesearch.json) exists in the app folder its configuration will be applied to the current app. To apply Live Search on the client level see Client configuration !!! FIX ME LINK !!!). To apply on the form field level directly, see Form development !!! FIX ME LINK !!!). The structure The top level element is an object which contains settings and fields properties./mobileapps/config/modules/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/modules/index.htmlAperio App forms are arranged into modules. A Module is a folder that contains Aperio Client HTML forms. Module folders are placed in /mods app subdirectory. Apps can use one or more modules. It is the app configuration file (modules property) that controls which modules and in what order are used by the app. Various module folders allow to arrange forms according to e.g. modification levels: base, country, customer etc. If the same form exists in more than one module, the one that is found first - according to the module list - will be loaded./mobileapps/config/localizations/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/localizations/index.htmlLocalizations allow to run mobile apps in different languages. The application language is picked by default from your browser settings. If your browser language is English, you will get the app in English. You will get English locale (date format, numbers format) also. If you want to change the application language you can: change the language in the browser settings run the app with lng URL query parameter - look Overview for more details If you do not have the translation made for given language or it is not complete then the whole app or some literals appear in base language (usually English)./mobileapps/config/table/index.htmlMon, 13 Jul 2020 17:13:07 +0200/mobileapps/config/table/index.htmlThe form table settings allow to configure the behaviour of form tables, mostly pagination. Configuration file location The base settings are configrued on Aperio Client level in the file: /XT/bin/AperioClient/cfg/table.json The settings may be overridden on the app level: /mobile-app/cfg/table.json Properties The following properties may be configured: