Access Levels

rgates@ttcdas.com

Simple question:

I have a BO that I want to control Access on. I want the creator to have the ability to maintain the object include deleting. All other users can view only. The administrator can do all operations on the object.

tford

I'll use a Customer BO as example.

1) create attribute Customer.CreatedBy -- reference to RegularUser

2) Add 2 rules:

If Customer IS NEW Then Customer.CreatedBy=LoggedInRegularUser

If Customer.CreatedBy<>LoggedInRegularUser AND Customer.CreatedBy IS DEFINED Then PROTECT Customer FROM ALL

rgates@ttcdas.com

I was hoping that there was a way to do it via the Access Levels. I thought I was possibly missing something when I couldn't get the right access level configuration in place.

Thanks

tford

I use rules to do this. It looks like you shoud be able to do this via access levels but I could not figure it out either.

rgates@ttcdas.com

I have a query that displays all the rows. The PROTECT doesn't prevent the non-author from DELETING. It only handles "editing". I know that I can put a rule at the query level so as to prevent the Delete Operation/Button to only be applicable under certain circumstances. It just seems to me that the PROTECT at the BO level would take care of this.

My rule is slightly different then you proposed mainly because I want the System to be able manage the data when need be. Does the Query Delete operation occur within the context of the System or the User?

tford

The PROTECT doesn't prevent the non-author from DELETING

You are right. I will send a sample BSV to support demonstrating this.

rgates@ttcdas.com

Support,

Are you investigating this issue?

aware_support

PROTECT is not related to DELETE at the moment - you'll have to add the condition to the DELETE operation as well.