Ideas

A centralized Developer Cheat Sheet for OutSystems Developer Cloud (ODC) would greatly help both new and experienced developers quickly understand and adopt the platform. Similar to the existing O11 cheat sheet, this should provide a concise overview of key ODC concepts, architecture, development flow, best practices, and differences from O11. It would serve as a quick reference guide to help developers ramp up faster and become productive in ODC projects with minimal learning curve. This resource would be especially useful for: New developers getting started with ODC Experienced O11 developers transitioning to ODC Teams looking for a quick refresher on core concepts Providing such a cheat sheet would improve onboarding efficiency, reduce confusion, and accelerate project delivery within the ODC ecosystem.

I would like to be able to configure Mentor AI so he behaves like a true member of our team. I want to give him our coding guidelines so he always codes the way we do. Example: always adding comments to every function, combining variables into records to reduce clutter, or using PascalCase for naming. On top of that, I want to control how he communicates. Sometimes I just want him to do the work with as few words as possible, and other times I want a detailed explanation of every decision he makes.

As AI and Large Language Model (LLM) integrations become more common in OutSystems applications, developers need better ways to monitor and manage how these services are used. Currently, when calling APIs like OpenAI or Azure OpenAI, developers must manually track important metrics such as token usage, latency, errors, and estimated costs. This is repetitive and usually implemented differently in each project. This idea proposes a Forge component called AI Observability Toolkit for OutSystems that provides a standardized way to execute LLM calls while automatically capturing key metrics such as: Prompt and completion tokens Total token usage Response latency Model and provider used Estimated request cost Execution status and errors The component could optionally store this information for monitoring purposes and include a ready-to-use Screen Template (AI Observability Dashboard) that developers can select when creating a new screen. This dashboard would display metrics like AI request volume, token usage, latency trends, and estimated costs. This would allow developers to quickly add AI monitoring and observability to any OutSystems application, helping teams better control costs, troubleshoot issues, and manage AI-powered features.

Hi Outsystems teams, Since the OS charing static entity for 1 AO, to save some cost for clients, in many projects, we hardly use static-entity even though it should use Static-entity for many purposes. We need to use alternative ways to implement the static concept, like using structure, hardcode... This led the development become more complex in design, implement, and more hard-code used, but we can't spend 1 AO for just 5 records stored in static-entity like status, type, etc... Actually many projects opened just to Delete all static entity from the code to save cost. From begining we've learnt how to use Static entity, and in real project we need to learn how to not use Static entity to save AO, this make static entity very dead. Can Outsystems consider to lower the price of AO somehow like count it 1 AO = 3 or 4 static entity, or consider make it free if there are < 10 record store in static entity, this would be a great thing for Outsystems developers and clients. Thanks :)

The Julian Number to Date Converter on the ODC platform enables users to quickly and accurately convert Julian dates into standard calendar dates. It simplifies date interpretation for datasets that use Julian numbering, ensuring consistency, readability, and error-free date handling across analytics, reporting, and operational workflows. This utility improves efficiency when working with legacy systems, data integrations, and time-based calculations within ODC

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

