Add an over all quiz module at the end of the Reactive Web Developer Course, It will give Overall idea about the Certification Exam and It give some confidence to candidate while taking Exam.And those Question not to be repeated or not to be same question comes in between modules.it will help to beginners as like me

Currently, OutSystems UI provides built-in Open and Close actions for individual Tooltip components. However, if we review the Tooltip API implementation, we can see that there is also a GetAllTooltips method available. https://github.com/OutSystems/outsystems-ui/blob/53a8f0e/src/scripts/OutSystems/OSUI/Patterns/TooltipAPI.ts#L2 If you want to show all the tooltips in the screen you need to rely on a iteration and trigger the open tooltip action. Add the GetAllTooltips and ShowAllTooltips to the list of OutsystemsUI Actions.

 AppFlow is a fantastic cloud tool to build and deploy mobile apps in an automated way. Right now, OutSystems developers have to manually take care of uploading their mobile apps to the app stores, and managing all that complexity. Since AppFlow is a tool made by Ionic , which was acquired by OutSystems I believe it would be of great value to developers to have these tools integrated, saving a lot of time and headaches. Cheers, Tiago

Implementing a change log for site properties in Service Center using OutSystems can enhance visibility over configuration changes, which is crucial for maintaining the integrity and reliability of applications. This feature can help teams track when a site property was changed, who changed it, and what the previous value was, thereby improving auditability and troubleshooting capabilities.

On the OutSystems version 11.10.16 Aggregates tend to be difficult to read, since both Sources and Joins areas are very small:Furthermore, the combobox and inputs in the "Test Values" tab are very small and it is not possible to see the chosen values properly (static entities values or text values):It would be great if the vertical space in Sources and Joins were increased and the spaces of "Test Values" could be increased so that the developer could be able to see what he is choosing or writing.

Collation is a problem in sorting when you have characters like "ÅÄÖ". Those are sorted incorrectly.Platform thinks that those ÅÄ = A and Ö = O , but that is wrong. Those should be after Z ....TUVWXYZ ÅÄÖIdea how to fix this:possibility to set collation in lifetime on platform level (this sets platform default level collation)possibility to set collation in application (module properties > overwrites platform level collation)When user sets collation either ways, platform adds automatically database searches  (SQLs + aggregates) COLLATE clause after TEXT attributes.Maybe add possibility to remove use of it in aggregates (checkbox: use collation [x]).SELECT {Sorting}.* FROM {Sorting} WHERE {Sorting}.[Sortedcolumn] LIKE '%'+ @SearchString + '%' COLLATE Finnish_Swedish_CI_AS ORDER BY @TableSort COLLATE Finnish_Swedish_CI_ASAnother possibility is to set collation on server or directly database, but this is probably not possible in AWS? See community discussion and current workaround: https://www.outsystems.com/forums/discussion/63776/incorrect-sorting-of-scandinavian-characters/#

Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If. J.Ja

The option to remove unused dependencies by eSpace is realy great! But I think it can be implemented to Applications at all. It wold be nice to have an option in ServiceCenter to remove all unused dependencies by an Application.

The OutSystemsUI theme currently ships around 200 lines of CSS that are only used inside Service Studio. The rules end up being empty because (I'd guess) there's a process that removes declarations that start with "-servicestudio". Our users should not have to download extra CSS that is only used for developers. I think OutSystems should consider moving this rules to Service Studio itself. Cheers, Tiago

 Overview OutSystems' 1-Click Publish with comment is a great addition that helps development teams maintain traceability — especially during hotfixes or production changes were knowing why a module was published is just as important as what changed. However, there's a gap in the workflow when publishing through OML upload and Service Center, which undermines this traceability. The Problem In regulated or collaborative environments, teams often follow a change management process where a developer must: Upload the OML file in advance Wait for approval/permission before going live Then publish the module once permission is granted Currently, when uploading an OML via Service Studio, there is no option to attach a comment. This means: If a developer uploads and publishes directly through Service Center (bypassing Service Studio), no publish comment is recorded The permission details, change reason, or hotfix context are permanently lost from the audit trail Teams lose the very traceability that the 1-Click Publish comment feature was designed to provide The only workaround today is: upload the OML, wait for permission, re-open the uploaded module in Service Studio, and then publish with a comment The Proposal Add a Comment Field to the OML Upload Screen: When uploading an OML file via Service Studio, provide an optional comment/reason field. This comment should be associated with the module version and recorded in the publish history if the module is subsequently published. Why This Matters Audit & Compliance: Many enterprises and regulated industries require documented reasons for every production change. A missing comment on a PROD publish is a compliance gap. Team Collaboration: Other developers monitoring deployments via Service Center have no context for why a module was published — especially critical during incidents or hotfixes. Consistency: The comment feature exists in one publish path but not others, creating an inconsistent and incomplete audit trail.