My idea is to keeping the existing behavior but with the possibility to turn off automatic fetching data.Suggestion: Button like Test button (advanced queries) inside the aggregator to be able to disconnect or connect to the server.

Scheduled deployment is a smarter, more efficient alternative to manually clicking the deploy button. By automating and scheduling deployments, organizations can improve consistency, reduce errors, and optimize resource usage. Adopting scheduled deployment as part of a robust CI/CD pipeline ensures smoother, more reliable software releases, ultimately leading to better operational efficiency and user experience. Benefits of Scheduled Deployment 1. Reduces Human Error Manual deployments rely on human intervention, increasing the risk of mistakes, such as deploying the wrong version or skipping a critical step. Scheduled deployment eliminates this risk by automating the process. 2. Ensures Consistency and Reliability With manual deployment, inconsistencies can arise due to variations in execution. Scheduled deployments follow the same automated process every time, ensuring reliability across different releases. 3. Optimized for Off-Peak Hours By scheduling deployments during low-traffic periods (e.g., midnight or early morning), teams can minimize disruptions to users and reduce the risk of downtime. 4. Frees Up Developer and Operations Teams Developers and DevOps engineers no longer need to be present at odd hours to manually deploy updates. Instead, they can focus on more critical tasks while the deployment occurs automatically. 5. Enables Continuous Deployment (CD) Scheduled deployment is a key component of Continuous Deployment (CD), allowing teams to release updates frequently without manual intervention. This results in faster iteration cycles and quicker time-to-market for new features. 6. Supports Rollback and Disaster Recovery With automated deployment, rollback strategies can be implemented to quickly revert changes in case of failure. This ensures better disaster recovery and system stability.

Add a small icon decoration so that on the espace tree we can differentiate which actions are public on an espace. While you're at it do it also for the ones that are functions...

Once in a while I have a project where 2 (or more) different types of users ( paid/free consumer/business etc) use the same application/flow/pages but require different styling.I know currently I can:- make different applications- make 2 flows- etcBut these options often result in doing double workSo I can:- Use a webblock with conditional css (not very pretty)- Use a class and write seperate code for each case in the css fileThe latter will result in unnecessary code in the css file (currently the best option I think thought)So it would be nice to have a (site property controlled) conditional theme. This way we can make a base them and then base the conditional themes on that.Alternatively allowing for SCSS would be a nice addition to create user personalized themes in your applications in a pretty way

At this moment, when we set the "Align" property of a container, it generates the align property in the HTML.Example:Align -> RightGenerates: <div align="right"></div>My proposal is to generate "system" classes the same way "OSInline" is added when a container doesn't have "Width" property set.My suggestion is (following above example):Align -> RightGenerates: <div class="OSAlignRight"></div>.OSAlignRight {    text-align: right;}.ar .OSAlignRight {    text-align: left;}The motivation:- I'm working in Arabic applications and it's a pain in the ass to go around that "align" property. Even after telling the whole dev team "don't use that crap, use our classes".Please, also update the SILK UI "out-of-the-box" RTL stylesheet to override this system classes.

OutSystems displays the table widget in tablet and phone devices as a stack of rows. Each row is shown as a card appended above each other. It would look better if it is displayed as cards, like in a gallery. To achieve this I had to use CSS to change each row style to appear as a gallery of cards. If implemented, it would save much to be done by frontend developers, and add to the UX design of OutSystems. I think it should be a configuration in the table widget, with other options for the display mode, and customizable number of columns for a gallery view mode.

Sometimes we need to navigate through the module, when merging. I think that is a good idea to allow to navigate through the module while doing the merge, without the need to close the merge popup. This is usefull to check the code on other actions (not on the merge)

Would it be possible to add a Test input at the beginning of any logic flow, or within an expression. Similar to the Test feature within aggregates or SQL. For expressions it could be helpful when there is data processing or functions involved. For logic flows it would be great to be able to enter a test value at the beginning or somewhere in the middle of the flow and see how it behaves through the logic. Doing this via debugger is not always as direct to test, and sometimes logic is only triggered at certain instances which can be challenging to trigger during debugging. It could be similar to having a debug option to start from a location within the code, with a data input set. Rather than having to trigger the logic from the front end.

Instead of manually restricting double-clicks using local variables or JavaScript, it would be more efficient to have built-in protection against double-clicks as a default behavior or as an optional property on the Button widget.

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