Details
-
Improvement
-
Resolution: Fixed
-
Minor
-
3.1.1
-
None
-
When accessing doctypes via the REST API currently Blueprints are returned that are actually no doctypes. For simplicity we should assume that doctype candidates without metadata, properties, and sections should not be considered doctypes.
This may be problematic for doctypes without model and without a property value that is used to derive doctype information. But we need to be stricter here since this service should support use cases where users select a doctype in the UI.
When accessing doctypes via the REST API currently Blueprints are returned that are actually no doctypes. For simplicity we should assume that doctype candidates without metadata, properties, and sections should not be considered doctypes. This may be problematic for doctypes without model and without a property value that is used to derive doctype information. But we need to be stricter here since this service should support use cases where users select a doctype in the UI.
