Hello,
I have seen a few posts on this and did not see any mention of this in the 10.4 beta information, so I was curious where both of these items were at:
- Child status inheriting 'unmanaged' status of parent/dependency. I can't imagine why this great feature (children getting unreachable status if a dependency is down), left out the same logic for the dependency being unmanaged
- Related to the above point, if the behavior of children is not affected by an unmanaged parent/dependency, at least give us the ability to unmanage a group
Is there an update - will this be in 10.4?
I just moved to 10.3 from being on 10.0 for a long time and was excited to finally do away with all 400 of my site alerts that I had to set up for suppression of child nodes, only to find that the implementation of this great feature doesn't follow the unmanage status... unmanaging is probably the second best reason to have built-in dependencies and groups.
Most of the posts are unanswered, so I figured I would ask again.
Thanks!
