Login
Register
Search
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Forums
Integration / Customization
IPA/ProcessFlow
Branch
Home
Forums
Jobs
LawsonGuru
LawsonGuru Letter
LawsonGuru Blog
Worthwhile Reading
Infor Lawson News Feed
Store
Store FAQs
About
Who's On?
Membership:
Latest:
Jeffin Joy
Past 24 Hours:
0
Prev. 24 Hours:
0
Overall:
4988
People Online:
Visitors:
32
Members:
0
Total:
32
Online Now:
New Topics
Top Forum Posters
Name
Points
Greg Moeller
4184
David Williams
3349
Kat V
2984
Woozy
1973
Jimmy Chiu
1883
Kwane McNeal
1437
Ragu Raghavan
1377
Roger French
1315
mark.cook
1244
Chris Martin
825
Forums
Filtered Topics
Unanswered
Unresolved
Active Topics
Most Liked
Most Replies
Search Forums
Advanced Search
Prev
Next
Forums
Integration / Customization
IPA/ProcessFlow
Branch
Please
login
to post a reply.
2 Replies
0
Subscribed to this topic
53 Subscribed to this forum
Sort:
Oldest First
Most Recent First
Author
Messages
TommyT
Veteran Member
Posts: 58
2/21/2011 3:21 PM
I have a situation with about 25 conditions that a flow has to evaluate. Am I seeing things or can a branch only handle 10 conditions? Do I need to split into several branch nodes at this point in the flow?
Shane Jones
Veteran Member
Posts: 460
2/21/2011 4:00 PM
Split
Yep.... Sounds like you will need three branches to go 25 different directions...
I have not tried it but I would think if you know jscript and you are using the branch to set a variable you might be able to do that in an assign with added script and a case function - but I usually just branch to a branch....
Shane
Woozy
Veteran Member
Posts: 709
New Poster
Congrats on posting!
2/22/2011 4:56 PM
Split
If you are trying to branch to different places with each option, then you'll have to do multiple branch nodes. However, if you are just evaluating to do variable assignments (or if this will simplify your branching), then JavaScript is the ticket.
I've done something similar using JavaScript Assign nodes using IF-THEN-ELSE stacks rather than CASE (though I'm not sure why I didn't use case instead...). The only trick is ensuring that the syntax is exactly correct - don't forget the semicolons.
if (vOption=='1')
{
vDestValue='A';
}
else if (vOption=='2')
{
vDestValue='B';
}
else if (vOption=='3')
{
vDestValue='C';
}
else
{
vDestValue='';
}
I'd think that a case (actually switch) statement would be better:
switch(vOption)
{
case 1:
vDestValue='A'
break;
case 2:
vDestValue='B'
break;
case 3:
vDestValue='C'
break;
default:
vDestValue=''
}
I hope this helps. Good Luck!
Please
login
to post a reply.