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 .

When the option "Find usages in all eSpaces"  is selected, and we have more that one eSpace using the resource would be useful to have the option to select the eSpaces to be open.

No one have doubts about that aggregates are very powerful but in lot of cases the Simple Queries do the same and are more appropriate.The main reasons for this idea is this post . And I just passed to an Idea to know how much developers agreed with this so Outsystems can bring back Simple Query since the code is already there.Thanks and Version 9 is awesome!

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

HiFrom my Service Studio, I can connect to different environments but once I connect to that environment, that server details stays there permanently. I would like to have an option to clear that drop down of environment names.Also once I remember password, it is saved permanently, I would like to have an option, to clear the password so that it won't show unless I want it.Thanks and Regards,Suraj Borade

Need to be able to show a total footer at the bottom of record list widgets (Table Records & List Records) and the functions necessary to calculate totals, etc.

Developers can leave comments on screens and action flows. Currently, there is no overall view of TODO: (work to be executed). It would be nice if ArchDashboard would list TODO: comments per module, so that no TODO get's overlooked.

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.

Not too long ago, we got For Each nodes to display the name of the Record List as its default label . Could we get something similar for Assign nodes with multiple assignments? Current behaviorWhen creating an Assign node with only one assignment, its default label becomes the name of the assignment.After adding 2 or more assignments, the default label changes to a generic "Assign" name. Proposed behaviorThe default name of the Assign node would be the conjunction of all common leftmost names of its assignments.If a common name cannot be resolved, then it defaults to the generic "Assign" name.Examples below: Example #1 - Common name "MyStrucutre.InnerStructure" Example #2 - Common name "MyStructure" Example #3 - No common names, defaults to generic "Assign" name RemarksThe "Assign" generic name does not add any value to the understandability of the code. Thus, any feature that attempts to display a meaningful label instead of this generic name is a valid product enhancement effort IMO.Good practices say that you should always custom-set the labels of your Assign nodes. However, as we know it, many assignments created every day by the average user are unlabeled.With the proposed behavior, developers are more likely to split big Assign nodes -- that contain assignments of different/unrelated records -- onto smaller Assign nodes (each containing values of one individual record) due to the automatic naming convention, improving code readability.

Please can we have the option to clear a date picker that's native to the widget itself. Like the Dropdown search widget does