With Find Logic for an element, sometimes the Find Logic uses Text Content on initial element recording and other times the Find Logic uses ID. 

I request for functionality in Test Studio to prioritize what logic is actually used in the Find Logic.  Generally speaking on the applications I have used Test Studio to automate testing, there are elements that has specific text content on a page.  These elements start out with their Find Logic to have TextContent since I think that is the most unique identifier about them.  But as TextContent is concerned, there is a possibility of change of text on that element.  So I would target the element with the ID of the element or the ID of a parent element and then use tagindex to be specific.

After initial recording, I put in the extra time to modify the Find Logic to fit my need.  

If an element does not have an Id, but the element has a direct parent (only 1 level above) element with an ID, use that parent element and then the additional find logic for specific element over using TextContent. 

Having this functionality of Find Logic prioritization will hopefully provide a general consistency to improve my user experience.