daniel.broomall - Monday, May 21, 2007 2:59 PM:
Quick question ... have you considered (or already implemented) field level security? As far as I can tell, I don't see it employed anywhere and I wasn't sure if you were considering that type of security for future releases. I'm sure I'm not the first to ask, but I know my users will be interested in controling data entry to that level.
Thanks for your time.
Bill - Monday, May 21, 2007 3:42 PM:
Well, I don't think this is exactly what you mean, but there are two features of Forms you can to help manage data entry.
1) Fields can be set to be read-only using the Disabled flag.
2) You can assign different forms for different Identities on the Views tab of the ItemType.
Combine these two features together and you load one form that has the field available for editing, and another with the fields as read-only.
You could even make these fields not available at all, on the alternate form altogether.
-Bill
RobMcAveney - Monday, May 21, 2007 5:15 PM:
There is currently no formal field-level security in Innovator, but there are ways to accomplish the same effect. As Bill pointed out, there are ways to control the UI to prevent users from editing certain fields. Using different forms for different Identities is one way to do it. Another way would be to use a method to dynamically enable/disable fields when the Form is loaded. These approaches have worked well for some users, but keep in mind that this is only UI-level control. You can use server-side OnBeforeAdd/OnBeforeUpdate methods to implement a more robust field-level security scheme. I've done some experimentation with this approach and it really isn't too difficult. If there's enough interest we can look at a more standardized approach. Anyone else out there need it? If so, how soon?daniel.broomall - Wednesday, May 23, 2007 10:48 AM:
Bill
Thanks. I hadn't thought about the different forms for different Identities. That would be a quick way of achieving the same thing. I will have to do a pilot test of that (along with the suggestions Rob made) to find the best solution for us.
Thanks again for your response and your time.
Peter Borsje - Tuesday, October 1, 2013 4:38 PM:
Rob,
A property is also an Itemtype in Aras and probably also have a permission set that can be configured. Can this be used to prevent properties to be edited/changed?
Peter
