Setting Up Mobile Access to Manage 2000 7.3 sp3

Manage 2000 7.3 sp3 mobile features are designed to run in webkit browsers such as Mobile Chrome or Mobile Safari.  These are the built-in browsers for IPhones and many Android phones. The next major version of Manage 2000, currently under development, supports many other mobile device browsers.

To configure mobile users on Manage 2000 7.3 sp3:

Use CNT.SYSTEM.REFS to assign mobile preferences for a web user role

For example on the SYSUSER role assign MobileUser as the menu for system users

1. Start CNT.SYSTEM.REFS
2. Call up record SYSUSER
3. Add a Preference Code of 25 Mobile Menu
4. Set the value to MobileUser
5. Add a Preference Code of 22 Mobile Stylesheet
6. Set the value to mobile.css
7. Add a Preference Code of 26 Mobile Items Per Page
8. Set the value to 5

You may assign preference codes 22, and 26 in WEB.CONSTANTS Default Web Preference settings instead of on each role in CNT.SYSTEM.REFS since they are likely to be constant for all roles.

Use CNT.SYSTEM.REFS record CM to assign preferences for customers accessing Manage 2000 via an externally facing portal. The MobileCustomer menu can be used as the mobile menu.

Use CNT.SYSTEM.REFS record SLSREP to assign preferences for sales representatitves accessing Manage 2000 via an externally facing portal. The MobileSalesRep menu can be used as the mobile menu.

Use CNT.SYSTEM.REFS record DEVELOPER to assign preferences for developers or administrators. The MobileAdmin menu can be used as the mobile menu.

Mobile devices are automatically detected. If the user has a mobile menu assigned and is accessing the site from a recognized mobile device then the user will be directed to a mobile login and from there to the M2000Mobile navigation app. The FullSite web function may be used to re-enter the site in non-mobile mode. Logging off the website and logging back in will place the mobile user back in mobile mode.

The a fore mentioned menus have been supplied as examples and starting points for configuring mobile access to Manage 2000 7.3 sp3.  The mobile navigation options may be modified in MENU.BUILD by changing the menu items. REPORT.BUILD web function definitions may be used (See WEB.REPORT.BUILD for information on setting up FN.BUILD entries to run REPORT.BUILD reports from the web). Web functions built using the roiHyperQueryControl will also be optimized for mobile automatically, this includes about 65 standard Manage 2000 web functions.

While the desktop portal system is not yet available from this mobile navigation you can recover some of the portal feature by setting the Use Last Key As Default preference to Y. This will default in the last key used as users select different web functions from the mobile menu emulating the key integration you get from portals.

There are about 220 Web functions that have not yet been optimized for mobile use in Manage 2000 7.3 sp3.  They may be used, but will likely prove inconvenient for the user.  The next major release of Manage 2000, currently under development, has all web functions and portals optimized for mobile.

Out Of the Box Experience (OOBE Newbie New)

Well the development cutoff of Manage 2000 7.3 sp3 is done. I have upgraded our build system and development web server to sp4 where 7.3 future development will happen, and created the views for patching sp3. Now I wait and wait and wait while Release Control readies installs for the field and customer sites slowly rollout new service pack upgrades or come on board from older major releases.

One of the areas I have been trying to enrich is the How To documentation on various web setup processes. I hope this combined with more appropriate Sales Rep and Customer menus and default role preferences will make setting up external access to Manage 2000 less daunting, and thereby give more Manage 2000 sites ROI justification for upgrading to the newest Manage 2000 release.

Imagine Sales Reps, Service Personnel, Buyers for customers at trade shows pulling out their IPhone, Droid, or IPad and interacting directly with your Manage 2000 site.

IE 9.0 Firefox 4,5,6... and counting and Chrome

Manage 2000 7.3 sp3 is now building in development with IE9 compatibility in standards mode with HTML 5.0 support. WhooooooooooooHooooooooooooooooo!!!

Development is scheduled to continue till mid-October giving a nice cushion for alpha testing to clean up any construction debris. So things are looking good for 7.3 sp3.

I still need to spend some quality time with the roiScreenControl used in the web product configurator to implement the new scrolled set capability and make it cross browser compatible with Chrome and Safari. But other than that everything seems to be running well in IE9, Chrome, Firefox and Safari.

A nice side benefit of the IE9 project for 7.3 sp3 is that more of the mobile tools and applications slated for 7.4 will make an early appearance. The ESOP module in particular will start sporting a sleek mobile look with a sales product code browsing app with add to cart capability, and mobile formatted shopping cart and checkout pages.

ITouch'd Manage 2000

Well the Manage 2000 7.4 web repository is finally branched and 7.4 only development can now be checked in. But one last web tools development project did make it into the 7.3 sp3 code base before the branch; MT/M2000Mobile/M2000Mobile.aspx provides navigation based on MENU.MASTER trees and DEMO/MobileStockStatusByLoc/MobileStockStatusByLoc.aspx which provides an example application to copy.

The idea is to build HTML, javascript, and CSS styles that mimic mobile applications, rather than building applications in proprietary environments one end-user device at a time. Using micro-frameworks like WebApp.Net one can build a web page that looks and feels like a mobile app although it runs in the browser.

Sp2 just went out the door so we won't be launching sp3 for awhile but it should be available in plenty of time for stocking stuffers.

iManage2000

This last month I've been testing and researching issues related to accessing Manage 2000 web functions from IPhone and Android based mobile devices. Since these internet enabled devices include web browsers the basic ability to run Manage 2000 web functions is built right in.

However there are stumbling blocks to their usability. The most obvious problem is the small screen and the large complex pages of standard Manage 2000 web function pages. A little further examination reveals navigation problems in the drop down menus. These are rendered by Infragistics UltraWebMenu controls which do not work properly with WebKit based browsers. Another issue to consider is performance when accessing the net through slower connections. (How many G's are there in T1?)

So, though you can go the discount route and setup phone desktop buttons to target specific standard Manage 2000 web functions, a little more work can lead to a much better user experience.

The road map to a better user experience includes replacing the standard heading banner with a navigation app based on IUI, WebApp.Net, or Sencha Touch. The menus should still be administerable in MENU.BUILD, but the whole mobile menu tree would get loaded to the mobile browser as a multi-layer page with anchor navigation between layers. This would provide the user with rapid menu navigation including familiar slide transitions and header navigation buttons.

Functions would work off of standard hyperlinks and load and postback in their usual fashion. Though any specific mobile web function development should consider leveraging the layer tools in these micro-frameworks. Other mobile web function best practices would include avoiding the IG Grid in lieu of lighter weight options, minimizing the information displayed in any given layer to 5-7 items and providing multiple choice data entry in place of fill in the blank wherever possible.

Sizing the formatting table to 480 x 320 can help give a design time feel for mobile screen territory at standard magnification. HTML meta tags like <meta name="viewport" content="width=device-width; initial-scale=1.0;" /> can be used to control the magnification level of the web function when initially displayed. Since these micro frameworks tend to use CSS hiding techniques they interfere with the design time WSYIWYG in Visual Studio. You can temporarily comment out the stylesheet link in the aspx file to get a better designer experience.