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

With REST services, we can open the documentation from the context menu. With SOAP web services, we have to type the URL (which is not easy to find) to get there. It would be great if we had a context menu option "Show Documentation" for SOAP as well.

Currently, supermarkets limit the number of people inside the space, but there is a problem outside the commercial space, with the cluster of people waiting for their turn to be able to enter and purchase the goods they need.The idea is to create an application that performs the virtual queue management in which people can schedule their place in the queue before leaving home. The application generates a number in the virtual queue and will indicate to the user what time is most likely for him to enter the supermarket. In addition to the information in the application, the user receives an SMS indicating the place in the queue and the estimated time of entry. The information is updated with time intervals to be defined (5m, 10m, 15m, etc.). It will be necessary that each of the participating stores use the application and agree to create a specific virtual queue for the users of this application.The application can be applied to othet type of stores than supermarkets. Stores that use the application will be helping to reduce the risk of contagion, as there are clusters of people outside the commercial space.

At this point of time it is not possible to select multiple resource file during import.

Inconvenience:If a user is having multiple accounts, they can very well able to link their primary account with their secondary accounts, but their community ranking doesn't get linked. because of this the ranking gets disturbed.Idea:In order to maintain proper ranking, Outsystems can provide an option called "Merge Ranks". By using this, the rank of the primary account will get reflected in all the linked accounts. So that, the secondary accounts won't disturb the ranking order. If user is not interested in merging their ranks, then they won't opt for it.

Currently, if we define a Sorting by an attribute, that sorting becomes unresponsive after introducing a Group By in the aggregate, as the sorted attribute is no longer part of the aggregate output . This does not raise any errors or warnings in the TrueChange Tab or any signaling in the workspace. I find that this is an easily overlooked situation that can lead to unexpected behavior or inconsistent results. I suggest the implementation of a typical Outsystems background validation that triggers a warning (written on the TrueChange Tab and a visual cue on the aggregate) whenever the aggregate's sorting references attributes that are not part of the aggregate output after a Group By, ensuring consistency and preventing silent issues.

Premise: When projects and team dynamics become complex, people end up having to maintain reverse-engineer code, often with little or no documentation. Idea: Any action in ODC Studio would have an "AI Summarize" option. This will do an AI Analysis of the action, including analysis of all of the consumers of that action, and produce a human-readable summary of the action. Target: This could transform the 'maintainability' category of AI Mentor into a mostly automated feature.

Sometimes I want to pass only a small feature from one environment to another and when I merge them I have like 20 different devs with a check box to unselect. If there was an option "Select All" on each side, i could easily take all out and select the only one I want to merge. Ex:

Like ListClear action there should be one for records. With just one action and just passing the record name as argument it could set the record attributes to the default values. This would be easier, faster and much cleaner than setting all attributes one by one or assigning the record to a blank one.

When I have a block containing a pop up, that pop up will be collapsed in instances of that block. When I have a placeholder inside that pop up, and I need to add a significant amount of design inside that placeholder, using the widget tree only gets very tedious. Therefor I would like to be able to display the content of the block, or at least the placeholders.