Webrun call details for ==> RQ04 search

I'm looking for a call string to use when trying to initiate search for a resource in RQ04 (via a webrun node). Using an example to clarify the ask; to recover a job in lawson in IPA using webrun node, i'd use the specific call details below in the node:

/lawson-ios/action/RecoverQueuedJob?jobName=<!LwsnQuery9040_JOBNAME>&jobNumber=<!LwsnQuery9040_JOBNUMBER>

I'd like the similar string i can use to make a search call to RQ04 if possible. Thanks.

Find more posts tagged with

Process Automation (IPA) - General Discussions

Accepted answers

All comments

unknown

You specified "search for a resource in RQ04" but you have a jobName name value pair example.

Are you trying to find a resource e.g. requester, a defined RQ04 job, or RQ04 job history ?

Are you onprem ?

unknown

Hi. Please disregard the string above. I was trying to give an example of what i was looking for with something unrelated.

We are on-prem. In short - I am looking for a call string (for the webrun node) to make a search in RQO4. I can easily use javascript to parse the result of the search. The end goal is to use the outcome of the search as a criteria to provision Requester identity/service in Lawson. As always, feedback is appreciated. Thanks.

0904080826502268.xls

unknown

Use Requesters (RQ04.1) to define a requester (the person, department, or function that is entering a requisition). If end goal is a Requester identity, then you are validating if a Requester exists, right ? why not use DME to Requester table ? You don't need the form.

something along the lines of...

portal.domain.net:1443/.../Erp

FYI you can add Requester Identies via loadusers, you can just define the <IDENTITY> nodes so long as the Requester has an RM identity...unless you are going ldap route.

**The reason I asked if you are on prem. You can put portal in debug mode, I think that is still supported. This opens a trace window. All web service calls are fully formed and write to the trace window. results are returned as XML, takes the guess work out of it

portal.domain.com/.../index.htm

unknown

Correct. If the Requester exists in RQ04, then i choose to provision them with a Requester identity in Lawson. If they don't exist in RQO4, no provisioning happens.

Not exactly sure how i'd make that specific DME call in this case. The closest thing i came across to what you posted was when i was digging around Chrome's developer tools - when i did a search on the RQ04 form for a resource and captured the string below.

/servlet/Router/Drill/Erp?_OUT=XML&keyUsage=PARAM&_TYP=RL&_PDL=TEST10&_SYS=RQ&_TKN=RQ04.1&GOT=ACCTU&RRU=33389&_KNB=RRU&RRU=33389

A longshot, but i figured i'd run a small test with this string - replacing the employee ID "33389" with a variable, and inserted it into a webrun node. I expected that the webrun node variables (WebRun5580_informationCode, WebRun5580_returnMessage, WebRun5580_outputData etc.) would clue me to the node findings and i can use that within a javascript to build some logic there. Got nothing useful tho.

If you do know the specific DME call to use to query the RQ04 table - i'd appreciate it.

Copyright © 2025 Infor. All rights reserved.