Good morning. I've always thought about component exceptions (specifically for compliance) as attributes of a component rather than an object in and of itself. This may have been a dream or just really wishful thinking, but I seem to recall this method changing (or planning to change) to allow a bit more flexibility by having the exception defined as its own object that can be related to multiple components. This would allow one point of management for adding or removing components and simplify reporting as the current method relies on all the exceptions happening to have the same name (which works until you add more down the line and enter it in wrong).
Am I dreaming or does this actually exist? If it's just clear blue sky, I can certainly submit it as an idea but I certainly don't think that it was mine to start with.