Difference between revisions of "Mobile Forms (proof of concept)"
(→Configuration) |
|||
| Line 17: | Line 17: | ||
Mobile GUI can be enabled automatically (browser detection), but it can be also forced manually. | Mobile GUI can be enabled automatically (browser detection), but it can be also forced manually. | ||
| − | To enable automatic browser detection set parameter MobileFormsAutodetection="true" (parameter defined in agility config.xml in application section). When parameter MobileFormsAutodetection is enabled then request from mobile device to agility will be automatically redirected to mobile version. It is also possible to run mobile version of agility regardless of device, configuration or browser. Instead standard url use <pre>http://agilityurl/mLogin.aspx</pre> | + | To enable automatic browser detection set parameter MobileFormsAutodetection="true" (parameter defined in agility config.xml in application section). When parameter MobileFormsAutodetection is enabled then request from mobile device to agility will be automatically redirected to mobile version. It is also possible to run mobile version of agility regardless of device, configuration or browser. Instead standard url use: |
| + | <pre>http://agilityurl/mLogin.aspx</pre> | ||
| + | When '''m'''Login.aspx is used then all subsequent requests from that session will be treated as requests from mobile device. | ||
[diagram] | [diagram] | ||
Revision as of 15:54, 22 February 2017
Described below functionality is not production ready. It is proof of concept which use current FastNET rendering engine to enable Mobile Friendly User Interface. JQuery Mobile framework is used to ensure native mobile look on any modern mobile device (Android, iPhone, iPad, Windows Phone).
Potential Use Cases
Although Mobile Forms functionality is not production ready it is available in 7.2+ systems. It is disabled by default and do not affect standard UI. There are two potential use cases for Mobile Forms:
- Online Forms for Agility For Android. Sometimes it is required to enable additional forms on Agility For Android which are handled directly by agility service (instead offline form embedded on android). There are many reasons why such online forms are good solution, one of them is ability to use lookups on data which is not cached by android (for example asset registry). It seems that Mobile Forms fits perfectly into such pattern.
- Online Work Management tool (similar to the original "Alite" application). Attempt to describe functionality of such application as wall as quotation is provided in Issue 6446. Please refer Issue 6446 for details.
None of above cases is available without additional development.
Configuration
Mobile GUI can be enabled automatically (browser detection), but it can be also forced manually. To enable automatic browser detection set parameter MobileFormsAutodetection="true" (parameter defined in agility config.xml in application section). When parameter MobileFormsAutodetection is enabled then request from mobile device to agility will be automatically redirected to mobile version. It is also possible to run mobile version of agility regardless of device, configuration or browser. Instead standard url use:
http://agilityurl/mLogin.aspx
When mLogin.aspx is used then all subsequent requests from that session will be treated as requests from mobile device.
[diagram]
It is also possible to temporary switch particular form into mobile version. It is very handy during form design.
[standard scan]
To render mobile version of particular form add m prefix to ScanForm.aspx or DetailForm.aspx.
[mobile scan]
