Because sometimes you already know your timer execution has gone bad and you just want to stop it.

For a DropdownSearch there are options for translating/changing NoResultText and SearchPrompt It would be good if the OptionalConfigs also have a configuration for clearButtonText

Add tools to allow the enhanced organization of application icons in the user's environment in Service Studio. Filter, Sort, View mode (List, thumbnails, ..), ...

I would like to right click on a Entity in a non-production Environment and generate one script with delete in cascade to clear all the records from that entity and avoid the error "The DELETE statement conflicted with the REFERENCE constraint".

Hey guys,I think it would be really helpful to have a new tab besides the TrueChange tab that shows the Architecture Dashboard report for the specific module we're seeing.Apart from being more accessible, developers can easily look at the report in the module scope and more proactively reduce technical debt.

Currently when I want to delete records from an entity and I get an error, the error gives a technical name of the entity that prevents me from deleting a record. Please show the name of the entity as noted on the logic tab

When the screen has too much information and the performance starts to decrease one of the options we have is to create a web block with some of that information and do a lazy load.It would be nice to have something similar to "Extract to action" where you can select the elements in the screen and "Extract to Web Block".In case of a table, it would:- Remove the query from the preparation of the screen into the preparation of the Web Block;- Remove the actions from the screen into the Web Block;- Remove the selected elements into the Web Block;- Add the necessary input parameters to the Web Block.

Considering the fact that the cloud version does not support internal network for IP white listing, I think adding an extra layer of security to secure service center  with Two factor authentication should be a standard in the Outsystems platform.

Right now when you want en entire Row of a table clickable (or another event), you need to put the OnClick event on every Row Cell and point to the same action every single time which is quite repetitive and prone to mistakes. If you add a new Row Cell because extra data needs to be shown, you need to put the OnClick action again for this specific Row Cell even though it point to the same end point as the other ones. It would be nice if we could put the event handler on the entire Row instead of on the Row cell. Like this, newly added Row Cells will automatically point to the same OnClick action and you won't forget it. The option to put different handlers on the different Row Cells should still stay. This would just be an extra way to make an Action for a whole Row at once.

It would be really helpful to have an "OutSystems Agent" that has knowledge about our codebases and can answer questions, generate insights, suggest actions, etc etc. It could also be connected to app metrics so we would be do some queries like: Why is X app slow today? What changed in the last deployment? Show me all missing role checks in app X Generate sample test cases for screen / action Y and so much more