NLX

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.

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.

Have an action where you can feed a JSON string. Define what parameters to parse out and store values for in variables within an action set. This will be handy for AI use cases where JSON is returned as a string within a variable. Currently, the R...

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.

Add the ability to preview a page as a permission set so you can view the page with a security context without creating a test user in that permission set and adding a separate browser profile to login as a different user.

UPDATE: It appears you can drag a component left or right to take it out of a wrapper or put it in. If you have an index with a wrapper and sub components and you want to add something below the wrapper, Page Designer assumes you want it in the wr...

There are times you want to add a field to a form more than once. Page Designer does not allow this in the UI. Example use case: One field is editable and one field is read only. You use display logic to show the appropriate field.

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.

It appears client side logic cannot be included in filter grouping logic. Filter grouping logic appears to only affect server filters. For example if you have two client side filters (1 & 2) and then a server side filter, your grouping logic c...