Difference between revisions of "Mobile Forms (proof of concept)"
(→Detail Form) |
(→Detail Form) |
||
| Line 89: | Line 89: | ||
===Detail Form=== | ===Detail Form=== | ||
| − | Design of detail form looks exactly like standard form. Unfortunately number of supported controls is very limited. Some controls are usable only in read only mode (like date time control). Grouping controls like GroupBox or Tabs are not available. Grids on details are not available | + | Design of detail form looks exactly like standard form. Unfortunately number of supported controls is very limited. Some controls are usable only in read only mode (like date time control). Grouping controls like GroupBox or Tabs are not available. Grids on details are not available also. It seems that some controls are easy to patch to make them mobile friendly, but most of controls require full rebuild. |
Even with such limited number of controls it is possible do define application which is able to go through basic WO flow: | Even with such limited number of controls it is possible do define application which is able to go through basic WO flow: | ||
Revision as of 17:02, 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).
Contents
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.
It is also possible to temporary switch particular form into mobile version. It is very handy during form design.
To render mobile version of particular form add m prefix to ScanForm.aspx or DetailForm.aspx.
Available Pages
Login
Please note that not all standard functionality which is provided with standard login page is currently available in mobile login. Please refer Issue 6446 for details.
Main Menu and Forms Menu
Mobile version do not contain designated mainmenu page. Instead designated page with menu each page contain menu. Main menu is available on each form on left top side. On right side available is context menu it contain known in standard agility FormMenu but it also contain one hard coded option to logout from system.
Main menu is available on any page but it is not rendered each time. It is using HTTP protocol caching mechanism. Main menu is described by export and it is placed in import/export repository: Mobile Main Menu
Below form do not contain any items declared in form menu so only option in action menu is Sign Out
Dashboard
In standard Agility dashboard is placed on main menu form. In mobile version there is no MainMenu page, initial form is opened directly without any additional container (iframe). Initial page is defined exactly the same like in standard Agility by selection Initial Form To Open on user menu definition.
Scan Form
Similar like regular scan form mobile version is displayed as grid. Grid can be problematic in small vertical screen orientation, considered columns availability and order should solve most problems.
In scan action menu, apart from form menu items available is special Columns... option. This option allows to switch visibility of particular columns. This functionality is not based on similar functionality which can be found in standard agility GUI. Columns selection is processed fully on client side and state is remembered until page is opened. Reopening scan will reset any previous column selection.
Special popup menu allows to apply or cancel row filter
Detail Form
Design of detail form looks exactly like standard form. Unfortunately number of supported controls is very limited. Some controls are usable only in read only mode (like date time control). Grouping controls like GroupBox or Tabs are not available. Grids on details are not available also. It seems that some controls are easy to patch to make them mobile friendly, but most of controls require full rebuild. Even with such limited number of controls it is possible do define application which is able to go through basic WO flow:
Selecting priority from mobile combo box:
