Protect Rule

vinsnash

Can someone explain why you have to use a negative to get Protect to work?

Example:

If Not (LoggedInRegularUser.Prorate = 'Yes') Then Protect NSCPers.months From All

rather than

If LoggedInRegularUser.Prorate = 'No' Then Protect NSCPers.Months From All

'No' is the default and 'Yes' is the exception. Number 2 seems to me to be the intuitive choice.

Vins Nash

tford

I have used rules like #2 just fine.

Have you looked at the logs while using rule #2?

vinsnash

I didn't see anything in the log to indicate a problem. It seems to only work with a negation.

Here's another similar quirk.

I have two yes/no attributes on the main object form which I want to disable when inputting new so I use the following rule:

If NSCPers Is New Then

Protect NSCPers.NewId From All
Protect NSCPers.Reenroll From All

Both Yes/No attributes are set to initial value 'No'. However, the user can still click the box and the check mark will appear briefly then reset the first time. Clicking it again leaves it set as 'Yes' and the object can be saved that way which is a problem. I would prefer that the user not be able to visit the attribute at all when creating new. Is there a way to do that?

Thanks for any help.

Vins Nash

vinsnash

The initial problem is solved. #2 doesn't work, of course, because the value was initially undefined - Jersey head slap for that one.

The subsequent problem with the two yes/no attributes still exists and they are set initially to a value of 'No'

tford

I would prefer that the user not be able to visit the attribute at all when creating new. Is there a way to do that?

Don't put those 2 attributes on the form used for creating new instances.

vinsnash

More than one way to skin a cat. I prefer not to have a separate form for two attributes. I changed it to simply make both fields = 'No' when New. The fields can still be accessed and the check mark set but on save they are set to 'No' and don't affect other processes. A little messy but it works.

There should be a way to disable the fields to prevent any access depending on a condition similar to a number attribute I have on the form. When the condition is met the field is inaccessible and grayed out. No confusion of ambiguity possible.

I'll report it in the 'problem' forum.

Vins Nash

BobK

Vins Nash,

I think the following will give you what you want:

If NSCPers IS NEW Then
READ PROTECT NSCPers.NewId FROM ALL

With READ PROTECT, the fields will not even show on the forms.

tford

In the Advanced tab of the rule, set it to "Use rule during initialization".

vinsnash

If NSCPers IS NEW Then
NSCPers.SupportAct='Yes'
Read Protect NSCPers.NewID FROM ALL
Read Protect NSCPers.Reenroll FROM ALL

The rule is set to use during initialization but the check boxes still show on the form and they are still enabled. For now I'll stick with

If NSCPers IS NEW Then
NSCPers.SupportAct='Yes'
NSCPers.NewID = 'No'
NSCPers.Reenroll = 'No'

It is messy but it works which is what counts for now.

Thanks