Actually, I am here with one point might be this is the good place. If everyone think on my opinion (and agree than it will be helpful). I was trying, to convert my record list to excel and when I go to the selection of attribute, I am selecting everything (approx 40 attribute), after that got there is all attribute is already present which is good. But, we got that visibility first instead of last will be good (From my POV) .if anyone already know select ALL attribute is present then he directly select that. I also think crossly on this (as everyone everytime not select all the attributes). but still if, I need to select 40 attribute from 50 I can check first all attribute and then scroll done and remove the unnessary/unused attribute in the Excel. IF option is present and not visible first (at first instead I think everyone will get confused it is not a blocker but for user prospective I thought to give as an idea) Image Show all attribute after all the attribute

Hi!The idea is:Set a module as Internal/Private relative to its application so that its public elements can only be consumed by other modules in the same application.When an element is set to public in a module it becomes available to be consumed by all other modules (with the exception of some rules that relate to the type of modules).But sometimes the public elements of a module should only be consumed by other modules in the same application because that module is just a supporting/internal module; its public elements should not be consumed by other modules external to its application.Being able to set a module as "Internal" or "Private" to its application to achieve the goal above would allow better control on the dependencies, improve on the architecture, and prevent incorrect consumption of public elements. I give two examples to support this idea:1) Integration Builder produces per integration two modules: An "IS" module and a "DRV".To use the integration you should only consume actions from the "IS" module and not from the "DRV" module, even though the "DRV" exposes public actions.This is even explicitly documented in Integration Builder.2) The Forge component "Human Readable Change History" contains two modules: an extension AutoEntityDiff and a module DiffEntityDataToText.Although of the extension AutoEntityDiff  exposes public actions they are only meant to be consumed by the module DiffEntityDataToText which in fact implements the intended functionality, but by mistake any developer can consume directly from the extension.For the possibility of modules being moved from one application to another application, consumer modules would become with outdated dependencies and when republished they would be broken if they consumed public elements from an Internal/Private module that did not belong to its application.--Tiago Bernardo

When working in Service Studio whenever we need to create a new application we need to either select a color for our application or upload an Icon, however in big factories there are usually specific Icons to identify different groups of applications or different domains, it would be great if we could select from the existing icons in the factory to avoid needing to go search for the icon if it is another person creating the new application.

Create a Built-in Function Switch, under the Miscellaneous tab. It makes it easier for developers to understand the intended behavior than having several if's chained. It may cause fewer errors, since it is not necessary to check the same variable/condition several times.

Like many others of you, I read from the ideas, we also have problems indicating changed/new labels.When you add a new label, the label will be indicated 'To be defined', but when you copy another label, the translation will be same a the old one, and it's it's indication is 'Translation'. And also, if you change a label, the indication won't change back to 'To be defined.So, how can we identify that a label have to be reviewed? We have hundreds of labels to translate and every Sprint there are some changes. It's impossible to review all the labels again and again.Since my idea of putting those changed labels back into 'To be defined' is rejected by OutSystems since users only doing typos have to put everything back into 'Translate'  again... I got a better idea now. Let's add a last_changed_date(time) so we can sort on that field and only check the labels we changed recently.Please like this idea to get this into attention of our Outsystems IDE developers.

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.

It would be nice to be able to set the required order of columns when output in the excel file.We've had various requirements/complaints about the column ordering in exported files that make life harder than it needs to be for business users.PS: I am eager to assist in extending the widget ;)

Since a while now, it's possible to convert an Aggregate to an SQL query. This is a great feature, but it has a number of limitations. For one, discoverability is low. Why not add it to the context menu when clicking an Aggregate?Secondly, the limitations listed are annoying, if Service Studio can run the query on the database, it should be able to convert it to SQL. The limitations listed: The option to convert an Aggregate to a SQL element will only be available if your Aggregate doesn't include: Structures in Sources Calculated Attributes Group By attributes Dynamic SortsIt would be nice if this feature would be improved, so that all (or most) of these limitations are gone.

We could have the option of, within the context of espace in Service Studio, perhaps in the Module menu, "Move Espace to ...", the same action that occurs from within the context of the Application, where you choose which application to use for the space be moved.This is useful, for example, when cloning a space, either to test some functionality separately or even to definitely split the architecture (This would avoid, for example, having to go to Independent Modules and then move again).

Outsystems portal need to add some loaders, I click on buttons it takes much time to see any interaction in system that causes I click many times on it. it's given me negative imprecision and bad UX. also in create Case Screen error raised Twice, one during writing case details other after clicking next