Read ACL on Incident - Troubleshooting

[jshatney]

Creating a pretty standard READ ACL on the Incident table. The requirement is to allow users in the same department the ability to read other user's incidents.

Type: Record

Operation: read

Name: Incident

ourUser = gs.getUser();

department = ourUser.getDepartmentID();

if (current.caller_id.department == department || current.opened_by.department == department){

      answer = true;

}

This same ACL is working without issues on the Request and Requested Item tables (obviously with small changes). The conditions are coming back as true on the Incident table, however, it does not display all records for the user's department - only their records.

I cannot seem to write an ACL that allows a user to view any other records on the Incident table than their own.   I checked for an onQuery business rule or other ACLs that may be conflicting with this.

Does anyone have any idea what may be going on here?

Thanks~!

[Brad Tilton · Accepted solution]

You mentioned you checked onquery business rules, but there is an out of box business rule no incident called 'incident query' that restricts incidents for ess users so they only see incidents they've opened or are the caller on. Could you double check for that business rule? It would be there and be active unless you've deleted or deactivated it.

[jshatney]

/bangs head on table..

I knew that rule existed and went to go and find it, but for some reason (I blame Friday afternoon) I didn't see it.

Went back and re-checked and there it was... TGIF

[Brad Tilton]

We've all been there, sometimes you just need a sounding board.

[Matt Saxton - G]

var ourUser = gs.getUser();

var department = ourUser.getDepartmentID();

if (current.caller_id.department == department || current.opened_by.department == department){

      answer = true;

}

Try declaring your variables i'm not sure if thats the issue but worth a shot.