In what is a common design paradigm, I have cases that can have multiple assignees. Depending on the permissions of the loggedInUser(), they should either see cases which are assigned to them or cases through the entire system (Global Viewers Group). The global viewers group should also be able to search by assignee. One of the more common ways this way accomplished in the past was via a double query - one for the assignee table which returned the list of case ids and subsequently another one to the case table.
I wanted to use the newer Appian Record functionality, and based on the Appian Playbook, it seemed that Appian had found a more performant solution to this common use case, but I am still seeing duplicates in my Record List View.
I tried modifying the Default Filters in the example application with the instructions here from the Appian Playbook: https://community.appian.com/w/the-appian-playbook/207/record-level-security-for-entity-backed-records under the Managing Global Viewers section as shown in the screenshot below.
When I view the record list from tempo/sites, the grid duplicates the cases. Considering that the entity backing the record has duplicates, I'm not surprised to see duplicates. But, based on the link in the playbook, it seemed like Appian had handled the duplication issue.
Am I missing something obvious?
Discussion posts and replies are publicly visible
Hi,
I can't see any issue with your code since source has got duplicates same thing is being displayed in record list. I couldn't find anything specific around handling duplicates on the documentation so not very sure if Appian has handled it but they have provided the application patch as well as the test data so it would be worth importing the application and check the code on how duplicates have been handled.
When the user is member of the global group, the filter must look like this
Hi Stefan,
Does it mean for each cases, there should a separate row having value as groupName?
Eg:
id. Caseid. user
1. 1. user1
2. 1. globalUserGroup
3. 2. user1
4. 2. user2
5. 2. globalUserGroup
When you need that group to have access to all cases, yes. This does not have to be the name of the group, any meaningful string will do it.
Stefan and Nitesh, thanks for the answers and discussions. So, the playbook claims that their method avoids exactly the pain point brought about by having to enter assignee rows for the groups that need to have access to the cases.
- I am going to update my filter to use the record field, instead of how I have it structured and will revert back, though I anticipate little to no change.