Fixed Table Header

Outsystems Forge provides a large set of reusable assets that help accelerate application delivery. These assets are made available by our community uses and by Outsystems.

When searching Fixed Table Header in Outsystems Forge.

Description

Fixed Table Header (or sticky header) is a common user interface pattern that keeps the table header in a fixed position while users scroll down the page. This ensures that the header remains visible for better usability in applications with large data tables.

Forge presence

The asset information in forge must be clear and complete. For this, the asset must have the following characteristics:

A meaningful name: Fixed Table Header

Short description: A component to keep table headers fixed while scrolling.

Long description: The Fixed Table Header component allows table headers to remain fixed or 'sticky' at the top of the screen while users scroll through the table content, improving readability in large tables.

Correct categorization and tagging (e.g., UI Patterns, Table Header, Sticky Header).

Correct type (e.g., Traditional Web).

Screenshots showing the sticky header functionality.

Trusted or supported dependencies (e.g., UI components that work with it).

Documentation explaining how to use the component.

A demo showcasing how to implement and customize the sticky header.

Installation

The asset must install successfully. For an asset to install successfully, the following requirements must be met:

No missing dependencies.

No dependencies on deprecated assets from Forge.

Documentation on additional configurations (e.g., CSS or JavaScript setup for sticky behavior).

Functionality

The asset must work as expected. For this, the asset must have the following characteristics: 

Must deliver the described functionality: headers remain fixed at the top while users scroll through a table.

The functionality should be built on OutSystems' latest stable versions, using current best practices (avoiding deprecated actions).

Usability

The asset must be easy to use. For this, the asset must include the following:

Clear documentation on how to integrate and use the Fixed Table Header component.

Document specific elements required, such as the structure of tables and the behavior of the fixed header.

Include a demo that illustrates different use cases for the sticky header in various table designs.

Implementation

Trusted assets must comply with the implementation best practices described in this section. The Outsystems Curation team uses the AI Mentor Studio to perform the necessary validations.

Architecture: Aligns with the layers of the OutSystems Architecture Canvas if part of a larger application.

Security: All parameters in SQL queries must be sanitized (if applicable).

Performance: Ensure that the sticky header functionality doesn’t cause performance lags, especially for large tables.

Code Maintainability

The asset code must be easy to maintain. For this, the following requirements must be met:

Keep code structured and commented, especially if using custom CSS/JavaScript for the sticky header functionality.

Ensure clear and logical separation of components (HTML, CSS, and JavaScript) for easy maintenance.

No disabled or redundant code.

Compliance

The asset must ensure license compliance. For this, all libraries  (e.g., CSS/JavaScript used for fixed table header) must be used correctly according to their license terms.

Maintenance and Support  

The asset must be kept up to date. For this, the asset must have the following characteristics:

Available in the latest Outsystems version

Description and documentation must be up to date with the latest asset version

The asset owner must provide the following required support:

Reply to any comments or questions

Solve the reported errors