In the Dropdown Search component, it would be beneficial to enhance the OnChange event by allowing it to include additional attributes. Currently, OnChange only provides five default attributes from the DropdownOption structure: Value, Label, ImageUrlOrIconClass, GroupName, and Description. It would be helpful to introduce a JSON attribute where developers can pass extra information about the selected item. This enhancement would reduce the need for additional local variables and data aggregations, streamlining the retrieval of supplementary details within the component. Currently: Ideally:

It would be beneficial to have a centralized page in the Service Center or within the OutSystems platform that provides a comprehensive listing of all Site Properties across environments. This listing should include the following details: Application Name Module Name Site Property Name Default Value Created On Created By Additionally, there should be an option to mask the Site Property value for sensitive data. If the "mask" option is enabled for a Site Property, its value should be hidden in the listing. Otherwise, the value should be visible along with its default value.

Idea: A portal in which people who are looking for help get linked to people who offer help. In the portal people can actively contact each other and they receive notifications when a possible match is found.What we can offer: We have a team lined up to build the portal. Two junior developers will build the portal as part of their onboarding programme. They get assisted by an experienced OutSystems developer.What we need to succeed: We need to get in contact with potential end-users to help us setting the requirements. We already started initializing this.

Hi,Sometimes we have to clear the entire local storage on Mobile Local for the sake of User Switch.For this scenario right now we have to manually call all the Delete Actions of all Entities when user log-out.Would be quite easy if outsytems provide an action to clear all entities in an optimized &  fast way.Thanks

Like overriding the endpoint URL of APIs through service center, we should be able to turn off documentation on the Production environment for security reasons.This is currently being configured in the Service Studio (Yes or No values) and will be carried over to deployed environments. Not really safe to do publishes in the production just to turn off documentation.

When creating an entity diagram, there should be an option to configure the display of the data types of the attributes of each entiy.This way, it would be less prone to errors and could be exported as an Entity-Relationship Diagram Model.Best Regards

It is already possible to create a structure from JSON.It would be useful to get the opposite: the JSON for a given structure.The feature would be something as: right click on a structure -> see in JSON format. Or something similar.Sometimes it is useful to pass a serialized structure to parse in Javascript, for instance...

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 would be nice to have a way, in ServiceStudio, to select two actions at a time and compare the code like we have in the merge eSpace at the action's level.This could be a useful feature for code cleaning and reusability (easier to track duplicated code).

It would be nice to automatically create the structure or a collection of entities that can accomodate the data from a XML without having to create it manually. It could also create methods to read a XML created in compliance with schema provided and colect the data to the structure or set of entities previously created.