Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
User Experience
Lawson Design Studio
Passing values from DS to PF
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
NonnieBear1776
Past 24 Hours:
0
Prev. 24 Hours:
1
Overall:
5161
People Online:
Visitors:
214
Members:
0
Total:
214
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
JonA
3288
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1348
Roger French
1311
mark.cook
1244
Forums
Unanswered
Active Topics
Most Liked
Most Replies
Search Forums
Search
Advanced Search
Topics
Posts
Prev
Next
Forums
Lawson Design Studio
Passing values from DS to PF
Sort:
Oldest First
Most Recent First
You are not authorized to post a reply.
Author
Messages
LCM
Basic Member
Posts: 8
2/11/2009 8:24 PM
Hi,
I am attempting to build a hybrid Design Studio and Process Flow solution for MA43 but I have run in to some difficulties. The request that I received is that when the Change button is used that I need to evaluate each line item to determine if the user has increased the value of the Invoice field. If so, a PF is to run that among other things sends an email to the buyer listing what happened and who made the change. I have built a DS page that initially builds an array of what the values are for each line at the time of the inquire and then compares them to their values when the change is entered. I can see via alerts that I have the values I need written to arrays for each line. I have also used the Wizard to build a PF trigger that passes DB values to the flow and creates the email.
Now for my difficulties:
First for the trigger, I have been unsuccessful integrating the PF trigger in to the script conditional (i.e., xml & JS). Consequently, at this point the flow runs every time the change button is pressed regardless of whether or not the conditions of the change occurs. Is it possible to refine the PF trigger in DS to run under conditions beyond what the Wizard allows you to build?
After spending a good chunk of time on this without success, I figured that I would just do the analysis on the flow side instead. The problem I ran in to here is getting the values contained in my global variables in DS in to my flow. I have no problem passing Lawson values but I have not figured out how to pass the variables I created in my functions on the Script portion of DS since they do not appear as “User Variables” (and I do not get values when I simply replace a variable with the name of one of my variables).
I am at an impasse here and would appreciate any suggestions that anyone has to offer.
Thanks!
David Williams
Veteran Member
Posts: 1127
2/11/2009 9:05 PM
The best work around for what you're trying to do is to build an AGS call to trigger ProcessFlow in stead of using the form action. You would use the OnAfterTransaction function to see if the action was a Change and then check your criteria before triggering your flow.
If your criteria is met then do an AGS call to WFWK.1, passing all of the data elements. If your criteria is not met then just do a Return True so the form continues on as normal.
Terry P
Veteran Member
Posts: 234
2/11/2009 9:06 PM
Drop me a note at pickering@4j.lane.edu with your email address or phone number.
LCM
Basic Member
Posts: 8
2/13/2009 10:36 PM
Thank you David and Terry for pointing me in the right direction. I now have this request functional (although I still need to add a few things) and I have learned quite a bit while doing it. I neglected to add that we have moved to LSF9 earlier and that added some confusion for me since I did not think I could make an AGS call to WFWK anymore.
This is a great site. Thanks again.
Gary Davies
Veteran Member
Posts: 248
3/9/2009 10:45 AM
WFWK still works, it just has been moved to the application product line instead of LOGAN in 9.0
You are not authorized to post a reply.