enhancement Filter for group picker

[Peter Clough]

There is a customised field in intelligent captures called Group Picker, and another in the outcome custom questions options for human tasks within workflows called Hornbill User Group Picker.

At present, we can filter this by group type (teams, companies, divisions, etc), but are unable to narrow it down further.

For example, we currently have teams for ICT, and teams for HR, however this picker shows all of these teams in the list, regardless of department. If I want to have a picker to put a request to a specific team, then there is nothing to stop someone accidentally picking an HR team and trying to send an ICT call out of the department, which will then fail to assign, and break our process.

Would it be possible to have either an option that restricts the list to the service the request sits in (like a normal assignment action), or let us add a filter to pick an organisation so that we can correctly restrict these choices.

[Darren Stather]

+1

As an MSP, we manage a number of different instances, some with multiple organisations sharing an instance. To allow filtering on the Group Picker is necessary to allow (for example) end users to select their Department when completing a new starter form.

[Steve Giller]

On 14/03/2025 at 13:27, Peter Clough said:

If I want to have a picker to put a request to a specific team, then there is nothing to stop someone accidentally picking an HR team and trying to send an ICT call out of the department

Where is this picker being used?
If you're selecting a Team to assign to, there is a dedicated form for that in the IC, and an Action on the Request - both of which will only display Supporting Teams.

[Peter Clough]

We have a process around certificate expiry, where we put a request into a holding queue until a target time, at which point it assigns to whichever team is responsible for it. Using the IC form to assign puts it straight to that team, which is what we've been doing so far, but it's noticeably unpopular among the teams, and I've been asked to look at changing it.

Also, we are introducing teams that are designed to be unassignable manually, and so the assign function is disabled to those teams, but we still need certain workflows to be able to assign to them. As they are again variable, we use the drop down picker to find the team, which the request is then sent to. This happens a fair bit in our change process, when picking, mid-workflow, which team will be managing the next stage of a request.

So this is relevant to both the capture and the task versions of the setting.