Skip to main content

Hello,

I am trying to digitize a complex financial decision process in which the user is able to first toggle to select or deselect several categories, and based on these decisions additional fields allow further specification of the case's details. These decisions happen on multiple levels, asking the user to further specify his selections. If a setting is not active however, further specification is not required. (Imagine this as a decision tree which only adds branches when required)

 

In this scenario, the very same form elements might show up at many different places in the process, and would influence different variables each time. However, the user should only be confronted with those forms if it's relevant for the actual case (if he/she rejected an option, there is no need to further configure it).


Rebuilding the form for every possible scenario would cause it to become enormously big and complicated, with hundreds of widely identical elements.
A soultion to this would be a form template container which is repeatedly loaded into the workflow and assigns a distinct variable name every time. I have not been able to find such a function.

Does anybody know whether such functionality exists or could suggest a workaround?

 

Thank you for your help!

 

M. H.

You can group controls(https://help.nintex.com/en-US/nwc/Content/Designer/FormControls/Group.htm)  and hide/show on bulk but currently no way to have a container that will keep making new variables. Groups and using rules may be enough, but without knowing the exact requirements it is hard to say. You could try suggesting this functionality on uservoice(https://nintex.uservoice.com/).



 



 

@mh_informotion like @leighburke said, I think the group control will be your best bet currently. Once you have created your initial grouping of controls, you can then create a copy of them:





 



And then assign custom names to the copied controls:





 



Hope that helps!

@butlerj Thank you very much for your suggestion. I have considered this option as well, but it only seems to work within a single form. In other words, if I want to reuse the group in another form, I have to rebuild it entirely.



 



I might suggest this feature as there should also be other use cases for such a template function.. 



Thanks for your help!

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings