Currently all comments have the same color. In Dark Theme they appear black and in Light Theme they appear gray. This makes it difficult to distinguish important notes or identify who added them. The proposed idea is to allow users to define the color of their own comments so that in action flows it becomes easier to see who contributed. If full customization is not feasible an alternative would be to provide three predefined colors such as normal yellow and red to indicate severity or importance. This would help draw attention to critical comments and prevent them from being overlooked.

Some teams have been keeping technical documentation on a separate document format instead of generating using OutDoc to leverage, which makes this Indicator, especially in cases where the Application is not meant to be a component or widget, unnecessary.So, maybe if there was a Settings feature where we could set this Indicator as optional / mandatory for a given Application, it would be helpful.

We use SolarWinds for database performance analysis which just shows the raw SQL executed and often it is very hard to work out where it was called from.If the platform could insert an SQL comment with the name of the Aggregate/SQL it would be extremely helpful!We also use Lifetime analytics, but tools like SolarWinds can provide alternative insights.

I realize that often company logos on their websites are in SVG format and I need to convert them to PNG to use as an application icon.

In Service Studio, static entities have a Description property (like all other things you can create like actions, structures, attributes and so on). However, given the nature of static entities, each record has a specific use, which currently can't be described. It would be nice if it were possible to add a description to each record, in addition to the static entity itself. This will help the developer assign the right value. This description could then also be shown when hovering over a record in the static entity selection pop-up.

OutSystems now supports storing settings as secrets in both OutSystems 11 (Site Properties as Secrets) and OutSystems ODC. However, secrets often have an expiration date, and without proper tracking, they can expire unnoticed, causing disruptions. Proposed ideas : Optional Expiration Date for Secrets – Allow users to set an expiration date for secrets stored in Site Properties (OutSystems 11) and Secrets (OutSystems ODC). Reminder Notifications – Enable reminders to be sent before expiration to a specified role so they can take action. This feature would help OutSystems 11 / ODC users proactively manage secrets and avoid unexpected failures due to expired credentials.

Create a single, global collaboration platform exclusively for OutSystems User Group Organizers to connect, share, and co-create. This platform would act as a community backbone, enabling organizers worldwide to: 🌍 Discover upcoming and past User Group sessions globally 📚 Share session decks, recordings, notes, quizzes, and formats 💬 Discuss ideas, challenges, and best practices 🤝 Call for collaboration on joint sessions, meetups, or masterclasses 🧠 Brainstorm unique, proactive, and high-impact session ideas 📣 Invite other organizers or speakers for cross-region events

It would be great if we could integrate with Git directly (out of the box) with Service Studio to manage Javascript/JQuery/React/.. and CSS projects.With Git being one of the most popular and powerful Source Control providers, harnessing its power from within Service Studio would just be icing on the cake.

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.

Hello everyone, I would like to suggest adding a placeholder for a footer in the sidebar. While I understand this may not be as critical as other issues, I believe it could enhance the overall widget experience. I'm aware of some workarounds for this, but we've encountered problems with our current approach due to the address bar's position on tablets and mobile views. We discussed this internally and agreed that it would be a worthwhile suggestion to raise. Thank you for your attention!