https://community.appian.com/discussions/f/best-practices/14274/why-are-the-rules-on-what-layouts-can-be-nested-what-they-areJust curious about why Section Layouts cannot contain other Section/Form/Dashboard Layouts and so on for other Layout Components, is related to restrictions in the Java that backs SAIL forms or is it a best practices thing to try and keep interfaces fromen-USTelligent Community 12https://community.appian.com/thread/64431?ContentTypeID=1Mon, 04 Feb 2019 17:33:09 GMTd3a83456-d57b-489c-a84c-4e8267bb592a:482e1404-98e2-4784-8ea6-f8884bbaee89Mike Schmitt<p>The only two rules I know off the top of my head are:</p> <ul> <li>a!formLayout cannot be embedded underneath any other layout type (i think this also applies to a!dashboardLayout, but i&#39;d have to double check).&nbsp; It must be the top position, which makes sense because the a!formLayout should reflect the entirety of whatever form the user is currently seeing, and any other subcomponents can be governed by using items contained in the formLayout.</li> <li>a!sectionLayout cannot be a child of another a!sectionLayout.&nbsp; I think this might be a bit of an outdated restriction at this point, going back to when forms and sections could only contain two columns and the experience was overall a lot more restrictive than now.&nbsp; However I suspect they&#39;re keeping this restriction at least for now because even if you have sections nested, there are no graphical clues provided onscreen which hint at the hierarchy, as all sections appear in-line and roughly equivalent to each other (though this would get more complicated once you consider the issue of multiple columns).&nbsp; AFAIK most use cases for having nested columns are currently handlable by just having subsequent, non-nested sections; and when you need nesting, we now have boxLayout which provides a pretty flexible and nice-looking alternative.</li> </ul><div style="clear:both;"></div>