I have a bunch of forms that will be either editable or readonly, based on the user's permission.



My first try was to create the permission, then use roles to either allow GRANT or READONLY. I assigned this permission to the forms.....doh, that doesn't work as forms only work with GRANT (anything else is deny).



As I look at the options and the help file, I'm getting lost. I obviously need to set the permission at the BO level, but I'm confused as to how. Specifically, these issues are confusing me:



- there are four security settings on a BO. Do I need to set them for add,delete and update? I understand query is only related to auditing, so that one I won't set (right?)

- The help file says (in the "Security Keys on Forms and Business Objects") to not allow readonly when for permissions that attach to business objects or fields. So, forms don't accept it and business object and fields don't either...I'm confused

- Are maintenance toolbars manages when permission is readonly? How?



So, how do I configure RBS to have a form that is readonly or editable based on a permission?

You would need to create a security key (permission) that you want to assign to the business object that will be read-only.  Then, go to the BOMapper and assign that permission key to all of the fields on the business object (the same key to all fields).  Then, when a user has that permission at runtime, any control bound to that field will be read-only.

Only field-level security allows things to be read-only.  We tried allowing forms to be read-only, but it was horribly inefficient to cycle through all of the controls on a form to make them disabled, and you cannot set a form's Enabled property to False without some interresting reprocussions.  So, you'll have to stick to making fields read-only.

Any quick way to do this? Seems like a lot of work for something that I would think would be very common need. (I do understand why it is done at the field level, thanks for the explanation).

...every single customization that is available for a field in the BO Mapper is available in the customize wizard EXCEPT the security key...Big time enhancement request

Aye, quite honestly, we thought about it and left off that field because we were thinking that the security key would be different for each field... and it wasn't until I answered your last post that I even thought about using the same key on all fields to make an entire business object read-only.  I will definitely post this enhancement request

ah, those (us:w00t pesky users!



Thanks! That will help a lot. Setting permissions on each field is trivial but time consuming. The bigger problem is handling all the buttons/toolstrips on each form...aiiiyiiiyiii