Stream: implementers
Topic: Forge 'valueString' workaround
Brian Reinhold (Jul 03 2017 at 13:12):
I am not sure how serious this is but when selecting a value[x] that is a valueString, Forge does not provide the normal filtering of the remaining choices. It creates an element that looks like this
<element id="Observation.component:labelStringComponent.valueString:valueString">
<path value="Observation.component.valueString" />
<sliceName value="valueString" />
<definition value="The value given by the string in the label string attribute." />
<min value="1" />
<type>
<code value="string" />
</type>
</element>
But what it needs is to create an element pair that looks like this:
<element id="Observation.component:labelStringComponent.value[x]:valueString">
<path value="Observation.component.valueString" />
<sliceName value="valueString" />
<type>
<code value="string" />
</type>
</element>
<element>
<path value="Observation.component.valueString.value" />
<definition value="This is the value of the label string attribute." />
<min value="1" />
</element>
If you hand-edit the xml as above Forge will re-load the xml and display the structure definition correctly. I am not sure how critical the element id is in getting the Forge tool to display the structure definition correctly. If you do any editing in Forge and save it, you might lose your entries so make a backup copy so you can rebuild it.
Last updated: Apr 12 2022 at 19:14 UTC
