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.

Model Actions

Model actions allow you to trigger action flows so that they run automatically when model-level events occur. This means the actions don't need to be tied to a button or intentionally activated by the end-user, but are activated "behind the scenes" when specific things happen on the page. Model actions are useful for creating simplified, automated operations, even for complex processes.

Create a Model Action

  1. In the Elements panel, click the Models tab.
  2. Click the model.
  3. Click the Actions tab.
  4. Click Add action.
    • Set interactions (and properties of those interactions) in the When section.
    • Add specific action framework sequences using the Actions tab.
  5. Click Save.

Properties

When talking about model actions, interactions are model changes that begin action flows actions.

  • Interactions

    • Model saved: When the model is saved, whether as the result of user input or an action.
    • Model requeried: When the model is queried, which can occur on page load or by an action.
    • Model cancelled: When changes to the model (as the result of user input or an action) are cancelled.
    • New row created in model: When a new data row is added to the model, as the result of user input or an action.
    • Row in model updated: When one or more fields are updated as the result of user input or an action flow trigger. You may select whether this initiating event applies to specific fields or to all fields in the model.
    • Row in model marked for deletion: Marks the selected row on the model for deletion as the result of user input or an action flow trigger.
    • Row in model un-marked for deletion: Unmarks the row on the model selected for deletion as the result of user input or an action flow trigger.

    Changes to model conditions can also be selected as interactions.

  • Model condition changed: If the value of a model's condition changes (even in the background, unactivated).

  • Model condition activated: When a model's condition is activated, whether or not the model affected by it has been requeried.

  • Model condition deactivated: When a model's condition is deactivated, whether or not the model affected by it has been requeried.

  • Model condition reset: When the condition's value is reset. This can only be done through the JavaScript API.

    • When which conditions are changed? For each of the previous condition-related events, select trigger to begin the sequence. Options include:
      • Any filterable condition
      • One or more named conditions.