Stream: implementers
Topic: Composition Sub-Sections
Richard Kavanagh (Feb 02 2017 at 12:49):
When using Forge to profile COMPOSITION we are slicing the "section" so as to profile the primary sections in the COMPOSITION. We do however have requirements to also have some SubSections. When you Slice a child section it does not reveal all of the properties for the section.
Does anyone else create profiles with "subSection" requirements in COMPOSITION and if so how do they do it? @Michel Rutten
Mirjam Baltus (Feb 02 2017 at 12:57):
Hi, thanks for reporting this. We would love to have Forge handle recursive delarations the way you indicate. The new snapshot generator is capable of handling it, it's just the Forge UI that doesn't reflect that yet. It is on our roadmap to be implemented.
Mirjam Baltus (Feb 02 2017 at 13:00):
I'm afraid for now you'll have to do this by hand. You can make some changes to the top-level section, save the XML and then change the XML paths to Composition.section.section. If that is done correctly and you reload the XML in Forge, Forge will then be able to show you the sub-elements of the sub-section.
Richard Kavanagh (Feb 02 2017 at 14:03):
Would we change that in the "Differential" or "Snapshot"?
Mirjam Baltus (Feb 03 2017 at 10:05):
I've tried it in the differential, because that's easier to read. It's a bit of a hassle, but it worked.
Last updated: Apr 12 2022 at 19:14 UTC
