94 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
18 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Hey guys, would updating the email notification messaging to reflect that the workflow was intentionally cancelled meet your needs?
Happy to say this feature has now been released..
36 votesRoanna Gunaratnam responded
Hi, Could you please contact me regarding this request, there may be an alternative solution that may meet your needs. Thanks.
I’m happy to say this feature has now been released, for more detail on how it works check out the blog – https://community.nintex.com/t5/Community-Blogs/Introducing-Workflow-failure-notifications-for-Office-365/ba-p/107432
446 votes35 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
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…
Without going into the technical detail; the previous value made available in conditional start is actually the current value just before any updates are made to the item. When the item is updated, we lose the ability to get the value prior to the update.
To restate the workaround as indicated in the idea; create an additional column in the list or library and update this with the current value of the column of interest. Then when the actual column is updated, the previous value is still available in the additional column. Of course one need not make this additional column visible in the view or Form so the users are not confused.