All ideas

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.

If you use a workflow form component in Apps, it does not surface/calculate the user context. Usually this is not needed because the workflow can retrieve the user context variables but on the odd occasion where we want to work with them on the fo...

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.

Take data within an action set and store it into a collection variable. This is handy when kicking off component workflows. collections is the primary way NAC accepts rows of data to be used in repeating sections of forms.

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.

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

There are no elegant solutions currently for comparing versions of app pages when deploying between environments

Quick way to add a table component with all the fields in a model. We had this as a double-click on model in v2.