O que é isso? Uma ferragem colaborativa integrada à plataforma sobre os desenvolvimentos podemos comparar, comparar e aprender com métricas de desempenho de aplicativos do mundo real desenvolvidos no OutSystems. Problema que resolve: Os envolvidos frequentemente enfrentam gargalos de desenvolvimento, mas não têm uma referência sobre o desenvolvimento de aplicativos semelhantes. Não há um local centralizado para compartilhar práticas recomendadas específicas de otimização. Cada desenvolvedor "reinventa a roda" testando soluções isoladas. Como funcionaria: 1. Contribuição de métricas anônimas Os desenvolvidores enviiam dados de desenvolvimento de seus aplicativos (tempo de resposta, consultas lentas, uso de memória) Informações confidenciais podem ser anonimizadas Sistema se compara à comunidade: "Seu aplicativo é 30% mais lento que aplicativos semelhantes" 2. "Receitas de Performance" Biblioteca de soluções testadas: "Reduzir consultas N+1 em ListRecords" com comparações antes/depois Votação comunitária: qual solução funcionou melhor? Integração com controle de versão: em qual versão do OutSystems cada solução foi eficaz? 3. Desafios mensais "Otimizar esta aplicação problemática" - colaboração comunitária Recompensas simbólicas: emblemas, reconhecimento, destaque de perfil 4. Integração do Service Studio Plugin que exporta automaticamente métricas de desenvolvimento Um clique para compartilhar com uma comunidade

An AI agent that acts as a "Guardian" for our Data Fabric. When a developer changes an entity (like changing a User_ID from a LongInteger to Text), the AI scans not just the OutSystems code, but also the "Contracts" with external tools like Power BI, Snowflake, and external APIs. It warns the developer before they publish: "Stop! This change will break the 'Sales Dashboard' in Power BI." Real-World Example Imagine we have an OutSystems app for Order Management. We decide to change the Price field from a Decimal to a Text (maybe to support currency symbols). The Internal Impact: OutSystems tells us to fix the math formulas in the app. We fix them. 0 Errors. Happy! The Hidden External Impact: * Power BI: A "Revenue Chart" was pulling that Price field. Now it crashes because it can't "Sum" text. Snowflake: An automated data pipeline was expecting a Number. Now it rejects every new record. The AI Sentry Solution: Before we click "1-Click Publish," the AI pops up with a - "⚠️ External Impact Detected: The Price attribute is consumed by Snowflake Pipeline 'Orders_Sync' and Power BI Report 'Global_Sales'. These systems expect a Decimal. Changing this to Text will cause 2 downstream failures. Do you want to notify those teams?" Low code tools that already address this issue - Atlan - Automatically maps how a change in a database affects a dashboard in real-time. Informatica (CLAIRE AI) - Uses AI to predict the "blast radius" of a metadata change across different systems. Collibra - "Harvests" metadata from different tools (SQL, APIs, BI) to show a visual map of dependencies.

Just like the option to export/download certificates, it would be great to have the same functionality available in the Achievements section as well. The exported file will give information about all the achievements under the achievements section.

Hospitals will start having issues with ventilators during this high usage times that are approaching. After doing shifts for more than 48 hours it won't be easy for medical and technical staff to properly troubleshoot the cause.For instance, sometimes ventilators stop working and the problem is the UPS. What needs to be done is simply connect the ventilator to the energy outlet rather than the UPS.The purpose of this system will be to allow technical staff to submit issues with ventilators (by brand and model) and have specialists indicating possible solutions.

Everyone knows that descriptions are helpful to understand the meaning of a variable or anything. My suggestion is to show the site property description in the lifetime as we can see in the service center.

There is a great subdomain "charts.outsystems.com" that explains how the charts can be customized. However, I think it is missing some crucial information. For example, there is the following page that explains different chart types and how to implement them: https://charts.outsystems.com/samples/chart-with-multiple-chart-types There is a warning there implying that it is not possible to do a "step line chart" with the config options of the chart block (see attachment): "Currently, it's possible to convert any series to the following types: Line, LineSpline, Area, AreaSpline, Column, Bar and Pie." In reality, it is actually possible to do this with addon extensibility configurations; i.e. with a certain client action ( SetHighchartsSeriesConfigs ) from the Charts library, as partly explained in this video: https://www.youtube.com/watch?v=uzNnX7oqhNY It would be great if such information is also added to the https://charts.outsystems.com/ subdomain.

Hi OutSystems Team, It would be incredibly valuable to introduce a feature in Service Studio that allows developers to select and manage specific versions of producers when configuring dependencies. This enhancement would align with the familiar workflow of Visual Studio’s package manager, empowering teams with precise control over which producer versions their applications depend on. Key Benefits: Stability & Reliability: Locking dependencies to verified versions minimizes the risk of unexpected changes or regressions. Simplified Rollback: Facilitates quick reversion to previous versions if newer updates introduce issues. Improved Developer Experience: Mirrors established practices in other development environments, making dependency management more intuitive. Collaboration Support: Promotes consistency across teams by ensuring uniform dependency versions, reducing integration conflicts. Please find below a mockup illustrating the proposed implementation.

The Forge component page should include more details, that allows one to judge the impact on and OutSystems factory without needed to install it first:Number of Application Objects (AO's)Number of integrationsPaid license required for a third party integrationExternal integrations overview (some components have APIs just to collect usage, this should be more visible.If it bootstraps data on publish (some components generate users, etc.)If applicable version of OutSystems UI used (OutSystems UI has a high rate of updates and deprecated functionality/breaking changes)Regards,Daniel

Whenever we are on the viewing the widget tree of a page or Webblock, if we click on the "Go to <insert element here>" we continue on the same widget tree view mode and need to click again on the widget tree icon to finally see the element we selected as demonstrated on the gif below. The rationale is that if we are using the "Go to" context menu, 9 out of 10 times we want to open the original module to inspect/change the element selected.It would be nice that when we use the "Go to <insert element here>" context menu it would change to the view that actually allow us to "go" to that element

Will be helpful to have a build-in fuction to remove duplicates from a listExampleList {A, B, C, A, B }Result list {C}