Ability to configure different default categories for same node item type based on document category

[ptc-4058643]

Document - CS122709 decribes how the content of the Document > Create menu is generated in Integrity. For example: Requirments Documents, System Requirements Documents, SW Requirements Documents...

Those are all Requirements Documents, just different categories.

For the Requirement node item, it is possible to define one default Category only.

There is the need for the functionalty to configure the default category for node items based on the document category. Meaning, different default categories apply for the same node item type.

For example,. in a SW Requirements Document, Category is SW Requirements Document, then node item Default category should be SW Requirement. In an EE Requirements Document, it should be EE Requirement default in node item, etc.

[mrump]

We would love to see that for the following reason as well.

  We need the opportunity to move or copy nodes from one document type to another

e.g.

 A System Req. Document contains a System Req. Node. This Node turns out to be a SW Component Req. as well. Therefore it shall be copied into the SW Component Req. Document.

Currently this is only possible if all "xyz Requirement Document" Items use the exact same the same Node type (Requirement, and Shared Requirement) otherwise they are not exchangeable. This can and will lead to "mixed categories" documents sooner or later. And these "general purpose" requirements most times have either to few or to much fields than can hold required additional infos.

But if i want to create a Special Document type e.g. a SW-Component Req. Document type that allows only SW-Component Req Nodes, I have to create a special Node type as well to constrain the available categories. Only the shared Node can be reused.

But creating a special node type automatically disables the chance to copy or move nodes as described above.

So we loose anyway 😞