So I understand that there is no dropping of BO's on webforms, you create the BO reference in your ApplicationBasePage and it available to the entire website. Check.



Does that mean I need to create many BO's if I need them populated differently? For instance I have a BO that contains codes used to fill all my applications dropdowns, I have a BO on each form that calls a fill specific for the proper contents of the BO based on a "codetype" field.



So the generic question is this, since BO's essentially don't get instantiated into individual objects on a webform where I can call different fill methods, is the answer to make many BO's specified to their task, or am I on the wrong path?

Keith Chisarik

My need is actually for a HR person to be able to review a lengthy application. So the data should not be editable.

I use the same form as when the applicant does data entry for application review by HR staff, this saved (time and budget)having to create a PDF or report of the application, they just go to the app via a "special" link and the form knows to pull up the corret populated application for review and print. So I dont think I can allow the data to be changed.

Keith Chisarik

If this is the case, why not bind to a label? On the web especially, this can make this type of thing far easier to work with. I am just throwing some ideas out there.