End users showing up in Assign to
Thanks in advanced
Best Answer
-
Ryan_Lane Cireson Support Advanced IT Monkey ✭✭✭Alright, then it is most likely that the Incident.js and ServiceRequest.js template files are missing "FilterByAnalyst: true" when defining the field.
You should be able to find the relevant files within your CustomSpace directory. Here's a screenshot of mine with the relevant lines marked:
Just in case that's hard to make out here are the two lines I have for Assigned To and Primary Owner:{ DataType: "UserPicker", PropertyDisplayName: "AssignedTo", PropertyName: "AssignedWorkItem", FilterByAnalyst: true, ColSpan: 3}, { DataType: "UserPicker", PropertyDisplayName: "PrimaryOwner", PropertyName: "RelatesToIncident", FilterByAnalyst: true, ColSpan: 3}
1
Answers
Assuming this is true (and again, I can't say for certain) my only thought would be is perhaps Cireson stopped filtering the Global Operators Group?
1. When searching from the Assigned To field that the request from the browser is filtering by analyst:
/api/V3/User/GetUserList?userFilter=&filterByAnalyst=true
2. That the AnalystsADGroup setting under Portal Admin Settings > Setting Items is correct.
If those both look right then I'd check the ServiceManagement database's CI$User table to make sure that the end users aren't somehow being set as Analysts:
We went from 7.4.2012.3 to 8.9.4.2016
1-3. Opening Developer Tools panel (F12 works)
4. Click on the Network tab to start monitoring the page.
5. Start a search in the Assigned To field.
6. Select the request to view its Headers.
You should be able to find the relevant files within your CustomSpace directory. Here's a screenshot of mine with the relevant lines marked:
Just in case that's hard to make out here are the two lines I have for Assigned To and Primary Owner:
Versus
Not a problem
**Disregard, I am an idiot and it's been a long day. Just added it at the end of the line and it resolved it for me.**
EDIT: Glad you got it!