03-28-2019 11:33 PM
We implemented a rule using security keywords for a user group where Keyword 'Restricted Access' does not equal 'Yes'.
However, from testing it is restricting access to documents where 'Restricted Access' does not equal 'Yes' AND where a value has not been set for this keyword. To be clear if it is blank the access is still restricted even though that rule hasn't been specified.
so if I have three documents...
1. restricted access = yes
2. restricted access = no
3. restricted access = <blank/null>
and the rule 'Restricted Access' does not equal 'Yes'.
OnBase would restrict access to that user group to documents 1 and 3, when it should only restrict access to document 1.
Has anyone else experienced this odd behavior or have a workaround to resolve?
Thanks
Adam
03-29-2019 07:23 AM
This sounds like typical behaviour with NULL values. you would have the same issue if you reversed the logic. A security keyword should always have a value.
03-29-2019 07:23 AM
This sounds like typical behaviour with NULL values. you would have the same issue if you reversed the logic. A security keyword should always have a value.
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.