Job queue parameter???

Does anyone know the parameter for specifying the job queue when submitting a job in IPA? In the old designer it was QUEUE=, but I tried that and my job did not run in the queue I specified. It ran in the default one, ************. Thanks!

/lawson-ios/action/SubmitJob?jobOwner=<!_configuration.main.SCMBatch_user>&jobName=POSIEMENS&QUEUE=SCM

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

I've always run fiddler along side of a job submitted through portal or Ming.le with the criteria I'm looking for. Fiddler should display it back in the command line. sample: /lawson-ios/action/SubmitJob?jobName=HR211.AD2&jobOwner=COB<userID>&startDate=20161222&startTime=080000&jobQueue=<QueueName>&displayOldFormat=true&OUT=XML. Hope this helps.

russel-cornelson

/lawson-ios/action/SubmitJob?<PARAMETER>=<KEY>&<PARAMETER>=<KEY> ... etc

Required Parameters

jobOwner - alphanumeric - the owner of the job to be submitted

jobName - alphanumeric - the name of the job to be submitted

Optional Parameters

jobQueue - alphanumeric - the job queue to place the submitted job on

startDate - YYYMMDD - a future date to submit the job on, if not used default is submit now

startTime - HHMMSS - a futre time to submit the job on, if not used default is submit now

wait - true/false - If set to true the web service will not exit till the job has performed.

NOTE: You should never use wait=true if you are using IPA; this hijacks the workunit thread from a limited pool for the life of the job and in modern IPA there are too many places for this call to timeout and fail. A IPA Wait node should be use to periodically call ..

---------------------------------------------------------

To check on the status of the submitted job, first you need to pull the job number. The submit job returns an XML output. So using javascript in an assign node:

var xmlString = WebRun2810_result.replace(/<?xml.*?>/, ''); //strips the xml header so we can read it as xml

var myXML= new XML(xmlString); //sets a myXML variable from the output, remember to rename WebRun2810

jobNumber = myXML.QUEUEDJOB.@jobNumber; //this pulls the value of the jobNumber

jobNumber = "0000000000" + jobNumber; //this adds a bunch of leading zeros. submit job returns integer only.

jobNumber = jobNumber.substring(jobNumber.length - 10); //this takes the last 10 characters in string.

soo SubmitJob returns JobNumber = 123456; adding 10 zeros then concatenating job on the end gives you 0000000000123456; then pulling last 10 characters gives you 0000123456 which is what is needed in the call to look at the status of the job.

---------------------------------------------

lawson-ios/action/ListQueuedJobs?filter=jobNumber%20EQ%20<!jobNumber>

**this works for me

Again ... xml content is returned so you can use javascript to pull the jobStatus with something like this...

var xmlString = WebRun4550_result.replace(/<?xml.*?>/, '');

var myXML= new XML(xmlString);

jobStatus = myXML.LIST.QUEUEDJOB.@jobStatus

unknown

Thank you- jobQueue is what I needed.

unknown

I have discovered that if I submit a job via IPA with any user it puts the joblog under the correct user, but the print manager jobs go to the Lawson user account. I went back to the v9 designer and it works the same, so I don't think it's new to IPA. Should I be submitting all jobs using the Lawson user or in our cloud instance, svc_infor user?

/lawson-ios/action/SubmitJob?jobOwner=INFORBCscmbatch&jobName=POSIEMENS&jobQueue=SCM

So in the above submission, the joblog appears under scmbatch user but the print manager output is under svc_infor. Here are the screen shots. If I submit the job manually with scmbatch user, it does it correctly.

jreese

The job is going to be submitted under whatever user id you have entered on the Web tab of the Process Flow Configuration. We have a separate service account for each area, Finance, HR, Supply, created under separate configuration sets, and then create distribution groups on those jobs so that the printed output is in the proper print managers.

unknown

Thank you- we must be missing the distribution groups.

Copyright © 2025 Infor. All rights reserved.