Ok, Thanks. This got us on the right track. I think we may have discovered a bug in the process, too. To summarize what works:

1. Make a user task and on the assignment tab, choose "A specific team."
2. Use the Filter editing tools on this section to create a filter for each team that you want to use as a dynamic team. In our case, we created a filter with the same name "primary contact" for each team.
3. Then change the assignment selection to "A team based on variables."
4. Check the Dynamic filter box, and insert the name of the filter you created above.

As for the bug... We had some pre-existing teams and filters from our 10.1 installation before upgrading. It seems that any filters we had created using 10.1 do not work with the dynamic filters in 10.2. We had to delete the existing filters and recreate them on the "A specific team" section before we got things working.

Yes, those are the correct steps. We'll update the documentation to clarify that, see if there's a better user interface to indicate this behavior and investigate the possible bug. Thank you for reporting these issues.

Could you please provide us more detail about your team configuration and dynamic team setup regarding " any filters we had created using 10.1 do not work with the dynamic filters in 10.2 "?  It should work and we'd like to look into it if it's not.

Thank you.

Sure. The steps we followed were:

1. In Forms 10.1, created several teams, Team A, Team B, and Team C for example, in the standard way from the Administration area. Within each team, we created 2 roles (Primary Contact, and Backups) and divided the users into each role.
2. Constructed a process with an initial form, containing a checkbox field that explicitly listed each of the teams we set up.
3. In the process modeler, after the initial submission, we had a parallel gateway with one branch for each of the teams we had created. Each branch corresponded to a single team, and had a User Task on it that was assigned to that team.
4. For each of those User tasks, we used the Filter option from the process modeler to build a filter that would send the task to the users with the "Primary Contact" role. We named this filter "Primary Contact" consistently across each group (yes, the filter name was identical to the role name... maybe not a best practice). The rest of the process doesn't matter.
5. When 10.2 came out, we wanted to change this explicit parallel gateway to a dynamic teams setup. Performed an in-place upgrade to Forms and then upgraded the Forms database from FormsConfig. No errors or issues with this.
6. Went into our process and deleted the parallel gateway, all of the conditional outflow paths, and all but one of the User Tasks. Reconnected the initial submission to the remaining user task with a new outflow path with no conditions.
7. Went into the settings for the remaining User Task and noticed that all of our existing groups still had their filters as well (carried over from the upgrade). I then changed the radio button from "A specific team" to "A team based on variables."
8. Entered the filter name "Primary Contact" into the dynamic filter field.
9. Ran through a submission with the process, and it becomes suspended on the User Task, with the error message "No filter could be found with the name 'Primary Contact'. [LFF6108-RuleNotFoundByName]"

To resolve the issue, I simply went into the user task and used the "A specific team" section to delete all of the existing "Primary Contact" filters. I then used the same interface to re-make the filters (using the exact same script expression), only this time I saved each filter as "Primary" instead of "Primary Contact". This was mainly so I could easily tell which groups I'd updated and which ones I hadn't, but you never know if there is some weird naming bug.

I can't give you any screenshots or exports of the process in the non-functional state because we have since corrected the problem. Hope that helps.

Hi Scott, 

Thank you for reporting this issue.

We figured out there's a bug in 10.2.0 that team filter couldn't be resolved properly when multiple teams happen to have filters with the same name.

So in your case it could be the team you chose that made it work (e.g.: you have "Primary" filter created in TeamA, TeamB and TeamC; filter works when you dynamically assign to TeamA but doesn't work if you choose to dynamically assign to TeamB or TeamC). So potentially the issue is there if those teams are still having filters with the same name.

This issue will be fixed in the coming hotfix.

Thank you.

Lifei 

Thanks for all of the extra info on dynamic filters.  I look forward to this information being added to the help website so the end users have easy access to it.  A couple of related follow up questions.  What happens if the Team exists but the filter:

1. Does not exist for that team?
2. Does not have any people assigned to it?
3. Is not valid because it calls a value (e.g. a role) that does not exist for that team?

My hope is that for all 3 it just assigns it to the team still and does not just die.

Also, was the bug with the identically named filters resolved?

Was this issue ever resolved?  I'm bumping into exactly the same issue in Forms 10.4.4.444.  I'm selecting the team based on a variable and using a dynamic filter to pick the users but the teams have identically named roles.

Am I going to need to make sure the role names across teams are unique?