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 master 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 event-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 App Elements pane on the left side of the App Composer, click fa-cogs Action Sequences.
  2. Click fa-plus-circle 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 fa-cogs 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 fa-cogs Action Sequences pane, and click fa-code-fork 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 [[]]

  1. On the Actions tab in a component’s properties pane, click fa-sitemap 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 fa-cogs 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 click fa-sitemap 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.

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)
  • Channel: Sets the channel—another event property to further narrow scope—where Skuid listens for events.
    • Note: 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.

One default event available is Skuid Page: Rendered, which signals that the Skuid page has finished rendering and can be used for page load actions that should occur whenever users visit the page.

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 on Salesforce, you can also use this action type to publish standard Lightning Experience events and communicate with custom Lightning components.


Inputs provide the flexibility to have different properties in each instance of an 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 or event-triggered action sequences.

To add inputs to an action sequence:

  1. Click the fa-cogs Action Sequences pane.
  2. Click the action sequence.
  3. Click the Inputs tab in the Properties pane.
  4. Click fa-plus-circle 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.

Setting input values in a sequence

Whenever the reusable action sequence is called within another action script, or triggered 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.

In contrast, event-triggered sequences determine the actual values of their inputs as a parameter of the event they listen for.

For example, an event-triggered sequence may have the following configuration:

  • Properties
    • Event Name: QueryModel
    • Listen for Events published from: Only this page
  • Inputs
    • Name: ModelToQuery
    • Type: Model
  • Actions
    • Action Type: Query Model
      • Model: ModelToQuery(Input)

That sequence could be triggered with a Publish Event action:

  • Action Type: Publish Event
    • Publishing Scope: Only this page
  • Parameters:
    • Parameter Name: ModelToQuery
    • Value: Account

In this example, the Account model would be queried. Note that the parameter name matches the sequence’s input name exactly.


Inputs may also be set by JavaScript or external Salesforce Lightning components as long as their parameters match an input’s name on an event-triggered sequence.

Using input values in a sequence

You may to want reference the value of a Value-type input within a Model Condition-type input, or perhaps block the UI and show a message with the value of an input.

To do so, use the name of your input, namespaced within the $Input merge variable, in merge syntax.



Ensure that $Input is capitalized.