Hi Everyone, When working with large modules that have many entities, adding entities to the Entity Diagram becomes difficult. The list is too long and there’s no way to search or filter it. We have to scroll through everything to find the entity we want. In projects with lots of tables, this takes time. It would be really helpful to have a simple search box or filter option when adding entities to the diagram, similar to other search inputs in Service Studio. Even just typing a few letters to filter the list would make things much faster. I believe this would improve productivity, especially in bigger applications. Thanks!

It's good if we have option to share our achieved badges to social media like LinkedIn. Whenever we achieved a badge in mail as well as the profile page , it's good to have a share action. By showing it to outer world, it's showing our achievement as well as it will create enthusiasm among others who watching this post in social media. So I think it will be better to have this feature in OutSystems. Regards Murali

 To aid in the current COVID-19 situation we are some persons who have started Society4Healthcare. Citizens and companies that are not able to participate in the clinical work are provided with a way to help the healthcare staff during the crisis through Society4Healthcare. By coordinating various tasks that help the hospital, its employees, patients, and their relatives we try to make daily life a little bit easier for them.We need to develop a solution for communication, enrollment, distribution of tasks and status reporting both per task and for the whole situation.

My idea is to have a similar mechanism that is done with Exception Handlers to REST APIs errors, this is, the ability to choose if we want to log the error or not.For example, in the OnAfterResponse of a REST API I would like to don't log the exception that occurs when condition 2 is true.This exception is logged with the module REST (Consume).

Hello,Just a small thing where sometimes when you'll create an action you'll need an input/output/local variable that is based on a structure. Instead of making a new variable and fill in the right name (where you sometimes first check the name of the (referenced) structure it would be nice to have the option to copy a structure and paste that structure as an input/output or local variable to an action.Just like this:Kind regards,Evert

We currently have the capability to create structures using a JSON editor, but it lacks the functionality to edit or update them. I propose implementing a feature that allows users to edit and update the structure directly within the JSON editor.

Be able to refresh a Reference by right-clicking an option menu over an existing reference in ESpace explorer reference's folder. In the References' popup screen it would be nice to have a button/link to refresh the existing Espaces or Extensions without having close e reopen the popup References' screen.

It would be nice to have in the advance query editor a mechanism that allowed SQL auto indentation , such as exists in some applications of SQL management . This feature would allow a better understanding and performance ( in terms of readability ) for the developer , especially in more complex queries .

When creating a new application in Service Studio, I really appreciate how the platform automatically extracts the primary theme color and generates a default logo based on the uploaded application icon. This greatly helps with the initial branding setup. However, I’ve noticed that the favicon is not automatically set in the same way. It would be a great improvement if the favicon could also be auto-generated or defaulted to the uploaded application icon, just like the logo and color theme. This would ensure a more consistent visual identity for new applications right from the start, without requiring additional manual steps. Thank you for your continuous improvements and for considering this suggestion!

 It would be useful to have, what we could call, site properties that would be shared between multiple eSpaces. This would avoid the replication of site properties with the same value over multiple eSpaces.