In many online games with ranking systems, such as League of Legends, players are grouped into tiers and divisions like Bronze, Silver, Gold, Platinum, etc. Each tier reflects a player’s experience and performance, such as how long they’ve been playing and how many wins they’ve achieved. While this is mainly a very simple UI concept, it’s actually a very cool one 😄 For example, if a user’s rank is above 50,000, they could be placed in a tier like Bronze, which can be displayed on their profile and also used as a filter when browsing members. If their rank is below 6,000, they could be Silver, and so on for the other tiers. Features like this were very motivating for me personally. They encourage users to progress for the next tier within the community, serving as a strong source of motivation alongside of course the other elements like badges and achievements. On top of that, tier-based badges could also be added, such as Bronze, Silver, Gold, and Platinum badges when a user reaches one of these tiers, to further reinforce progression and recognition.

ODC is still undergoing many changes and raises doubts in some questions in the certification exam - as some changes happen in a period close to the test we have scheduled (has the answer to the test already been corrected) For example, roles, initially the roles could not be shared, but later they could. I suggest having an email or a form of communication - it could be in the course material itself indicating that the certification questions already refer to updates to the material, or something like that, to ensure that there are no doubts about what we should answer. Or of course, and perhaps easier to manage, a certification is only released after the OutSystems version and the documentation is stable.

The constant concern with accessibility has forced us to be extra careful with the HTML semantics with which we build our pages. Depending on the context in which we are building an application, it's always a good practice to carefully structure our information hierarchy.So, even if there are situations where we don't want a DIV to be rendered in our DOM, we want that DIV to exist in design time to help us organize the elements, and consequently keep the code in a more effective and cohesive way.The idea would be the existence of a "ghost DIV" that is only used to organize the elements in Service Studio (in design time), completely ignoring it in the rendering of the page.

To improve Forge quality, which in my opinion is decreasing day by day, OutSystems should moderate all the new components submissions.Instead of being instantly available after submission, they should wait for someone from OutSystems to check them and approve.This would avoid the submission of tests, spam, exploits, redundant components, etc.

The logs generated by the platform (screens, errors, integrations...) help us a lot when we are investigating an error. But I think it would be better if the platform allowed us to turn off these logs. We have recurring problems with the log database due to the large number of logs generated by accessing screens and integrations. Most of the time we do not need these logs but we cannot prevent them from being saved. We know that the logs are saved asynchronously, so there is no impact on the application (we use a separate database for logs), but we would like to have autonomy to turn on/off the generation of logs.

A weekly/monthly competition can be done for the community members to upgrade there community ranking. Where all community members can participate and showcase there skills. It should have some time limit. MCQ questions in first level and then in second level best practice question which can help people in there certifications too. Just a thought !!

Please can you provide an option to use the uploaded Demo as a Try Now option, hosted on the forge server. Currently, if you don't have a corporate account/server you are willing to make publicly available, you have to use you personal account for the Try Now , but that expires and gets deleted every week or so, causing the Try Now to die.

The help page you are given a link to when publishing from ODC to the Forge is completely blank. Can someone add some details please?

When we develop actions and specially change them later we sometimes remove code in the flow.When a variable is not used anymore after changing / deleting some code in the flow service center warns you about this (yellow line under the variable and a message in the warning panel).When an aggregate is not used anymore service center does not warn you about this.I would like service center to warn me so I can check if the aggregate can be deleted or not.In the example below the GetUsers aggregate is not used.

 When we publish a component, we earn points on our profile, when we answer a question on the forum, we earn points on our profile, when we watch training, we earn points on our profile. But, when we send a security report through the OutSystems page, we do not earn points on our profile. Just like answering a question on the forum, or publishing a component, people who analyze and send security reports to OutSystems are also contributing to a safer product. Analyzing, detailing, writing and sending a security report to OutSystems, in my opinion, should be scored, as the professional has an account in the community and is helping to keep the product or website safer .