Allan Nevala
My feedback
-
47 votes
-
38 votes
-
1 voteAllan Nevala
shared this idea
·
-
41 votes
-
20 votes
-
15 votes
Thank you for your feedback. We are exploring a way to include new controls easily into SmartForms, which may address your request. Stay tuned for more information, and we'll update the status of this request as projects continue.
-
29 votes
-
6 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment -
34 votes
An error occurred while saving the comment Allan Nevala
commented
One use case is when you're doing mass item updates and you want to run the workflow, which modifies records, as if it were run by a service account so that no one contacts you about it down the road. A downside to this could be security (e.g. who actually modified it?) or who to contact if the values are now bad. Who made the changes so that we can backtrack? You'd need versioning turned on to track who or when.
Allan Nevala
supported this idea
·
-
56 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →Allan Nevala
supported this idea
·
-
323 votes11 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Lisa Tam
responded
Hi all, we have recently released a couple of features to address the root problem first which is around not having the visibility on the health of the content database and a reliable tool to perform the purge. Please check out the January 2019 Release notes for more details – https://community.nintex.com/t5/Release-Notes/Nintex-Workflow-2016-Release-Notes/ta-p/87905
Allan Nevala
supported this idea
·
-
1 voteAllan Nevala
shared this idea
·
-
15 votes0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →Allan Nevala
shared this idea
·
-
410 votes
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.
Allan Nevala
supported this idea
·
-
18 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →Allan Nevala
supported this idea
·
-
34 votes2 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Allan Nevala
commented
Here's a related idea post that suggests using the "Publisher" as the permissions used:
Allan Nevala
shared this idea
·
-
9 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Allan Nevala
commented
To clarify, "3) Allow 1st, 2nd, 3rd, or 4th weekday (e.g. Friday) of the month." as in "The 3rd Thursday of the month".
Allan Nevala
shared this idea
·
Have you tried adding a separate action (e.g. Query user profile) to get the user's manager, storing that in a variable, and then setting the "Delegate to" equal to the variable?