Hi Victor,
If I am understanding the need correctly, you are looking to restrict the values that appear in some of the dropdowns, but this time, based on group, is that correct? If so, this is a bit tricky because it depends on which dropdowns specifically you are trying to restrict, and whether those dropdowns (whatever object they are) had a group attribute on them or not. The limitation with data partitions constraints is that you cannot cross objects or use an "if then" type statement. Additionally you can also only have one constraint of each constraint type (update, view, pre-update etc.) on an object.
So for example, lets say the dropdown field you wanted to restrict by group is the "symptom" field. You cant have a constraint that says you cant view the symptom called "high CPU usage" IF you are in group XYZ. If the symptom field had a group attribute on it, you could restrict it in a way such that the logged in user would have to be a member of the group in which that symptom value is associated with. BUT, most drop down fields don't have the group attribute, so it will be difficult to do this.
If you can provide us with a few use cases here of specifically what fields you are looking to restrict by group, we can give you a better idea of what options are possible.
Let us know,
Thanks,
Jon I.