Stream: conformance
Topic: Forge - extending a default slice
Jonny Rylands (Sep 06 2016 at 10:41):
@Michel Rutten Hi Michel, noticed something in Forge - not sure what is the correct behaviour. If you extend a 0..*element, then slice the element and add a slice, the extension disappears from the treeview, however is still present in the differential XML.
Jonny Rylands (Sep 06 2016 at 11:00):
The extension appears after the setup slice but before the added slice. I'm assuming this means that the "default slice" (i.e. when slice rules are open or openAtEnd) has the extension, but the added slice does not?
Michel Rutten (Sep 06 2016 at 11:03):
@Jonny Rylands When you click the Slice button, Forge hides all existing child elements constraints of the selected element in the UI. However the constraints are still present in the in-memory object graph and will still be serialized to XML. I'd like Forge to also provide access to default constraints of a sliced element, but I'm struggling how to model this in the UI without confusing the user. I have some ideas about it, but currently this is not on our near-term roadmap.
Jonny Rylands (Sep 06 2016 at 11:12):
OK thanks. Possibly add extra slice with a "(default)" suffix to the name? Appreciate it's tricky to make it clear to the user!
Michel Rutten (Sep 06 2016 at 12:26):
Yes, I was thinking along those lines. I've made a ticket in our Jira system, eventually I'll get around to this.
Lloyd McKenzie (Sep 06 2016 at 14:48):
+1 for "(default)"
Chris Grenz (Sep 09 2016 at 00:37):
Except it's not the default slice, it's things that apply to all slices. If I slice Patient.name into "officialName" and "usualName" and then add (not in either slice) the Patient.name.given element with min=1, then given must always be present regardless of the rules in the slices. So, maybe (all) rather than (default).
Chris Grenz (Sep 09 2016 at 00:39):
Would be nice though to have a default too...all elements NOT in one of the slices.
Last updated: Apr 12 2022 at 19:14 UTC
