Hi everybody.I don't know wheter this is an idea or a question, or maybe we don't know a tool exist for this situation.We, at my company, are quite new working with Outsystems Platform. Some few days ago I did a minor upgrade from 9.0.0.2 to 9.0.0.19 version. Following the Upgrade Guide is a straightforward process but there is a point where things can become complicated: we have to republish every application and module manually, being specially carefull with dependencies.I think it would be really nice that this process could be automated as a taks performed inside the platform.What do you think?

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).

With the rise of AI/GPT, the community pages Forums and Ideas, are more and more receiving posts, replies, and ideas that for a part, large part, or complete are generated by AI/GPT tools. Not only community members use it, but also spammers. I would like OutSystems to consider embedding a feature similar to what sites as zerogpt.com to automatically detect & AI content. For example today the following reply was posted, and its 57% likely AI/GPT generated: For community members, it will help to understand if someone is providing information based on experience, or by relying on AI/GPT to generate an answer. For OutSystems community moderators, like myself, it will help to filter content and double check if the generated reply makes sense (as unfortunately we see many times the generated content is not correct). Furthermore, OutSystems moderators, also need to validate replies marked as Spam or marked as To-Reviewed, the score that the automatic AI content detection would give, speeds up the process to determine a reply is spam or not. No worries, this text is human written ;)

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.

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.

OutSystems already provides entity relationship diagrams after creating entities, but it would be even more useful to have a simple, editable flowchart feature to visually represent the data or process flow throughout the project. This feature would help developers and teams easily map out how data moves between screens, actions, and entities without needing to use external tools like Draw.io, Miro, or Lucidchart. It would be a quick way to narrate workflows or data movements directly within OutSystems during client discussions or internal planning. Example: For instance, consider a project with entities like Customer, Order, and Invoice. A built-in flowchart could show how data flows: Customer → Order → Invoice → Payment , and developers could edit or annotate the flow to demonstrate logic or upcoming changes. This visual approach would make it easier to explain ideas, document workflows, and align technical and non-technical stakeholders all within Service Studio.

In OutSystems, when a user tries to access a specific page without an active login session , they are redirected to the login page. However, after successfully logging in, the user is not redirected back to the original URL they attempted to access. Instead, they are sent to the default portal or home page. This behavior can be inconvenient from a user's perspective. Users are forced to manually navigate back to the desired URL, which disrupts their experience, especially in scenarios where deep links or bookmarked URLs are involved. Proposed Solution: Modify the authentication flow so that if a user is redirected to the login page due to an inactive session, their original URL is preserved. After a successful login, the user should be redirected to the URL they initially attempted to access, rather than the default portal or home page. Benefits: Improved user experience and satisfaction. Enhanced support for deep links and bookmarked pages. More intuitive behavior aligned with common expectations for web applications. This enhancement would make OutSystems more user-friendly, particularly for scenarios requiring frequent logins or when users access the application via shared links.

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

Currently, OutSystems documentation provides a list of compatible browsers for generated applications. However, verifying this compatibility at runtime requires developers to manually implement logic using functions like GetBrowser or GetUserAgent from the HTTPRequestHandler extension. This approach has drawbacks: Manual Maintenance: Developers must update their code whenever the official compatibility list changes, risking outdated implementations. Difficult Diagnosis: Identifying issues caused by unsupported browsers can be time-consuming, as seen in a real case where support intervention was required. Suggestion:Introduce a built-in Action in the platform to automatically verify browser compatibility using OutSystems’ maintained compatibility list. Benefits: Simplifies development by removing the need for custom maintenance. Speeds up issue diagnosis related to browser compatibility. Enhances user experience by providing immediate feedback if an unsupported browser is detected. IsBrowserCompatible() -> Boolean The Action would return True for compatible browsers and False otherwise. Additional functionality could provide details about the detected browser and compatibility issues.

 Current Situation When configuring multiple modules, the system performs individual Catalog updates for each module, which increases execution time when the number of modules is large. Problem Statement When the number of items increases, users are required to: Select and configure each item individually . Proposed Enhancement Introduce a “Select All” option that enables: Selecting all relevant items at once Executing a single batch update on the Catalog instead of multiple individual updates