Just wondering what other people are doing in terms of restricting process visibility in the Central Cases list? Is anyone doing this based on privilege? For example, Council Tax and Benefits processes in the cases list should only be seen by people with the Revenues and Benefits privilege rather than by everyone.
Could you expand on what you mean by “Process visibility”. I might be being a bit slow it is a friday afternoon.
With regards to filtering lists you should use subsets. If you wanted to have a page where multiple service areas can drop in and see a list of their Cases, you could put multiple case lists on a page:
You would then subset the revenues list to only show revenues processes, then add a Visibility Subset or Visibility Privilege as well to target the users you want to see it. Then it should show based on the logged in used on the page.
I would suggest compartmentalising your application as having multiple service areas in the same place can lead to it not being as scalable, but it’s all down to your needs
Hopefully I’ve understood your issue and if not feel free to reply with more info and I will update my answer.
Hi Dan, I’m not sure whether others have the same set up as us - we have a cases page where all cases can be seen by all users. I was wondering if anyone else has the same setup but hides certain cases from the list unless you have a particular privilege assigned.
By process visibility I mean a process showing in the list of cases. For example, it’s fine for anyone to see a missed bin report, but not a safeguarding report or temporary accommodation claim.
From what you’ve said about, it sounds like having separate lists for each service area rather than one list showing all cases is the suggestion?
Just chipping in…
Yes, as Dan says, having separate widgets makes it easy to show/hide whole lists of cases based upon a privilege of the logged in user.
But there is no way to use a privilege to select which rows within the listing are included.
Perhaps you are using a parent object with dynamic relationships to various case-type objects to get them all in one listing? If so, then a ‘read’ privileges on each object would mean users would be prevented from reading data from appropriate case attribute fields… But I think the row would still be there in the listing.