Can accommodate this need by using a huge number of different Windchill "Document soft Types" (sub types of WTDocument or Reference Document) but this may not be necessary or the best approach.
Different sub types allow:
- different soft attributes
- different user permissions
- different lifecycle / revision series
But - All 71 "types of (business) documents" could share one Windchill "document type" if you set up for either:
A) All 71 use the same Windchill states, Revision series and method to change state (the content files for each can be different); with this, changing state can be via different processes by either having users manually selecting the correct process or the system branching on type (in Promotion or Change processes)
B) Each is stored and managed in a separate Windchill Library; in each Library, a different appropriate Lifecycle / Revision series is assigned on creation via the OIR for that Library which can override Site/Org configurations. The methods to change state are applied (via the OIR used in that Lirary); user permissions can also be managed in each Library distinctly.
This "design" of the Windchill configurations is every bit as involved as the system level design of any product - and has major, major impact on the users. It's worth a lot of planning - and prototyping / testing. The one hard fact above is that different types are needed to use different attributes - but look carefully at the business purpose of the attributes.
