I am seeing that I can't add variables on one branch AND on another. Is this by design?
I must choose one or the other.
Thanks
I am seeing that I can't add variables on one branch AND on another. Is this by design?
I must choose one or the other.
Thanks
What behavior are you getting exactly? I just built a test workflow and I didn't have any issue trying to add variables to more than one Set Business Process Variable activity.
It only populates variables for one or the other.
Okay, so based on what Miruna said it only uses one update. You probably want to branch them at the same point in the workflow and make sure your activity updates all of the relevant variables.
Another option would be to create the token outside of the condition and leave it blank or set a default, include it in the final business process variable activity, then only change the value of the token in your conditional branch.
Yep. I have already implemented a workaround. It just seemed to be counter intuitive for the activity to work that way. Thanks for the ideas!
Fascinating. Just came across this issue in production and it is definitely counter-intuitive AND not documented anywhere!
Please update the documentation and/or Set Business Process Variables widget to advise end-users and other customer that the last activity to run is the one that sets the variables in the form.
-- Update --
For perspective, we had a process that would run in-between form submissions to ensure data in the form was always up to date based on external datasources (such as CRM).
Although less-efficient, I have been under the impression that we could call a workflow that would move through and update blocks of the form variables conditionally as needed. Looks like we'll need to rethink how we do this.
@████████
@████████
Has there been any official update on this?
I just found out that I have been experiencing issues due to the same limitation.
I have 2 "Update BP Variables" activities on the same branch so both are being traversed however only the 2nd activity that is further down the branch is the one that actually pushes its update to the forms process variable.
Currently working on work around of using tokens and updating all forms vars at the end of the workflow.