As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
<xs:complexType name="deliverableReference"> <xs:sequence> <xs:element name="ref" type="xs:anyURI" minOccurs="0" maxOccurs="1" /> <xs:element name="name" type="xs:normalizedString" minOccurs="0" maxOccurs="1" /> <xs:element name="guidance" type="xs:string" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:complexType>
<pm:deliverablereference> <pm:name>Some deliverable</pm:name> </pm:deliverablereference>
<pm:deliverablereference> <pm:ref /> <pm:name>Some deliverable</pm:name> </pm:deliverablereference>
Thanks Harry, I've managed to resolve it using a different mechanism and the Alfresco team is looking at the problem I was having.You can find the files attached to the JIRA issue I created. And here is the solution:By changing the ref attribute to an element… <xs:complexType name="deliverableReference"> <xs:sequence> <xs:element name="ref" type="xs:anyURI" minOccurs="0" maxOccurs="1" /> <xs:element name="name" type="xs:normalizedString" minOccurs="0" maxOccurs="1" /> <xs:element name="guidance" type="xs:string" minOccurs="0" maxOccurs="1" /> </xs:sequence> </xs:complexType> And then, I discovered the problem was because I wasn't writting a <pm:ref> because there was no "reference".So I just wrote out a blank pm:ref and it all worked. So the code for a deliverable reference, rather than being: <pm:deliverablereference> <pm:name>Some deliverable</pm:name> </pm:deliverablereference> Becomes: <pm:deliverablereference> <pm:ref /> <pm:name>Some deliverable</pm:name> </pm:deliverablereference>