David Racchini
My feedback
-
92 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
43 votesOpen for voting · 0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
102 votes9 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
89 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Roanna Gunaratnam responded
Hi All,
With each of the requested actions could you please tell be what scenarios you are using each of them? From the list could you please order them in most important to each import?
Cheers,
RoannaDavid Racchini supported this idea ·
-
188 votes5 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
88 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
267 votesOpen for voting · 12 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
203 votes
David Racchini supported 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.
David Racchini supported this idea ·
-
248 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
281 votes
Hey guys, would updating the email notification messaging to reflect that the workflow was intentionally cancelled meet your needs?
David Racchini supported this idea ·
-
476 votes21 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Jon Hardy responded
The task ID is populated once the task is completed. Before this the task list items can be locked by the task engine for processing and a workflow accessing this task may fail. There has been therefore a strong reservation form our Engineering group to implement this capability even if technically feasible.
If one wishes to delegate the task then the delegation should be used.Should you have other use cases for accessing the task list before the task is completed then please let us know what they are. There may be an alternative way of meeting this need that will not introduce the possibility of workflow failure.
David Racchini supported this idea ·
-
9 votes0 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion Ryan. We will be revisiting how data driven controls are triggered with Universal Forms.
I will update this feature when I have more detail.
Cheers,
EuanDavid Racchini supported this idea ·
-
38 votes0 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion Caroline. As we are building Universal Forms, we are very aware of this limitation and looking at how we can address through the new technology.
I will update this feature when we ship Universal Forms for SharePoint.
Cheers,
EuanDavid Racchini supported this idea ·
-
128 votes4 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion Jason.
As we are currently working on Universal Forms and rebuilding all the functions in our new forms technology, I will add this to the backlog.
Cheers,
EuanDavid Racchini supported this idea ·
-
310 votes19 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Hi all,
We will soon begin the development of the List Lookup control for Universal Forms and take this feature request under consideration.
Cheers,
EuanDavid Racchini supported this idea ·
-
35 votes0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
David Racchini supported this idea ·
-
28 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Thanks for the feedback, we are currently reviewing this request.
If this is something you would like to see added, please remember to vote up the idea.
David Racchini supported this idea ·
-
13 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Alex responded
Hi Ken,
Thanks for the feedback. I am interested in understanding this requirement a little more. Can you give me some specific scenarios where the current approach is clunky
David Racchini supported this idea ·
-
26 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
Thanks for the feedback, we are currently reviewing this request.
If this is something you would like to see added, please remember to vote up the idea.
David Racchini supported this idea ·
David Racchini shared this idea ·