Steps to reproduce:

-Open a Process diagram
-Close one of the container nodes that contains some children.
-Go to Navigator.
-In the Navigator tree select one of the children which are inside the collapsed
Diagram element.
-The Diagram element remains collapsed and therefore the node selected in
Navigator is not visible.


Recommended fix:
UC1  - User is traversing and selecting Navigator nodes - some of these Navigator
nodes correspond to Diagram elements which are in a collapsed state.
- User selects a Navigator node that not visible in diagram because the element
in inside a collapsed container
- Diagram container should auto-expand in order to show the selected navigator node.

Supporting argument for recommendation 
- this is how the the competition's Navigator works relative to collapsed
diagram elements. The elements auto-expand on navigator node selection.
- this is what at least SOME users will expect.

Counter arguments against this recommendation
- Some users may not want auto-expansion. They may want the expansion to occur
only on demand - like DBL-Clk on Navigator node.
[ Problem with this is that our current Navigator / Diagram story is a very
eager sync (as is competition). Eager sync means that simple selection of
navigator node results in parallel selection of Diagram element. DBL-clk on
Navigator node invokes default action for the node.]
- There is no way to re-collapse Diagram from the Navigator, user will have to
switch to Diagram to re-collapse Diagram element. [Should there be a way to
collapse Diagram nodes from Navigator?]

HIE - do you have an opinion? Absent rebuttal, we will implement the recommendation.