A forms subworkflow displaying another form disables ability to set initial parent form element properties
I have a parent form (form1) and when a button is clicked it launches a subworkflow. I want to use this subworkflow to update the text of the parent form1 but i want to ask the user some questions (form2) based on form1 results. When I try to update the text in form1 after display form2 in subworkflow, it fails with this error message in the console :
Error in footer element's clicked event in a Display Form activity: The form does not contain this element: [object Object]
I've attached a workflow that I created to demonstrate this issue.
I've used both text1 and =$form1.state.text1 as the element ID's in the Set Form Element Property
I am assuming that since form2 was loaded the connection back to form1 is lost until that form1 is loaded again.
-
Hello Nelson,
Thanks for providing a sample workflow and reproduction steps. I've filed an issue as I wasn't able to find a workaround/fix for this error either. There is likely a loss of context within the parent event during execution of the second form.
Thanks, Stefan
0 -
@Stefan Schweigert? - I noticed this isn't resolved in 5.6, is there any update on this?
0 -
Hi Nelson,
I've raised this issue again with the development team to hopefully look at soon.
Thanks, Stefan
0 -
Thanks Stefan!
0 -
@Stefan Schweigert? What's the latest on this issue? Still getting this error with nested display forms.
0 -
Hi Chris,
No updates on this issue yet. In order to support this scenario, it might cause unintended changes to existing workflows.
Thanks, Stefan
0 -
@Stefan Schweigert? - It's been a while for this issue. I'm running in to this again with a different workflow...but in this case I would like a element in my parent workflow to re-load when the subworkflow form is completed. Is this possible or is this the same issue I was dealing with two years ago? Thanks!
0 -
Hi Nelson,
This issue is still outstanding but is on our road map for the next few releases. I've included your interest in the comments.
As mentioned before, the change will be far-reaching and needs to be confirmed that no existing workflows will be affected.
Thanks, Stefan
0 -
Any update on this? I've just encountered a similar situation. My subworkflow form opens but just hangs with the three "thinking" dots flashing. No errors being displayed in the developer console.
0 -
Hi all,
Yes, this work was completed in GXWF 5.18 and made available in Web and Mobile in the 5.10 releases. The change now allows you to use the Element input for Activate Form Element, Clear Form Element Error, Filter Form Element Items, Get Form Element Property, Hide Form Element, Set Current Form Element Item, Set Form Element Error, Set Form Element Item Property, Set Form Element Items, Set Form Element Property, and Show Form Element activities to specify a particular form's element to interact with.
There is also a new "Target Form" input to specify a different form for the Add Form Element activity.
Thanks, Stefan
0
Please sign in to leave a comment.
Comments
10 comments