The Reimpact platform aims to provide a streamlined user experience. One aspect of this is ensuring that UI elements, such as widgets, are compact and efficient in their use of screen space.

The Problem: Widget Padding

QuickLinksWidget cards, used for displaying quick access links, were taking up more space than necessary due to excessive padding.

In the Reimpact platform, we're always striving to optimize performance and ensure smooth operation. Recently, we encountered an interesting issue with the TopExceptionsWidget model that highlights the importance of correctly defining primary keys, especially when dealing with subqueries.

The Problem

Filament, our admin panel framework, relies on $record->id to uniquely identify rows in

When developing widgets in Reimpact/platform, efficiency is key. A recent update addresses an issue with Filament's default sorting behavior in subqueries, specifically within the TopExceptionsWidget. Let's explore the problem and the solution.

The Problem

Filament, a PHP framework, automatically applies ORDER BY model.id when using HasRecords. This default behavior becomes problematic

Introduction

The Reimpact platform is undergoing continuous improvements to enhance its monitoring and reporting capabilities. Recent updates focus on refining how exceptions are tracked and how data is presented to users, ensuring a more informative and user-friendly experience.

Addressing Query Builder Compatibility

One of the key updates involves resolving a compatibility issue within

Introduction

We were experiencing slow query times in the Reimpact platform when using Eloquent subqueries with anonymous models. The issue stemmed from unintended default ordering and a mismatch between the model table and the subquery alias.

The Problem

Eloquent was automatically adding an ORDER BY pulse_entries.id clause, even though `pulse_entries.

The Reimpact/platform project is focused on [description]. Recent development efforts have concentrated on improving the way DPR (Data Protection Report) data is presented and managed within the platform. This involved transitioning from a static HTML table to a dynamic Filament TableWidget, offering enhanced features such as pagination, search, filtering, and translation support.

Introduction

The Reimpact/platform project focuses on providing a streamlined user experience. Recent efforts have been directed towards improving the layout and responsiveness of sections within the platform.

The Challenge

Previously, sections on the platform did not always stack vertically as intended on smaller screens or when content required full width.

Working with large datasets in Filament can sometimes be overwhelming. Displaying all the information at once can make it difficult to quickly grasp key insights. This post explores how to enhance Filament tables by collapsing details by default and using translated filters for a more user-friendly experience, as recently implemented in the Reimpact/platform project.

Collapsing Details by

Introduction

When working with Filament, especially when displaying data from sources other than Eloquent models, you might encounter situations where the built-in features for filtering, searching, sorting, and pagination don't work out of the box. This post describes how to manually implement these features for array-based report tables within Filament admin panels.

The Challenge: Array

The Reimpact/platform project is undergoing improvements to its data presentation layer, focusing on enhanced readability and structural clarity. This involves reformatting data reports to be more user-friendly and logically organized.

Enhanced Data Reporting

The recent work centers around improving the way data reports are rendered. Instead of repeating headers for each row in a data