Workflow Change Event Causes Form Elements to Fail to Work
We have an issue that has surfaced in Workflow Forms (5.33.1, 5.34.0). Referring to the screen cap below... Form Element A has a Change Event to populate the descriptions for both B and C - which works great. Form element D fails to load any values to pick from if I use 'Depends On' (element A). In fact, any change event in A at all (even a blank sub workflow) prevents the loading of values in D. If I remove the change even in A, then I can use the Depends On option, but then can't actually populate B and C. Anyone else seeing this?
-
I never use the Depends On property myself, I instead put the logic I need in the upstream element's .change event. Regardless, it kind of seems like a bug to me.
I want to say that your described behavior is why I do that, I seem to recall fighting with this like 3 years ago, but honestly I'm not sure of the reason I do it anymore (so if the issue only just popped up in WFs that previously worked then that's probably not it). Maybe there was some other or similar reason I started doing this, maybe it's just the way I do; I certainly like having a the added control and flexibility of managing my elements manually even if it takes a few extra activities. I get a lot of cases with multiple upstream dependencies so maybe that's the reason I am the way I am. ¯\_(ツ)_/¯
Lately, on a side note, I've been calling a lot of Subworkflows from the multiple upstream elements' .change events and those things have been a game changer for me.
0 -
Hey Zack - Thanks for your reply. I agree it's a bug. I will attempt to file that today.
I do agree that just putting the logic only in change events upstream is an alternative and what we used to get around this issue. I just put the info needed for D in the change event in A.
0 -
They key here, per support, was to add a 'Propagate Form Event' activity at the end of my change event in form element A. Works like a charm now.
0
Please sign in to leave a comment.
Comments
3 comments