In many Products or Libraries (and possibly Projects, etc.), various configurations are set up to accomodate only one or a few types of documents, especially if there are workflow templates assigned to the Document directly in that context that rely on Document attributes for routing, etc. Sometimes it's essential to allow only the intended type; in other situations it's just an inconvenience.
Where only one type can be created, the New Doc wizard skips right to the other attributes, streamlining the process.
OTB, all Document sub types can be created in all Contexts where permissions allow. It's laborious to manage these. Where permissions deny creation, the user has to wade thru quite a bit until they get an error message.
in general, in all of our special-purpose libraries, we only allow one sub type of document - for which that special Library exists.
Two current workarounds:
1. In the OIR, specify a folder for the type and a "folder does not exist" for types that are not allowed. Downside: No error message until the user attempts to create.
2. In the OIR, specify a lifecycle that doesn't exist for types that are not allowed. This has the advantage of not automatic prevalidation such that the user does not see any types specified this way.
Idea: Provide a much easier way for admin's to select which type(s) can be created in each context.