1. First thing you need is a way to make HTTP calls from your VB code. If you’re using VB.NET, the HTTP object is built into the .NET Framework. For VB6, I use an ActiveX HTTP Control from /n software IP*Works! v6.0 ActiveX/VB Edition (see http://www.nsoftware.com/ipworks/technologies.aspx?sku=ipa6-a).
   


2. Next, you need VB code to drive the HTTP Control. For VB6, I wrote a VB class that calls AGS and DME using the IP Works HTTP Control. For VB.NET, the code is similar, but uses a lot more of the .NET Framework to do the grunt work. I won’t bore you with the code sample, but this is the technique I use to pull security class data out of GEN to populate my security class viewer utility:
   
   
    
3. The last (and hardest) thing you need to do is figure out what you need to include in the AGS URL string. Here’s a sample for blanking out cycle 1 on an employee’s deduction via PR14:
   
   http://lawwebserver/servlet/ags?_PDL=TRAIN803&_TKN=PR14.1&_EVT=CHG&FC=C&_LFN=TRUE&_OUT=XML&EDM-COMPANY=4321&EDM-EMPLOYEE=1000&EDM-DED-CODE=BCD1&EDM-DED-CYCLE1=%20
   
   When the call completes, you'll receive an XML document.  You need to check the <MsgNbr> tag; if it's not 000, display <Message> tag contents.

- QUOTE OF THE ISSUE –

“Celebrate any progress.
Don't wait to get perfect.”

-- Ann McGee Cooper

Share your Tips & Tricks. Send them to mailto:letter-tips@lawsonguru.com.
You can view other Tips & Tricks on the Tips & Tricks page on LawsonGuru.com.

String to Date in JavaScript, Round Two

Last month (see https://www.danalytics.com/guru/letter/archive/2006-07.htm), I included a JavaScript tip from David Williams to convert a date value in a string variable returned from a DME call (in MM/DD/CCYY format) for use in an AGS call (in CCYYMMD format).

I told you it would only work with locales that enter dates in MM/DD/CCYY formats, since the code was looking in specific locations for the various parts of the date:

RQDELDT = RQDATE.charAt(6) + RQDATE.charAt(7) + RQDATE.charAt(8) + RQDATE.charAt(9) + RQDATE.charAt(0) + RQDATE.charAt(1) + RQDATE.charAt(3) + RQDATE.charAt(4)

What I should have written was that you’ll probably not need to worry about it in ProcessFlow, since DME calls always returns dates in MM/DD/CCYY strings. But if you do, you’ll need to modify the pflow.js JavaScript file that is shipped with Lawson ProcessFlow, and add additional variations for the pfDate() function.  Here's how to do it.

Technically, this is NOT a customization, since the ProcessFlow documentation states:

“To make other date variables available in Expression Builder, you may add them to the pflow.js file in CCSDIR/lawson/processflow or, on the Designer side, in the Designer install directory.”

When you make these changes on the server in $CCSDIR/lawson/processflow/pflow.js (%CCSDIR%/lawson/processflow/pflow.js on Windows), you need to copy the updated pflow.js to the ProcessFlow Designer directory (e.g. C:\Program Files\Lawson Software\ProcessFlow) on each machine on which the ProcessFlow Designer is installed..

There are two changes required to the pflow.js file:

First, the function definition needs to be added to the top section, which is source of the function drop down list in the Designer:

//*****Function Definition -->Date=pfDate(var1,'dd/mm/yyyy') //

Then, in the pfDate function itself in pflow.js you’ll need to insert an additional case:

case 'dd/mm/yyyy':
{
    tmp = dateStr.substring(0,2);
    retval.setDate(tmp);
    tmp = dateStr.substring(6,10);
    retval.setFullYear(tmp);
    tmp = dateStr.substring(3,5);
    tmp = tmp-1;
    retval.setMonth(tmp);
    return retval;
}

Once you copy the updated pflow.js to the ProcessFlow directory on your workstation, you’ll then see a new function, pfDate(var1,'dd/mm/yyyy') when you drop down the function list: