• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Display exec

 7 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Lance Kelley
Advanced Member Send Private Message
Posts: 24
Advanced Member
7/25/2011 10:25 PM
In our TEST requisition approval PFlow's User Action node, in the "Display exec" field, I'm referring to a portal page "req_appr_page.xml" (that I created with Design Studio).

This works without issue when I key in "req_appr_page.xml" directly into the Display exec field, but the process fails when I use a variable I set up <!--splayExecPa-->in that field (that points to the same exact page).
 
I need the variable there because I want to feed the new display to some employees I have testing the system, yet give the default display to all other employees. With that in mind, I fill the Display exec variable with "req_appr_page.xml" for the test employees, and fill it with "" (null) for everyone else.

The $64 question is: Can I use a variable in the Display exec field within the User Action node?  If yes, any other ideas why it might be failing with a "404 - File or Directory not found" error?

Thanks ...Lance
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
7/25/2011 11:47 PM
I know the system automatically determines whether to use the Design Studio XML page or the HTML page based upon the file extension in the Display Exec field. It could be it doesn't translate the variable correctly. What value shows up in the WorkUnit log?
You could use a Branch to direct to different UserActions (with the Display Exec values) based upon which one you want to use.
David Williams
jamesraceson
Veteran Member Send Private Message
Posts: 52
Veteran Member
7/26/2011 11:36 AM
Lance,

I have had varied results with trying to use variables in fields that are inside of the nodes in ProcessFlow. For example, for the 'To:' field for the email node, this works great. ProcessFlow reads different fields differently depending on what the node is. Sometimes it will read a variable, sometimes it takes literally what is there. What ConsultDavidW is suggesting is probably going to be your best way to handle the different situations that you want to set up (with the Branch node).
Lance Kelley
Advanced Member Send Private Message
Posts: 24
Advanced Member
7/26/2011 1:42 PM
Thanks ConsultDavidW and jamesraceson,

I like the Branch node idea because I'm sure I can hit my target that way.   Thank you!
RoxanneS
Basic Member Send Private Message
Posts: 12
Basic Member
7/26/2011 4:01 PM
Did you define all of your variables in the Start node of your ProcessFlow? I remember the teacher in our PF class said that not defineing them there is what causes the biggest problems with variables & PF. I've only written a few PFs but all have had the variables defined in the Start node and I haven't had any issues with variables thus far.
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
7/26/2011 4:19 PM
With the exception of variables used in the MsgBuilder - they don't have to be defined first.
David Williams
Lance Kelley
Advanced Member Send Private Message
Posts: 24
Advanced Member
7/26/2011 9:44 PM
RoxanneS,  In this case I did define the variable in the Start node (a pre-caution as I heard the same thing you did about that).   It wasn't that because it had failed with that initial trial. 

It's good to know, though, (ConsultDavidW) that the Start node variables are only needed for the Msg Builder node...I didn't know that.

Thanks to both of you.

I used a separate branch to choose the correct UA node (one with the Display exec, and one without) and the flow is working as needed.
Lance Kelley
Advanced Member Send Private Message
Posts: 24
Advanced Member
8/4/2011 10:42 PM
To close this out...

Lawson support said there is currently an outstanding JT 223289 for this issue where the Display exec field in the UA node 'will not translate a variable'.

The fix is pending.

...Lance