Change ENTRY.work_flow_id to ENTRY.workflow_id


in Content.xsd Entry class a has wrongly a work_flow_id property instead of workflow_id



Thomas Beale
February 12, 2016, 5:45 PM

I think our provisional approach on this was to create the current XSD as an 'R1' version of the XSD, and then fix this problem and release the fixed version as 'R2'. I.e. use proper versioning on the XSDs, independent of the underlying RM release.

Pablo Pazos
January 9, 2019, 5:32 PM

I'm OK with the fix, and would like to see some tool generating schemas to avoid these typos introduced by manual edition of the XSDs.

Seref Arikan
January 9, 2019, 6:43 PM

I'm also against this change. We have lots of real data using this field and the data is going through an XML based pipeline.

Thomas Beale
January 9, 2019, 7:01 PM

Is there a way to create a synonym attribute name in XSD?
Re: generating, we can look at generating from MagicDraw. When I get a moment, I'll do an XSD generation and see if it is any good.

Pablo Pazos
January 9, 2019, 8:37 PM

@Seref, the change should be reflected on a specific newer version of the XSD ITS, current implementations should not be affected by this, are just implementing a previous valid version of the XSDs.


Sebastian Iancu

Raised By

Sebastian Iancu


Affects versions