When I compare/merge an espace with another version, then I also get differences like: - Position of elements have changed - Translation Behavior has changed In most cases I'm not interested in those changes, so it would be nice if I can turn those off. In this way it's easier to see what's really changed in the eSpace.

It would ease readabillity and avoid mouse clicks if all screen space is used to show as much of a filter definition as possible in the Filters tab of an aggregate definition.

When typing in a formula with a logical statement, I often spread it out over several lines.Now when I end my line with "or" and press enter it gets autocompleted to some random function with "or" in its name. It would be nice if Service Studio would recognize "or" as something that does not need completing.

The Idea is Giving Privilege of Integrating External Database in Service Studio .Point AService Studio has Application Layer which has 4 tabs Process , Logic ,  Interface and DataSo there should be a fifth tab name Integration Which would contain Folder for DatabaseUnder which there should be a menu list for database who are compatible with out systems. For example :- If you selected SQL from the folder then the wizard will appear where you  can provide the credentials and can test the connection.Once the Connection is successful then under Data Tab there should be the External DB folder which will contain an integrated entities.The main purpose of the Idea is to cut the Integration studio process and making it more flexible from giving privilege to service studio.

The idea is to right click a screen aggregate and convert it to a data action that has the same aggregate inside the flow and as Output parameters the sources of the aggregate. This could accelerate the process of building an output of an already existing screen aggregate that needs additional logic.

It would be tremendously more eficient for us, if there we can delete the variable and the assign value with one single button. Instead delete 1st the variable and the the value.If you need to delete 5 variable and the corresponding values instead of:   click variable   select all   delete   click value   select all   delete   repeat more 4 times the set of action mention.with the button should be like delete 5 times and done, we dont need to do 30 actions to delete 5 variables.thank you

In the Test Query tab, there's a scrollable list of tenants sorted by tenant ID to pick which tenant to test a query with. That is fine with a dozen or so tenants, but we have a few hundred in our test environment and that list is impossible to deal with. The scrollable list should be replaced with a more robust search system... allow us to pick by name or tenant ID. J.Ja

Have you ever had trouble analyzing a bad indented code?I feel the same when the elements are not equidistant.Service Studio has invested in improving the organization of the code, but still find it difficult to keep the elements equidistant.See the gif.

Currently, if you want to integrate with Amazon DynamoDB, a popular NoSQL database service provided by Amazon Web Services (AWS), you would need to use a Forge component called Amazon DynamoDB Connector. This Forge component provides pre-built connectors and actions that simplify the process of integrating OutSystems applications with DynamoDB.Simplified development: With native support, developers wouldn't need to rely on a third-party Forge component. They could directly access DynamoDB functionalities through Integration Studio, reducing the need for additional installation and configuration steps.Enhanced productivity: Native support would provide a seamless development experience within the OutSystems environment. Developers could leverage visual tools, such as drag-and-drop actions and configuration wizards, to quickly build integrations with DynamoDB.Standardization and stability: OutSystems could ensure that the integration with DynamoDB is well-maintained and kept up to date with the latest changes in DynamoDB's APIs. This would provide developers with a more stable and reliable integration option.Easier learning curve: By incorporating DynamoDB integration into Integration Studio, OutSystems could provide documentation, examples, and tutorials specific to DynamoDB, making it easier for developers to learn and utilize the service.

My idea is to make a function that clears a local variable, for example a variable of any structure type. I want to display a form in a popup and then clear the variable so that the form will not be filled in by default for the next click. Instead of creating another similar variable and assigning it again, or clearing the structure variable attribute by attribute, I think it's more practical.