RELATED IDEAS
enable/disable sub-specifications
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
all product owners using specifications |
What impact would it make? |
Less specification templates required (partial use) |
How should it work? |
I've created a specification that exists of 4 sub-specifications. When de-activating 1 of the sub-specifications by de-activating the relation with its parent specification ALL specification input fields of the sub-specification will be disabled. |
Why is it needed? |
It reduces the number of unique specification templates because it allows partial use by enabling/disabling sub-specifications (child specifications). |
Additional feedback, background or context:
I forgot to mention inriver feedback on this Item when I reported it as a bug:
This case has been discussed internally by our senior product experts, and the consensus reached is that the current behavior you describe here is the intended functionality of the product as it stands, unfortunately. The disabling of a link is generally only applicable in the context of channels, where it is used to prevent a hierarchy of being followed any further down an existing link structure.
To have the specification fields removed the link itself must be deleted, however this will also delete any data stored in those specification fields, which might be undesirable depending on your intended application of this. There currently is no way to make specification fields hidden or Read-only by disabling the link to the specification templates.