Barry
My feedback
-
92 votesBarry
supported this idea
·
-
54 votesOpen for voting · 1 comment · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Barry
supported this idea
·
-
450 votes
Reinstating this request as it is clear that delegation is required and not escalation.
Barry
supported this idea
·
-
40 votes2 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →Barry
supported this idea
·
-
10 votes
An error occurred while saving the comment Barry
supported this idea
·
-
11 votesOpen for voting · 0 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →Barry
supported this idea
·
-
1 voteBarry
shared this idea
·
-
41 votesBarry
supported this idea
·
-
331 votesBarry
supported this idea
·
-
56 votes
An error occurred while saving the comment Barry
commented
Given the frequency with which workflows suspend for various unhandled reasons e.g. failing to communicate with SP Online, time outs etc I think this is essential. I am constantly dealing with users chasing up..."where is my purchase order at?" etc. when in fact the workflow suspended weeks ago for some random reason. We need to be able to sort / filter 100s of in progress POs by internal status.
Barry
supported this idea
·
-
22 votes
Hi all,
I am pleased to announce the choice controls (single/multiple) can now support commas.
Cheers,
EuanBarry
shared this idea
·
-
298 votes
Hi all,
Thank you for your interest in this idea. We have no plans to support the Event content type at this time.
If our position changes, I will update this idea.
Cheers,
EuanBarry
supported this idea
·
-
173 votes
Hi all,
We have no plans to incorporate BSC into Nintex Forms for Office365 right now.
We have released Data Sources for Nintex Forms for Nintex Workflow Cloud which may fulfil your requirements.
Cheers,
EuanBarry
supported this idea
·
-
Support lists with versioning turned on and where "Append Changes to Existing Text" is set to "Yes."
360 votes44 comments · 4 - Nintex Forms for Office 365 » Form Filling Experience · Flag idea as inappropriate… · Admin →Hi all,
This is no longer planned but is still in the backlog to be done. I will update this ticket if the position changes.
Cheers,
EuanBarry
supported this idea
·
-
699 votes52 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.
Barry
supported this idea
·
-
377 votes
Happy to say this feature has now been released..
Barry
supported this idea
·
-
469 votesOpen for voting · 14 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →Barry
supported this idea
·
-
750 votesOpen for voting · 48 comments · 3 - Nintex Workflow for Office 365 » Runtime · Flag idea as inappropriate… · Admin →Barry
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
Barry
supported this idea
·
-
359 votes
An error occurred while saving the comment Barry
commented
2.5 years ago I saw an update from the community manager saying watch this space...well??
Barry
supported this idea
·
I'd like to support the specific case described above! Please provide error handling when sending email using the external sending service. Currently, if an invalid recipient is added the workflow terminates. A long and complex workflow process has terminated near its end because someone has entered .com instead of .com.au ! If the error could be captured this could be handled gracefully.