It would be nice if Laserfiche Forms Teams could be set up as a data source out of the box without having to manually set it up. This would help with the dynamic assigning of tasks to a team using a variable value by populating a drop-down field for example with a list of teams.
Question
Question
Feature Request: Forms Teams and LFDS Users and Groups as a Data Source
Answer
With Forms 11 Update 2(https://support.laserfiche.com/kb/1014352/list-of-changes-for-laserfiche-forms-11-update-2), you can add AD/LFDS group to team and the users in the groups will be automatically synchronized so the users from the groups can participant in the team as get email notification when task is assigned to the team, take team tasks etc.
Replies
I've set-up my own Views on the LFForms database to achieve this (I'm happy to share if anyone wants them), but I think you are right - it would make a lot of sense for this to be a standard out-of-the box functionality in the system.
I'd like to be able to connect an AD or LFDS Group to a Forms Team to make team management easier
Hi Pieter,
We have this feature in our backlog items and it stays on top of the list, but we don't have a exact plan yet for when it will be implemented.
With Forms 11 Update 2(https://support.laserfiche.com/kb/1014352/list-of-changes-for-laserfiche-forms-11-update-2), you can add AD/LFDS group to team and the users in the groups will be automatically synchronized so the users from the groups can participant in the team as get email notification when task is assigned to the team, take team tasks etc.
I added the feature request of supporting using teams/users inside Forms as data source for lookup rule in our internal feature requests list, we will evaluate when plan for new releases.
Wanted to check and see if this was still being evaluated?
It has been evaluated when planning for the coming release for self-hosted Forms but other features were identified as higher priority so we don't have plan to work on it recently. We will look into it again when planning for future releases. For now, you can create views for the Forms database as documented at https://answers.laserfiche.com/questions/184051/TeamRoleUser-Views-That-Can-Be-SetUp-on-LFForms-Database and use them in lookup rules.
I wish LFDS accounts were a data source too, for this exact reason. We don't use forms teams often, but almost always have a need to dynamically assign tasks to individual users.
Either one would be great. We currently have to maintain external lookup tables for the purposes of allowing people to select users who are in the system.
What I have done is to create a Single Team with Roles which I then assign a Single User to each role. Then I assign the Task to the team role using Filters and select the Round Robin button. This way it pushes the task to the individual. When I want to change the user, I simple change the person assigned to the Role in Teams which means I don't have to change my Task assignment and I still have flexability to reassign Task when required.
You can also use the Team Role in a DB lookup to show the Role as a selection as opposed to Users
Like Matt, in some cases I too have built queries for the LF Forms DB tables for Teams info but it would be nice if Teams could be related back to Groups in LFDS to simplify the creation and management of users in a team/role
Steve, that's a good workaround. At the risk of getting further away from Blake's original point, I think the bigger picture here is team logic--being able to see each other's tasks and grab one if somebody is out--is great, but there's a lot of administrative overhead to make it work.
How would you use team as a data source?
1. Auto populate a field with all the teams names in the system?
2. Match a team name with a field then fill another field with the members in the team?
I have one form where the user can select from the teams to choose where their form will be assigned.
Another where they can select from the roles within a specific team.
I had one set-up to pick the users from a particular team, but in the end, I ended up doing something else, using an employee database instead because I trusted it to be more up-to-date.
@████████, both.