Documentation Index

Fetch the complete documentation index at: https://docs.unqork.io/llms.txt

Use this file to discover all available pages before exploring further.

Smart Component Output Type Compatibility

Prev Next

Centauri logic components, including the Decisions component, Initializer component, and Data Workflow component, can target Smart Components with output actions. Not all output types produce an effect. Unsupported types are silently ignored with no error.

For definitions of each output type, see Output Types Reference.


Output Types That Work

Type Effect on Smart Components
Value Updates the component's input value. The component reads this on its next update cycle.
Hidden / Visible Toggles component visibility. When hidden, the component is removed from view.
Clear Clears the component's current value entirely.
Reset Restores the component's visibility to its original state.
Trigger Re-executes Logic and Query components with current inputs and outputs. Has no effect on UI components, which render continuously.

Output Types That Have No Effect

These output types are silently ignored when targeting a Smart Component. No error is raised.

Type Category Why
Custom Class Display Smart Components control their own styling. External CSS class injection is not part of the Smart Component contract.
Message Display Smart Components do not have a validation message slot.
Pop Message / Pop Error Display Global modal notifications, not component-level feedback.
Label Display Smart Components render their own labels. There is no external label slot.
Title Display Smart Components have no title element.
Prefix / Suffix Display Native input decorations. Smart Components are not form inputs.
Content Display Injects raw HTML into a content slot that Smart Components do not have.
Disabled Interaction Smart Components manage their own interaction state. The platform does not intercept end-user interaction at the container level.
Read Only View Interaction Smart Components control their own visualization and data can be complex objects.
Required Interaction Smart Components have no built-in visual indicator for required state. No feedback would appear.
Required And Visible Interaction The Visible part applies but Required does not. Use Hidden / Visible instead.
Currency Formatting Number component display format.
Duration Formatting Timer component-specific.
Steps Formatting Number component stepper.
Minimum / Maximum Formatting Centauri validation expects a simple primitive. Smart Component data can be complex objects.
Pattern Formatting Regex validation expects a string. Not reliable with complex Smart Component data.
Editable Component-specific Grid component only.
Select Values Component-specific Drop-down and multi-select components only.
Validate Component-specific Smart Components have no registered native validator.
Dynamic Refresh Component-specific Panel content replacement only.
Component Reference Key Component-specific Advanced Datagrid component only.
HTML Read Only Component-specific HTML Element component only.
Navigation Navigation Navigation component only.
Page / Page Open Navigation URL redirect actions. Unreliable when configured with few outputs. This is a platform limitation, not specific to Smart Components.
Runtime Workflow Module-level toggle, not component-level.
Multi Workflow An async decision wrapper, not a standalone output type.
Vega Execute / Vega Operation / Vega Value Workflow Workflow Builder-specific.
BYO Component Update Workflow Bring Your Own Component-specific.

Changelog

Date Change
2026-07-28 Initial draft — editorial pass on engineering draft (EN-7976).