colin_e
My feedback
-
105 votes
Thanks for your suggestion Mohammed.
An error occurred while saving the comment colin_e supported this idea ·
-
19 votes0 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e supported this idea ·
-
4 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e shared this idea ·
-
21 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
EuanAn error occurred while saving the comment colin_e commented
Managed Metadata is only PARTIALLY supported in web forms. Getting and setting values from Javascript is a major pain as there is no easy API for the form control, and things like default values, help text and validation have all been problematic.
I agree managed metadata should be a "first class" data type that is fully supported, on all platforms.
colin_e supported this idea ·
-
6 votes
colin_e supported this idea ·
colin_e shared this idea ·
-
6 votes
colin_e supported this idea ·
-
34 votes3 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
colin_e supported this idea ·
-
56 votes2 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
colin_e supported this idea ·
-
28 votes
An error occurred while saving the comment colin_e commented
Definitely. Please also ensure the Move and Copy actions return the item ID in the target list/library. Currently Copy doesn't do this which is a pain.
colin_e supported this idea ·
-
4 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment colin_e commented
This is a critical requirement in a typical enterprise environment. I am bascially prevented from using any of the web service based actions (Call Web Service, Query Excel Services etc.) because they require hard-coded login credentials.
Hard-coding passwords is really bad practice in general.
Further, just like the OP our IT policies mandate password changes every 90 days. Having a workflow set up that's guaranteed to fail every 90 days unless someone goes in and edits the code is a recipe for disaster. What happens when the guy that wrote the workflow leaves the oganisation for example?
colin_e supported this idea ·
-
248 votes4 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment colin_e commented
This is related to the requirement I have to-
1) Have a proper atomic "Move" action for list and library items, rather than having to use "Copy" then "Delete", which introduces issues like, what happens if the WF fails in between the two actions?
2) Have the "Copy" and "Move" actions both return the ID of the new item added to the target list/library.
Ideally Nintex would solve all these issues in one go.
colin_e supported this idea ·
-
5 votes
colin_e shared this idea ·
-
6 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e shared this idea ·
-
41 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e supported this idea ·
-
16 votes2 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
EuanAn error occurred while saving the comment colin_e commented
You can do this today by using custom CSS in the form.
-
7 votes
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e supported this idea ·
-
12 votes2 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Thanks for your suggestion.
I will update this idea if there are any updates to share.
Cheers,
Euancolin_e supported this idea ·
An error occurred while saving the comment colin_e commented
You might be able to do this with calculated fields and lookups today (not sure), but I agree a more dynamic image control is needed.
-
123 votes
colin_e shared this idea ·
-
16 votes1 comment · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
colin_e supported this idea ·
-
168 votes5 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
colin_e supported this idea ·
Agree. Currently I have had to hack a custom solution for this (for one attachment only) but it's hard work.