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.

It would be great to have a test at the end of each "path" to verify if you miss something important. Also it would be great if that question will be at the same format as on the certifications exams.

Create the possibility of folders in the CSS editor.This way we can better organize the components and make it easier to update them.

Hi everyone, I would like to propose the creation of an official training path and a specialization certification focused on Digital Accessibility, covering both OutSystems 11 and OutSystems Developer Cloud (ODC). As Low-Code developers, we have the responsibility to ensure that applications are inclusive by deeply applying WCAG standards within Service Studio and ODC Studio. My suggestion is for OutSystems to offer: Accessibility Guided Path: A comprehensive training focused on using OutSystems UI accessibly, handling ARIA roles, managing focus, keyboard navigation, and testing with screen readers. Specialization Exam: A technical validation for developers who have mastered the implementation of accessible interfaces in Reactive and ODC applications. Profile Badge: An official badge on the community profile, allowing partners and clients to easily identify developers capable of delivering high-quality, inclusive projects. Why is this important? Market Differentiation: Accessibility-certified professionals are rare and highly valued by large enterprises. Product Quality: It reduces technical debt and ensures that "High Performance Low-Code" also means "High Inclusion." Platform Strength: It demonstrates that OutSystems leads the market not only in speed but also in social and technical responsibility. I believe an "Accessibility Specialist" badge would elevate the technical level of our community and help build a digital world for everyone. #Accessibility #Certification

To prevent the population included in the group most vulnerable to contagion by the new coronavirus leaving home, namely the elderly and people with chronic diseases, the Municipality of Proença-a-Nova and the Parish Councils and Unions created a solidarity network for situations of emergency, namely for the purchase of medicines or essential goods, among others.In each village, an interlocutor between the population and the Parish Councils is being defined to communicate needs, and the Municipality is responsible for the subsequent delivery of orders.To facilitate all the communication between the interlocutors and the Municipality, volunteers developed a web and a mobile app during the weekend using OutSystems and made available to Municipality employees to use, tracking the daily requests with the necessary details.

While creating Agentic App. the models on the ODC portal are available for every developer without restriction. this could hinder with governance policies while dealing with multiple teams. Suggesting to add Management layer similar to OS 11 lifetime teams to manage development teams more effectively enabling governance of apps and AI Models.

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

 Proposal In Lifetime, when we do a promotion to another environment, we have the ability to add custom steps between environments to create a pipeline. In these custom steps we could connect to AI mentor, BDD tests, another test tolls or even a custom application. In a simple vision this could be a URL parameterisation and a result that is expected. Added value to OutSystems customers 1. Avoid to spend more money in 3rd party tools and devops engineers to create custom pipelines (Azure devops, Jenkins, ...) 2. Increase speed in delivery because all steps are inside our platform 3. Simplified and unified release process.

New Accessibility category in Ideas and new Accessibilty tag in Forums. It may be that this was decided internally as not necessary, but with accessibility becoming a must, and since it's a very broad topic, I feel that a dedicated category and tag in the Ideas and Forums, respectively, would benefit and facilitate the search for this topic.

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