Nicholas
My feedback
-
31 votes
An error occurred while saving the comment Nicholas
supported this idea
·
-
641 votes
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
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
·
-
38 votesNicholas
supported this idea
·
-
161 votesNicholas
supported this idea
·
-
449 votes35 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Hi All,
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…
Cheers, Rick
Nicholas
supported this idea
·
-
459 votes
Reinstating this request as it is clear that delegation is required and not escalation.
Nicholas
supported this idea
·
-
286 votes
Roanna Gunaratnam
responded
Hi All,
This is currently a SharePoint limitation, however we have made sure that our lazy approval feature only allows people who are assigned a task to specify an outcome.
As a workaround a user is able to query the task list to see who was assigned the task and who modified the task. We are looking at how make the task querying process easier. Thanks.
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
·
-
258 votes23 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
Please have a look at the condition builder just released as part of conditional start. Is this the kind of condition builder that you need in “wait for field change in current item” ?
Nicholas
supported this idea
·
-
75 votes5 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Nicholas
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