Hi all,In our Infrasctrure we have more than one Development Environment, but we can only use Architecture Dashboard for one Development Environment.From Documentation :"Currently, you cannot have more than 1 Code Analysis environment (usually development environment) per installation, i.e, with the same activation code."I know that is only impacts in big software factories with different development pipelines, but is a nice tool for all developers.

Now if we don't want to show the content of a web block in their consumers we need to add an if statement there to show an image or whatever we want to show in the consumers. Like in the image below:It would be good to have an attribute in the block to set an exhibition icon, and this would avoid us to write code only to show an image that also pollutes the content of the web block.

Some application are built specifically for development purposes (SQL Sandbox, impersonate pages etc..) and It would be useful to have a setting which could designate an application as Not For Production to avoid having them deployed into a production environment.This could be a configured on the application level.

It would be great if outsystems can support storage of JSON datatype in the attributes of an entity, since now, MSSQL, Oracle and MySQL all support this already.

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

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.

We have reasonably big (medium-big) sized OutSystems projects. We have number of objects (screens, blocks, server actions, entities, etc) in these projects. These projects go through multiple phases of constant development. There are multiple developers work on these projects, and many of the developers are hired when needed. These new developers start with very minimal knowledge about the application. These developers usually work on shared components. So, it would be easier, if there is an EXPORT option that helps us export the specific screen/server action/block that they work on. Before they start the development, they can export the component/object. This EXPORT-ed file/source can be used as a backup. So if we need to restore we can easily restore.

 /chat/completions should be editable so we can use https://api.openai.com/v1/responses

The Demos in Forge projects take up a TON of SUs/AOs. But if you delete the demos after installing, the next time you upgrade the component you get the demo code again.Solution: have the component author upload a demo (OAP, OML, or OSP) separately from the component itself (OAP, OML, OSP, or XIF). Then allow the Forge user a choice of "Download Component Only" or "Download Component + Demo".To make this better, add a "Project" that is similar to an OSP, but can contain Applications as well. That way, the Demo can be a separate Application from the Component, and they can be delivered together in one download. A level above "Application" has been requested a few times already.J.Ja

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.