Who's On?

	Membership:
	Latest: Saef
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5226

	People Online:
	Visitors: 544
	Members: 0
	Total: 544

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

IPA: Using Landmark Transaction node to pull PFIWorkUnitVariable info

5 Replies

0 Subscribed to this topic

52 Subscribed to this forum

Sort:

Author

Messages

LisaN

Veteran Member

Posts: 53

9/10/2013 7:10 PM

We are new to IPA and we're trying to fix some of our PFI converted flows that used to use a query node to pull workunit information from the Logan WFVariable table.

I've replaced the qry node with the Landmark Transaction node and we're reading the 'PFIWorkUnitVariable' table. The node successfully reads the table and pulls the WU information.
However, There are other Lawson Query nodes in the flow that reference certain variable values.

In PFI you could simply reference the WFVariable value information you wanted by using a variable like (in this example it would pull REASON_1 of the personnel action workunit).

But in IPA I can't figure out how to pull the information. Do you need to have a Landmark Transaction node for every variable value used/referenced in your flow/process?
For example:
have a node that pulls the value of variable 'REASON_1' for the work unit, and then another for 'REASON_2' .

Any advice?
Thanks,
Lisa

David Williams

Veteran Member

Posts: 1127

9/10/2013 7:30 PM

Lisa,
What I have done in PFI is to query all of the WorkUnit variables with one DME call and then use an Assign to pick up the ones I need using a JavaScript expression (I'll send you an example). You might be able to duplicate this type of functionality with your LandmarkTransaction.

David Williams

Veteran Member

Posts: 1127

9/10/2013 7:38 PM

If your WorkUnit has these variables, why do you have to query for them? They should be available to the ProcessFlow by default. In my example, the variables could be updated and that's why I had to re-query them.

Woozy

Veteran Member

Posts: 709

9/10/2013 7:59 PM

Hi LisaN,

I'm with David. I don't understand what variables you are trying to reference, and it looks like maybe some of your text was deleted - probably due to brackets???. Are you looking for the variables that are being passed into the workunit and variables that are created/updated by the flow nodes, or are you looking for variables from other workunits?

Generally the variables can be referenced as "variablename" or "nodeid_variablename" (I've excluded the brackets so these will show in the post), even if they don't appear in the CTRL-SPACE variable list. This is true of trigger variables, start-node variables, query node variables, etc.

LisaN

Veteran Member

Posts: 53

9/10/2013 9:36 PM

the variable we used to use in PFI was something like "Query6530_22_VARIABLE_VALUE", that would pull the 22nd variable value read from the work unit, or seqnbr 22. When looking at the console to see what is pulled for the lndmrk trx that type/naming convention of variable doesn't exist.

The Lawson qry node is trying to pull the description for the personnel action reason code used in the work unit from the table 'PAACTREAS', so for the variable value 'PC PROMO' I need to pull 'Pos Chg Promotion' (the description is used through out the process in emails).
I just created 2 new Lndmrk Trx nodes to pull each of the seq nbrs I need (one for seqnbr 22 and one for seqnbr 23) and used those variable values in each of my qry nodes; each qry node pulled the correct PAACTREAS description.

LisaN

Veteran Member

Posts: 53

9/10/2013 10:14 PM

oh my goodness; you are right. I've been working on this too much.
I just needed to use the variable name like you said; like "Reason_1" to pull the value of "PC PROMO" for this test action I entered. It makes perfect sense now.

I guess I just need a break and your help. I'll continue working thru the process.
Thank you very much.