Proper documentation is essential for maintaining and collaborating on OutSystems projects, but manually filling in descriptions can be time-consuming and often overlooked. I propose an AI-powered feature that automatically suggests descriptions for elements such as: Variables Actions Screens Blocks Entities The AI would analyze the element’s name, its usage in the code, and overall context to generate an accurate description. The developer would then simply accept or edit the suggestion , making the process faster and more efficient. Benefits: ✅ Time-saving documentation process – Developers can focus more on implementation and less on manually writing descriptions. ✅ Standardization – Generated descriptions would follow a consistent and clear format, improving readability and maintainability. ✅ Better collaboration – Teams can quickly understand the purpose of each element, even if they weren’t involved in its creation. ✅ Easier onboarding for new developers – New team members can familiarize themselves with the codebase more quickly. This feature would enhance documentation quality and significantly boost developer productivity in OutSystems projects. If you find this feature useful, upvote and share your thoughts!

It would be awesome if there was the possibility of Uploading & Publishing multiple modules at once through Service Center.

OutSystems created a what's new page to keep everybody aware of what is being released. That's great! But there's no way to be notified every time there is a new entry :(In my case, since I want to be aware and check every awesome stuff released, that would help me be updated.My suggestion is to have an RSS feed or an email (you could use the daily community updates email).Thanks :)

Service Studio prevents creating foreign keys that reference a static entity defined in a Library module.This makes sense for Protect and Delete rules, because the static entity defined in a Library module is not backed by any database tabe.However, IMO nothing is preventing us from using a foreign key with Ignore rule. These foreign keys will not have any database constraints, and will just be syntactic sugar to their underlying type (Integer, Long Integer or Text) but with the additional type checking and suggestions we come to expect from Identifier types.For example, it should be possible to define static entities that augment the capabilities of OutSystems UI by using this pattern, as described in https://medium.com/@leonardo-monteiro-fernandes/extending-static-entities-part-1-bec8b3b7631cThis would also allow values obtained from SOAP enumerates (which are mapped to non-persistent static entities) to be stored in database entities, without discarding the type information.

When calling a service action, the platform seem to internally set a fixed 100 seconds timeout on the request, so if the action takes longer then that, a "time out" exception is raised on the "Client side" but the action will keep running on the "server side".I'm not sure if i'm missing a setting here, but in case i'm not, my suggestion would be to either raise the 100 seconds timeout or make it configurable when calling service actions.

To keep the code cleaner and avoid circular dependencies, it would be interesting not to let a module publish when you had to create circular dependencies.

Often, I want to get a list of all espaces with broken and/or missing references.It would be a nice feature to have a combobox on top of the espace and extension list which allows to filter based on status- all- all ok- missing references- broken references- missing & broken references

Hi,I would like to suggest that it might be helpful if Service Studio alerts when using preparation data on screen actions, which increases hugely the view state and it would be aligned with the performance best practices .

Current CSPs rely on allow-listing domains which is difficult to secure, and vulnerable to attackers bypassing the CSP. As an example, it is currently impossible to implement Google Tag Manager without compromising an Outsystems Content Security Policy, as it requires both the unsafe-inline directive. It also requires allow-listing the www.googletabmanager.com domain which is found to host JSONP endpoints, which also can be used to bypass the CSP. See: https://csp-evaluator.withgoogle.com/ for a report The recommended approach is to use server generated nonce tokens in the CSP, and also in the scripts that are allowed to load. These scripts are considered trusted and may in-turn safely load script from other, cross domain sources. For tag manager, a recommended setup is here https://developers.google.com/tag-platform/security/guides/csp My suggestion is for Outsystems to support generation of nonces in the CSP headers returned to the client, and allow the front end to load a developer defined script with the same nonce tag. From there we could load any other cross domain resources without needing to weaken the CSP. For more information, see https://web.dev/articles/strict-csp

There is a limitation in OutSystems Service Studio where folders cannot be nested inside other folders. As a result, application elements must be kept in a flat structure, which reduces clarity, organization, and long-term maintainability. Why not allow developers the flexibility to create a better and more structured folder management system?