Edit Option 'ReadOnly' doesn't propagate to child sections and if the conditions are set for nested sections, then edit mode of the parent is not considered when evaluating the edit mode of the child.
Steps to Reproduce
Scenario-1: Edit option does not propagate to child sections.
Create section a with a dynamic layout.
Add section b to the dynamic layout, and in the Presentation tab, make it read-only.
Add section c to section b.
Add controls to both section b and c.
Add read-only conditions to controls in both section b and c.
Expected behavior: Conditions should evaluate to false. Section B and C to be displayed as readonly.
Actual Behavior: Controls in section b will still be read-only, controls in section c will be editable.
Scenario-2: Edit mode of the parent is not considered when evaluating the edit mode of the child.
1) SectionA includes SectionB with Readonly condition 1
2) SectionB includes SectionC with Readonly condition 2
3) SectionC includes SectionD with Readonly condition 3
4) SectionD includes two text inputs without any Readonly condition auto
Actual Behavior: Section D is displayed as editable as per condition 3.
Expected Behavior: Section D should be displayed as readonly whenever condition 1, condition 2 , condition 3 is evaluated to true.
For Scenario-1: The pzsectionBodyIncludeInCell function removes the "SectionReadOnly" param after it has included the section. This causes a problem in any trailing controls of the parent section because the "isControlEditable" API incorrectly depends only on "SectionReadOnly" and the read-only when/expression. The "isControlEditable" API needs to additionally call the "hasInputEnabled" API to check the edit mode of the control.
For Scenario-2: In PZSECTIONINCLUDEINCELL rule, consider the edit mode of the parent when calculating the edit mode of the child section included inside a cell.
This issue is resolved by hotfix item HFix-29793.