Dear all,The AD has a chart with the overall technical debt trend for all applications within Outsystems factory, however should be very interesting to have something similar for each application.Something like:Best regards,João Paulo Pires

When recovering deleted code or working with another person in the same app, during merge and publish it would be very helpful to have an option to 'Select All' for the versions we want, instead of selecting them one by one.

It would be great if I could expand an assignment to some structure like is already possible for parameters of an action.

When we do a merge with two OML, would be useful to have a search box to filter whats been shows in Compare and Merge box.

It would be helpful to be able to create multiple plans and schedule when they are being published or add them to a publishing queue.Our company has a large number of applications and we are running into the situation where we have so many applications its taking a long time to publish.  If we can split up the applications being published and schedule it to run in off-hours it would improve performance.Another case is we have multiple developers trying to publish to the same environment. Sometimes we forget to go back so the QA spends time waiting for all of the changes to be published for testing.

The accelerator should allow developers to easily configure the behavior of the Delete action, providing the option to choose between hard delete and soft delete based on project requirements. This enhancement would: Improve data integrity: Prevent accidental data loss by allowing for easy recovery of "deleted" records. Enhance auditing capabilities: Maintain a historical record of deleted entities for analysis and compliance purposes. Increase flexibility: Provide developers with the choice of deletion behavior based on project needs. Reduce development effort: Eliminate the need to manually implement soft delete logic for each entity. Additionally for the existing feature, enhance the OutSystems Entity Action Wrappers Accelerator to include a built-in option for soft delete. By default, the generated Delete action should mark the entity's 'IsActive' flag as 'False' instead of performing a hard delete. This will improve data integrity and provide greater flexibility for data recovery and auditing purposes. By incorporating this feature, OutSystems can further streamline the development process and provide developers with more robust and flexible data management capabilities.

A collate definition attribute for each table/entity in the join will be useful, so as not to force the use of SQL Advanced and to reduce the risks/chance of errors in the development. By default, the collates will come with what is in the bases of origin of the tables, so that they can then be changed according to the need. We have a scenario in which we make joins between tables with different bases and one of them has the SQL_General_CI_AS collate while the other uses SQL_General_CP850_CI_AS. This shows a warning in the column of the join involved, it allows publishing but incurs a runtime error. I thing something in this position:

The <span> that gets added around items in ListRecords causes a lot of issues with jQuery and other things. For example, we tried using a div with display: table-cell and it did not work because of this. J.Ja

Hi guys, we use something similar here, but we do it manually.We know that good architecture is very important in our projects. It is a wonder if we could see in our tree view the actions and other dependencies with the same color they were classified in the discovery tool.For instance: library modules can have the default icon green and core modules a default color orange.So, when you are in a green module and try to consume an action from the core module, you can see you are doing something wrong directly on your tree view and safe time to run the discovery and check this later.Even the developer who is not so expert in 4LC can help to keep the architecture in the right lines.

Introduce a unique icon for private actions in OutSystems to visually distinguish them from public actions. This improves clarity, reduces accidental misuse and supports better encapsulation of logic. A key benefit is that it eliminates the need to reorganize code into folders or rename actions. Observation: I could not find this exact idea already proposed. If anyone knows, please let me know. Attached a example.