-
Type: Bug
-
Status: Resolved
-
Priority: Minor
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 2.9
-
Component/s: None
-
Backlog priority:150
A common problem when configuring the "new" document is that when the current container does not define avec sub types, hitting the button "new" will have no effect (and produce a javascript error)
=> add a filter condition like the default "new" action on Nuxeo and produce a validation error when user explicitely wanted the "new" button to be available but defined no sub types for this document (see NXS-1277)