When checking a forge component, the only way to inspect what this component offers (screens, server and service actions, blocks, entities, etc...) is to install the component first. It often happens that the component in question is not what a developer wanted or had in mind. Showing a structure view of a component's public elements directly in the Forge Component's detail page, before downloading, would make it much easier for us to be able to assess preliminarily whether a component fits our needs or not, without having to download it first. The idea is to have this step automated, without having to rely on the manual documentation (that often is missing from components), similar to the automatic documentation that Outdoc offers for target applications but of course that exact level of detail won't be necessary. A high-level preview of the elements would perhaps be enough.

There are plenty of scenarios in which the base built-in actions are not enough. For example, if creation of a specific entity record demands that other entity records be also created, or if certain restrictions apply that cannot be modeled with static "default values". Or simply because you want to audit operations over sensitive entities. Currently the way to do this with the Agile Platform is clumsy: isolate entities in their own eSpace, make them available read-only, and create sets of actions to do the required tasks. This works, but: It is ugly - when actually using those actions, you will not see them associated with entities; you need to remember that they need to be imported, look for them under "referenced actions", remember from which eSpace they come from - or go look in the entity list; It can lead to errors - if a new developer in a project using the pattern, for some reason, is not properly informed, he might simply go into the eSpace and switch the read-only property off, anticipating that it being that way was an error.

Although there exist about 15 ideas on improving handling of unused references, non of them state the obvious: it could be done easily by OutSystems fully automatically! My proposal is that developers keep whatever references in DEV (or remove them if they want), but that on deploy to the next environment, OutSystems first automatically removes any unused references, before it starts the deployment. There is in my opinion NEVER a need for unused dependencies in the next environment where someone deploys an application to. As is is never needed, it can always automatically be removed.

The forum has slowed down a bit recently, with fewer questions and answers over the past few months. Everyone is very busy, yet they still participate in discussions and provide answers. I think it would be a good idea to offer rewards—such as certification exam vouchers—to the top 10 contributors each month.

Improve Record Definition Selection UX Current Behavior When selecting a Record Definition, the current selection dialog is not very intuitive. The dialog displays the Entities / Structures tree along with a Select button, which makes it seem that the user should select the required Structure and then click Select to confirm the selection. However, the actual behavior requires the user to click the Entity/Structure in the tree, which immediately adds it to the selection. There are also some additional UX issues: If a Record Definition is already selected and the user wants to remove it, they need to select the existing item and right-click it to access the delete option. The delete action is not obvious or easily discoverable, as there is no clear action or button indicating that the selected Record Definition can be removed. If the user selects another Structure while a Record Definition already exists, the new Structure is added instead of replacing the existing selection. This makes it unclear how to replace or clear the current Record Definition. The UI also does not clearly indicate which Structure is currently selected. Suggested Improvement Improve the Record Definition Selector to make the selection, replacement, and removal behavior more intuitive and consistent. Ideally: Clicking a Structure should select/highlight it, while clicking Select should confirm the selection. If a Record Definition already exists, selecting another Structure and confirming it should replace the existing selection rather than add another Structure. Provide a clear and intuitive way to remove/clear the current Record Definition without requiring the user to right-click the item. Clearly indicate which Structure is currently selected. Keep the interaction consistent with the expected behavior of a selection dialog: select → confirm, rather than adding the item immediately when it is clicked.

The new 1-Click Publish With Message is a good idea, but to be useful, it needs improvements. 1. It should have the ability to hide the normal 1-Click Publish to force messages, or some other way to enforce this 2. The last message should automatically populate a new publish, or maybe a dropdown with the last 5 or so messages.

It would be nice to have a button, in ServiceStudio, to remove all unused references in an eSpace, or a list of unused references which we could then remove.

Sometime you work on a certain part and are not able to finish certain parts, or want to skip certain parts, like complex queries.Then it would be great to disable or, comment out certain tools in the action flow. so you don't have to worry about them now.Perhaps they are not complete yet, or unusable.With an if-block, it would always follow the true-line, it would skip the for-each etc. etc.

Hi there, In traditional it was possible to download an image trough an URL by simple add the download widget at the end of the preparation. By this was you'll could load images in your application by setting the source of the image widget to the URL of the screen with the download widget. This doesn't work in reactive (which makes sense), but make this option available. Kilian made a blog how to accomplish this trough an API (see: https://itnext.io/exposing-a-url-for-downloading-a-file-with-outsystems-reactive-f19f2f7345a9 ) only then you'll need to do more regarding authentication etc on the API method. So make a option available, I can think of add a parameter in the download widget which enfoce this, or option to the screen (is download screen) so our life can be easier with just adjusting a parameter instead of creating a custom Rest API. Kind regards, Evert PS: topics on forum I saw with same issue/questions (these where only releated to the issue there are so many topics on this): 1. https://www.outsystems.com/forums/discussion/100024/getting-url-from-binary-data-to-use-it-externally-as-a-link/ 2. https://www.outsystems.com/forums/discussion/101809/get-binary-data-by-url-server-side-loading-an-image/ 3. https://www.outsystems.com/forums/discussion/60967/how-to-add-mime-type-for-downloading-the-file-in-reactive-web/

Hi, I found that 100 espace limit in a page was too few.I usually maintained Platform Server once in a few months.And it really a chore when deleting old versions of espace.Maybe add a configurable paramater instead of static 100 entries.