Please can we have the option to clear a date picker that's native to the widget itself. Like the Dropdown search widget does

Having identical icons for client and server side built in functions makes it tricky to know which one to use. For example the ListFilter shown below - how is one meant to know which you can use client side and which you can use server side? I remember it like this: client-side one is on top because the request always comes first from the user on the client side - i.e. the first/top one. But I think a slight variation in icons would not be a big change but would be beneficial.

Hi Outsystems,texts from StyleClass should be removed from the translations file:Nobody wants translate CSS classes ??Should be hidden from the file of translations or at least with default don't translate.Cheers,Luís

I would like to suggest a logic clarification (or modification) to the training for the archiving. It's possible there has been an oversight, or the training may lead to a dangerously wrong solution, or I'm just an idiot. (More than one option may apply.) https://learn.outsystems.com/training/journeys/web-developer-exam-2993/data-archiving-best-practice/odc/7017 Here is the current logic in question: Text below it it, whole section pasted for clarity: Set Archive Threshold - Sets the number of records to archive by iteration. This threshold can be defined using a Setting, so it can be adjusted without redeploying the app. Set StartTime - Sets a local variable with the current time when the execution starts. CheckRecordsToArchive - Validates if there are records left to archive, according to the conditions defined using the control columns. Has Records to Archive? - Validates the output of the previous query and executes the archive branch if there are records to archive. MoveIntoArchiveStorage_InBulk - Executes a bulk INSERT INTO SELECT statement from the primary storage to the archive storage, combined with a clause to limit the amount of archived records (using the Archive Threshold set in 1). It implements the archive condition. MainStorage_SetArchivedFlag_InBulk - Executes a bulk UPDATE to set the IsArchived flag of the records archived in the previous step. Can Process More? - Validates if the current execution duration is approaching the Timer’s timeout (using an expression like DiffMinutes(StartTime, CurrTime()) < 15, for a default timeout of 20 minutes). If there’s still time, it continues checking for more records to archive. This approach helps prevent the Timer from timing out and having to repeat work. CommitTransaction - Commits the transaction to make all changes permanent in the database. WakeArchiveData - Re-wakes the Timer to check if there are still records to archive. My suggestion it that something should be added to step 6 " MainStorage_SetArchivedFlag_InBulk " to explicitly clarify that they should not use the exact same logic (where clause) used in step 5 to select items in step 6, because the data may have changed , leaving the data in query different. This will result in the wrong records being flagged as archived, and subsequently getting deleted by the clean-up process. They need to do some sort of check (inner join?) against the archive table. I understand this is an edge case, but we all know one in a million edge cases tend to happen within a week of functionality going live. Maybe there is an assumption that someone will know to do it this way, and I'm just being dumb, but the wording of the guidelines would tend to lead to someone reusing the same query logic, especially as an inner join query would be assumed to be much slower....? Does anyone from OutSystems training, or in fact, their business processes team, have any thoughts on this. It this a flaw in the training content, or in the archiving logic that was envisioned? Or am I just barking up the wrong tree here? (I'm guessing this scenario is used in the exam as well.)

Whether employees are working in the office or on-site, they are exposed to an increasing number of systems and more complex communication channels, resulting in dozens or even hundreds of emails being received by a single person each day. These emails include a wide range of content, such as notification messages, business requests, urgent issues, and meeting invitations, with varying levels of importance. In this environment, there is a strong need for an AI-powered application that can automatically analyze incoming emails, identify items that are truly meaningful and must not be overlooked, detect schedule-related information, summarize key content, and automatically register relevant tasks or events into the user’s work platform. We believe this kind of intelligent email analysis and workflow automation solution can be effectively implemented on OutSystems, enabling rapid development, seamless integration with enterprise systems, and an improved user experience across both web and mobile environments.

Make an upgrade path that can upgrade app from O11 to ODC. Make a clear checklist and check it against the application. The process must be secure and achieve with a minimum click.

Any publish that takes more than 1min can encourage the developer to start other task and forget the publishing.A Notification popup when the module finishes publishing, like skype/teams/browser but for 1CP, would be a nice reminder to go back coding.Possibility to enable/disable by module.

Video Example for Each And Every WidgetOutsystem  consist of many widgets , give some demo videos to each and every widget how it works. it will help to outsystem beginners and they know how effectively use that .Thanks in Advancekishorevijay

I have seen multiple other ideas about this, but none were at the level that I need. When you have an application that is composed of multiple application modules (we'll call them) and you refresh a single module that then throws all of the modules out of sync, being able to refresh all of the modules in a specific order across multiple application nodes would be amazing. Say, I need to refresh something in my _CW application that then throws multiple modules in my _BL application , into the UI application. Being able to select which modules to refresh in which order would save a lot of time.

I propose that in the community forum  all the posts must be have a "flag" where the user must choose if the post applies  to Web , Mobile or both.