yes we can also say that. true.
On 1/21/07, David E. Jones <[EMAIL PROTECTED]> wrote:
So, you're thinking of more of a permission system? -David On Jan 21, 2007, at 9:10 PM, Anil Patel wrote: > If we have Form meta data in Database then we can enhance the screen > rendering system to read field visibility attribute from the database. > So lets say, userLogin.userId belongs to Casher User group. So when > rendering a ScreenA::FormX, System will look for visibility > attributes of > fields on FormX as part of ScreenA for Casher userGroup. > > I have seen PeopleSoft does this. > > Regards > Anil Patel > > On 1/21/07, David E. Jones <[EMAIL PROTECTED]> wrote: >> >> >> On Jan 21, 2007, at 6:33 AM, Anil Patel wrote: >> >> > This is great, Can we do this, Save Screen and Form definition in >> > Database >> > (Sceeen and Form widget file will loaded into database.), Party >> Group >> > Preferences set of Entities can be designed to store the >> > information like >> > which field should be visible/hidden for a Party Group.. >> > By doing this we can customize what user sees on the Screen. >> >> This sounds quite a bit different from what Jacques was proposing, >> but if I understand right what you are proposing this is something >> I'm happy to write long and loud against. >> >> What would we gain by putting these things into the database? >> >> What will we lose by putting these things into the database? >> >> I'm interested in your thoughts so I won't answer these quite yet, >> though if you (or anyone) is interested in my answer this is >> something I've written about in the past quite a bit and you'll find >> stuff in the old mailing list archives. Still, I'd rather hear >> other's opinions about it before I express my own, just to make sure >> I don't miss anything that people might not want to say when I come >> down hard on this. As I mentioned above, I have very strong opinions >> about this and these are based on some very bad experiences. >> >> -David >> >> >> >>
