Brick Configuration Panel
Last updated
Last updated
When you select a specific brick in the Brick Actions Pipeline, you'll see a panel appear to the right that has options for configuring specific information about that brick.
The Brick Configuration Panel is the heart of the Page Editor. This is where you will configure the nuts and bolts of your bricks.
The Brick Configuration Panel showing the configuration for the Window Alert Brick
A custom step name to display in the Mod Outline Panel and in error telemetry. If you do not provide a name, it defaults to the name of the Brick
The output variable name. The field will appears as disabled if the brick does not produce an output. For example, the Window Alert brick in the screenshot above does not produce an output.
Output Key Tips:
If you enter name, it will be available to other bricks as @name . (The field adds the @ prefix for you automatically.
Two bricks can have the same output key. The second brick’s output will replace the output of the first brick. For readability, the best practice is to use unique output keys. The exception is when the bricks are configured to conditionally run (See Advanced Option: Condition)
The Input section contains the primary brick-specific configuration for the brick. The configuration options vary by brick.
If the brick is from the PixieBrix Marketplace, you can view its documentation by clicking the View Documentation link at the top of the card.
To the right of each input field, there’s a dropdown for controlling the input entry mode for the field. You can learn more about these entry types in the Brick Data Types documentation.
As the name implies, the Advance Options section includes advanced controls that may not be necessary for most uses but can be helpful for specific actions.
If you provide a condition, the brick will only run if the condition evaluates to a truthy value. For convenience, PixieBrix considers some text as truthy: true, yes, y, on, and 1 .Learn more about how to set logic and control the Conditional Field on Bricks.
The Target Field controls where the brick executes. The most frequently used targets are:
Current Tab: the current tab/frame (default)
Opener: the tab that opened this tab
Target: the most recent tab that this tab opened. For example, when using the Open a Tab brick
💡 Example of using Target: Target Tab to automate form fill
If you want to open a tab and fill out a form on the tab
Add the Open a Tab brick with Target: Current Tab (self)
Add the Form Fill brick with Target: Target Tab
Some bricks are “root-aware”. They operate using the context of an element on the page. For example, when creating a Trigger that runs on an element, the bricks attached to the trigger run in the context of the element that caused the trigger to run.
Root-aware bricks use the element to base selector evaluation on (to find a sub-element), or to determine which data to return about an element.
The Root Field has two options:
Inherit: use the current root element
Document: force using the document as the root element
There's one more panel to explore in the page editor. Explore the Data Panel to view your brick's output.
