(this page was created automatically. In case of formatting issues, please visit the official Wiki Page)

Static Boardlet Wrapper

The Dynamic Static Boardlet Wrapper is a specialized component that enables integration of microfrontend-based static boardlets into your application. This wrapper serves as a container that loads and displays external microfrontend components, allowing you to incorporate functionality from other applications while maintaining a consistent UI experience. It's ideal for bringing specialized features, visualizations, or integrations from other systems into your application.

Properties

General Properties

• displayName - Sets the display name of the component shown in the structure panel. For example, "Customer Analytics Boardlet" provides clear identification of the integrated component's purpose in the component hierarchy.

Visual Properties

• microfrontend - Specifies the microfrontend application that contains the static boardlet. This property uses a dropdown to select from available microfrontend applications registered in your system. For example, selecting "analytics-app" will allow you to use boardlets from the analytics microfrontend.

• staticComponentName - Selects the specific boardlet component to be rendered from the chosen microfrontend. This property is dependent on the microfrontend selection and will show only components available from that microfrontend. For example, "CustomerChartBoardlet" might be a component that displays customer-related charts.

• externalConfig - Provides configuration parameters to the static boardlet component. This object contains properties expected by the specific boardlet being used and allows customizing its behavior. For example, for a chart boardlet, you might specify: { "showLegend": true, "chartType": "bar", "dataLimit": 20 }.

Event Actions

• events - Configures the events that the component can trigger and respond to:
  • ON_INIT: Triggered when the component is initialized. Can be used to perform setup operations or pass initial context data to the microfrontend.
  • ON_DESTROY: Triggered when the component is removed from the DOM. Useful for cleanup operations or releasing resources allocated to the microfrontend.

Testing Hooks

• dataTestId - Sets the testing hook ID for automated testing. For example, setting it to "customer-analytics-boardlet" allows test scripts to reliably locate this wrapper during automated testing.