Can "Search Users" Action/Method Results Be Limited by Group Membership?

Does anyone know of a way to restrict the results of the "Search Users" action from the iPaaS TDX Common connector to either just members of one or two groups or prevent users from a specific group from appearing in the results? I know this can be done with a custom attribute on a TDX form, but since we need to use an iPaaS form for this item, I'm looking to restrict the results of the connector. Unfortunately, since the groups in question have between 30K and 105K members, it's not really feasible to either use the "Get Users by Group" action to search from or populate a shared data list. I also have a custom attribute that could be used as a filter, but this call doesn't allow for that.

Asked by Corrine Knox on Thu 1/18/24 3:46 PM
Sign In to leave feedback or contribute an answer

Answers (2)

This answer has been marked as the accepted answer
Mark Sayers Fri 1/19/24 10:04 AM

Hi Corrine, I'm posting in a new thread because of the content length of this response:

Since ipaas can't do anything that the APIs can't do, and it looks like the user search API has no option for searching within groups: https://solutions.teamdynamix.com/TDWebApi/Home/type/TeamDynamix.Api.Users.UserSearch

what i would suggest is instead doing "get members of group" for all the relevant groups: https://solutions.teamdynamix.com/TDWebApi/Home/section/Group#GETapi/groups/{id}/members

but you said explicitly in your response, "Since all of these identity groups are very large (30K members, 105K members, 400K members), I cannot simply get a list of members and search from that for this." Unfortunately there's no solution for this, we can't have iPaaS do something the APIs aren't capable of doing.

This would have to be an enhancement request to ask for some way to achieve this.

Sincerely,
Mark Sayers
Sr Support Consultant, CS

No feedback

Mark Sayers Thu 1/18/24 3:52 PM

Hello Corrine,

Let me check on this with the iPaaS teams, but in general API usage is just restricted by your own account's level of security role permissions and application access in TDX.

I'll see if iPaaS role permissions might help with this though, but I do not suspect that results can be prevented if they can make the API search call at all.

Sincerely,

Mark Sayers

Sr Support Consultant, CS

No feedback
I may have been unclear in my question. What I'm looking to do is when someone triggers a flow that runs the "Search Users" action, it would either only return users who are members of one or two groups or return users who are not members of a specific group.

We recently loaded some groups from our Identity Management system that identify users who are employees, who are students, who are guests, etc. We want to make it so that when someone searches for a user from an iPaaS form, the result the get will not include any guest users. Since all of these identity groups are very large (30K members, 105K members, 400K members), I cannot simply get a list of members and search from that for this.

If we needed just employees, we can use the IsEmployee flag as a filter on the call, but since we need to include students in the results, too, I was trying to find another way.
- Corrine Knox Thu 1/18/24 4:48 PM
I haven't heard back just yet, but I do have a question in to ask about this. I don't know of a way to do this without having flows just execute in the back end, then have steps to parse out the results before presenting them to a user on a form or something. - Mark Sayers Fri 1/19/24 10:00 AM