A personal, honest, and relatable post that breaks from the standard "how-to" format. It's about sharing a real-world mistake, the consequences, and the critical lesson learned. This builds trust and shows vulnerability, which is rare in technical forums. Post Content: Confession: Tell a story about a specific mistake, like accidentally creating a server-side loop that crashed the environment, or a data model change that wiped out a client's data. The Aftermath: Describe the frantic troubleshooting, the communication with the team, and how the issue was eventually resolved. The Lesson: Distill the experience into a key takeaway for other developers, like "Always double-check your loops for a clear exit condition" or "Never make schema changes on a production database without a backup and a rollback plan." Invite others to share their own "confessions" in the comments, making it an interactive and community-driven post.

Make a app that count the number of Wash Hands.People need to create sereral Challanges while they wash there hands.After complete the challange they share the video on social media and challange other people.With this game we can make people fight the virus and have fun.Hope it helpsFM

As the community grows, we get an increasing number of inactive users.As natural as that is for any social network, that also means we'll have an increasing number of outdated Forge components .I believe that goes against the goals of helping the community with brand-new, cutting edge components.Whenever I find a component that I'd like to use, but it's old and/or deprecated, I try to convince their authors to add me onto their team so I can update it. A recent example is the CodeMirror component , which stopped receiving updates since platform version 7.However, that does not always work. If the author of a given component went inactive, his/her component lays there forever and nobody else can update/improve upon it.An example is the TinyMCE component, for which I tried to contact its author asking him to accept me into his team so I can update it ; since I didn't hear back from him, I had to upload a separate component named InputToTinyMCE, ultimately splitting the same plugin into two components and forcing the community user to decide which of the two should be used.I have a couple of suggestions to overcome this situation which I expect to become more and more common in the future years.Disable components (so that a new one can be created with the same name) that do not have a version compatible with the latest 2 major platform versions (e.g. P9.1 and P10) -- after giving a prior notice to its author(s).Allow other users to join teams whose components haven't received new versions in a while (maybe taking into account a minimum required community rank or forge score for security reasons).If items 1 and 2 are not applicable: any other mechanism that allows new users to contribute to "dead" components that may clutter Forge in the long run.

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

Hello, I think to have a option to disable the manual swipe on StackedCards would be a very usefull feature. Thanks, Paulo Torres

We already have the string join as a server action, but since it's server-side only, we can't use it when working on client-side specific logic, like offline mode in mobile apps. Therefore, having a client action with this functionality would be nice.

An entity foreign key attribute has a Delete Rule property which can be set to Protect, Delete or Ignore by a developer in ServiceStudio. A Performance Best Practice is to set this to Ignore, but that could lead to database inconsistencies. Therefore, during development, it is safer to use Protect. This means developers need to remember to set this rule to Protect during development and then to Ignore after testing has been completed and before deploying to production if they want to conform to this Performance Best Practice.You can imagine this process is prone to errors. So how cool would it be if you could set a Platform Default Delete Rule per environment in LifeTime or ServiceCenter and then be able to select 'Platform Default' as the Delete Rule in ServiceStudio?So, for example, in DEV & QA the Platform Default Delete Rule could be set to Protect and in PRD it could be set to Ignore using LifeTime or ServiceCenter. Then, when a developer chooses 'Platform Default' as the Delete Rule on a foreign key in ServiceStudio, the platform makes sure that the Delete Rule is set to Protect on the database when Publishing/Deploying to DEV and QA and that the Delete Rule is set to Ignore on the database when Deploying to PRD. So the platform automatically sets the Delete Rule on the different environments according to Performance Best Practices!

 https://www.outsystems.com/ideas/2555/Unused+variables%2c+actions+or+functions+should+give+a+warning+on+TrueChangeFollowing up this idea, it would be expected to have the same behavior on unused Session Variables  and Site Properties

The Responsive Ruler/Grid Overlay Widget is an amazing widget for everyone working on the UI in OutSystems, specially if you want things to look nice and align perfectly. And your Screen should be pixel perfect then this will help. Think of it as the perspective of a designer - A see-through grid on which you can build and examine your application. You turn it on and off with a button, and with the help of it you have got perfectly spaced lines helping you to make sure everything is aligned properly, spaced evenly, and it majorly helps with the responsiveness of screens. This is like having a ruler or grid paper in real-world, but inside your OutSystems application. Thank You

Ability to split an eSpace by choosing the objects you wish to carry to a new eSpace. The previous eSpace will automatically consume references from moved objects. Entities will keep their data.