Under Consideration

Form Hierarchy Issue

Let's assume we have a form called "Form A" (reusable, not directly associated to an activity). Let's say this form has some logic in "Actions & Validations" that makes a field editable or not.

If we reference "Form A" from "Form B" and we make it readonly, then, during execution, "Form A" still executes Actions & Validations and the field is editable even though its parent field has made the whole "Form A" readonly.

This behaviour is also seen when "Form B" is a process Summary Form.

Best Answer
photo

Dear Jaime,

According your question, this situation arises because it is the behavior defined for reusable forms. In this case, these forms will not give the expected behavior therefore must create a form for that particular case.

Regards

photo
0

This also happens if you have a Tab Container and make a tab readonly and inside this tab you reference a form with Actions & Validations ("Form A" in the example).

photo
0

Dear Jaime,

According your question, this situation arises because it is the behavior defined for reusable forms. In this case, these forms will not give the expected behavior therefore must create a form for that particular case.

Regards

photo
0

This might not be a problem since it is how it was designed.

I would like to change this conversation to an idea since I believe Actions & Validations hierarchy needs improvement especially when you are composing forms from entity and process forms.

There is no way to specify priorities and conflicts happen when child forms also have Actions & Validations .

photo
0

Dear Jaime,

According your request, we have changed it as an idea.

regards