Workflows Form Error: Assignee does not have update content access to queue
Best Answer
-
Nate - I’ve had customers take the approach of dynamically creating the group, adding the users, sharing the queue, then deleting the group and so on.
I have a function I can share with you, that will allow you to programmatically share a queue. Here’s another thought. Could you make a dynamic group with a rule that automatically puts the user in the group, and share the queue with that group? Then enable assignee security so they can only see what’s shared with them?
I’d imagine you could create a rule that would only apply to new users, and have them automatically be in the new users group. You could also have a workflow that runs whenever a new user is added that puts them in the new users group, and then wants some number of days and removes them from that group (60 days later or something) if there wasn’t an easy way to make the rules you wanted for the dynamic group.
0
Answers
-
@NateBI , is the task assigned to a group? Or do an individual?
You do need to make sure that you go into Queues, and share the queue with the appropriate people. That isn't something that we've done dynamically in the workflow, but suppose I could help you write a function to do that.
The current guidance would be to go to Task Center and share the queue with all the people who may need to have a task assigned to them in it. If they don't have access to the Queue, it will fail as you see here. Leveraging GROUPS in these cases (sharing the queue with a group) can be a good work around to having to give a bunch of individuals access.0 -
The task is assigned to individuals as a part of an onboarding workflow. The group method is less appealing, I presssume I would need to create a group, assign new users to the group, asign tasks to the group and track the responses at the individual level (feels like a lot of faff). The function may be the way to go here @DanHendriksen. That being said, would the function require doing all of these actions just backend(pydomo) 😅
0 -
Nate - I’ve had customers take the approach of dynamically creating the group, adding the users, sharing the queue, then deleting the group and so on.
I have a function I can share with you, that will allow you to programmatically share a queue. Here’s another thought. Could you make a dynamic group with a rule that automatically puts the user in the group, and share the queue with that group? Then enable assignee security so they can only see what’s shared with them?
I’d imagine you could create a rule that would only apply to new users, and have them automatically be in the new users group. You could also have a workflow that runs whenever a new user is added that puts them in the new users group, and then wants some number of days and removes them from that group (60 days later or something) if there wasn’t an easy way to make the rules you wanted for the dynamic group.
0 -
No matter what, responses will be tracked at the individual level, by the way. The metadata will always show which user actioned/completed the task.
0 -
@DanHendriksen Ok I'll have a crack at it and keep you posted thanks!
0 -
Nate, how did you get on?
0
Categories
- All Categories
- 1.9K Product Ideas
- 1.9K Ideas Exchange
- 1.6K Connect
- 1.3K Connectors
- 305 Workbench
- 6 Cloud Amplifier
- 9 Federated
- 3K Transform
- 107 SQL DataFlows
- 648 Datasets
- 2.2K Magic ETL
- 4K Visualize
- 2.5K Charting
- 774 Beast Mode
- 75 App Studio
- 43 Variables
- 733 Automate
- 186 Apps
- 471 APIs & Domo Developer
- 62 Workflows
- 14 DomoAI
- 40 Predict
- 17 Jupyter Workspaces
- 23 R & Python Tiles
- 403 Distribute
- 117 Domo Everywhere
- 277 Scheduled Reports
- 9 Software Integrations
- 137 Manage
- 134 Governance & Security
- 8 Domo Community Gallery
- 44 Product Releases
- 12 Domo University
- 5.4K Community Forums
- 40 Getting Started
- 30 Community Member Introductions
- 113 Community Announcements
- 4.8K Archive