Update - This is affecting queries too...and as a twist, I have further proof of a different bug I reported earlier.
I have a BO called Entity. Certain users aren't allowed to see the BO and certain users aren't allowed to edit the BO. But users that are allowed to see, but not edit, are not able to see a query listing Entity because of the buggy PROTECT feature. This is my rule:
If EXISTS LoggedInPerson AND LoggedInPerson.Architecture IN 'No Visiblilty','Survey Only' Then
READ PROTECT Entity FROM ALL EXCEPT Administrator AND System
Else If LoggedInPerson.Architecture<>'Responsible (Full)' Then
PROTECT Entity FROM ALL EXCEPT Administrator AND System
If I delete the "Else If" clause, those users who don't have Architecture IN 'No Visiblilty','Survey Only' (and are also not 'Responsible (Full)') can see the list again.
And here's the twist: If I just disable the rule with the "Else If" clause intact, the list still does not show. So the rule is being implemented even though it's disabled. 3 weeks ago I reported a ghost-effect that a disabled rule can create (More bugs>). This issue is more like a poltergeist. Until this is addressed, disabling should be considered unreliable.
