Critical Project contract-management-nuxe is holding two workflow definitions with a similar "start" and "stop" nodes.
Problem is that the same schema with the same name is generated for both, see contract-management-nuxe-10.2.0.jar
and generated extensions.xml content:
<extension target="org.nuxeo.ecm.core.schema.TypeService" point="schema"> <schema name="bccontract" prefix="bccontract" override="true" src="data/schemas/bccontract.xsd" /> [...] <schema name="var_start-node" prefix="var_start-node" override="true" src="data/schemas/var_start-node.xsd" /> <schema name="var_stop-node" prefix="var_stop-node" override="true" src="data/schemas/var_stop-node.xsd" /> [...] <schema name="var_start-node" prefix="var_start-node" override="true" src="data/schemas/var_start-node.xsd" /> <schema name="var_stop-node" prefix="var_stop-node" override="true" src="data/schemas/var_stop-node.xsd" /> <schema name="var_BCContractValidationWf" prefix="var_BCContractValidationWf" override="true" src="data/schemas/var_BCContractValidationWf.xsd" /> </extension>
TODO
- When a workflow is created, instead of using an hardcoded id (start-node & stop-node) task id should be generated dynamically like when we drag and drop them from the library.
