restrict access to tickets

[jna2756]

Hi All,

I am trying to restrict users from being able to read tickets if they are marked restricted(custom true/false field) unless they are member of the group the ticket is in or is the "requested for".

I believe the best method would be to use a on-before Query Business Rule however I am having trouble getting the "addQuery" right.

I want to do the following with addQuery rather than addEncodedQuery as the addEncodedQuery doesn't seem to work right in the script section.

Encoded Query: u_restrict=true^assignment_groupDYNAMICd6435e965f510100a9ad2572f2b47744^ORu_requested_forDYNAMIC90d1921e5f510100a9ad2572f2b477fe^NQu_restrict=false

is it possible to do this with an addQuery statement?

Any help would be appreciated.

Thanks,

Joshua Anderson

[Chuck Tomasi]

A valid point (and comparison) Trevor.

Joshua, thoughts on changing tactics to an ACL?

[jna2756]

Hi Chuck and Trevor,

I would prefer to use the Query Business Rules over the ACL as it seems like it would be simipler to implement and maintain.

Thanks,

Joshua Anderson

[Joshua Cassity]

Did you ever get this working?

We're trying to do something very similar but more complex on Incident records and the issue is that we have ACLs in place but when users go to the listing it displays empty rows in addition to the items the user has access to - which our management really hates. Folks should only see what they have access to. The encoded query always acted up on us.

[jna2756]

HI Joshua,

Unfortunately, no we were not able to get it to work. We ended up going with ACL's instead and which was easier than we thought to do.

Thanks,

Joshua Anderson

[Joshua Cassity]

How did you get around users who didn't have access to those records getting blank rows / rows restricted by security constraints?

Or did you?

~ J ~