All ideas

Currently, the "Required" field properties are only visible near the Field label in a Form when the Form is in Edit mode. It would be helpful to be able to have a property to allow that Required property to be visible in other modes besides Edit.

Store procedure is a very important component when client decided to store their data in SQL Server. Store procedure could easily build the data schema that need to display in Nintex Apps.

When building Action Flows, we can drag and drop actions. It would be nice to be able to copy & paste actions, then drag them where we want them.

It would be nice if we could make the Skuid.debug console command made into a component that we could put directly into a page. Taking the code out of it and making it low code/no code.

Many Salesforce orgs have integration licenses included with their Salesforce orgs, and it would be incredibly valuable to use an integration license rather than a full Salesforce license to connect Nintex. That would allow us to use a unique user...

Would you please allow the dynamic assignment of the design system on a page? Example: Two design systems (light mode & dark mode)User can set and store their preferred design system in an object related to their user id or change their design...

The current File Upload component has no ability to restrict the type of file being uploaded, which means a custom solution (Apex trigger) is needed for this requirement. It would be nice to have the ability to set the file types allowed within th...

More robust Formula documentation for Ui-Only formula fields, including examples and real-world use cases

More robust Javascript documentation, including examples and real-world use cases

When you have a complex app and multiple components and styles, it would be helpful to have a way to see For each component, which pages it's used on For each style variant, which pages it's used on