Sometimes when working with clients that still dont really know what they want, we need to change UI that was already closed or even to reamake it. When doing those changes we realise that the UI could be using the same code in the form of blocks because now they do look the same, when before they were not. So instead of having the same code "cloned" around the app we need to create a block with that code. So the idea is to allow the user to: 1. Right click on an element in the widget tree 2. Select an option like "Convert to block" And by doing so, everything that element contains would be converted to a block where every variable present in the expressions would be an input parameter of that block. Is true that we can accomplish that with cut and paste, and after that create the input parameters by hand, but with a feature like that it would save us more time and make OS11 even more accelerated. Thank you very much for your time.

The O11 traditional App is equipped with a feature that enables character counting. Character Count Implementing JS/CSS to obtain the character count on the input widget is necessary since the component is not available in Outsystems UI for O11 Reactive and ODC. just like https://www.outsystems.com/forums/discussion/79668/character-count-for-reactive/ It would be great to have this feature in both O11 reactive and ODC. Regards Nikhil kumar vijay

We know that OutSystems cannot grow in the market. Well today, anyone who hasn't confirmed OutSystems looked at its round red logo. Visual identity is very important for a company. That's why I want to inform you that when we access the Service Center, the "FAVICON" does not have the OutSystems logo, I suggest that to maintain the visual identity of the OutSystems company, we have to have the FAVICON with the company logo. Sabemos que a OutSystems não para crescer no mercado. Pois hoje quem não confirmou a OutSystems olhado para o seu logotipo redondo vermelho. Pois é a identidade visual é muito importante para uma empresa. Por isso venho informar que quando estamos a acessar o Service Center, o "FAVICON" nao esta com a logo da OutSystems, sugiro que para manter a identidade visual da empresa OutSystems, temos que ter o FAVICON com o logo da empresa. https://personal-e42hcvj3.outsystemscloud.com/ServiceCenter/

Criar uma análise de todo o código backend e banco de dados frontend, etc... onde foram reportados diagnósticos de segurança e erros a serem corrigidos utilizando IA para otimizar todo o processo para proporcionar maior segurança no desenvolvimento em OutSystems. Google translatre: Create an analysis of all backend code and frontend database, etc... where security diagnoses and errors to be corrected were reported using AI to optimize the entire process to provide greater security in OutSystems development.

It would be helpful to be able to search for errors on specific modules. Now it's only possible to select 1 module. By having a multiselect, it is possible to check on 2 or more modules that you are interested in at the same time. The other way around, you can "select all" and then deselect a module that is having a lot of errors (which is troubling the error logs) to be able to find the errors you are interested in more easily. The same would be for the application search.

For improving WCAG compatibility we need OS to include a couple of additions when it generates an error message. For a screenreader to pick up the warnings/exception messages the platform should include a ARIA role like: role="alert". I see no reason why these shouldn't always be included. ( also when de accessibility feature is disabled ) Additionally, it should be possible to tab to the message so that it can be dismissed; currently the keyboard-focussable is off, but it should be on. We are now reverting to popups as these are requirements for a successful implementation of WCAG compatibility.

Greetings, I'd like to propose some enhancements to elevate the user experience of your profile. By incorporating these elements onto the profile page, we can provide users with a richer and more informative experience: Activity Metrics Visualization: We can introduce interactive graphs and charts that display various metrics related to your OutSystems activity. Users will have the option to filter these metrics by time intervals such as weekly, monthly, and yearly. These metrics can include the number of Forge downloads, comments made, solutions posted, ideas contributed, and overall engagement levels. Profile View Count: Adding a "Profile View Count" feature will allow you to track how many times your profile has been visited. This not only provides valuable feedback but also encourages user engagement. Notification Center: To streamline the notification process and prevent important updates from getting lost in email inboxes, we can introduce a notification bell or icon located next to your profile picture at the top. This notification center will consolidate all profile-related notifications, such as comments on your posts or replies to threads you are following. By centralizing these alerts, users can enjoy a more organized and user-friendly experience. These enhancements aim to create a more engaging, user-centric, and efficient profile experience. Any feedback and suggestions you can add here. Best regards, Tousif Khan

Debug an action alone without triggering the application run. Enable the debugger to run the action alone by taking the input values from the initial assigned or default values. Just to test the flow of action it will be easy instead of going to run the application. Currently, it is achieved by running the action in a timer or in an API.

Currently, the SanitizeHTML function only has one input parameter for the html that needs to be sanitized. To allow better flexibility, it would be great if there was a second optional parameter to allow developers to specify certain tags and attributes that they hope to be excluded in the sanitization process. For example, in our current use case we were hoping to exclude iframe tags since we need it to embed youtube videos. A second use case was to exclude the target attribute since we need it to specify which links open in the same or new tab.

In the workspace of Service Studio where you design, deploy, and debug the modules of your applications, the toolbox should provide developers with an easy integration of common plugins that are used in a Mobile app such as Notifications, Location, Camera, GPS, etc. These should be served as a simple drag and drop widget, where developers can easily add these functionalities to the app screens. This will definitely improve the process of integrating the process of integrating external plugin in a OutSytems Mobile app. These widget will help reduce the time of developers finding the right Cordova plugin on the Market/Forge, adding it to the Extensibility configuration and then integrating with the app.