Note: Nintex Apps data centers are located in West US and Australia (AUS). In-region processing of Nintex Apps data is only available in these regions.

Modals

A modal—sometimes called a popup—is a dialog box that overlays, a page, allowing the end user to see and interact with a selected set of Nintex Apps components and their data without actually leaving the page.

How data is displayed within a modal is determined by which components are added to the modal's dialog box.

Using Modals

Add modals wherever you can add action triggers to the page. Add a Show modal action wherever action flows are used (for example, on the Table component when creating row, global, or mass actions, or interactions.

Once you create the trigger, add an icon and/or label that end users can select to open the modal.

Then, customize the modal box itself by clicking Configure modal:

  • Add a Title that will display on the modal's header. You can also adjust the Width or even change the icon used to close the modal.
  • Since the modal is essentially a container, add components to the modal to display data:
    • As always, be sure to attach the component to the appropriate model, and configure it to display the necessary data.
  • To prevent a modal from accidentally closing when a user clicks elsewhere, consider enabling the Restrict closing the modal property. When enabled, the only way to close a modal is to click the X button within it (or leave the Nintex Apps page entirely).

Best Practices

  • Because modals are a way to display a small subset of data without navigating away from the page, they often include one (or more) data components. But bear in mind that a modal is a limited space, a temporary "working area." Use modals for specific, concentrated tasks that the user needs to complete before returning to a workflow on the underlying page.
  • To display a more complex or detailed set of tasks in an element that nonetheless allows the end user to easily navigate back to their main workflow, consider using a Tab Set component.

Properties

Component properties

  • Title: A descriptive name for the modal that will appear in the modal's header.

  • Full screen modal: If checked, the modal displays across the available width of the screen.

  • Width: Adjust the width of the modal using percentage, pixel, or other forms of measurement.

    Note:  This property is not available if Full screen modal is checked.

  • Restrict closing the modal: When enabled, modals can only be closed by clicking the X button within the modal—pressing Escape or clicking outside the modal will not close it.

  • Show close icon: If checked, the modal displays an icon at the corner that can be used to close the modal.

    • Close icon ( optional ): The icon used to close the modal. Click the field picker to select an icon.

  • Show header: If checked, the modal includes a header with the Title contained within it. If unchecked, the header (and title) does not display.

  • Show button footer: If the Builder clicks add Add Button in the modal, this determines whether that button displays. If checked, the modal includes a footer with one (or more) button. If unchecked, the footer—and the buttons--do not display.

    • Footer button alignment: Choose the alignment of the added buttons:

      • Left
      • Middle
      • Right
  • Unique ID (optional): Nintex Apps automatically generates an alphanumeric ID for the modal; if preferred, give it a practical name.
  • Moveable: If checked, end users can move the modal to a different location on the screen.
  • Resizable: If checked, end users can resized the modal.

Global styles for this component are set in the Design System Studio. The following Style properties can be adjusted for an individual page.

  • Style variant: Style variants are created and set in the Design System Studio. Some components have pre-defined variants for a specific aspect of a component's style. Also, Nintex Apps builders can style and customize elements to create their own themes within the DSS. These themes will dynamically populate as selectable values in the Style Variant dropdown menu.

    Note: 

    To refresh available style variant options, click refresh Refresh style variants.

    This is useful for when changes to the design system (like style variants or variable options) have been made in another browser window or by another user.

Note:  For information on individual condition properties, see the Display Logic docs.

Style variant conditions

These conditions govern which style variant is applied and displayed on a component or element.

Note: 

You can create one, or more, style variant conditions and set each individually.

  1. Click Add a new condition to add a new style variant condition.
  2. C lick the new style variant condition and configure.

When Nintex Apps executes the display logic, the style variant conditions are evaluated in order.

  • Use this Style Variant if...: The model conditions that must be met to enable the styling.

    • ALL conditions are met
    • ANY conditions are met
    • Custom logic is met
      • Condition logic: The custom logic for grouping and applying one or more conditions.
    • Style variant: The style variant to be rendered if conditions are met.

Set actions that will occur once the modal is closed.

Click add Add action, then select:

Nested elements

When you add buttons to the modal, these buttons have their own properties. All modal button properties are the same as those for Ink Button Set buttons.