LaKisha
My feedback
-
55 votes4 comments · 2 - Nintex Forms for SharePoint » Form Filling Experience · Flag idea as inappropriate… · Admin →
I am pleased to announce this feature will be included in the new Universal Forms in the future.
An error occurred while saving the comment LaKisha
supported this idea
·
-
14 votes0 comments · 2 - Nintex Forms for SharePoint » Form Filling Experience · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers, Euan
LaKisha
supported this idea
·
-
18 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
EuanLaKisha
supported this idea
·
-
133 votes5 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Returning a data set rather than a single value is something we have discussed internally and are interested to explore. We will be revisiting how we query for data as we are building Universal Forms.
LaKisha
supported this idea
·
-
23 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment LaKisha
commented
The current action uses this API call to download the document /accounts/{accountId}/envelopes/{envelopeId}/documents/1, so it only retrieves the first document in an enevelope, instead of using /accounts/{accountId}/envelopes/{envelopeId}/documents/combined, which retrieves all of the documents in the envelope.
LaKisha
shared this idea
·
-
248 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
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.
LaKisha
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.
LaKisha
supported this idea
·
-
102 votes9 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
238 votes12 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
701 votesOpen for voting · 52 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
10 votes0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
267 votesOpen for voting · 12 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
43 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
shared this idea
·
-
78 votes3 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment LaKisha
commented
I used not(contains(string,element))
-
47 votesLaKisha
supported this idea
·
-
11 votesLaKisha
supported this idea
·
-
47 votesLaKisha
supported this idea
·
-
25 votes0 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
-
16 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →LaKisha
supported this idea
·
This is the one item that is preventing me from converting my infopath forms to Nintex Forms!