Deanna Velasco
My feedback
-
48 votes
Thanks for your suggestion. We will update the status of this idea if there is anything to share.
Cheers,
EuanAn error occurred while saving the comment -
25 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
67 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
6 votesOpen for voting · 1 comment · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →
-
3 votesUnder Review · 0 comments · 5 - Nintex Workflow Cloud » Workflow Designer · Flag idea as inappropriate… · Admin →
-
22 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
24 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
17 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
238 votesPlanned · 3 comments · 5 - Nintex Workflow Cloud » Form Designer · Flag idea as inappropriate… · Admin →
-
50 votes
Thanks for your suggestion. I will update the ticket if we have anything to share on this idea.
Cheers,
EuanAn error occurred while saving the comment Yes. Hiding or disabling the submit button would prevent a lot of issues we see where someone opens the form just to look at it while at the same time someone else has the form open to edit it. The editing person submits the form and their changes get saved to the list item, but then the person that was just looking at the form, also hits submit which then submits all of the old information in the form back to the list, overwriting what the other person just added.
If I could disable or hide the submit so that users can't click it unless they actually updated information (based on a rule I create) then it would prevent me from having to go in and fix these issues.
-
6 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
98 votes
An error occurred while saving the comment Any updates on this? like the others, I am not understanding why this request is being ignored.
-
57 votes2 comments · 3 - Nintex Workflow for Office 365 » Store / Actions · Flag idea as inappropriate… · Admin →
-
698 votesOpen for voting · 50 comments · 1 - Nintex Workflow for SharePoint » Workflow Actions · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment I am a new Nintex customer (using mainly NWC) and during my development I just realized we can't ever view a completed form and this honestly shocks me. We keep our completed forms for many years for auditing and legal archive requirements and most of our processes will require this. We should not have to pay extra money for such a simple requirement. With almost 700 votes, why isn't this made more of a priority with the development team?
-
20 votes
Thanks for your suggestion.
I will update the ticket if we have anything to share on this idea.
Cheers,
Euan -
19 votes
Hi all,
This is currently being reviewed.
Cheers,
EuanAn error occurred while saving the comment Yes this would be very helpful so that we could easily and efficiently reference those files throughout the workflow in forms without having to create so many steps to pull them back in from the list item and loop through each!
-
66 votesPlanned · 5 comments · 5 - Nintex Workflow Cloud » Form Designer · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment The situation is this: A form routes to different people and those different people are allowed to make edits to those fields. If the field is a data lookup, it is not possible to 1) display the previously selected value at the same time as 2) allowing the options for the data lookup.
I think if we can set a default value from a list or start event variable, then it should show that value first in the data lookup field but the user could click on that field and change it based on the other values returned from the data lookup connection.This situation is very common for many of my forms.
I hope you will consider this. -
70 votes
Hi all,
We are currently working on the ability to return multiple properties from a Data Source. Will update this feature when I have more to share.
Cheers,
Euan -
133 votes5 comments · 2 - Nintex Forms for SharePoint » Form controls · Flag idea as inappropriate… · Admin →
Returning a data set rather than a single value is something we have discussed internally and are interested to explore. We will be revisiting how we query for data as we are building Universal Forms.
An error occurred while saving the comment I am hoping to be able to return multiple data fields in a single SQL query in NWC
-
38 votes
Thanks for your suggestion. We will consider a button control for future releases.
Cheers,
Euan
Please can you get this working? I am not able to use NWC due to missing functionality so I still have to use O365 workflows and this limitation is very painful.