#1771 - Change case Name field based on Role
Hello.
Is it possible to change which field displays as the Case "name" depending on the Security Group?
For instance, say Group A creates a Case called "Secret 1," but I don't want Group B to see the name "Secret 1" and would like to make a different field display as the case name for Group B. Is this possible?
9 years ago
Hi there,
Yes, that is one of the nice features of SecuritySuite. Inside Studio go to the Cases module and click on the Layouts folder on the left outline. You will a "Select a Group Layout to Add" in the main pane like this: https://www.dropbox.com/s/74jooe5o2q8yb2z/Screenshot%202015-11-30%2014.25.11.png?dl=0. Copy the layout to Group B. Then outline will refresh and you will see a Group B folder under the Layouts folder. Alter the layout as needed for that group now.
Let me know if you have any other questions.
9 years ago
We have done this for several groups. The problem is related to the way the case name appears in the Recently Viewed, List View, etc.
When this was originally set up it was for 2 help desks, and each one could share all information, but now new groups are being added and the same module must be used. The issue is that the help desks started putting information in the Name field that should not be accessible to groups outside of the help desks. Since we have hidden this field from the new groups, there is no "name" associated with cases created by the new groups and when a call is moved to one of the new groups, the new group can see the name the help desks gave it (in the List View, Recently Viewed, etc.)
9 years ago
Got it. Unfortunately this is due to how SugarCRM needs that name field to be used. I would suggest wiping that info from the name field and giving the help desk a different field to use for this purpose.
9 years ago
Yeah, I figured. I tried manually creating a new field with the same type, etc. but to no avail. The problem is that it has apparently become a documented procedure in their workflow, so purging the records, etc. and creating a new field won't really fly.
9 years ago
Slap some wrists! That documented procedure is causing sensitive info to be leaked.
Best of luck!
9 years ago
Thanks though!