For Traditional Web the "Convert to aggregate to SQL" feature was introduced last year.It would be nice if this would also be implemented for Reactive Web, where the aggregate is then converted into a Data Action, which then has the Advanced SQL inside it. The mapping of the SQL output to the Data Action output should all be part of this conversion function.

Whenever I use raise exception widget, I am able to enter the exception message, but I couldn't edit exception name. It would be good if platform allow developers to enter exception name directly here instead of renaming under exception folder. It will increase readability

Create a dashboard in OutSystems that responds to voice commands using the browser-based Web Speech API or other third party voice libraries to control UI navigation, form inputs or logic actions.

Hi everyone,I am currently working on some client/server side validations, and noticed that the Client/Server separation often requires a duplication of code (validations in client side and validations in server side). Because of this, I thought of the idea of potentially having some "Flexible", "Elementary" or "Basic" Action types that could be reused on both Client and Server Actions, considering that OutSystems uses its own set of basic data types that are shared between client and server side logic.The constraint of these types of actions would be:When they are called within a Client Action, they run as Client Action (client-side logic, runs in the browser); when they are called within a Server Action, they run as a Server Action (server-side logic, runs in the server).They cannot contain calls to Client or Server Actions. They can only call other "Flexible" actions in their flow and basic operations that are already available both in Client/Server Actions, such as: If, Assign, For Each, etc.They would generally be used for primitive operations: basic arithmetic and logic operators, and built in List-related actions, restricting any functionality that might make the "Flexible" behavior technically impossible.I understand that Server Actions can be used normally within Client Actions, however (as far as I am aware), they require a server call and therefore cannot be used as validations that run exclusively in the browser.In general, these could be useful wherever a shared foundation codebase between client-side and server-side logic would be useful, such that it could also be extended on both sides independently. The first scenario I can think about is client and server side validations, but I am sure there are similar scenarios where such a functionality would be useful to avoid code duplication.

After some years of development, the OutSystems database that supports a DEV environment have a lot of unused tables, attributes, system data, and also the process to remove  the unused espaces doesn't shrink the CLOB's data (ORACLE) and neither remove the spaces that are producers to another unused espaces. Regarding the CLOB's, it's necessary to execute a manual process to shrink the tablespace. To maintain the database healthy and tuned, I think that a processes to housekeeping the database will be a nice to have on OutSystems Platform. Regards, Pedro Matias

Hi there.In order to respect the architecture principles defined by OutSystems, it is recommended that developers install the Discovery application. The application is extremely useful and very necessary, but is only used to validate the architecture and it has about 50 application objects...I believe that applications such as this should should not be considered in the Application Objects count, for licensing purposes.Best regards,Maria

Outsystems Platform 8.0.1 uses Font Awesome 4.0.2 for the Richwidgets Icon Widget.Font Awesome 4.1.0 was recently released and include 71 new icons:https://fortawesome.github.io/Font-Awesome/whats-new/Some of them, like the new file format icons are really useful.Like jQuery, this type of scripts\fonts\etc, need more frequent updates..

create new tool allow developer to display visual Producers / Consumers for application and modules

Create a filter by date or version number would be faster to search the service center, this would decrease the search time and make the search more objective.

 Problem Statement In web development, managing CSS styles across various style sheets, inline styles, and components can become complex. Developers often struggle to understand the overall picture of how styles are applied to different elements. This lack of clarity can lead to inconsistencies, maintenance challenges, and performance issues. Proposal Let’s introduce an AI-powered solution that automatically identifies CSS elements from style sheets, inline styles, and other sources. The goal is to create an element mapping overview, similar to entity diagrams, that visualizes how styles cascade and affect different parts of a web application. How It Works CSS Element Detection: The AI analyzes existing style sheets, inline styles, and related CSS components It identifies CSS selectors, properties, and values associated with each element (e.g., tags, classes, IDs). Mapping and Visualization: The system constructs an overview diagram that represents the entire application. Each element (e.g., HTML tag, component) is a node in the diagram. Connections between nodes represent CSS rules (inheritance, specificity, etc.). Layered Visualization: Similar to entity relationship diagrams, the overview shows layers of styles. For example: Base styles (user agent styles, global styles) Component-specific styles (from style sheets or inline) Overrides (specificity-based or media queries) Interactive Exploration: Developers can interact with the overview: Click on an element to see its associated styles. Highlight paths of style inheritance. Identify conflicting rules. Dynamic Updates: As developers modify styles, the overview dynamically updates. New elements, changes, or deletions are reflected in real time. Benefits Clarity: Developers gain a holistic view of how styles propagate. Efficiency: Faster debugging and optimization due to visual insights. Collaboration: Teams can discuss and align on styling decisions. Maintenance: Easier identification of unused or conflicting styles.