Since I started using Geopak SS3, as soon as I saw all the options listed as End Condition Properties under Component Properties and under Point Properties, plus Point Properties' Horizontal Feature Constraint. It took me quite a while to figure out how they all work together.
In the case of Horizontal Feature Constraint, other than the obviously reduced functionality (not being able to specify a target alias), I'm still not sure how it would compete with the component's end condition (though I'm guessing the end-condition component would override), but that wouldn't be obvious if you were limiting your search to the point properties. New users may not expect that they need to consider the component properties too because it is quite obvious that the Horizontal Feature Constraint is right there on the point properties.
Further, because a given point might be a member of multiple components, it might be a member of one or more end-condition components. And how does all of this work? In my experience, such cases behave either irregularly or in a way that I couldn't hope to expect, so I write it off and find that I need to unmerge points.
Again, because a given end-condition component have more than two member points it is not obvious what to expect the component to do if more than one of them has been set to Check for Interception, etc. Complicating this even more, one or more of those points might have set Do Not Construct so it is even more complicated to determine how they all interact.
The enhancement suggestion I have is to present all point conditions in the component properties window. The rest of this suggestion could be rendered a couple different ways, but for now I'll suggest that you present a table of all the member vertices and display each of those points' end-condition properties. Even better could be to allow the user to modify those options within the component properties window. If one of these points is looking for a Horizontal Feature Constraint, that should be noted.
Also to present all component end conditions (or just the prevailing one in the case that only one component's condition is valid among many) when viewing the point properties. Probably disable Horizontal Feature Constraint where it conflicts with Check for Interception.