Anonymous
My feedback
-
57 votes2 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Anonymous
supported this idea
·
-
6 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
-
125 votes8 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanAnonymous
supported this idea
·
-
44 votes
Hi all,
This feature has been depriortized at this stage and moved into the backlog. I will update this ticket when we revisit this idea.
Cheers,
LisaAnonymous
supported this idea
·
-
468 votes
Reinstating this request as it is clear that delegation is required and not escalation.
An error occurred while saving the comment Anonymous
commented
We really need this functionality!
Anonymous
supported this idea
·
-
6 votesAnonymous
shared this idea
·
-
11 votesAnonymous
supported this idea
·
-
20 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Anonymous
shared this idea
·
-
78 votes3 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Anonymous
supported this idea
·
So here are our use cases:
1. We are using "Office 365 update item permissions" to control who has the ability to edit list items. We only want the user who has been assigned a task to edit the item. Afterward, they only have read access. Default permissions are Add & View Items. Because the task id takes a while to get assigned and update the permissions, when the user clicks on the url in email notification to complete their task, it doesn't allow them to do so for several minutes. It would be great to be able to set the initial email notification to None and add the Send an Email node after the permissions take effect (task id found).
2. One of our workflows goes through 9 levels of approval. At level 5 of the approval process, a team reviews all of the open items. Then one of the team members needs to go in and mass approve/reject all of their open tasks for the items discussed in the meeting. They don't want to get all of the email notifications... just approve/reject through Workflow Tasks list.