Please can you add the ability to apply field descriptions to ODC External Logic components. If there is already a way to do it, it's not in any of the very scant documentation.

Please add the ability to upload a demo app for ODC External Logic components.

Please can you provide an option to use the uploaded Demo as a Try Now option, hosted on the forge server. Currently, if you don't have a corporate account/server you are willing to make publicly available, you have to use you personal account for the Try Now , but that expires and gets deleted every week or so, causing the Try Now to die.

The help page you are given a link to when publishing from ODC to the Forge is completely blank. Can someone add some details please?

As requested by OutSystems Support Team, I am creating this Idea because it's important that the build log for any compilation on mobile on ODC be similiar to what we have in O11. Today, the mobile build is a huge amount of text that can be difficult to understand what is the main reason your mobile app is not compiling. In O11, it's more easy to understand. Maybe on ODC, put the main error on the top (or at the end) of the file so the developer can easily identify the root cause of the APK/IPA being broken upon compilation.

The default behaviour of datetime variables in Reactive apps is to convert from UTC to local time. This is a great in a lot of use cases, but hard to work with if a user want to see data in a different timezone.In this forum question , some 'hacks' are proposed:Use datetimes as textCompensate at server side for the difference in client timezoneThe prefered solution is to let developers set the config for this automatic conversion. The default behaviour to convert is good, but make an option to overwrite the default behaviour.

I the Rest configuration in Service Center should have the same fields that are in Service Studio. When I configure the Authentication in Service Studio appear the field Scopes But in Service Center this field doesn't exist You should have the same fields in both places

One of the purposes of publishing a solution, is to refresh all modules in it, and reflect a change of an upgrade. What I propose, is to remove unused dependencies between the defined modules in the solution. I recommend for it to a configurable option. But it would be helpful especially in big projects, where the architecture is big and complicated. Also, it could be a helpful option before checking the architecture in Discovery. Before the check we have all modules refreshed, and all unnecessary links broken.

Quite often, I am repeating the same set of joins in queries (both normal and advanced), that I would ordinarily put in a view. Think e.g. of a CRM system that regularly needs "all active clients" or an ordering system that needs "all open orders". Of course if you need just that, it's easy to put it in an action, but I often find myself needing the result and join that with some other tables. Unfortunately, for some reason OS does not allow to define database views, which imho is a great gap. Therefore, I'd really like to see support for database views or something similar (e.g. queries you can define on eSpace level and join the result of with another query, but that amounts to the same).

When I edit or look up data during development with 'View Data' in my entity, the order of the attributes are so random. I'm getting pretty crazy of scrolling and searching for my attribute and it's value. (Especially in my 225 attribute entity! Yes, I could optimize) Why are the attributes not ordered by the way you ordered them in the entity? or at least on alfabatical order? Seems like an easy fix. Also what decides if a attribute is collapsed or expanded? seems random also.