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

During the development, when you add functionality through the editor view itself (not drag and drop from the Logic-Tab, stars are sparkling over the last added LogicNode. It would be great to disable that UX-Element, because als long as those stars are sparkling, you are not able to click the logic node below. This slows down the development speed. Thank you, Kevin

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

Our community has developers with many years of experience but for some reason or another, some of them don't have certifications... But they still are good developers and part of our community. This year several times I have heard during the Next Step and OWDC people saying "well I can't collect the certification badges because I don't have one. But I still like OutSystems and have been using it for years already".In a way to bring our community together and make everybody more embraced by our swag what about create a new badge?!Let's create the dinosaur badge and give it to the ones with more than 10 years of OutSystems experience!!!!Unfortunately, I'm not part of those with more than 10 years =( hehe

As requested by OutSystems Support Team, I am creating this Idea because it's important that the build log for any compilation on mobile on ODC be similiar to what we have in O11. Today, the mobile build is a huge amount of text that can be difficult to understand what is the main reason your mobile app is not compiling. In O11, it's more easy to understand. Maybe on ODC, put the main error on the top (or at the end) of the file so the developer can easily identify the root cause of the APK/IPA being broken upon compilation.

Many posts can be found on the Forums about how to calculate the difference between two dates in milliseconds.The current Diff-functions that are available as built-in functions are DiffDays() , DiffHours() , DiffMinutes() and DiffSeconds() .Let's add a  DiffMilliseconds() function to that list to speed up development even more as it comes in handy for numerous use cases.

 An app that allows small local businesses that do or do not have website/ e-commerce to advertise their services and changes , in context of COVID-19, on their business operations t o local Neighbors.As main users, we will have citizens  and Local business owners/representativesThe main use cases we propose are: Local businesses can sign up through a platform and fill in their information , like: Updated opening hours/delivery hours, contact information, location, list of services they deliver, changes to their business operations in effect right now and series of small posts/tweets Citizens can easily find and consult the information above in their immediate neighborhood / current location.  They should be able to filter by services and even quickly find who is open or delivering right now or for a certain time. They can then contact the local business or head there.The main challenges we are assuming that we going to face with are:Getting the local businesses to sign up;Information can be outdated fast;Validating the information given (avoid fake businesses and misinformationIt needs to be easy for businesses to use.

Service Studio should provide more built-in icons for actions. Upload icons is a pain process and allowing developer to upload any kind of images polutes the code readability. If Service Studio could provide some icon options this could standalize the code flow. I would suggest icons for Private actions like: If this could be done automatically, it would be great.

One of the purposes of publishing a solution, is to refresh all modules in it, and reflect a change of an upgrade. What I propose, is to remove unused dependencies between the defined modules in the solution. I recommend for it to a configurable option. But it would be helpful especially in big projects, where the architecture is big and complicated. Also, it could be a helpful option before checking the architecture in Discovery. Before the check we have all modules refreshed, and all unnecessary links broken.

For example 30 people are working in same environment in a same project. Some times multiple users publishing the same module, currently it goes to uploading state and finally gives concurrent publish error. If the button is disabled and gives an message of "Other team member is publishing this module", it will save lots of time for developer. In my scenario we work with clients in remote, so for publishing only we spend lots of time for this scenario.