From what I can tell, mapping all of the parent objects is only really neccessary in the Mapped Objects section and not so much in the alias section. Therefore, it would be nice if only the page obje...
This is a manual process... I agree, it would be nice to have this automatically done, but the question is... how does TestComplete "know" which objects are the ones you want and which ones aren't? It's not always clear. For example, we have a web application where it may seem like certain panels are not necessary for the automation. However, we use them for referencing certain attributes and contents that, while not something a user would interact with, are needed in order to validate certain functionality. So, we include them in the Alias even though not strictle necessary.
I'll vote this one up, but I think it's going to be a bit tricky to "teach" TestComplete some algorithm to determine which objects to include in Aliases and which ones not to.