All ideas

Overview When a Workflow is triggered from Nintex Apps, it should be possible for the workflow to return data back to the app, for example saying that it has run and perhaps sharing output variables. A key use case is when Workflow creates a recor...

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.

This has happened to me several times that the field is read-only and it takes a lot of investigation (or one of your excellent support agents) to identify the issue. It would be nice if the app checked and unchecked the read-only option when you ...

Currently Image columns created in SharePoint lists are not discoverable through NAC Workflows or SPFx Forms. This is a great feature within SharePoint so would be great for Nintex to start supporting this column type.

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.

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.

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...