Difference between revisions of "Mobile Forms (proof of concept)"

From Agility
Jump to: navigation, search
(Available Pages)
(Login)
Line 37: Line 37:
  
 
===Login===
 
===Login===
 
[[File:01 MF login.jpg|400px]]
 
  
  
 
Please note that not all standard functionality which is provided with standard login page is currently available in mobile login. Please refer [https://support.softsolsgroup.com/agility/DetailForm.aspx?FormDefID=%2f!1b2e5692!61323!!&DataKey=%2f!71d68945!6446!! Issue 6446] for details.
 
Please note that not all standard functionality which is provided with standard login page is currently available in mobile login. Please refer [https://support.softsolsgroup.com/agility/DetailForm.aspx?FormDefID=%2f!1b2e5692!61323!!&DataKey=%2f!71d68945!6446!! Issue 6446] for details.
 +
 +
 +
[[File:01 MF login.jpg|400px]]
  
 
===Main Menu and Forms Menu===
 
===Main Menu and Forms Menu===

Revision as of 16:26, 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:

  1. 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.
  2. 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.


Mobile forms detection.png


It is also possible to temporary switch particular form into mobile version. It is very handy during form design.

Scan std.png


To render mobile version of particular form add m prefix to ScanForm.aspx or DetailForm.aspx.

Scan mobile.png

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.


01 MF login.jpg

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.

02 MF dashboard menus.jpg


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

[File:03 MF main menu slide.jpg|400px]]

04 MF context menu.jpg

Dashboard

Scan Form

Detail Form