Forum Discussion
Naming convention of the objects is up to you. But it is generally a good idea to pick some sort of conventional rule that will make sure that a) the object is uniquely named and b) it's clear what the object represents. Things like "Panel44" don't really say what it is. But "panelCustomerServiceDropdown" is much clearer as to what hte panel contains and represents.
Generally speaking, for MOST applications, ObjectType + idStr or something similar is usually sufficient. But each application is differnt and will have different objects and properties and such that will be available to identify the object. You'll need to do some investigation on your own to find the best combination of properties to uniquely identify objects.
I have attached the screen shot of our application, the object browser tree to give you the context.
What is the de facto approaches or practices for the web application? Do we provide every object type a unique idstr? it will be lot of work as you can see the level of panels are quite deep down the tree.