When consuming a REST API that uses Basic Authentication, it's possible to statically specify the Username and Password (REST API properties and Service Center). However, I've encountered many REST APIs out in the wild that use Basic Authentication not for access to the REST API but for per-app or per-user credentials. As a workaround it's possible to support this with an OnBeforeRequest and adding the Authentication header yourself, but that is pretty cumbersome. It would be very handy if the Platform supports out-of-the-box capabilities for dynamically setting the REST APIs Basic Authentication Username and Password.Some posibilities:1) A property "use dynamic Basic Authentication" which if set on the REST API causes every method to have two extra parameters for Username and Password;2) An action that's exposed throught the REST API (comparable with the way actions are exposed through an entity) that allows setting the Username and Password once for a specific REST API.

Hi,Today, to create a new grouped attribute, you need to open an attribute menu in order to do it, while to add a new attribute ( not   grouped ), you have a column at the end of the aggregate:The "Add new attribute" in a context menu is not intuitive, and is not coherent with the most used "New Attribute" column.I would like to see the same behavior: A column at the end of the Grouped section with a New Group Attribute. It would be more intuitive, and would be the same behaviour we alread have in the filters, where an Add Group Filter appears when you have a grouped attribute.

I want to be able to have different onparameterschanged, depending on which inputparameter has changed.Now i have to create duplicate variables to check which inputparameter has changed.

Currently, OutSystems Service Studio organizes widgets, actions, screens, and entities in alphabetical order. However, users may prefer a more flexible arrangement based on their workflow. Introducing a drag-and-drop feature would allow users to customize the order of these elements, similar to how actions and widgets are placed within a screen. This enhancement would provide greater control, making navigation more intuitive and efficient. Users who prefer the existing alphabetical order can retain it, while others can rearrange items according to their preference, improving productivity and streamlining development workflows.

 Problem:If there is a suspicion of infection, old and young must quarantine themselves so that the virus does not spread further. This is where the first problems often arise. Who is going with the dog? Who can bring me food? How can I keep my child busy with schoolwork?It is particularly difficult for older, but also very young people to bear this isolation. SolutionThe solution could be an application that connects neighbors and helps to manage these everyday things.features:1. neighbors nearby offering help like walking the dog or shopping.2. calendar to arrange appointments with the neighbours3. payment system with which these small services can be implemented for little money (with the dog go 0.30 cent for example)4. video chat for children in the same class, so that they can do homework together, or just chat.5. webshop for food, where affected people can put together their food and the supermarket packs it up and hands it to the helpers who then take it home.

 On version 8.0 you have the 2-Stage Deploy option and configuration on the Environment Configuration:It would be nice to have one setting available when you are about to publish one solution to ignore the 2-Stage Deploy for the respective solution or vice-versa.This would be very useful if you only want to apply this feature for a specific solution or project.It would be nice to have a setting per solution to apply by default the setting defined on the environment  configuration, or to set for always make use of the 2-Stage Deploy  or to never use the 2-Stage Deploy  for that solution.

Many times during development it's necessary to either check or modify the Effective  Value  of a Site Property .  It would be great if you could right-click on a site property in Service Studio and have the option to jump to its value page Service Center.i.e. In this menu there would be an additional option "Manage Site Property":Clicking that option would take you here:There is additional complexity involved with multi-tenant site properties, but perhaps it could navigate you to the Site Property for the tenant you have configured to Test Queries in Service Studio...  Just a thought.

I would like to be able to see the SUs consumed by an eSpace without having to publish it. Doing it in Service Studio would be best. J.Ja

Currently, in MultiLanguage OutSystems applications, exporting Excel files in the correct language requires workarounds. The issue arises because structure labels are fixed and not stored in Multilingual Locales, making dynamic translations difficult. Current Problem Structures support only a single label value, preventing automatic localization. Labels are not included in the translation system, requiring manual mapping. Developers must create custom solutions, increasing complexity and maintenance efforts. Proposed Solution Link structure labels to the translation system: Store column names/labels in Multilingual Locales files Dynamic export support: Automatically select the correct translations based on the user’s language setting. Benefits Reduced complexity: Eliminates workarounds for translation management. Improved maintainability: Simplifies language handling in exports.

The "Convert feature of aggregate to SQL" enables users to convert an aggregate (a query that retrieves data from a database) into an SQL widget. This feature is very useful because it allows developers to work with SQL directly, giving them more flexibility and control over the queries they execute. However, there is a limitation to this feature when it comes to sorting. If you apply dynamic sorting (sorting based on user input or other variables) within the aggregate, you cannot utilize the "aggregate to SQL" feature. This means that the conversion of the aggregate to an SQL widget will not include the dynamic sorting functionality. On the other hand, if you only require sorting based on a single attribute or column, you can still use the "aggregate to SQL" feature. This means that the conversion will include the single attribute sorting functionality, allowing you to sort the results based on a specific column in the SQL query. Overall, the "Convert feature of aggregate to SQL" is a valuable tool for developers, but it has some limitations when it comes to dynamic sorting within the aggregate. However, single attribute sorting can still be utilized effectively with the "aggregate to SQL" feature.