👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you are looking for the Nintex roadmap, you can find that on Nintex Community
We ran into a security issue on a rather simple process/solution we were attempting to design for an event that is coming up:
Panel of judges by region should review a video and documentation submitted by contestants. They need to score the video and documents uploaded by the user, and score the entries based on categories on the task form.
Each region has a group of judges that all need to review at the same time. This varies between 5-15 judges pers region. The simple approach would be to do an assign a task and send the same task to group of judges based on dynamic conditions to set the task assignees. We don't want judges seeing scores the other judges submit.
The issue is, the help documentation is a bit misleading, and we thought if we hide completed task form details - that all task forms, with the exception of the task assignee's own task - would NOT be visible. This seems to only work for other tasks within the same instance - it hides the task details and completed forms.
It's not feasible for dynamic approvals to do parallel tasks, unless the # of tasks do NOT change - it's far too much work for something so simple.
An alternative is also to create a component workflow to mitigate that issue to fire off tasks per judge. If we did this, we run into issues where we are forced to managing tasks in SharePoint lists to query back ALL the information we need from the task form itself later on in the process. NWC actions are limited and only provide system data for task details, not custom fields created by designer on task forms. It's extremely frustrating to manage tasks outside the system that offers task management solutions for reviews and approvals.
I have had to do this for two processes so far, and it's not a fun concept. Time consuming and managing of task status and data and so much more, it's a pain!
We need the completed forms of each task assignee also hidden from each task assignee. Add an option to the My Nintex Settings to also hide individual responses of the same task.