When you're working on the OS PaaS environment, the time that is displayed when a module is deployed is the server time. I would be nice to have a setting in lifetime where we can set our own timezone so for our company the correct time when an application is deployed is shown.In some cases we need to check when something was deployed and we need to 'calculate' when it was deployed. Als when people don't know it's a different timezone the will be some communication errors.It's that small thing that make life easier (-:

Currently, the "OutSystems Mentor" title on member profile pages is static text. To better bridge our community with the global mentoring ecosystem, I propose making this title a clickable link. If a member is a verified mentor, clicking their title should redirect users directly to their ADPList mentor page. This streamlines the process for mentees to book sessions and view the mentor's full coaching credentials without manual searching.

 Issue: The Table Grid component in OutSystems is currently missing several helpful features found in the Data Grid, including the column picker. As a result, developers frequently resort to the Data Grid solely for offering column customization features, even though the Table Grid would be more suitable for less complex scenarios. Moreover, the Table Grid lacks a native feature to establish row gaps (spacing between rows), which would enhance readability and visual aesthetics in numerous situations. Concept: Upgrade the Table Grid feature by incorporating: A column selection tool enabling users to dynamically display or conceal columns. A row gap feature to manage spacing between rows for improved visual appeal and readability. Advantages: Lowers the necessity to utilize Data Grid for straightforward use cases. Enhances user experience via personalization and improved layout management. Maintains lighter pages that are simpler to manage while providing increased flexibility.

It would be great to have these events in a SOAP webservice also, so we could also manipulate Headers and RequestText of the SOAP Message.

When we add non-mandatory attributes to structures (for example input/output structure of a Service Action), there will be no impact on the consumer modules ONLY if the added attribute is a basic type. You can read this in the documentation Handle Changes in Exposed Functionality , 'The following changes made in the producer do not have impact on the consumer modules: ' Add an optional Attribute (basic data types only) Structure In my perspective, there should also be no impact on consumers when adding non-mandatory composite/complex attributes like adding a record, or a list, or list record... Here is a scenario we are facing right now. We use Service Actions instead of internal REST API's to promote a loosely coupled architecture. There is benefit in using Service Actions as the platform handles the security and findability of Service Actions, whereas with REST API's, you have to do it yourself. All our Service Actions communicate with input/output Structures. When we want to add a non-mandatory structure to the output structure of the service action, then the consumers are impacted. Now both applications have to be deployed together, which complicates loosely coupled deployment strategies. Here is an screenshot to describe the issue.

In the Language Translations editor, please enable multi-select dropdown support for the Behavior filter. Currently, when searching for a word to translate, the editor also shows results already marked as Don't Translate, which adds extra effort to filter them out manually. If Service Studio allowed filtering to show only items marked as To Define and Translate, it would significantly simplify the translation process.

Add a field Timeout on the tab Integrations on Service Center, this way I don't need to publish by Service Studio and Deploy the module to another environment.

When an input parameter is removed from an action in OutSystems, the platform should automatically remove all references and assignments of that parameter throughout the application to maintain consistency and prevent warning.

The idea is to right click on a reference and choose 'Manage Dependencies', open the 'Manage Dependencies' window already with the filter filled with the module name. We would have a big gain in performance.

Right now, ideas are scored like this: It feels like only quantity is valued, instead of quality. In my opinion, a better system would be to award points not for creating an idea (which promotes "idea spamming") but for the thumbs up the idea gets. There could also be an extra point award if the idea is implemented.