The Dispatch Table Builder routes incoming data to different Actions based on defined conditions. It is useful when one source Action receives several values and each value should trigger a different destination without writing the routing logic manually in Lua.

Each row in the Dispatch Table contains a condition, the parameters to forward, and a destination Action.

Example Workflow

An Action named route(string value) receives the names of different show states. The Dispatch Table can route them as follows:

When route("Pause") is called, PIXERA evaluates the second row and calls pauseShow(value).

The Builder generates and maintains the required Lua code in the source Action automatically.

Opening the Dispatch Table Builder

1. Navigate to the Control tab.
2. Locate the Action that receives the value to be routed.
3. Right-click the Action.
4. Select Launch Dispatch Table Builder.

If the Action does not yet contain a Dispatch Table, the feature can also be added from the Action's properties by selecting Dispatch Table.

Once a Dispatch Table exists, select the Action to find the Dispatch Table section in the Inspector. From there, use Launch Builder to edit it or Remove to delete all generated Dispatch Table code.

Adding a Dispatch

1. Trigger the source Action with the value you want to route.
2. Check Last received value at the bottom of the Builder.
3. Select the + button to add a row.
4. Enter or adjust the Condition.
5. Enter the values or expressions to forward in Parameters.
6. Enter the path of the Destination Action.
7. Select OK to apply the Dispatch Table.

When available, the Builder uses the last received value as the next Condition and the last parameter of the source Action as the default value in Parameters. String Conditions must be enclosed in quotation marks, so check the automatically inserted value before applying the table.

Selecting Cancel closes the Builder without applying the table changes.

Dispatch Table Fields

Condition

Defines when the row is executed. Conditions use Lua syntax, but the Builder also supports shortened input for common comparisons.

Assuming the source Action is named route(value), the following Conditions are valid:

For Actions with multiple parameters, a comma-separated list of literals compares the values in order. For example, the Condition 1, "Main" on route(number page, string name) is evaluated as:

page == 1 and name == "Main"

Parameters

Defines which values are passed to the Destination Action. Enter one or more Lua values or expressions separated by commas.

Examples:

The expressions must be valid in the context of the source Action. In most workflows, this means using the parameter names from the source Action signature.

Destination Action

Defines the Action that is called when the Condition evaluates to true.

For an Action in the same Module, enter its local path, for example:

startShow

An Action in another Module can be addressed by its full Control path.

Transport.play

If the entered local Destination Action does not exist, PIXERA can create it when the table is applied. Intermediate namespaces must already exist. To avoid accidental Actions or unresolved routes, select an existing Action path whenever possible.

Leaving Destination Action empty forwards the configured Parameters to the Actions connected to the source Action.

Managing Rows

Use the buttons at the bottom of the Builder to manage the table:

Rows are evaluated as individual conditions. They do not behave like an if/elseif chain. If several Conditions match the same input, all matching Destination Actions are called in table order.

How Dispatching Affects Connections

When a row with a Destination Action matches, PIXERA calls that Action with the configured Parameters and suppresses the source Action's regular reference forwarding for that route. This prevents the same value from also being sent automatically across the source Action's Node Connections.

In order to do so, the dispatch table adds to the code of the selected action.

When Destination Action is empty, the row calls the source Action's connected references instead. This allows a condition to control when selected values are passed to the normal Output.

For more information about reference forwarding, see pixc.callRefs.

Editing or Removing a Dispatch Table

To edit an existing table:

1. Select the source Action.
2. Locate Dispatch Table in the Inspector.
3. Select Launch Builder.
4. Make the required changes and confirm with OK.

To remove the complete table, select Remove in the same Inspector section and confirm the warning. PIXERA removes only the generated Dispatch Table blocks; other Lua code in the Action remains unchanged.

Attention

The Dispatch Table is stored as generated Lua blocks inside the Action body. Avoid changing the --dispatchBegin and --dispatchEnd markers manually. Invalid or incomplete markers can prevent the Builder from reading or safely replacing the table.

Troubleshooting

A String Condition Does Not Match

Make sure the string is enclosed in quotation marks:

"Start"

Without quotation marks, Lua interprets the value as a variable name.

The Destination Action Is Not Called

Check the following:

• The Condition is valid Lua syntax.
• The source Action receives the expected value shown under Last received value.
• Parameter names match the source Action signature.
• The Destination Action path and its namespace exist.
• The forwarded Parameters match the Destination Action's expected inputs.

More Than One Destination Action Is Called

Multiple rows may match the same value. Adjust the Conditions so they do not overlap if only one destination should be triggered.

PIXERA 26.1  | 5. August 2026 | J.B.