We found certain queries coming from clients and timers get stuck in IIS indefinitely, despite having timeouts. These queries were sitting in IIS without any way to know this until our environment was inaccessible and we had to reach out to support to resolve the issue. While this clearly is a bug, support stated they would not be resolving this issue and thus we should create an 'idea' for it. Truthfully, not an idea, a bug that needs to be resolved because it results in OutSystems environments slowing down over time, eventually leading to them becoming inaccessible, and customers don't have visibility into IIS. Additionally, as part of my 'idea', I would suggest the OutSystems website to reflect the fact that this can happen as statements like "Every web request done to an OutSystems application takes its time to process by the application server (IIS) and is ruled by a Request Timeout that prevents the existence of everlasting web requests", are false. Obviously such a change would only be necessary in the short term as ideally, this issue would be resolved, but until then statements of this sort on their website are lies.

A button to record a debug session, which would make it possible for us to go back in the debug if we wanted to or save it to watch it later while looking at the logic of what we are trying to fix.

If I want to check for the latest version of the OutSystems naming conventions, I have to go to a Video lesson and check it. https://www.outsystems.com/learn/lesson/1223/module-naming/?LearningPathId=0This is troublesome and a dedicated page or link could be available at https://success.outsystems.com/Documentation/Best_Practices/OutSystems_Platform_Best_PracticesThank you!

Hi Community, We may end up creating large objects based on our business requirements and there are instances where we need to empty the object or part of it in our logic, as of now we are explicitly assigning "" values by expanding each and every variable from that object, so it would be great if there's a built in function kind of thing to empty the same object or part of it like in traditional coding. Regards, Mahesh

On Service Studio, it would be nice to have an icon indicating if there are modules inside the applications that are broken (with errors).For instance, I've updated a component and after that there are 2 apps with broken eSpaces, but in my Service Studio list view of the apps I don't have a way to see it. I need to go into Service Center and go to the eSpaces' list, filter by the ones with errors, check the application and open on Service Studio to refresh the dependencies and publish (jumping in two different "windows" just to clear the errors).

There's still a gap in terms of documentation/training concerning integration, comparing to other topics.A certification involving Excel; APIs SOAP/REST; External DB; SAP; AZURE; Extensions; Login/SAML; AD; Integration Builder with proper documentation available would help to raise the level of developers.

Quality of Life Improvements in the ODC Deployment Cycle Dependency Overview, when deploying an end-user application, it’s helpful to see a detailed overview of dependencies that might compromise the deployment. While this is a valuable feature, it could be even more effective if it allowed direct interaction with those dependencies—such as clicking on them to initiate their deployment or making the process more seamless. Currently, if multiple core applications (e.g., 8 or more) must also be deployed, you need to manually track and list them, which can be cumbersome. Navigation During Deployment, if you decide not to proceed with deploying a specific application after selecting a revision, it would be useful to have an option to navigate directly back to the application selection screen via the left-side menu. At present, the process involves either restarting by going back to the “Deployments” screen or clicking "Back" multiple times, which is not ideal for efficiency. Improving Feature Toggle, managementFeature toggles are essential for enabling parallel development and hotfixes, aligning with best practices recommended by OutSystems. While it's possible to organize feature toggles using folders in the development studio, this structure doesn’t carry over to the cloud interface, where you manage toggle values. Improving toggle management in the cloud would significantly enhance deployment workflows, as it directly impacts the flexibility and control required during deployments. A last one that also goes hand in hand with the deployments are the secret settings that you might need for API's (just an example). Whenever you make use of a new settings or app that uses an existing api you will need to fill in the setting its value. Because they're secret and always filled in with a default prompt you can not tell that its value is already filled in and if it's filled in that it's correct. Obviously this is intended but it can make big deploys with multiple applications hard to manage. An easy way to fix this could be an 'updated on' field that shows when the value was changed if changed at all so you can easily see if you have already updated the value. Thanks in advance for all already made improvements. Kr, Owen

It would be helpful to have the Start Index parameter in the local storage aggregates as well.Right now it is only available for the server aggregates, meaning that if we want to implement the pagination functionality for local entities, we need to iterate through the list to make it work, which is not ideal.The standard pattern for mobile is the OnScrollEnding action, but for a tablet focused app, that pattern may not be the best fit. For tablets, it's also common to use the table widget, which doesn't have the OnScrollEnding functionality enabled, making the pagination the best alternative.

It would be amazing if we could have a system to detect duplicate logic (especially aggregates and SQL) so that it can be refactored to reusable code.

We would like to document everything in our code so we have descprion field everywhere.Also for variables in actions etc but not for parameters in the javaScript widget.So you can't specify what the purpose is of the variable.Please add the description field to the parameter field in the javaScript widget just like for normal variables.Kind regards,Johan den OudenOutSystems MVP