Enrico Knapp
My feedback
-
14 votes
Great suggestion and something we have been thinking about too. It’s not on our near term roadmap but we will continue to monitor interest.
Enrico Knapp
supported this idea
·
-
127 votes10 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →
Hi all,
This is still in the backlog to be done but it is not scheduled. When this is scheduled, I will update the status.
Cheers,
EuanEnrico Knapp
supported this idea
·
-
19 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanEnrico Knapp
shared this idea
·
-
67 votes
We understand that translations for the participants can be challenging. I will update this ticket if there is anything to share.
Cheers,
EuanEnrico Knapp
supported this idea
·
-
29 votes
This is currently a SharePoint constraint. Please see the MS uservoice and vote for this capability here. Thank you.
An error occurred while saving the comment Enrico Knapp
supported this idea
·
-
32 votesEnrico Knapp
supported this idea
·
-
4 votesEnrico Knapp
supported this idea
·
-
4 votesEnrico Knapp
supported this idea
·
-
3 votes
An error occurred while saving the comment Enrico Knapp
commented
Thats a good hint, Lisa. However customers would like to do that on their own and it's not really understandable why modifying the cases should be neccessary for the platform. But thanks anyway.
Enrico Knapp
shared this idea
·
-
252 votes
We have released the first phase of task attachments. You can now add attachments to the Initial task emails. For more details, visit our community blog https://community.nintex.com/t5/Community-Blogs/Task-attachments-and-CC-BCC-Workflow-for-Office-365/ba-p/112529
In the next phase, we will add an option to include attachments for Reminder and Escalation emails.
Enrico Knapp
supported this idea
·
-
459 votes
Reinstating this request as it is clear that delegation is required and not escalation.
Enrico Knapp
supported this idea
·
-
286 votes
Roanna Gunaratnam
responded
Hi All,
This is currently a SharePoint limitation, however we have made sure that our lazy approval feature only allows people who are assigned a task to specify an outcome.
As a workaround a user is able to query the task list to see who was assigned the task and who modified the task. We are looking at how make the task querying process easier. Thanks.
Enrico Knapp
supported this idea
·
-
472 votesOpen for voting · 14 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →Enrico Knapp
supported this idea
·
-
144 votesEnrico Knapp
supported this idea
·
-
7 votesEnrico Knapp
supported this idea
·
-
16 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Enrico Knapp
supported this idea
·
-
38 votesEnrico Knapp
supported this idea
·
-
99 votesEnrico Knapp
supported this idea
·
-
44 votesEnrico Knapp
supported this idea
·
-
449 votes35 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Hi All,
We’ve just released the ability to capture comments from via LazyApproval, apart from that you can also easily store and retrieve those comments (including ones made via Nintex Forms or directly via the task) into a new task action variable (Task comments).
For those who are specifically interested in capturing from LazyApproval the way you do is by supplying the outcome separated by a comma and then the comments .e.g. ‘Rejected, Need more detail before can approve’.
Check it out and let me know what you think…
Cheers, Rick
An error occurred while saving the comment Enrico Knapp
commented
Hi, this new functionality helps a lot. Thanks for that. However, right now in the comments generated there is always the name of the assignee the task was originally assigned. As there is no security check about who opens the task, people can forward the task notification email to delegate the issue. If another person now completes the task, the comments still show the name of the initial person as approver. It would be good to reflect the name of the person that finished the task.
Enrico Knapp
supported this idea
·
I constantly run over this issue. You can help yourself with saving the previous value in a separate field and moderate this with a workflow but this is a lot of effort, not elegant and costs you pecious action count in small workflows. So I really miss this functionality.