The order that fields are displayed when using parent/child web content structures has been reversed from 6.2

• Type: Bug
• Status: Closed
• Resolution: Fixed
• Affects Version/s: 7.0.X EE, Master
• Fix Version/s: 7.0.0 DXP FP26, 7.0.X EE, 7.0.4 CE GA5, 7.1.X, Master
• Component/s: Dynamic Data Mapping, Dynamic Data Mapping > Form Builder
• Labels:
  • liferay-digital-enterprise-70-sp5
  • liferay-fixpack-de-26-7010
• Branch Version/s:
  7.0.x
• Backported to Branch:
  Committed
• Fix Priority: 1
• Git Pull Request: https://github.com/liferay/com-liferay-dynamic-data-mapping/pull/300

When hierarchical web content structures were used in previous versions of Liferay, fields from the Parent structure appeared before fields from the child structure. DXP reversed this, which leads to situations where the order of fields for customers' web content structures doesn't make sense anymore. As referenced in this comment this UI change was not intended and should be reversed.

Steps to Reproduce
In Liferay DXP:
1. Create web content structure called 'Parent structure'
2. Add a text field called 'Parent text field'
3. Save 'Parent structure'
4. Create web content structure called 'Child structure'
5. Set 'Parent structure' as parent
6. Add a text field called 'Child text field'
7. Save 'Child structure'
8. Create new web content item using 'Child structure'

Expected:
'Parent Text Field' appears before 'Child Text Field'.
Actual:
'Child Text Field' appears before 'Parent Text Field'.