Resource Query Node

In your ResourceQuery select People and enter the Product Line and then click Get Attributes.
Select the values you want to capture, like ID. Click Next
Select the Agents tab and the Agent productline_COMPANY
Select the Expression COMPANY and enter your company value
Click the Add Expression button
Click Next
Click Test your Query and if successful, click Finish

Thank you for your response David.

I have tried this...However, when I select the Agents tab, the only 'Agent' listed is that of the poduct line the product line and the only 'Fields' listed are DOMAIN_USER, PASSWORD, SID and UID.

Any idea why I wouldn't see productline_COMPANY as one of the agent fields to choose from? Thank you!

Can you log into Lawson Security Administration and check what values are available on your user records?

david, please disregard my last post. I was using an obsolete, test product line. Now that I have the correct test product line identified, I do get 'productline_EMPLOYEE' as one of the agents and I am therefore able to select the COMPANY field = #### to get the expected records.

Thank you kindly for your assistance!!!

I hope this thread is still active...I have another issue with my resource Query that I am hoping someone can help me with.

I have built a simple flow, which just performs a resource Query (by company number and the presence of a particular role) and generates a file and emails it as an attachment. However, it times out on me when attempting to run it through Designer. I found a KB article on Lawson's site, but it is in regards to a system Admin node, which I am not using. It references that Designer has a built in 30 second timeout and recommends running the flow from the server.

I tried this, but still through Designer and it still times out. How can I run the flow outside of designer? It's a simple flow, built for use by the security admins in IT, intended to only ever be run from within Designer. (I've never built a trigger before.)

Any ideas? Thanks!!

I believe that if you are running version 9 of process flow, from designer you have the option to 'run on server'. Even though your Designer will time out, the actual flow will still continue to run behind the scenes on the Lawson server box. The only drawback is that you don't know when it is actually completed unless you look at the workunit in bpm/menu.do.

Unfortunately I don't know of a way to extend the designer timeout option.
Shawn

Even if you run on the server it could stilk timeout depending on how many records you have to spin thru, my experience is anything over 3000 causes issues when you include service agents in the criteria. Adding and additional criteria can help