On SS be able to set a property of "Data Encrypted" on an entity attribute

Currently, the 'HTML element' widget does not allow de 'dialog' tag, which is valid HTML. The dialog tag is very useful to create modals, so it should be allowed. See Dialog Tag

When creating a custom API log entity, it would be helpful to save a reference to the Service Center integration logs using the request key. We can use the Request_GetKey action to add the key to our custom entity. This key is visible on the Integration Details page or can be used to join the Log_Integration entity. Additionally, I propose the following improvements: 1. Add a “Request Key” column to the table on the Monitoring > Integrations screen in Service Center. 2. Include a filter field to search by “Request Key” directly in this screen. These changes would make it easier to find specific logs and enhance debugging and monitoring

When we develop actions and specially change them later we sometimes remove code in the flow.When a variable is not used anymore after changing / deleting some code in the flow service center warns you about this (yellow line under the variable and a message in the warning panel).When an aggregate is not used anymore service center does not warn you about this.I would like service center to warn me so I can check if the aggregate can be deleted or not.In the example below the GetUsers aggregate is not used.

Hi Team, As we know OutSystems provides the automatic documentation generated for an exposed Rest API which is super helpful and can be shared among the developers as per the below link: https://success.outsystems.com/documentation/11/integration_with_external_systems/rest/expose_rest_apis/document_an_exposed_rest_api/ but not every organisation or client wants to expose the details of their API documentation without any authentication or anonymous. It will be super helpful, if there is any configurable option available to secure the exposed rest API documentation. Thanks, Manish Jawla

To improve Forge quality, which in my opinion is decreasing day by day, OutSystems should moderate all the new components submissions.Instead of being instantly available after submission, they should wait for someone from OutSystems to check them and approve.This would avoid the submission of tests, spam, exploits, redundant components, etc.

It would be interesting to show the execution time of the query when pressing the "Test" button in the SQL Editor for advanced queries.Yes, it's not a real view of how the query is doing, but it may help in understanding if a query is REALLY slow, or slightly slow.

It would be really cool if there was a button as an accelerator to create a filter using the GetUserId() function, since it is a very common operation.

When deploying applications with DevOps Pipelines using the LifeTime API, the deployment started with the API will skip the "Configuration or confirmation" step and will assign the modules automatically to the "(Main)" catalog causing a lot of manual rework in Service Center assigning the correct catalogs. When exactly the same deployment plan is executed with LifeTime the deploymet stops at the "Configuration or confirmation" step. With this idea, we suggest to apply an option to activate the "Configuration or confirmation" step when a deployment is started via the API. It is not desired to assign the catalogs via the API, however that could be a great additional functionality but it is not desired to get "our" pipeline problem "fixed".

When viewing large tables, it's quite difficult to find the column I'm looking for. It would be nice to have a menu entry to focus/highlight an attribute when previewing data from tables. Mockup