Infor Technology

« | Main | »

Background server calls made by Infor Smart Office for Lawson Applications

January 17, 2017

By Vince McGowan, Senior Principal Software Developer

Infor Smart Office for Lawson applications provides many custom features which are made possible by meta-data retrieved from the Lawson application server in the background. But these features come at a cost of increased network traffic and additional server utilization which could impact performance. This document will identify this background activity and describe the purpose of each so clients can decide whether or not the feature is useful enough to incur the cost. If not, there are settings provided to disable them.

Some of the settings identified here are only available in Smart Office version 10.2.1.0.196 (hot fix 19) or greater.

It may be helpful to know that much of this meta-data is cached on the client machine so as only to make the server call once and even if a feature is disabled and does not request certain data, the same data may have to be retrieved in some other context, such as to render a related form.

Also, this overview does not identify all background server calls as many other calls are necessary just to provide the base functionality. Examples of this include retrieval of the application screen definition (form XML) and the field help.

Context Messages

Context messages refers to meta-data useful to the Ming.le feature of Smart Office. If the Ming.le feature of Smart Office is not enabled, this feature of Lawson should definitely be disabled. This can be disabled for all users in the ISO Settings Editor. Or it can be disabled at the Role level in the Lawson Role Manager. (See screenshots below.)

If not disabled, the application will attempt to detect whether or not Ming.le is enabled and automatically disable context messages.  If the context messages are enabled, you would likely see a call similar to this in the MangoClient.log as each form is initially loaded:

/lawson-ios/action/InquireIbcm?productLine=PATCH10&token=HR11.1

The purpose of this call is to provide a default message based on the last form action when making a post to Ming.le. If disabled and Ming.le is enabled, it simply means no default message will be constructed before the ‘post to Ming.le’ dialog is presented.

Table Cache

Table cache has two purposes: 1) it is required if the Ming.le feature is enabled to aid in the lookup of context messages, and 2) to provide useful information when displaying field info. The field info was provided to help script developers when writing custom Jscript. So again, if Ming.le is not configured or a default message is not important this feature can be disabled in the same way as context messages (see below).

If enabled, you will likely see one or more server calls similar to this in the log as each form is first loaded:

/servlet/Router/Data/Erp?OUT=XML&MAX=10&PROD=GEN&FILE=FILEDEF&INDEX=FDFSET3&KEY=PATCH10&FIELD=FILENAME;SYSTEMCODE;&SELECT=PREFIX^=EMP

Table name in the Field Info popup

 

Application settings to disable Context Messages and Table Cache

 

Role settings to disable Context Messages and Table Cache

Form Attachments in the Toolbox

If the ‘Show Form Attachments’ feature in enabled, as each inquiry type transaction is performed on forms that support attachments, calls are made to retrieve any available attachments meta-data and to display links in the toolbox area of the form.  The calls would look similar to this:

/lawson-ios/action/ListAttachments?
dataArea=PATCH10&fileName=EMPLOYEE&indexName=EMPSET1&outType=XML&K1=1104&K2=1

This feature can be disabled either at the application level in the Settings Editor (see below) or by individual user in Lawson User Settings. When disabled, other attachment functionality for a form will still be available.

Job Related Print Files in the Toolbox

With this feature enabled, there are actually 3 server calls for each inquiry type transaction on a batch token form and multiple bits of functionality provided. First, as the name implies, it allows links to job print files to be displayed, but it also enables most of the special actions available on the Actions menu.

Features enabled by option to show print files

Here are examples of the server calls involved:
/lawson-ios/action/LISTJOBS?maxRecordCount=250&filter=jobName EQ VMCU210 AND jobOwner EQ u17499
/lawson-ios/action/LISTREPORTS?
maxRecordCount=250&filter=jobName EQ VMCU210 AND jobOwner EQ u17499 AND reportOwner EQ u17499
/lawson-ios/action/LISTQUEUEDJOBS?
maxRecordCount=250&filter=jobName EQ VMCU210 AND jobOwner EQ u17499

This feature, like form attachments, can be disabled application-wide in the Settings Editor or by each user in the Lawson User Settings.

Disabling form attachments and print file links application-wide

Job Polling/Auto Monitor

Enabling this feature provides a checkbox (Auto Monitor) on the Job Scheduler screen. When checked by the user, the current query will be refreshed (a server call) every 15 seconds. The call will look similar to this:

/lawson-ios/action/LISTQUEUEDJOBS?
maxRecordCount=250&filter=jobOwner EQ u17499 AND state EQ completed

This feature can be disabled at the Role level (see below).

Info Browser Refresh

The feature provides users with the option to have any Info Browser on a user’s canvas to periodically refresh (a server call) the current query. The call could be varied but would be to the Data service and be prefaced with:

/servlet/Router/Data/Erp

Like Job Polling, this feature can be disabled at the Role level (see below).

Disabling job polling and Info Browser refresh

Mouse Over Preview of Buttons on Forms

Mouse over preview is most useful for new users or those not familiar with Lawson applications. When the mouse is hovered over button on an application form, help text on the use of the associated form is displayed.

Example of mouse over preview

Depending on the number of buttons on a form, enabling this feature could result in dozens of server calls that look similar to this:

/servlet/LawSearch?PDL=PATCH10&TYPE=Programs.token;Programs.name&ROF=Programs.token&q=AP03.1

This feature can be disabled application wide in the Settings Editor or at the Role level in Role Manager and if done so, the mouse hover would instead simply disable the token id, AP03.1 in the example above.

Application setting to disable mouse over preview

 

Role setting to disable mouse over preview

Comments

Leave a Reply

Your email address will not be published. Required fields are marked *





About this Blog

The latest on Infor Technology

Follow

RSS Feed
By Email
Facebook
LinkedIn
Twitter
YouTube





Copyright Notice

© Copyright . Infor. Unauthorized use and/or duplication of this material without express and written permission from this blog's author and/or owner is strictly prohibited. Excerpts and links may be used, provided that full and clear credit is given to Infor and blogs.infor.com/S3Tech/ with appropriate and specific direction to the original content.