Who's On?

	Membership:
	Latest: Brady
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5274

	People Online:
	Visitors: 367
	Members: 1
	Total: 368

	Online Now:
	bmoore

New Topics

Name	Points
Greg Moeller	4184
David Williams	3349
JonA	3291
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1375
Roger French	1315
mark.cook	1244

Persistent Variables

4 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

Terry P

Veteran Member Send Private Message

Posts: 234

6/25/2008 6:12 PM

Are there other variables available within the flow itself besides the very limited ones listed in the manual?

I'm trying to get the LOGINID of the person who is actually taking USERACTION on the work unit. Since it's not something known at the time the WFWK record is created, but instead at the time a user selections an action, I can't pass the variable in the normal way.

I need to know this, so I can do a query on the person's RD30 WEBUSER record (I'm picking up their BUYER-CODE and EMAIL).

Any suggestions?

John Henley

Posts: 3351

6/26/2008 6:22 PM

A work unit normally will have service-specific variables (i.e. for requisitions, the req number, requestor, etc.) associated with it. You should see them defined with the particular service, and can access them within the flow.

Terry P

Veteran Member Send Private Message

Posts: 234

6/26/2008 10:48 PM

That's not the problem. I pass several variables and access them just fine. The problem is these are variables AFTER the work unit has been created and it's sitting waiting for a User Action.

How can you tell which user is taking action from the inbasket. Example, I have a PO that was created and this custom trigger kicked off the flow. Now it's sitting in the insbasket for a task that has four users assigned to the task.

I want to know which one is taking action. I need to look up info from their RD30 record to see what their Buyer Code, email address is. The only way I can do it is if I know what their LOGAN is. I find very little on variables that are system wide avaibable during the proces flow itself, unless you passeed them to the service. Since the ones passing the serviced are not the same ones processing the services I'm stumped.

John Henley

Posts: 3351

6/27/2008 7:06 PM

Look at the WFWORKUNIT table for a couple of your work units. I'm not sure, but the WF-RM-ID might is the last person who touched the workunit (or it may be the person who created it).

David Williams

Veteran Member Send Private Message

Posts: 1127

7/1/2008 12:19 PM

The WF-RM-ID is the ID of the person who created the WorkUnit - who triggered the flow. For this particular solution, if you include the user's ID on their Buyer Code (PO04) record then you would have a quick way to view who should be taking the Action.