Webrun error

What version of Lawson are you on? If v10 then jobrun has been replaced.

I am on version 10. I am using a training document from September 2012 version 10 for reference. That is what they had. What has it been replaced with? Thank you.

Use // http://lawson_server/laws...p;jobOwner=dwilliams instead of jobrun

Try // http://lawson_server/lawson-ios/action/ to see the list of available actions

Hi David,
Do you know where I can find documentation on this? I want to use it in a flow. When I tried using a browser I get an error.
I used:


I receive the error - No access to token data of job

I turned off security. Do I need to add this using tokendef?

No, the token is MM280. Try to get the list of available actions. That might be where you have a security issue.

Hi David,
I found the problem. I needed to use Domain\lawson instead of just lawson for the jobOwner. If I use this in the webrun node for a flow how do I get the flow to wait until the job is done? Thank you.

I haven't found a WAIT option for the new process. You will more than likely have to query the GEN JOBQUEUE to see if the job completed and include a pause (Wait node or JavaScript loop) until it does.

You can use &WAIT=true to get it to wait until completion before continuing your flow. If you use OUT=xml you can put 63 in the SuccessString field and it will then tell you if it was successful or not (just successful job completion, not errors in the job output).

David, I'm on v10 and I don't get any response from the url you sent for the /lawson-ios/action. Where did this come from?

&WAIT=true doesn't work for the new job submit function
I found this pretty much by accident - I can't find any documentation.

Thank you David for all your help. I did try &WAIT and it did not work. I am still hoping to use jobrun.exe as it does allow you to use &WAIT. I want the flow to wait until the job is done because I want to use the CSV file it creates for use further on in the flow. The information you provided might be useful for other projects. I am working with Infor Support to see if we can find out what is causing the error.

The &WAIT=true was for the jobrun.exe. I use that for many of my processes in v10 and it works great.

Thought I would let you know that Infor was able to duplicate this issue so they have created JT-787297 for this issue. The KB article is: 1624286.

David,

Can you post the javascript code for a wait loop that you mentioned?

It could be something like this:

on the QueryJob node you put this code: PROD=GEN&FILE=QUEUEDJOB&INDEX=QJBSET11&KEY=ebfinusr=&FIELD=JOBNUMBER&SELECT=STATUS%3C60&OUT=CSV&DELIM=~

This set up will check for the status of a previously submitted job, if QueryJob node returns 0 records (QueryJob_RECORD_COUNT == 0) then continue, else wait a number of seconds and query again. Hope this help.