Who's On?

	Membership:
	Latest: John Bonin
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5270

	People Online:
	Visitors: 304
	Members: 0
	Total: 304

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

Workunit Folder for WorkObject

3 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

cBreeze

Basic Member Send Private Message

Posts: 20

5/28/2013 2:25 PM

I have a Requisition approval PF. This creates a Work Unit. (And a Work Folder for that unit- that can be seen in PF admin linked to RQ10)

If it is a specific type of req (by Vendor#), I go to a Work Object and call the 2nd PF. This creates another Work Unit, but not a Work Folder record.
I pass almost all of the variable in the workObject and they show up in the wu.log.
Just not creating Work Unit folder linking to 2nd Flow.
(Would like to have the user be able to drill to RQ10 from Inbasket Folder.)

I Appreciate any thoughts..
I am thinking that I am not passing something to 2nd PF?
Regards,
Curt

JonA

Veteran Member Send Private Message

Posts: 1163

5/28/2013 7:04 PM

We do something similar. Based on the requesting location we kick off a second flow and a new work unit along with the work unit folder is created. We're passing the Company and Requsition Number variables plus we have the "Pass all start activity/Service variables" box checked.

cBreeze

Basic Member Send Private Message

Posts: 20

5/29/2013 4:13 PM

Jon,
Thanks for response.
I checked off "Pass All" (Still not getting it.)

When you say "passing the Company and Requsition "
Is that what is setup in your service definition/criteria?
My service definition/criteria for both are Company and Location..

It works for the first WU. I get a folder created.
Wondering if I have to change this service definition to include Req# on Both definitions

JonA

Veteran Member Send Private Message

Posts: 1163

5/29/2013 5:27 PM

The Company and Requisition variables were checked in the "Select Start activity variables to be passed" section. Which is redundant since I have the "Pass all" box checked so sorry for the confusion. If it helps our secondary flow does not create a work unit folder either but yet our end users can drill into the requisition data through the inbasket display. Could it have something to do with the display exec? Our secondary flow has a query node much like the first that queries the requisition info again. Is this needed for the drill around? Sorry, my PF knowledge is just enough to maintain/tweak the flows that we have. I don't know much about building them and they were built by the consultant we hired to implement Lawson 10 years ago.