How to make a nested Required ActionFieldName (Show Field) on ConfiForms?

[Agilan Ampigaipathar]

I'm trying to make multiple ActionFieldNames that show expanded fields when an option is clicked.

For example:

Required ActionFieldTest1 is a FieldName that has 4 multi-select options.

ActionFieldTest1 : Test1, Test2, Test3, Test4

When any of the 4 multi-select options are clicked, it would popup the selection's respective corresponding section. The sections are a radio option with 2 choices that is also required.

Test1 would popup Section1, Test2 would popup Section2, Test3 would popup Section3, Test4 would popup Section4

But, when Test1 and Test2, for example get clicked, then Section1 and Section 2 popups as expected, but the fact that Secton3 and Section4 are also mandatory, there is an error prompt that they need to be filled out despite it being hidden and not expanded as Test3 and Test4 were never clicked. How do I solve this to work as expected where the fields only popups when the corresponding respective parent field is clicked regardless of if other subfields are mandatory?

[Alex Medved _ConfiForms_ · Accepted solution]

If this question is about ConfiForms, as the title says then it is not about Jira software, but about Confluence.

As ConfiForms is a plugin for Confluence

Mandatory fields need to be filled in, making the fields hidden does not make non-mandatory

You need to make the field as not mandatory or set the default, not empty, values to the fields when you hide them

[Agilan Ampigaipathar]

set the default, not empty, values to the fields when you hide them, How do I do this, specifically I know as validation rules, "^(?=\s*\S).*$" checks if its not empty but when and where do I use this? Would the parent field and its child field also have to mandatory when using validation rules? How do I take into account when a fieldname is being hidden on the validation rules?

[Alex Medved _ConfiForms_]

You will need to define your validation rules in ConfiForms Rules for Field Definitions and make them conditional.

See more on our wiki

https://wiki.vertuna.com/dosearchsite.action?cql=siteSearch+~+%22conditional+validation%22+and+type+in+(%22space%22%2C%22user%22%2C%22page%22%2C%22blogpost%22%2C%22attachment%22)&queryString=conditional+validation

[Michael Taylor]

That works okay, until you get above 3 or levels deep of validation. Then it gets too messy.

I found that Smart classifier was much better, and easier. Vertuna's documentation is a little rough to get through, but this example will help you understand.

https://wiki.vertuna.com/display/TEST/Using+smart+classifier+field+built+from+a+from+with+3+columns+-+3+levels+deep+classifier