đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
We need the following default values enabled for the following on task forms and start event forms in Nintex Automation Cloud ("NAC").
People Picker Fields - If Active Directory is enabled in tenant why wouldn't ID be an option to default value as or login username etc?
Other times we want to default a person in a custom "initiator" control vs system initiator data for when a user is opening a form it defaults to their name but left unlocked in case the person filling form out is not the same person the request is for.
We can't pass data through for updating purposes - we can only show people information in text, read-only on task forms. If we need to default it and leave it open for editing on task forms, we can't. We have to show it and give a box to "update details" and allow them to then fill out a blank canvas. It's extra steps just to update people and make it clear what the user is being asked to do.
Multi-Choice Fields - this is a major issue considering we have forms that request multiple information and I can pass the data from start event form to sharepoint but not back from sharepoint to a task form since default value doesn't exist for these fields. When displayed in text it looks horrible.
We also have a need to have users COPY a previous form submission through NAC, the option doesn't exist YTD. Because of this we have to use a data source to filter users previous requests stored in SharePoint list. They pick a request and then we have rules to "auto-populate" values into controls on start form so they don't have to fill out a 8 page form all over again. I can't auto-populate any of these addressed field types because default values do NOT exist on control.
Repeating Section - we can't default a repeating section, I think this should be allowed in configuration if the repeating section is coming from another nintex start event form or task form, I understand not being able to do it between SharePoint and NAC repeating sections but why not within the same environment? I was able to pass repeating sections to sharepoint and then manipulate the data string for a repeating section to show back up on a NAC task form but because default value didn't exist it was a failed and wasted attempt and could not be done.
Outcomes - can't do a default value for outcomes.
1
Started
4
Completed
2
Completed
1
Started
An update to my Jun 14 comment...
My coworker showed me how to get the value of the first person in a people picker using the function first([Form].[ControlName].[Email).
And if you're reading comments on this idea. You may also be interested in upvoting this idea:
Populate a People control with an email address using a form rule
https://ideas.nintex.com/ideas/CNV-I-264
I see this Idea is in "Started" status and I'm aware that we are now able to set the current user email as a default value in a people picker.
What is the status of setting the value of a people picker via a form rule?
We would also like to be able to get the value of a people picker in a form rule.
We have also submitted this complementary idea at the request of Nintex for the ability to set the values of multi-choice controls. Please up-vote this idea if you're reading this. :-)
https://ideas.nintex.com/ideas/CNV-I-241
The common theme here is that these are collection controls, so we are hoping to receive the gift of this functionality for all the collection controls.
Being able to pre-populate a repeating section would be extremely helpful from a user experience perspective. We already have scenarios implemented where this would improve usability. People have expressed frustration about having to manually re-populate a repeating section when the information that should go in them has changed.
Hello, I’m thrilled to share that the people picker now supports default values.
The key elements of this idea for me are:
ability to default the people picker to the current user or other varable.
Ability to set the default, min, max number of rows to a variable rather than hard code number.
Upvoted this for the People Picker Fields. Should be able to set the default value of the people picker to the authenticated user.