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

Add a control/feature to each column in a table/list that'll provide users with the flexibility to determine which columns they want sorted. For example, I have several columns that are UI only fields for purposes of running formulas or creating H...

In Actions, please allow users to select which model conditions they want to deactivate. For example: When you run a Query Model Action, you're prompted to select which models you want to query. You can select 1 or 10, it's a multiSelect drop do...

I'd like to have Nintex Apps connect to Nintex Gateway. Nintex Gateway allows me to connect to on-prem services like SQL on-Prem. Right now, I'm forced to duplicate SQL on-prem data to Nintex Data tables. It's just an unnecessary intermediate st...

When building an app, there isn't a 'clean' way to communicate with other team members. For example, In many apps you can do something like "@Tom can you please review", and Tom will receive a notification/email. I'd like this type of feature with...

When you click a chart to do something (show a modal for example), you often need to pass what was clicked to that modal. Right now, this is done via {{$Chart.point.name}}. This variable is nowhere to be found, I have to manually type it. I don't ...

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.