A significant security and GDPR compliance requirement is being able to automatically disable accounts when staff leave the firm or a team.  Whilst we can build applications in OutSystems with various authentication options the only external authentication method available for the developer environment is adfs. Given the wide use of platforms such as OKTA for synchronising and managing cloud accounts it would be great if the OutSystems platform itself supported SAML2.0 and/or OIDC.

 As a developer, I want to assign set 3 values to a single Site Property for all environments. This will dramatically speed up a deployment, where you won't browse several modules and change Site Properties depended on Environment. It is common practice when we set a Site Property value to production value by default, and change it manually in Dev and Test. In this case we kind of avoid a "human error" if we forget it during deployment. But sometimes we have several such properties, e.g. SomeDomainUrl , which should be different for each environment. I would suggest to inherit the practice we use in not low code: we might have several configuration files for each environment, e.g.: appsettings.json appsettings.development.json appsettings.test.json That means during a deployment build process the compiler will choose corresponding settings. How I see it: When you add a new Site Property, you can add (+) two more for tst and prod . If a developer does not add it, they are the same by default. Like that: Site Property : fromEmailAddress Value : "noreply-dev@mydomain.com" (+) tst Value : "noreply-tst@mydomain.com" (+) prod Value : "noreply@mydomain.com"

I would like to suggest implementing a visual indicator in both Service Studio and Service Center that clearly identifies if it's a Forge component from OutSystems Forge. That would facilitate the visualization of components made by the factory and external ones..

 Add a possibility to do a Distinct Select from a field on a Simple Query.

Hi just want to add a BETWEEN operation in the aggregate where clause, as it's much simpler than the >= and <=

When perfform a release via LifeTime, in case dependent applications need to be published. But you don't always want this.In large factories, it's a lot of work to unselect all dependent applications.As select/deselect all button would be a nice feature.

Like ListClear action there should be one for records. With just one action and just passing the record name as argument it could set the record attributes to the default values. This would be easier, faster and much cleaner than setting all attributes one by one or assigning the record to a blank one.

When I have a block containing a pop up, that pop up will be collapsed in instances of that block. When I have a placeholder inside that pop up, and I need to add a significant amount of design inside that placeholder, using the widget tree only gets very tedious. Therefor I would like to be able to display the content of the block, or at least the placeholders.

If you watch a lot of training videos  at one day, you have to disable the subtitles for every training video, set the speed if you have a slow speaker and you have to set the quality over and over.I want that every next video "remembers" the setting of the previous video.

It would be interesting to have a Null() function that replaces NullIdentifier(), NullDate(), and NullTextIdentifier() in OutSystems, like traditional programming.