We have a big factory and multiple applications and solution publish takes over hour. Currently person needs to Login DEV Service Center Open Factory Go to solutions Open XXXX solution Select [x] Publish with full compilations Press (Publish) We need to make a scheduled solution publish after hours when developers are away. So create Service Center solution publish API per environment Login with needed credentials API call LaunchSolutionPublish(SolutionId, VersionId, IsPublishFullCompilations) This can be also included to LifeTime API, but then you need to add environment where the publish is wanted to do. Also creating version for Solution would be good for API call CreateSolutionVersion(SolutionId, Version[text], Description[text]): VersionId We can retrieve versions and solutions from System entities, but we cannot lauch solution generation. It would be possible to make own scheduled system for this if there would be these APIs. BR, -JP

Extend the platform's JavaScript Node and Client Action invocation contract to include a fifth built-in parameter: $event, exposing the native browser Event object alongside the existing $parameters, $actions, $roles, and $public. The change would be additive and non-breaking - I assume. Use case : implement an OnKeyUp handler that runs logic only when Enter is pressed, without manually wiring addEventListener/removeEventListener — the platform already manages the event listener, it just needs to forward what it receives.

Currently we have to use non -native methods to enable popup closing by clicking outside. It would be interesting to have it natively.

Allow 3rd option on Entities, Actions as "Friend" which will make entities and actions visible to all modules within the Espaces Application, but not to other applications.  This will simplify having to keep entities as read-only and then creating actions to do the CRUD operations of the entity.  It will also improve security so that espaces that shouldn't be using these entities won't have visibility of them.

The new DatePicker  of OutSystems UI, based on flatpickr library, contrary to the old one that is now named DEPRECATED_DatePicker, based in pikaday library, doesn't allow the user to enter a date in the input by typing directly on it  via a widget configuration, which makes it harder to allow that behavior.With this idea I would like to propose to OutSystems that an option is added in the DatePicker_OptionalConfigs structure, an input of the widget, to enable this behavior.The flatpickr library which the new component is based on already allows such a configuration but i's not exposed by the OutSystems UI webblock.Another alternative would be  allowing the developers to extended the widget capabilities by providing an open input (that would receive a JSON) like the old DatePicker used to do. The current approach limits the extensibility of the component and this idea is the only way to improve and extended the component.Below was the approach to enable more functionalities of the underlying library.I understand the expected functionality is possible with the use of a client action that enables the behavior but it requires additional overhead for development. It needs an initialize action for every instance of the component with the required config. With this ideia I challenge the current implementation to improve development experience.Please consider these options and allow the developers to extended the libraries.

I would love to build my portfolio or a small business using my personal environment in OutSystems, using my domain or having more space to use in the database . I'm not a Champion or MVP, but I believe that the idea would motivate even more OutSystems professionals to reach these desired prominent positions. My idea is that these professionals recognized by OutSystems MVP and Champion can have additional configurations in their personal environments , basic things like: Put your own domain eg: www.soarescorp.com or instead of personal-xasadk Having more than 2GB of database to actually store data. Allow 1 or more 2 developer accounts in personal environment. Only these first two items would be very good, so in summary, my idea is that MVPs or Champions have better functionalities in their personal environments , after all they are promoting the OutSystems brand frequently . Hug, Lucas Soares

Currently, only Forge components submitted in OutSystems 11 appear under the Activity section of a user’s profile. However, components submitted from ODC are not reflected there. It would be great to include ODC Forge submissions in the activity feed as well, ensuring consistent visibility of contributions across both platforms.

Implement a "Conflict-Free Data Replicated Type " (CRDT) based editor that allows two developers to work on the same screen or logic flow simultaneously, seeing each other's changes in real-time without needing a manual merge

Currently, when replying to a forum post , we use the " @ " symbol to mention a person, but users need to manually search for the name they want to mention. I propose an enhancement where, as soon as the " @ " symbol is typed in a forum reply, a list of users who have already replied to that specific thread automatically appears. This will allow users to easily select the name they want to mention without having to search for it. This feature would improve the user experience by saving time and making the process more intuitive.

Be able to restore the Screen State in Mobile apps while navigating through screens. By default, OutSystems already uses an hidden API (ScreenStateCache) that restores the screen state while navigating back to the previous screen, as stated in my article . The implementation of this idea would make this functionality available across the developers, making OutSystems mobile apps with an user experience much closer to the native ones.