Service Studio already ships with a powerful but underdocumented headless execution mode. Through hands-on reverse engineering, we have confirmed and validated the following commands: -d (diff), -refresh, -u, -uu, -exportSettings, -importSettings, -cleanup, -removeChangeTracking, -runTests, -export, -import, and -silentrecover. These existing commands prove that Service Studio is architecturally capable of running fully headless, without opening a GUI. This proposal builds on that foundation to request ten new CLI commands that would unlock: AI-powered codebase analysis on .oml files without a running GUI CI/CD pipeline integration via GitHub Actions, Docker, and Linux environments Automated dependency management, publishing, and solution creation Programmatic introspection of modules, applications, elements, and SS_Keys These requests do not change the OutSystems platform concept or runtime. They expose what the IDE already does — through a command-line interface that can be scripted, automated, and run in containers. Proposed New Commands 1. ss list-apps — List Applications with Names and SS_Keys Problem: There is no headless way to enumerate the applications available on a server, along with their SS_Key (the GUID used by servicestudio:// deep links and LifeTime APIs). 2. ss list-modules — List Modules with Names and SS_Keys Problem: Modules are the atomic unit of development in OutSystems, but there is no headless way to enumerate them with their SS_Key GUIDs — the identifiers required for servicestudio:// protocol links and element navigation. 3. ss check-deps — Verify Module Dependencies Before Publish Problem: Before publishing a module, a developer needs to know if its dependencies are up to date, or if a producer module was published with breaking changes. The current workflow requires opening Service Studio, navigating to "Manage Dependencies," and manually inspecting each reference. There is no headless equivalent. 4. ss publish — Publish a Module Problem: There is no headless command to publish a module to a server. The current workflow requires opening Service Studio and clicking "1-Click Publish." This blocks full CI/CD automation. 5. ss republish — Republish a Module (Service Center Style) Problem: Service Center provides a "1-Click Publish" that recompiles and redeploys a module using its last published OML source, without requiring the source file on disk. This is critical for environment redeployments, disaster recovery, and CI/CD rollbacks — but it has no CLI equivalent. 6. ss list-elements — List All Elements of a Module by Name and SS_Key Problem: To use the servicestudio:// deep link protocol (e.g., to link directly to a specific action from a CI report or an AI analysis tool), you need the SS_Key of the element. Currently, the only way to get element keys is through direct database access or by reverse engineering internal API calls. 7. ss add-action — Add a Simple Action Using a Mermaid-Style Flow Definition Problem: Creating a simple server or client action in Service Studio requires opening the GUI, navigating to the correct module, and manually building the flow. For repetitive, pattern-based actions (logging, error handling, standard API calls), this is a barrier to AI-assisted code generation. 8. ss for Linux — Docker and GitHub Actions Support Problem: Service Studio is currently only available for macOS and Windows. This means CI/CD pipelines running on Linux (the default for GitHub Actions, GitLab CI, and most Docker containers) cannot use any Service Studio CLI commands. This is the single biggest blocker for full OutSystems DevOps automation. Request: Provide a headless Linux build of Service Studio — or a dedicated CLI package — that supports the full set of headless commands (existing + proposed) on: Ubuntu 22.04 / 24.04 (standard GitHub Actions runners) Alpine Linux (Docker optimization) Debian-based containers 9. ss delete-unused-refs — Delete Unused References from a Module Problem: Over time, modules accumulate references to producers that are no longer used — dead imports that slow down compilation, add maintenance overhead, and generate noise in -refresh / -u verification output. Service Studio can detect these via "Manage Dependencies," but there is no headless way to auto-clean them. 10. ss create-solution — Create Solutions Programmatically Problem: Solutions in OutSystems are the primary vehicle for managing and deploying groups of modules across environments via LifeTime. Creating and maintaining solutions is currently only possible through the Service Center UI. For teams managing complex multi-module deployments, the lack of a CLI solution creator is a significant DevOps gap. Why This Matters: The AI Analysis Use Case The combination of -listModules, -listElements, and the existing -d (diff) enables a use case that is currently impossible: AI-powered static analysis of OutSystems codebases without a running GUI. Current Gap: To analyze an OutSystems application with AI today, a developer must: Manually open each module in Service Studio Navigate through hundreds of screens, actions, and flows Copy/paste relevant information into an AI tool The AI agent can then generate a report like: "Action IsElegivelAntecipacaoDZero (key: 11ea244a-...) accesses the server on every screen load. Consider moving this to an Aggregate with proper caching. → [Open in Service Studio](servicestudio://-downloadAndOpen -eSpaceKey 6acebf97-... -elementKey 11ea244a-... -url bin.dev.myenvironment.com)" This is only possible if -listElements exposes SS_Keys in its output. Summary We are requesting 10 new headless CLI commands for Service Studio, with Linux support as the foundational requirement for CI/CD automation. The existing headless CLI (-d, -refresh, -u, -exportSettings, etc.) proves the architecture is ready. These new commands extend that foundation to cover the full development lifecycle — from introspection and dependency management, to publishing, solution creation, and AI-powered analysis. The OutSystems platform is already exceptionally powerful. These commands make that power accessible to modern DevOps and AI tooling workflows, without changing a single line of platform behavior.

Greetings, Service Studio comments are used for notes, reviews & reminders. Most of the time the reminders act as an backlog to be resolve by someone in the team accountable. Currently there's no built-in way to highlight the accountability/ownership for a reminder [ except what we mention as a text] Having an feature of @mention-user-name where the studio to populate/autoSuggest the env IT Users/Developers would create a reference for the respective user so that while they access the module in studio its more easy for them to trace there accountable reminders. example : @abc.xyz please validate this aggregate filter - Auto Suggest when type@ - Would ne awesome if the mentioned user receive some sort of notificaton🔔 in studio itself 🙂 - More advance ahead; notification should navigate or open respective module & show the reminder action/respective stuff [ sync tree] Thank you for considering this enhancement in advance Assif

 Problem: When working with complex Advanced Queries in Service Studio, it is difficult and time-consuming to manually re-enter test values every time, especially for queries with many parameters. There is currently no native way to save these test sets. Proposed Solution: I suggest implementing a "Stored Test Values" feature for Advanced Queries to improve developer productivity: Versioned Test Values: Allow developers to save specific sets of input values as named "Test Versions" directly within the query editor. Auto-populate: Provide a dropdown or selector in the test input window to quickly select and auto-populate these saved values. Multiple Sets: Support saving multiple test scenarios (e.g., "Empty Inputs," "Edge Case - Nulls," "Standard Load") for the same query to streamline repetitive testing. This feature would significantly reduce setup time and ensure more consistent, repeatable testing during the development phase.

The current Community platform suffers from performance limitations and provides a restricted level of user interactivity. To improve the overall user experience, I propose migrating the Community to a Reactive Web architecture within OutSystems. The growth and increased user engagement in the OutSystems Community can be attributed to a more intuitive, faster, and interactive experience that encourages users to actively participate, share knowledge, and return to the platform more frequently. Let’s move forward with this improvement to unlock a faster, more engaging, and truly collaborative community experience for all users. This is a developer’s observation based on system usage and user experience.