1. Modeling
  2. Build Models
  3. Actions

Actions enable you to automate routine tasks such as processes, imports, exports, and other actions.

Using actions, you can:

  • Run, edit, and delete processes. A process is a sequence of actions.
  • Run, edit, and delete imports. You can also mark imports as production data.
  • Create, edit, and delete import data source definitions.  You can also import source definitions as production data.
  • Run, edit, or delete saved exports.
    Note: Saved History exports cannot be edited.
  • Perform other actions such as create and maintain actions that are used with numbered lists.

It's important to maintain a logical order of the lists and actions in your modules to help navigation in the model. 

Naming actions

When you name an action, it's helpful to include the source and the destination location to identify the action. Also consider numbering actions. This table demonstrates examples of action names that follow naming conventions, compared to actions that do not follow the conventions.

Actions that do not follow naming conventionsActions that follow naming conventions
Sales Reps from TP / Sales Rep Details – TBH updates1A) LIST IMPORT Sales Rep fr TP to Sales Rep Details - TBH
Sales Reps Active Direct Quota subset from Sales Rep Details1B) SUBSET Sales Rep Active Direct Quota fr Sales Rep Detail
Accounts from Account Bookings (Accounts).csv2A) LIST IMPORT Accounts fr account Bookings.csv
Historical Bookings by Acco from Account Bookings (Original)2B) MOD IMPORT Historical Bookings fr Account Bookings
Accounts from Account Attributes.csv2C) LIST IMPORT Accounts fr Account Attributes.csv
Pipeline by Accounts from Account Pipeline (Original).csv2D) MOD IMPORT Pipeline by Accounts fr Account Pipeline.csv

See Best Practice: Naming Conventions for more information.

Search for actions

To search for actions, click the search icon and then type the name of the action you want to find. 

The Actions tab

The Actions tab contains this information:

Column headingDescription
ActionThe name of the action.
Start Date and Time (UTC)

The date and time when an action was run (Coordinated Universal Time). The Open Dashboard action does not have a timestamp. If you run an action from the Actions tab, refresh the UI page or grid to see the updated timestamps.

When a model is copied, the time stamps in the copied model are removed.

Note: the time stamp only indicates when the action was initiated. It does not indicate that the action was finished, or that it was successful.

NotesShows notes that are added to the action.
Used in ProcessesThe configured processes that include the action.
Used in DashboardsThe dashboards that use the action.