Manage 2000 Version 8.0

The major version has officially rolled in the development environment.  Manage 2000 8.0 here we come. Whoo Hooo!!!

The development team decided a couple of months ago that with all the mobile web changes plus other un-celebrated technology changes that the 7.x branch should end with 7.3 and the upcoming release should begin the 8.x dynasty.  Look for it towards year-end of 2013.

So now that changing the numbering is done, it is time to change some more of the machinery as well.  I am currently hip deep in ASP.NET 4.5, HTML 5, and VS 2012, trying to solve too many equations with way too many unknowns.

The VS 2012 IDE has a lot to be said for it.  It feels faster, and seems to get confused less often by our sub-project pattern web architecture. The solution explorer drill down into project classes, the highlighting of the current variable in neighboring code, the javascript highlighting during edits are all wonderful developer productivity improvements.  There is a project level option to run a code analyzer at compile time that functions much  like the Manage 2000 BX Audits to provide developers with coding standards compliance feedback.

We are going to have to make a few mass changes to vbproj files and  a few references in aspx and ascx files.  Infragistics references will have to target ASP.NET 4 instead of 3.5. But it doesn't seem like the Visual Studio Tools Team broke anything critical to Manage 2000 this time around.  Whew!

There is an interesting convergence of client side technology happening as Manage 2000 web tools provide lots of client side javascript and JSON validation and editing features which run into some of the unobtrusive validation being supplied with VS 2012 and ASP.NET 4.5 with the inclusion of jquery.  And as we proceed down the HTML 5 path we are both running into the validation constraints being coded natively into browsers as they process HTML 5 markup.  So it seems I will be spending some time trying to smooth over some redundant repetition of validation on the client end.

How to develop web functions with Visual Studio

There are a number of different sub-topics here:

1. Creating a developer sandbox on your desktop
2. Loading the Manage 2000 DAC components and WebControls into Visual Studio
3. Configuring Visual Studio to 'see' the Manage 2000 web function wizards
4. Where to find out more about Manage 2000 Web Technology and how to use it

You can find answers on all of these topics in Manage 2000 7.3 sp3 on the SYS.WEB.HOWTOS menu:

1. SYS.DEV.SETUP describes how to set up your PC for Manage 2000 web function development.
2. WEB.VS.TOOLBOX.SETUP describes how to add Manage 2000 Web Components and Controls into your installation of Visual Studio.
3. WEB.VS.WIZARDS.SETUP describes how to configure Visual Studio to 'see' the M2k wizards.

And in the related courseware section you will find links to INTRO.WEB.COURSE and ADV.WEB.COURSE which are chock-full of web function development minutia.

But if you want to get somewhere quickly check out the new wizards for generating Visual Studio projects for HyperQueries, Mobile Web, and BTO Posting type functions.  These wizards allow you to describe your function in terms of Unidata file names and dictionaries, or in terms of Manage 2000 Business Transactions and then generate for you a working prototype with controls configured and named in useful ways and in some cases with extensive amounts of code-behind already plumbed out.

There are a couple of webex videos available under the Manage 2000 Web Presentations link above on the right.  For Visual Studio Manage 2000 web function development knowledge check out Mastering ASP.NET 3.5 and VisualStudio2008 for Manage2000 Parts I and II.

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.

Extending web portals by publishing REPORT.BUILD functions as web functions

Use FN.BUILD to create a web function that runs a specific REPORT.BUILD report from the web

Start FN.BUILD.

Create a new item with a name that matches the REPORT.BUILD report function name without space or periods and with only the first letter of each word captialized; so an entry to run RCVNG.RPTS.BY.DATE would be called RcvngRptsByDate.

Set the Type to W to specify a web function.

The module should match the module where the REPORT.BUILD report function exists.

Enter a suitable description. Shorter descriptions are nicer on mobile devices.

End out of the first screen.

Enter an extended description.

The additional parameters prompt will bring up a new screen with web function specific prompts.

For Web URL enter the Url to the REPORT.BUILD report interpreter /mt/ReportBuildRpt/ReportBuildRpt.aspx

Add a Web Query Parameter to specifiy the library (module) that the report resides in.
Use ReportLibary for the parameter. Use your module for the value.

Add A Web Query Parameter to specify the REPORT Id that should be used to generate the web page. Use ReportID for the paramter. Use the actual REPORT.BUILD report id (The PWS report name) for the value.

