Action Sequences

Action Sequences let you define sequences of actions at a page level. These sequences can then be reused in Action Framework scripts for model, row, global, and mass actions in Skuid pages (including principal pages), or set to listen to specific events.


The following properties can be found in the Sequence - New Sequence properties pane:

  • Type: Determines whether the sequence will be reusable or triggered.
  • Sequence name: Give the action sequence a descriptive name.
  • Description: Identify the purpose of the sequence.

Working with Action Sequences

Create a new action sequence

Action sequences can be created within the Action Sequences tab:

  1. From the Elements pane on the left side of the Composer, click action-sequences Action Sequences.
  2. Click add Add Action Sequence to create a new sequence.
  3. Select the sequence’s Type, which can be:
  4. Add a Sequence name and Description to identify the sequence.
  5. Add the desired actions.


As your library of action sequences grows, a descriptive name and useful identification of the sequence’s purpose will help you locate the sequence you require.

Edit an action sequence

Edit an action sequence from the action-sequences Action Sequences pane. Click the sequence name, and then add, delete, or move actions.


Once changes are made to a reusable action sequence, those changes become part of that sequence wherever it is used.

Clone an action sequence

To make a copy of an action sequence, select its name in the action-sequences Action Sequences pane, and click copy Clone. Rename the sequence and edit the actions.

Reusable Action Sequences

A sequence of action types—available at the page level—that can be called from any other Action Framework script within the pages. Change the sequence once—and those changes ripple through all instances where the sequence is used.

Create Reusable Action Sequences from Existing Actions or Interactions

  1. On the Actions or Interactions tab in a component’s properties pane, click action-sequences Convert to action sequence to turn any existing list of actions into an action sequence.


    All actions listed in the action script will be converted into a sequence. It is not possible to pick and choose from the actions to build the sequence.

  2. Name and describe the action sequence. The sequence will now be listed under that name in the Action Framework, and in the action-sequences Action Sequences pane.

Break down a reusable action sequence instance for editing

If you invoke a reusable action sequence using the Action Framework, but realize you don’t need all the actions in the sequence, the sequence can be broken down into its constituent actions—effectively serving as a template for individual action scripts.

Select the action sequence in the Action Framework and the click dots-vertical More actions menu. Select Break up into individual actions. This, in effect, changes this instance of the sequence into a script of individual actions, while the original action sequence remains intact. Edit these individual actions as needed.


Inputs provide the flexibility to have different properties in each instance of a reusable action sequence. With properly configured inputs, a general set of actions can be configured into a sequence. Then each time the action sequence is called, the various inputs it requires to run can be set at each instance, allowing for incredibly flexible, reusable action sequences.

To add inputs to an action sequence:

  1. Click the action-sequences Action Sequences pane.
  2. Click the reusable action sequence.
  3. Click the Inputs tab in the Properties pane.
  4. Click add Add Input.


  • Name: The name that Skuid displays as an input property on the action sequence wherever it is called. Multi-word names may be used.


    • Do not use periods in input names.
    • Whenever possible, do not change input names after their action sequence is used in a page. If you change the names of your inputs, you may need to set them again within each action or dependent input in the action sequence, as well as any individual action sequence instance.
  • Type: Determines where the input property can be used within various action types.

    • Value: For use within any arbitrary value properties.
    • Model: For use within any model properties.
    • Model field: (Requires a Model type input) For use within any model field properties.
    • Model condition: (Requires a Model type input) For use within any model condition properties.

Using input values in a sequence

To use the value of an input within the action sequence—for example, to use a Value-type input within a Model Condition-type input—use the name of your input, namespaced within the $Input merge variable, in merge syntax.

For example:



Ensure that $Input is capitalized.

Whenever the reusable action sequence is called within another action script, the various inputs will appear.


To see an example of inputs in action, see the Inputs How-To: Activate and Set a Condition and Requery Model topic.

Event-triggered Sequences

Within the Action Sequences tab it is possible to create event-triggered sequences, action sequences that will execute when their particular event is published.

Each event-triggered sequence has the following properties:

  • Sequence name (optional): Plain language name for the sequence.
  • Event name: The name of the event to listen for.
  • Listen for events published from: Determines how “far” from the Skuid page this event subscription should listen for events.
    • All active pages and Lightning Components
    • All active pages
    • Only this page (default)
  • Event channel: Sets the channel—another event property to further narrow scope—where Skuid listens for events.


If an identically named event is published on a channel other than the one listed in the subscription, that subscription action script will not activate.

Default Published Events

  • Skuid Page: Rendered: Published when a Skuid page has finished rendering. Can be used for page load actions that should occur whenever end users visit the page.
  • Network: Connected: Published when the end user establishes or reestablishes connection to the internet.
  • Network: Disconnected: Published when when the end user loses connection to the internet—potentially triggering offline mode.

The following events are only relevant if offline mode is enabled.

  • Offline Syncing: Started: Published when the offline syncing process begins.
  • Offline Syncing: Conflicts Detected: Published when the end user’s page data conflicts with data on the server.
  • Offline Syncing: Cancelled with Conflicts: Published when the end user cancels an offline sync that would overwrite conflicting data on the server.
  • Offline Syncing: Approved with Conflicts: Published when the end user initiates an offline sync that will overwrite conflicting data on the server.
  • Offline Syncing: Successful: Published when the end user’s changes have been successfully synced to the server.
  • Offline Syncing: Failed: Published when the end user’s changes do not successfully sync to the server.

Interacting with other contexts

Through event-triggered action sequences and the Publish Event action type, it’s possible to set a communicative structure to Skuid pages, allowing them to speak with each other. If using Skuid SFX, you can also use this action type to publish standard Lightning Experience events and communicate with custom Lightning components.

Hotkey-triggered Sequences

Hotkeys, sometimes called shortcut keys, decrease the number of clicks it takes to perform an action. Called at a page level, and configured in the Hotkeys tab of the sequence, hotkey-triggered sequences start a series of actions when a predefined combination of keys are pressed.


  • Modifiers (optional): The key or keys to be pressed in combination with a standard key, to execute a specified action or set of actions. Though modifier keys are optional, it is best practice to pair a modifier with a standard key to avoid accidental activation of a hotkey-triggered sequence. Modifer keys include:
  • Alt
  • Control
  • Command
  • Shift
  • Key: The standard key that is paired with the modifier to start the action sequence. Standard keys include:
    • Letters A-Z
    • Any arrow key
    • Any function key (F1-F12)
    • Backspace/Delete
    • Delete Right
    • End
    • Home
    • Page Down/Up
    • Tab
  • Ignore hotkey if end user is typing in input element: If checked, the action sequence will not activate if the user’s cursor is within an input field, such as a Table or search form. This ensures the action sequence is not triggered accidentally and prevents a hotkey from potentially overriding a system-level hotkey combination, like copy/paste or arrow keys.