Parameters to be passed along with jump to later steps
Pegasystems
US
It sounds like you'd be better off encapsulating the parameterized part as an inner activity so instead of merely branching, you'd have both branches call the same inner activity with the appropriate parameters.
PEG
US
I would create 2 Map Value rules which map the auth code into the appropriate MessageCode and MessageDesc. (It may be possible to do this with a single, or cascading rule, but I'm not sure about that). You would then call Property-Map-Value on the first map value to get the MessageCode and insert that into a parameter. Then call the second Map-Value rule to get the MessageDesc and insert that into a parameter. Then do the single Property-Set.
Your Map Value rules will have as many rows as you have auth codes.
Cognizant
GB
Alternatively, you may also want to try setting MessageCode & MessageDesc (with appropriate When conditions) using a Data-Transform rule, instead of an Activity rule.
If the use of Activity is must, then I would like to add by saying: try to avoid Jump conditions because we must remember that Activity only supports jumping to a later step, because the steps are always procedural.
Bank of America
IN
Pegasystems Inc.
IN
As far as I understand, you are looking to refactor this so that all message's setting is moved to one place for better maintainability.
But my concern is that even if find a way to pass params in Jump to later step, that step should still do something. Then why not set params in that step only and then finally jump to a step which takes those params and set into actually output property?
Let me know if I am missing anything here.