I have a use case where I need to apply visibility rules to requests generated in an application. In other words, if I create a request, only users from my department should be able to see it. In the client’s system, there are many departments, and creating a group for each of them doesn’t seem like the right solution. Additionally, new departments may emerge in the future. As a solution, I’m considering detecting the department code of the user initiating the process (this value is stored in the custom field ‘customfield1’). Then, when applying visibility rules to requests, I would calculate all users who have the same value in ‘customfield1’ as the user who created the request. My question is: Is there any issue in Appian if I assign tasks to an array of users instead of Appian groups?
Discussion posts and replies are publicly visible
Using groups would be the natural thing to do. Can you guesstimate how many groups you would end up with?
Yes, I can have 1400 groups, one for each department of my client. The requirement is that each department can only see its own
My idea was to calculate which users should do the task before assigning it, users do not change departments frequently.
Another option is to create the groups dynamically as they are needed. That is, when a task is generated, I calculate what its work group should be and if it does not exist, I create it, and if it exists, I assign the task to that group.
In general I do not consider this number to be a problem. But that depends a bit on the other applications on the same environment. Groups can become a performance issue beginning with 5-6 digit numbers.