Nicholas
My feedback
-
31 votes
An error occurred while saving the comment Nicholas
supported this idea
·
-
70 votesNicholas
supported this idea
·
-
54 votesNicholas
supported this idea
·
-
39 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
The work around for this is to create a list with the appropriate columns to store the data one wants. Use update list to store the data and query list to retrieve the data.
Nicholas
supported this idea
·
-
36 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
The work around for this is to create a list with the appropriate columns to store the data one wants. Use update list to store the data and query list to retrieve the data.
Nicholas
supported this idea
·
-
34 votes
Thanks for your feedback. We are reviewing this and encourage other users of UserVoice to vote if they feel this is important.
Nicholas
supported this idea
·
-
201 votes
Hi all,
We do not have any immediate plans to support this feature but will update this ticket if our position changes.
Cheers,
EuanNicholas
supported this idea
·
-
89 votes
Hi Sridhar,
Can you share some examples of how you are using constants in your workflows?
Ta, Rick
Nicholas
supported this idea
·
-
67 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
468 votes
Reinstating this request as it is clear that delegation is required and not escalation.
Nicholas
supported this idea
·
-
55 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
99 votesNicholas
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.
Nicholas
supported this idea
·
-
75 votes5 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
6 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
EuanNicholas
supported this idea
·
-
21 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
35 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
16 votes0 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
supported this idea
·
-
Support lists with versioning turned on and where "Append Changes to Existing Text" is set to "Yes."
373 votes46 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →Hi all,
There is no movement on this feature at this time. If the status changes, I will update this ticket.
Cheers,
EuanNicholas
supported this idea
·
-
76 votesNicholas
supported this idea
·
just a suggestion, please use something like the google time zone api to fix this issue, it is not ideal to have to republished scheduled workflows every 6 months