Loading Into Dropdowns

Contextual menu outlets allow your extension to add action items to dropdown menus within a platform — for example, adding an action to the account card dropdown on the landing page. This guide covers how to configure your extension to contribute items to one of these outlets.

How It Works

When a platform renders a contextual menu outlet, Tecton resolves which extensions have registered items for that outlet and dynamically inserts them as dropdown items. When a user selects your item, the platform navigates to your extension or triggers the configured action, passing the current context value along.

Configuring via the CLI

Run q2 tecton, select your extension, choose Outlet Configurations, then Dropdown Navigation Configuration. The CLI will walk through the available outlet locations and the action to take when your item is selected.

The CLI updates your extension's configuration file at configuration/{ExtensionName}.py.

Manual Configuration

Menu items are declared in your extension's configuration file under the appropriate outlet key. Each item specifies a label, the action to take, the module to load, and optionally the parameter name used to pass the context value:

ACCOUNT_DETAILS_DROPDOWN = [
    {
        'itemLabel': 'View Rewards',
        'action': 'navigateTo',
        'modules': [{'moduleName': 'RewardsDetail'}],
        'contextIdParamName': 'accountId'
    }
]

contextIdParamName specifies which parameter name should be used to pass the context value to your extension when the item is selected.

Context Filtering

You can restrict your menu item to appear only for specific account or transaction types by configuring context constraints. For example, a rewards action might only be relevant for credit card accounts.

Context filtering follows the same hierarchy as other outlet types. For details, see UUX Content Controls.