Adepters:
I'm seeing a very strange behavior from Epic (5.2 patch M120). Our schema has a definition similar to:
<xs:element name="defList">
<xs:complextype>
<xs:sequence maxoccurs="unbounded">
<xs:element ref="defObject"/">
<xs:element ref="defMeaning"/">
</xs:sequence>
...
A simple definition list with one or more required pairs of object/meaning elements. Works great! However, when I insert a defList in Epic and it auto-inserts the required defObject and defMeaning, I can then place the cursor immediately before the defMeaning element and Epic shows that I can -- and allows me to -- insert another defMeaning. Of course, it then fails a check completeness. My question is, why would Epic show me an invalid element for insertion?
Dave
Siemens
