Conceptual overview of accessing/security model

Hi

I am struggling in getting even a somewhat clear overview about the application of accessability for various users to an application (on forms, and field level), especially in the context when find is used as well.

For example, when unchecking a fields editable property, the field can be entered and acts as a search field when selecting Find (Cmd-F or Ctrl-F). When this field’s Accessible checkbox is unchecked in the security tool, the field’s content is not searchable any more (Servoy 3.5.7).

Additionally to the design time property editable there are the JavaScript properties enabled = true|false and readOnly = true|false (applying grey to the text and fields border)

As these design and programmable properties interfere/interact with each other in a way difficult to understand for me, I am asking if someone has found a consistent concept for this problem domain? Can anyone point me to some conceptual information?

In 3.5.7, it seems that there is only on security model for ALL solutions which, if true, prohibits the application of the security settings for various solutions in development (various solutions with a number of modules for each solution).

Best regards, Robert

PS: I would love to have a symmetrical instruction set (in Chip design terminology spoken) for Servoy, i. e. have all design time property as JavaScript programmable property as well and vice a versa.

Servoy security is group based, you set privileges for groups then if you don’t want some groups to be able to access some solutions it’s up to you to code that, users can be linked to several groups so it’s not so difficult to do that.

About your find issue: if a field is set to be not accessible it’s correct that it can’t be accessed for searches, not accessible doesn’t mean read-only. I think that you should use special search forms for your searches, using the same form for editing and searching in Servoy is not a smart idea IMO.

Anyway take a look at the docs, the security is very well documented.