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 :)

When creating a new application in Service Studio, I really appreciate how the platform automatically extracts the primary theme color and generates a default logo based on the uploaded application icon. This greatly helps with the initial branding setup. However, I’ve noticed that the favicon is not automatically set in the same way. It would be a great improvement if the favicon could also be auto-generated or defaulted to the uploaded application icon, just like the logo and color theme. This would ensure a more consistent visual identity for new applications right from the start, without requiring additional manual steps. Thank you for your continuous improvements and for considering this suggestion!

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

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.

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 .

We can define Content Security Policy (CSP) through Lifetime and Service Center. This applies the configurations we need to prevent some attacks. It would be great that Outsystems allowed to create a CSP in report mode only (header: Content-Security-Policy-Report-Only). This way we could test our rules before applying the CSP to the full environment. This would also be great if this Content-Security-Policy-Report-Only mode goes to the CSP Reports tab from Outsystems.

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.

When you configure Log Redaction to "Yes" it is only redacted if the header is sent on the exact same case as seen on Service Studio. It should have been case insensitive as RFC 7230 Section 3.2 states: Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace. This behavior happens with or without Name in Request set.