Related I think..
If you set a status in the workflow column it also modifies the Item the workflow is running against, thus changing the date modified.
AND worse still if you wish to state an approval workflow has completed, as the last action, you can't because it resets the approved state to pending!
Thanks for the feedback. We are reviewing this request with a view to inclusion in a future release.
Why no comments from Nintex on this.. It's been over 2 years now... customers are desperate to have the features that already exist onPrem!
I'm beginning to wonder if this is a deliberate act by Nintex, with workflows under 5 actions being 'free' without inline functions it is virtually impossible to do anything useful... therefore you have to work around the issues with multiple actions...
If I'm reading the very uninformative help correctly, inline functions are only available in forms? Is that correct?
If so, come on Nintex, you can't expect people to migrate from onPrem with these feature, to Online where the useful/critical bits are missing.
Couldn't agree more with all comments on the performance. So frustrating when coming from the OnPrem Nintex.
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.
Completely agree with Joanne below, came in this morning to be told by a user that the workflows haven't been working for a while.
Had to very slowly terminate 30+ suspended workflows from the last week, as they had all silently stopped...
It really doesn't give a good impression that admins have no idea of failures until the user base tell us.
I hope Hawkeye isn't your answer because doubling our license cost isn't the answer!!!
446 votes33 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
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…
We really need a fix on this to bring us back up to the functionality we had OnPremise.
You've got to wonder whether this is a deliberate ploy to ensure your workflows don't get under the 'free' 5 action limit!!!?
Would also be useful to have a 'Where used' report linked for from this usage report, so we can track where the WFs are being used.... This should be available to 'Standard' license customers as well as those with HawkEye.....
515 votesOpen for voting · 33 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →
Totally agree with Peter...
Maybe graphical view is a bit ambitious, but a run log of every action/status must be achievable?
Also a big fan of Nintex, but your not helping us with the O365 migration, with this critical feature missing.
With this is so high up the voting, are we going to get news on this soon!!?
I'd disagree with the statements about using Hawkeye to provide this level of logging, Hawkeye is not available under the Standard license.. Any additional progress monitoring / debugging must be provided via the standard platform..
629 votesOpen for voting · 31 comments · 1 - Nintex Workflow for SharePoint · Flag idea as inappropriate… · Admin →
194 votes19 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” ?
Yes that is exactly what we need... Thanks...
So surely it's just a copy n paste of the code and we're good to go!!!!! ;-)
Any plans,comments from Nintex on this request, it is a serious limitation compared to OnPremise?
Please add Contains, Not Equal, Begins with, Ends With. At least Not Equal to so that we can compare if the Item is Modified
182 votesOpen for voting · 12 comments · 3 - Nintex Workflow for Office 365 » Designer · Flag idea as inappropriate… · Admin →
22 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
17 votes1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Russ H shared this idea ·
I am pleased to announce this capability has rolled out this week as a Component Workflow. Learn more at https://www.nintex.com/blog/whats-new-component-workflows/
623 votes43 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
To support this requirement we’ve just release the following features
- Specify a customizable sender display name for both email and task actions, we understand one of the main requests was to be able to supply a custom from email address however due to many of the limitations in the cloud we are currently unable to deliver this request and so hopefully being able to add a From display name will get you one step closer..
- Add a customizable Reply To email address for the email action so you can control the email address when people hit reply.
Hope you enjoy these features and be great to hear any feedback once you try them out.