The Users-All picklist is not good enough. Please provide a user selection field to be based on a group(s). Either define this on the field level (idea pic below, like section permissions) or allow to define using picklists based on group(s). Consider a picklist called “reviewer”: I do not want the user to be able to select people that are not suitable (or who might not have permission) I want a small list of people to choose from. I do NOT want a Supplier user to see other Suppliers’ users. The typical workaround, using an Employee reference workspace (and picklists based on “where IS_REVIEWER is TRUE”, etc) is often a poor solution: ☹️Good flexibility, but high config effort, and needs synchronising to group members for permissions. ☹️Resulting field is “Picklist from a workspace”. This cannot be used in a Workflow transition PRE-CONDITION FILTER ☹️This means that I MUST use either a condition script, poor performance and cannot benefit from the PRE-CONDITION FILTER ☹️Result is that MY OUTSTANDING WORK has poor performance. The App Store apps all beautifully demonstrate this fundamental problem(!) As you start to scale the deployment, the “Users All By Name” becomes unusable, and the default Apps are seriously undermined. Conclusion: 😀For large installations, we need more ability to configure members of user selection fields. 😀This would allow to move to PRE-CONDITION FILTERS… 😀avoid Condition scripts 😀avoid the terrible performance seen on My Outstanding Work for large deployments, that cannot currently are forced to use Condition scripts We need even more than this in future…. 😋A picklist that can select groups in the system. 🤗An approval team item could select this group. 😍Then I want a task to be able to select an approval team, and have its group control the list of users selectable. … But the above would be a good start, and a massive improvement in the product for little development effort. Impressive mockup
Show More