PROTECT does not seem to work at the attribute level

ddumas

I have the following business rule code to write protect specific attributres against changes:

If LoggedInSystemUser = Project.Owner AND Project.ApprovalStatus='Approved' THEN
PROTECT Project.ProjectType FROM ALL EXCEPT Administrator AND System AND TenantAdmin
PROTECT Project.BusinessProcessArea FROM ALL EXCEPT Administrator AND System AND TenantAdmin
PROTECT Project.ApprovalStatus FROM ALL EXCEPT Administrator AND System AND TenantAdmin

I do not get syntax errors, however, all attributes now act as write protected. Is there a way to write protect at the attribute level?

Gabbitas

I have had similar problems with this. Try and break you rule down into 3 seperate rules. Have only one PROTECT action per rule. Ie 1 rule to protect ProjectType, 1 to protect BusinessProcessArea and 1 to protect ApprovalStatus.

If this works for you the I would like to know if AwareSupport would consider this a bug or if it is intentional? Or am I just completely wrong!

Thanks

ddumas

Gabbitas wrote
I have had similar problems with this. Try and break you rule down into 3 seperate rules. Have only one PROTECT action per rule. Ie 1 rule to protect ProjectType, 1 to protect BusinessProcessArea and 1 to protect ApprovalStatus.

If this works for you the I would like to know if AwareSupport would consider this a bug or if it is intentional? Or am I just completely wrong!

Thanks

So, I think this is a bug, and your observations led me to the workaround. I am able to reproduce.

For me, I am able to stack multiple protect actions in the same rule. Each PROTECT attribute works. Where it breaks (bug) is where I place code in an IF...ELSE... IF block. When I do this, the object then gets PROTECTED as a whole I.E at the object level, regardless of the logged in user.

So, the below code breaks, but if I separate into 2 separate rules it does not break. Therefore, the IF...ELSE...IF... logic is not executing properly, so it is a bug in my opinion.

IF
ProjectIssue.EnteredBy <> LoggedInSystemUser AND
ProjectIssue.Project.Owner <> LoggedInSystemUser AND ProjectIssue.AssignedTo.Resource.ResourceLoginName<>
LoggedInResource.ResourceLoginName
THEN
PROTECT Project FROM ALL EXCEPT Administrator AND System AND TenantAdmin

ELSE
IF ProjectIssue.Project.Owner = LoggedInSystemUser AND Project.ApprovalStatus='Approved' THEN
PROTECT Project.ProjectType FROM ALL EXCEPT Administrator AND System AND TenantAdmin
PROTECT Project.BusinessProcessArea FROM ALL EXCEPT Administrator AND System AND TenantAdmin
PROTECT Project.ApprovalStatus FROM ALL EXCEPT Administrator AND System AND TenantAdmin
PROTECT Project.ApprovalCurrentOwner FROM ALL EXCEPT Administrator AND System AND TenantAdmin