rule for view but not edit?

dianab

If I have a BO attribute that requires a field that the user can view but only admin can add/edit does it need to be a separate BO or can I have a rule that allows this.

To put it in a context. I deal with pets. People can add and delete their pets but I have dates for vaccinations that I must verify and change.

In pet BO I have name, size....and want to include date of vaccinations that admin can only enter/ edit but customer can view.

I didn't see a way to use a rule to accomplish this but then again I am very new and still testing the software. I was looking at "if user is not admin then Protect" but I don't think that will let my customer view the date.

I hope this makes sense.

Diana

tford

Diana,

You have the right idea. PROTECT and READ PROTECT are the two actions that can be used to accomplish restricting access to certain users.

dianab

Thank you,

I may be over-thinking but what is the software's definition of access the description is the same for both Protect and read protect. I am assuming that read access would be similar to a read only file which is what I want.

Diana

tford

READ PROTECT ensures the user can't read / view the attribute or BO.

PROTECT ensures the users can't update the attribute or BO.

hpl123

Diana,
To clarify:

READ PROTECT is NO ACCESS i.e. a user cannot see, open up (or change) and attribute. If a user opens up a form with a READ PROTECT attribute on it, it is not displayed at all.

PROTECT is READONLY i.e. a user can see an attribute, value etc. but not change it.