It is difficult to track down a version of a forge component once you have installed it in your environment and the component receives new updates from the community.It should be easier to check how far behind I am in adopting a newer version of a particular forge component by just going to Service Center or best in LifeTime itself.Based on a trustable hashing algorigthm, why can OutSystems not determine if the package hash for the version of Forge component is matching with a signature with a published component and if so flag it to me easily. If the match does not happen then tell me that I have customized the copy of forge component so it is not possible to track it against the public repository.

If there are any advance queries, replace that by aggregateDon't use foreach Loop in preparationDon't use if conditions in preparationi.e try to avoid if conditions in aggregateApply pagination on list pageDon't show more than 100 records on single pageMove JavaScript webblocks to bottom of pageDon't use preparation aggregates directly in screen actionsBefore using them in screen actions refresh themSuggested by  Suraj.

I have been using images that I have uploaded to the images resource folder but every time I have to select an image all I have is the name of the image as a reference , It would be nice to have a thumbnail next to the name of the image to allow me to preview the image before adding it to the screen/weblock. Images folder There should be thumbnails next to the names of the images

What I like to see: switchto be able to set the labels of the conditions instead of seeing 1,2,3,4 and otherwise do/while/do or  for-loopI really would like to see a simple do/while on a condition, instead of a cumbersome if statement. the "cycle" note is a nifty feature with it.wether is should be a for-loop with just an integer or a do/while I don't mind.except for esthetics perhaps, because I don't like "breaking" out of a for-loop

Right now, when we want to consume REST API with authentication (Auth2 or Basic), we should add the credentials manually and hard coded. But if we should use the same credentials for different API, we should have the ability to configure these credentials as Site Properties. With that, we can manage the credentials only once for all the API's.

The SortRecordList extension allowed to have multiple sort criterias. The ListSort should have feature parity with that extension, at least.Having this built-in on the platform would be useful for sorting third-party datasources. For example, imagine that a web service returns financial transactions, and has two distinct columns: Date and Time. We would need to sort on both columns to be able to present data in chronological order.

I often find myself pressing the "eSpace management" button in Service Studio just so I can start a timer. It would be useful if we could just right click a timer on the Processes tab and have a "Run Now" to instantly schedule the timer.

When an input parameter is removed from an action in OutSystems, the platform should automatically remove all references and assignments of that parameter throughout the application to maintain consistency and prevent warning.

The existing SEO URLs feature within traditional web applications is a very useful component within the OutSystems platform for making domains point to specific applications or pages, making URLs easier for users to follow and navigate, and presenting a "cleaner" look and feel.With React, this feature is now missing entirely and the only 'workaround' is to use links to traditional web, then push the user back into Reactive web again afterwards.Not only does this slow the load down, increasing load times and decreasing user experience, it also redirects the user from the url/domain they were expecting to see to a url with "too much code" in it, decreasing user trust in the website.SEO URLs are an existing feature in traditional web that should have been included with the initial roll out of React/Reactive Web and it is imperative this feature be restored ASAP in order for existing implementations to adopt React.

Having the possibility to remove the help from right click, because the help appears now in the same place that paste was before. So now I'm clicking it a lot of times :(This can be a option in settings, for example.