07-31-2015 12:01 PM
We are a newly implementing site. We have a document type for timecards.
We need all users to be able to see their own timecards only, but department heads should be able to see all timecards in the department. I wanted to use the existing All City Employees Active Directory group and put the UserID = UserId keyword on that group. Then, on the department heads, add the department security keyword. I discussed with our implementation team, they said it would act as an "OR". When I went to test, we found that wasn't the case, it seems to be ignoring the dept keyword on the dept heads.
We also need the employees that process payroll (who are not department heads) to be able to see all timecards. I thought I could get around this by adding Dept not equal to "z", which is not a department.
Has anyone fixed a similar issue without a new group that is All Employees minus department heads?
Thanks for your help!
08-03-2015 09:58 AM
Hi, Kris -
We had a similar dilema with our employee forms. We learned that security keywords are evaluated using "OR" logic as long as it's the same keyword type (Keyword One = "ABC" OR Keyword One = "XYZ"). As soon as you introduce a second keyword type it uses "AND" logic (Keyword One = "ABC" AND Keyword Two = "XYZ"). We also had no success with the "not equal" option.
Our solution was to create a generic "Access Control" keyword that can contain a variety of values like user name, department, form number, etc. We then add as many instances of that keyword as necessary (via workflow) to control access by the appropriate users or groups. The department head would successfully match on the department value, perhaps payroll would match on form number or another appropriate value. It was the best option we could come up with.
It might be something to consider, at least.
08-03-2015 09:58 AM
Hi, Kris -
We had a similar dilema with our employee forms. We learned that security keywords are evaluated using "OR" logic as long as it's the same keyword type (Keyword One = "ABC" OR Keyword One = "XYZ"). As soon as you introduce a second keyword type it uses "AND" logic (Keyword One = "ABC" AND Keyword Two = "XYZ"). We also had no success with the "not equal" option.
Our solution was to create a generic "Access Control" keyword that can contain a variety of values like user name, department, form number, etc. We then add as many instances of that keyword as necessary (via workflow) to control access by the appropriate users or groups. The department head would successfully match on the department value, perhaps payroll would match on form number or another appropriate value. It was the best option we could come up with.
It might be something to consider, at least.
08-05-2015 07:28 AM
05-29-2018 07:37 AM
06-04-2018 11:18 AM
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.