End out of FN.BUILD.

Test your web version of the report by typing in the upper and lower case version of the report name at a Menu or from ECL.

This web function may now be added to a web or PWS menu in MENU.BUILD

Note: In Release 8.1 this has been automated into the REPORT.BUILD function. Setting the Create Web Also flag to Y will create the corresponding FN.BUILD record for you.

Enabling Attachments in Web Portal Functions

Manage 2000 web portal  functions may be used to view and/or upload attachments. Web portal attachments are viewable from PWS and vice versa.

To enable viewing and downloading link type attachments from Manage 2000 web portals, add web preference 17 Enable Attachments and set the value to 'Y'. This may be done globally in WEB.CONSTANTS, or by ROLE in CNT.SYSTEM.REFS, or individually in CONTACTS. It may be necessary to logoff the web site and log back on to refresh your web preference settings. After entering a key in a portal, any objects attached to the portal base file and current key (that the user has security to access) will be added to a local menu named attachments.

To enable uploading attachments from Manage 2000 web portals add web preference 16 Attachment Storage UNC and set its value to a fully qualified UNC location or a UNC location relative to web site virtual directory root. After entering a key in a portal the user may click on the paperclip icon in the upper right corner of the portal which will navigate to the upload attachment page. Any objects uploaded will be attached to the current portal base file and current key.

Attachment Storage specifications starting with "\\" will be treated as UNC format. Specification starting with a letter followed by ":\" will be treated as a local disk drive location. Other formats will be treated as directories relative to the web site application root directory, "Documents\Attachments", for instance, specifies a directory in the websites "Documents" directory named "Attachments".

The suggested storage format is a UNC to a network resource that is available to the AppPool Identity on all Manage 2000 site hosting web servers, that is backed up regularly, and that is available to PWS users. Attachments from PWS users should be moved to the UNC Attachments Storage location and linked from that location in PWS using \O.I and specifying the file location using \\server\... rather than just attaching something from a location localized to the users PC.

How to setup AR KPI dashboard displays

Manage 2000 has included an AR Monitoring System since release 6.5.  Monitoring must be turned on in SOP.CONSTANTS and AR.CONSTANTS.

This results in real time updates in the MCD_DATA file tracking SO and AR activity.  The original interface in 6.5 for this information was found on the SYS.MONITOR menu.  But with release 7.3 these KPI counters can  be much more elegantly presented as a news feed into MS Outlook 2007 or 2010.

MSO's 1290 -1300 provide a variety of standard dashboard widgets. You can, of course, copy one of these and change time fences, graph types, and so forth for a particular result.

To get them to OUTLOOK simply wrap them in a NEWS.ARTICLE and attach to a NEWS.FEED. By specifying a news source of MSO and the MSO.ID to use as the source for the article almost all of the required setup will default in.

To find the feed run a Manage 2000 web function and then use IE9 Feed Discovery from the Tools menu. Then just copy and paste the required URL into the Outlook Add RSS Feed wizard.

Here is an ARCHIVER package of example AR news articles and a feed:

DASH.PMN AR Dashboard RSS example

1. Click to download it to your PC
2. From PWS use FILE.PASS to upload it into the PROJECT_LIBRARY
3. From PWS use the ARCHIVER function bring up record DASH.PMN and use the Extraction screen 4 to put the example feed into the NEWS_FEED and NEWS_ARTICLE files.

Web Performance Exception Reporting

One of the diabolical aspects of n-tier pooled connection processing used in web functions is the degree of difficulty there is trouble-shooting performance issues. The reality of many users sharing the same Unidata session as they make calls across responders make it difficult to untangle who's process is burning up bandwidth and forcing others to queue behind them.

In 7.3 sp3 we added a tune-able performance exception trace based on the RPC History tracing infrastructure used for development debugging.

You can set a performance benchmark in WEB.CONSTANTS defining how long an RPC call must last before being considered a performance exception and also how long to retain the RPC trace information for review.

Later, after activity across the responders, run WEB.PERFORMANCE.EXCPT to see RPC calls that exceeded the defined performance target. The report attempts to display 'important' parameters about what the responder was requested to do.

Since the performance exception logging is built on the RPC History trace tools you can use DEBUG.NET to dig deeper into the 'problem' calls and even re-run them from PWS for debugging and profiling purposes.