BluKavantUI Community 1.0.1

BluKavantUI Community provides 55 reusable UI components for OutSystems 11 Reactive Web, including layout, navigation, forms, feedback, media and a read-only Basic Grid.

No BluKavantUI account, subscription or license key is required to use Community.

Installation

1. Install BluKavantUI Community from Forge using Service Studio.

2. Allow Service Studio to install the included libraries and resolve their dependencies:

   • BluKavantUi_Community_Core

   • BluKavantUi_Community_Layout

   • BluKavantUi_Community_Inputs

   • BluKavantUi_Community_Feedback

   • BluKavantUi_Community_Data

   • BluKavantUi_Community_Content

   • BluKavantUi_Community_Grid

3. Open your Reactive Web application and select Manage Dependencies.

4. Add BluUICommunityTheme from BluKavantUi_Community_Core, together with the public Blocks and Structures required by your screens.

5. Set your application theme’s Base Theme to BluUICommunityTheme.

Community uses its own theme and components. It does not require OutSystems UI, OutSystems Charts, OutSystems Maps or BluKavantUI Pro. When changing the base theme of an existing application, review its existing screens and custom styles before publishing.

Full installation and module guide

Using components

1. Find a component in the Community catalogue.

2. Open its documentation and select OutSystems.

3. Use the Implementation tab for Service Studio setup, data binding and event-handling instructions.

4. Use the API tab for the native producer, input parameters, public Structures and event payloads.

5. Add the documented Block to your screen.

6. Bind its inputs to screen variables, expressions or application data.

7. Create Client Action handlers for the events your application needs, and connect them to your application logic.

Use the native OutSystems Blocks and their documented contracts. The Web/TypeScript examples describe a separate integration and should not be pasted into native Block parameters.

Data and configuration

Your application owns its business data and persistence. Components display and interact with the data supplied to them; they do not automatically save changes to your database.

Where applicable:

• Populate inputs using Aggregates, Data Actions or screen variables.

• Handle component events to validate input, update state or call Server Actions.

• Supply your own upload endpoints and external services.

• Configure any AI services used by chat components in your application.

Basic Grid supports client-side sorting, filtering, pagination, column sizing and single-row selection. For advanced Grid capabilities, consult the edition comparison and component documentation.

Demo application

The Community UI Demo is a separate, optional application. It is not required by the reusable libraries.

Open the Community UI Demo

To inspect its implementation, install the separate demo package after the Community libraries, then open its screens in Service Studio. The demo references the Community libraries and the platform’s Users application.

Updating and troubleshooting

After updating the libraries, open Manage Dependencies in your consuming modules and refresh changed public elements. Resolve validation messages, review your bindings and test affected screens before publishing.

If a component appears unstyled, check its producer references and the BluUICommunityTheme base-theme configuration. For data or event issues, compare your bindings with the component’s OutSystems Implementation and API guides.

Version 1.0.1 was validated on Platform Server 11.42.1.47790

Accessibility guidance and review results

Contact support — include your platform version, component name, reproduction steps and any error message.