When extending a BASE BC page object using a page extension object, global variables are not exposed from the BASE page to the extended page. I understand that when creating a new object in my extension I have the ability to specify that a global variable on a page object is Protected and then a page extension object based on that page would have access to the variable.
However, how are we supposed to access these variable from the base application when the variables have not been declared as Protected?
Are we to assume that all global variables at some point will be specified as Protected and so we should customize the Base page object now for variables we require access to in our page extension objects? Or are we supposed to mimic the functionality in our extension pages which then potentially requires duplicated code?
We have a very large ISV extension that we are creating and this is a big deal for us. We don't want to get this part wrong and then have to redo it down the road, so any help is greatly appreciated in learning best practices here.

Report
All responses (
Answers (