The connection timeout error message must include the request that failed, so we can determine screen and data fetch.Currently, the Stack is only mentioning thisCommunicationException: The connection has timed out at c.onTimeout (https://domain/module/scripts/OutSystems.js?dU8nDUaeDPfu6NWEtXEQEQ:3:7337)  at https://domain/module/scripts/OutSystems.js?dU8nDUaeDPfu6NWEtXEQEQ:3:4671Not even the screen name is on the detail of the error.

My younger daughter´s school is having them to do online school work in the form of online classes, research, presentations, etc to keep them busy and mainly to force them to continue with their normal school routine (albeit from home).I think this is a brilliant idea! However my eldest daughter has not been asked the same.Is this something we could help create for all schools in Portugal?It´s important children wake up early and feel like they are still part of school and have daily contact with their peers and teachers, as opposed to staying in bed til noon and do nothing all day because they dont have any goals, except waiting for this to end...

The Base URL for consumed REST services should be configurable at runtime:In some cases (like the JIRA Cloud REST api), the base URL of the web services varies according to the account used to access them. Since the URL is hard-coded in Service Studio (it can be overridden in ServiceCenter but the setting applies to all users accessing the REST api), there is currently no way to configure this based on the tenant being used or the user that logs in.

The user should be able to export site properties, which helps in deploy between environments.

There should be ability to add unit tests automatically for any actions. Also a unit tests should be automatically added to a Core Modiules.

A collate definition attribute for each table/entity in the join will be useful, so as not to force the use of SQL Advanced and to reduce the risks/chance of errors in the development. By default, the collates will come with what is in the bases of origin of the tables, so that they can then be changed according to the need. We have a scenario in which we make joins between tables with different bases and one of them has the SQL_General_CI_AS collate while the other uses SQL_General_CP850_CI_AS. This shows a warning in the column of the join involved, it allows publishing but incurs a runtime error. I thing something in this position:

It would be (very) nice to be able to copy/past, at least actions and structures, from one extension to another.

Hello everyone, I would like to suggest adding a placeholder for a footer in the sidebar. While I understand this may not be as critical as other issues, I believe it could enhance the overall widget experience. I'm aware of some workarounds for this, but we've encountered problems with our current approach due to the address bar's position on tablets and mobile views. We discussed this internally and agreed that it would be a worthwhile suggestion to raise. Thank you for your attention!

Currently, when we send emails using OutSystems, it doesn’t return the email ID after sending. This makes it very difficult to track/identify which emails were sent successfully and which ones failed. For example, if we are send 100 emails every day, we have to rely only on the system entity to check their status. But there is no provision to link this system entity to our application's transactional entity, so it’s hard to identify emails with their purpose or origin. It would be very helpful if the SendEmail action could return the email ID as output. This way, we could link the sent email with our business entity and easily track delivery status for each transaction.

Hello OutSystems Community, Building on the theme of making Application Objects (AOs) more visible in the Forge, I have another simple but powerful suggestion. The Problem: When we search for assets, the results page shows a list of component "cards." Each card displays useful info like ratings and download counts. However, to see the AO count, a critical piece of information for assessing impact and cost, we must click to open the asset's detail page. My Idea: My proposal is to display the AO count directly on the asset card in the search results list. This could be a small and clean UI element, perhaps next to the download or rating indicators. It would give us immediate, at-a-glance information for every component on the page. For example, the card could look something like this: [Asset Name] Rating: ★★★★★ (25) Downloads: 2.5k AOs: 8 <-- New information here Benefits: Instant Comparison: Allows developers to immediately compare the AO "weight" of different components without ever leaving the search results page. Improved User Experience: Reduces clicks and streamlines the workflow for finding the right asset, making the Forge much more efficient to browse. Works Perfectly with Filters: This visual aid would be a perfect companion to an AO filtering feature. We could filter for a range (e.g., 1-20 AOs) and then instantly see the precise count for each result to make the best choice. This small UI enhancement would have a huge positive impact on our daily workflow in the Forge. Thanks for your consideration.