There is a great subdomain "charts.outsystems.com" that explains how the charts can be customized. However, I think it is missing some crucial information. For example, there is the following page that explains different chart types and how to implement them: https://charts.outsystems.com/samples/chart-with-multiple-chart-types There is a warning there implying that it is not possible to do a "step line chart" with the config options of the chart block (see attachment): "Currently, it's possible to convert any series to the following types: Line, LineSpline, Area, AreaSpline, Column, Bar and Pie." In reality, it is actually possible to do this with addon extensibility configurations; i.e. with a certain client action ( SetHighchartsSeriesConfigs ) from the Charts library, as partly explained in this video: https://www.youtube.com/watch?v=uzNnX7oqhNY It would be great if such information is also added to the https://charts.outsystems.com/ subdomain.

Advance queries should have a property where we could say that it does not have an output. This should remove the need to assign an output structure in a delete or update statement.

Hi team,It would be good if we could have any certification for Testers in Outsystems as we already have a course for tester: https://www.outsystems.com/training/paths/10/becoming-a-tester-in-outsystems/This will give the sense of confidence to client as they have capable and aligned team with respect to low code.Thanks,Preeti Kumari

 Ultimate Goal :To provide free and universally the necessary psychological support in this scenario of pandemic and isolation, understanding each individual in the balance of her/his mental functions, by professionals or university students in the field of psychology. Context :Due to Covid-19 these are times of prophylactic isolation and quarantine at home for many of the Portuguese people. This social distance, the lack of contact with family, friends and the community, led to a change in everyone's routines and daily lives. These social and behavioral changes can also have an impact on everyone's mental health. To help maintain everyone's wellbeing, psychological counseling needs to be much more present than it has been up to now.In fact, there are a number of ongoing initiatives, which have been born out of group movements on social networks, which aim to fill this need and still support those who need it most, as examples are: https://www.instagram.com/adistanciadeumclique/ https://www.facebook.com/groups/2524269891155335/However, there is the fear associated with these groups due to lack of certainty in the veracity of the information conveyed, as well as the uncertainty of the professional skills of those who provide these services or informations.On the other hand, official communication channels for this purpose have already been created (or are being created), however mostly by telephone, so the interaction ways are more reduced and impersonal; examples: https://www.rtp.pt/noticias/pais/linha-sns-24-vai-ter-servico-de-apoio-psicologico_a1212418In other cases, access to these resources is restricted to a community only, and access to this cannot be democratized; examples: https://www.p5.pt/covid-19/psicologico/ https://www.psicologia.ulisboa.pt/linha-apoio-psicologico/This idea is being shared between me and Professor Jácome Cunha of the University of Minho, in order to bring the help of qualified people to the whole community. Professor Jácome is already in contact with the Psychology Association of the University of Minho as well as the “Ordem dos Psicólogos”.It should also be noted that Professor Jácome has already led a curricular unit in which the OutSystems platform was used for the development of projects in partnership with OutSystems, thus being aware how much this technology could accelerate the development and arrival of this aid to the community. Proposal :Development of a mobile application in which professionals or university students in the field of psychology can provide psychological support to those who need it. In this application people get centralized overview of the professionals that are willing to freely help them.The application must allow:each professional must be able to:register in the applicationenumerate schedules and availability to provide helptake and send help notes to the person being helpedeach person needing help:schedule a contact with a qualified personmake a video call with the qualified person Risks :There is a risk of a shortage of specialized know-how available on the platform, so the mitigation of this risk is already being put into practice by the contacts of Professor Jácome Cunha with Ordem do Psicólogos and Psychology Association of the University of Minho.

Several 3rd party web services we need to consume use WS-Security , which forces us to create extensions for them, instead of using the platform's native web service references. It would be nice if WS-Security, being a well-defined standard, works out of the box with the platform.

Enhance the OutSystems Entity Actions Wrappers Accelerator to: Centralize validation logic: Automatically create a dedicated wrapper for validation rules specific to an entity. Consolidate Create and Update: Generate a single, unified server action that handles both entity creation and updates, utilizing the centralized validation wrapper for consistent and maintainable logic." This approach would: Reduce code duplication: By separating and centralizing validation logic, developers avoid maintaining identical or similar rules in both Create and Update actions. Improve maintainability: Changes to validation rules can be implemented in a single location, ensuring consistency and reducing the risk of errors. Simplify development: Streamline the development process by requiring fewer actions and reducing the need to manage duplicate logic. This enhancement would significantly improve the efficiency and maintainability of applications built with the OutSystems platform.

 I would like to see a "Clone Database" button in LifeTime, which copies the Production database backwards into the QA and Dev environments. Each time a problem occurs on our production environment that can't be recreated on the dev environment for lack of similar data I get more and more frustrated with this platform. When developing on a dynamic web platform you often need real world, live data to test a behavior, even more so when troubleshooting an unusual behavior that has been reported by a user. This necessitates being able to quickly and easily clone the production database into the development environment. Unfortunately, OutSystems has an incredibly complex key and token system which turns a simple database clone into such a Herculean task it requires a 20 page technote! https://www.outsystems.com/home/document-download/1484/8/0/0 This is completely unacceptable. I would like to see a "Clone Database" button in LifeTime, which copies the Production database backwards into the QA and Dev environments. This would make diagnosing complex and nuanced issues that happen in the Production environment much easier and greatly improve the RAD timeframe and lifestyle. Sincerely, Braxton Bragg

It would be beneficial to have a centralized page in the Service Center or within the OutSystems platform that provides a comprehensive listing of all Site Properties across environments. This listing should include the following details: Application Name Module Name Site Property Name Default Value Created On Created By Additionally, there should be an option to mask the Site Property value for sensitive data. If the "mask" option is enabled for a Site Property, its value should be hidden in the listing. Otherwise, the value should be visible along with its default value.

Hi OutSystems Team, It would be incredibly valuable to introduce a feature in Service Studio that allows developers to select and manage specific versions of producers when configuring dependencies. This enhancement would align with the familiar workflow of Visual Studio’s package manager, empowering teams with precise control over which producer versions their applications depend on. Key Benefits: Stability & Reliability: Locking dependencies to verified versions minimizes the risk of unexpected changes or regressions. Simplified Rollback: Facilitates quick reversion to previous versions if newer updates introduce issues. Improved Developer Experience: Mirrors established practices in other development environments, making dependency management more intuitive. Collaboration Support: Promotes consistency across teams by ensuring uniform dependency versions, reducing integration conflicts. Please find below a mockup illustrating the proposed implementation.

When retrieving findings from AI Mentor Studio via the API, it should be possible to obtain the findings that were snoozed, as well as the user and the date when they were modified.