Quick start guide

Note: This quick start guide assumes you are working in a Nintex CE Platform environment. Available capabilities, options, and use cases may differ depending on your subscriptions and entitlements.

Nintex Apps is the application-building capability within Nintex CE Platform. It enables users to create applications that connect to data repositories and services using a user-friendly, drag-and-drop interface. With Nintex Apps, you can build rich application experiences for any device that allow users to interact with business data and processes.

Nintex Apps works with other Nintex CE Platform capabilities to help you create integrated solutions that connect data, automate processes, and improve user experiences. For more information, see Solutions.

Jump to:

Introductory training course

The best way to begin understanding Nintex Apps is by completing the Nintex Apps - Level I Nintex University learning path (login required).

After completing Level I, you can move on to the Nintex Apps - Level 2 Nintex University learning path (login required).

Nintex Apps concepts

Nintex Apps includes the following core concepts:

  • Create an app, which is a collection of pages, connections, files, permissions, and other assets. For more information, see Create and customize apps.

  • Connect to your external services and data. Each connection is made up of endpoints, credentials, and other settings required to access a particular service. For more information, see Connections.

  • Design and configure your app's styles using design systems. For more information, see Design system.

  • Design pages, where your end users interact with your app. Each page is an arrangement of components, models, and other elements. Your pages display data from your connection in components styled using your design system. For more information, see Page Designer.

  • Deploy an app in the following ways:

    • Standalone app: Deploy the app, publish its pages, and assign permissions. For more information, see Deployment.

    • App in a solution: Add the app as an asset to a solution when you create it, or add an existing standalone app to a solution later. Deploy the app as part of a solution package. For more information, see Packages.

Access the Apps page

  • Go to Apps.

You can access the following features:

  • Apps: View, search, sort, and filter the apps you have access to.

  • Create an app: Create a new app and configure it using App Designer. You can configure pages, connections, permissions, and all app assets.

  • Manage apps: Update app settings, preview apps, and delete apps.

  • Design system: Create and manage design systems that define the styles and visual elements used across your apps and pages.

  • Files: Manage assets used by Nintex Apps, including static files and certificates.


Page Designer concepts

The Page Designer is the workspace used to design and customize pages in Nintex Apps. Create or edit pages using the drag-and-drop interface, and configure components and actions. You can further enhance your pages with action flows, display logic, and JavaScript. For more information, see Page Designer.

Use components to build a UI

Components are visual building blocks that define the look and functionality of your page. Add components to the canvas to design the layout and content your end users see.

Some components provide layout options, while others display and interact with data. Components require a connection to a model to access data. For more information, see Components.

Use models to retrieve data

Models connect your connections to components in your app. When you create a model, select a connection, an object, and the fields you want to retrieve as data. Models use conditions to filter incoming data and can trigger action flows based on specific events. For more information, see Models.

Connect models and components to create pages

Connect models to components to display and interact with data on your pages. A single model can connect to multiple components. When multiple components use the same model, changes made in one component update the other connected components.

Connecting components to the same model helps create dynamic pages that provide end users with immediate feedback and simplify complex layouts.

Use action flows, display logic, and JavaScript for dynamic pages

Add actions and logic to your pages to control how they behave. Pages can respond to end user input, show or hide content, and trigger workflows or other actions.

  • Action flows: Update the page, trigger workflows, and perform actions based on user interactions.

  • Display logic: Controls when and how components appear on a page.

  • Nintex Apps and JavaScript: Add custom functionality, create formula functions, and use external libraries.

Use Merge syntax to insert values from models, connections, pages, and other sources into any field that supports merge syntax.

Save and preview pages

  • To save changes, click Save.

  • To preview the page at runtime, save the page and click Preview.

If the page has been published, any saved changes will be visible to end users.

Important:  Making changes directly to pages in a production environment while end users are accessing them can result in unexpected behavior. Follow a clear application lifecycle management process when making and deploying changes.

Deploy and publish

Deployment and publishing make apps available across environments and to end users.

App builders create and test apps in a development environment. Once an app is ready, deploy it to another environment, such as a test or production environment. Standalone apps use the Nintex Apps deployment process, while apps included as assets in a solution use a solution package for deployment with the other solution assets.

Follow an application lifecycle management (ALM) process when moving apps between environments to help ensure changes are tested and validated before they become available to end users.

The deployment package includes the app and its associated resources, including the URLs configured for the app and its pages.

After an app is deployed to an environment, configure the app for end users by setting up page URLs and permissions. Page URLs determine where end users access app pages, and permissions determine which end users can access the app and its resources.

Once page URLs are configured and users have the required permissions, the app is considered published and available to end users.