Document-like features (cases, case items, routing steps) sometimes need to be filtered from default types listings, sometimes need to be shown.
The document types contributed for these features also need to be filtered, but are not using the same criteria.
Examples:
- default doc type Case, CaseItem and DocumentRoutingStep are explicitely filtered from "Extends" selections, all document-like features should be (this is the case for now). Their schemas also.
- these default types appear in container types/accepted children types, but equivalent features (cases, case items, etc...) are not displayed (but they should be) => quick fixed by
NXS-698 - cases and cases items should appear in actions or events filters but only default document types appear => quick fixed by
NXS-699
Same problem appears for validation of available schemas/doc types (quick fixed by NXS-693).
A generic management with boolean markers should be developed instead.
- is required by
-
NXS-693 Erroneous validation errors on Case feature type
- Resolved
-
NXS-699 Add cases and case items to document types shown on events and actions features
- Resolved
-
NXS-698 Remove standard documents configuration in CMF for now
- Resolved
-
NXS-701 Add back standard documents configuration in Studio CMF
- Resolved