Lost approvers when going to 9.0

You have to use the ResourceQuery to get the Employee number from the userid.

The resource query has an ID field that contains the username.  I don't find a field that contains the employee number.  My admin guy says their is a field but it is in a different section and the field is not an option to me in the resource query.

I have a script that given the username, it will give me the employee#.  I can call this script with a webRun

The problem is I don't have the username.  The approvers log in with their username.  They go to their inbasket and perform the "work".  The userNode takes care of all the bookeeping.  But as I stated, it won't fill the username in the PAJOBREQ table because the approver fields are of type number.  Does the userNode create a variable that I could access that contains the username?

I need the username of the approver who logs in and does the "work" for a given userNode or I need the flow to know its own workUnit# so I can query the WFMetrics table.  Are either of these available in a flow?

If you are using the Employee # within Lawson Security (for ESS or MSS) then you can get to this "Agent" via the ResourceQuery.  I've attached some screen shots to show you how.

There is a system variable called oWorkUnit available within your flow which is the WorkUnit number currently associated to your flow.

Thank you for both your answers. Either will solve my problem. What is an agent?

An agent is Lawson's term for the additional identity information you can add to a user, like Requester ID (for RSS), Employee Number (for ESS & MSS), etc. By the way, these additional "agents" must be added for all application product lines (data areas). So for Test and Dev you have to add both Test_Employee and Dev_Employee.

<!-- Converted from text/plain format -->

An agent is used to retrieve security identities associated with a resource.  In this case it would retrieve the employee number of the approver based on their login when the make the approval.

What David is recommending with the ResourceQuery node is the best approach for you.   You would need to update your approval flow to include the ResourceQuery node.