On ODC Studio when you create a new agent, there is a configuration named Call Condition. By its description and behavior it should be called Stop Condition to avoid confusion: It is already there when you open the question mark icon:

To support the secure storage of runtime external access credentials or tokens, it would be useful to have the ability to set Site Properties as Encrypted . CA

The same way we can filter members from staff and Champions/MVPs, it would be great if we were able to find those who are willing to be mentors. Now that there are almost 100 people with that "job", it is hard to keep up. Specially because the OutSystems filter on ADPList is not great. And since you are at it, please add a filter for those who have been speakers. This is helpful for User Group organizers looking for speakers, and the both combined would help potential speakers to find guidance and overcome their fears. In short: every time you add a tag to the profiles, add a filter to it.

This aim of this idea is to propose a proactive, dual-layered security framework for O11 & ODC to ensure PII (Personally Identifiable Information) requirements on data model. The Manual "Is Sensitive" Flag Introduce a high-visibility Data Governance section in the Attribute Properties pane. Developers can manually toggle an "Is Sensitive" flag for attributes. Result: Data is automatically encrypted at rest using AES-256 and masked in all ODC Portal logs. The AI-Powered "PII Sentry" An integrated AI agent monitors the data model in real-time to catch human error. Pattern Recognition: When an entity is created or data is imported via Excel/CSV, the AI scans for sensitive patterns (National IDs, Credit Cards, etc.). Automated Action: The AI interrupts the workflow to suggest: "This field appears to contain PII. Should I enable the 'Is Sensitive' flag for you?"

Well, the title says it all.I mean, having it organized in folders like in the Logic tab would be great.

This is a project aimed for Portugal, in a first phase, but which can be extended to other countries.It is just an idea and I count on the support of this forum to make it grow and solve the challenges! VisionEnable and manage the delivery of food and basic goods, in the form of a basket, to people who are more prone to be infected with coronavirus, already has coronavirus or is in quarantine. PersonasHypermarketsVolunteer to indicate beneficiaries and transport basket delivery Use casesRegistration of Hypermarkets- Responsible for creating the basketsRegistration of Volunteers- Responsible for collection and delivery to the beneficiaries respective addressesRegistration of beneficiaries- Registration will be done by the volunteer who indicates a family that meets the conditions to be a beneficiary Challenges- How to check if the family should be considered to benefit?- Definition of the basket. Should we have multiple types with different prices?- Online payments (only).- How to deliver safely? User Stories (draft)US1 - Registration of Volunteers- With facebook or google and with indication of the area of residence to define a range of action- Indication of the hours available to make deliveriesUS2 - Registration of Hypermarkets- As OutSystems has a close relationship with Continente hypermarkets, it would be easier to articulate with them in a first phaseUS3 - Registration of Beneficiaries- This registration must be done by the Volunteers through their account.- Indication of name, address, number of people in the householdUS4 - Task assignment to the Volunteer- At the end of each day, generate a route for the volunteer, which should be done the next day.US5 - Task completion- The beneficiary must indicate that he received the basket.I hope that this helps to understand the idea and that it can grow with the support of everyone.Thanks!

Support datatype of jsonb, feature of Similarity Search, pgvector as vector database for LLM embedding storage.

With AI being our right hand and helping us with a lot of the product management/vision, it could be possible to create a standard widget structure in the widget tree from a HTML. Use Case: 1 - Use favourite LLM 2 - Generate mockup (using OSUI as theme for the generation - better results) 3 - Copy HTML 4 - Right click screen in ODC/O11 5 - "Build Widget Tree from HTML" 6 - The screen is populated with a bunch of widgets that respect the html

The currently used Icon Library - Font Awesome - is an outdated version, no longer supported or mantained. Updating it to the the current library would allow for an easier frontend development process as developers wouldn't need to use any aditional libraries, plugins or forge components.

Currently, the only way to share Outsystems code with LLMs or to show to a person on the forums, etc, is with a Screenshots, but a Screenshot cannot display everything at once: for example Input/Output parameters for several Actions in an Action flow in a single Screenshot. A single one side Service Studio -> Text Editor would open new doors, if you can Copy/Paste Service Studio elements in a text form to paste into LLMs or other text editors for AI code generations , context, creation of documentation, etc. It doesn't have to be perfect, it can be an imperfect, incomplete and invalid machine generated code (JSON, XML or any other text form, that is easier for the Service Studio team to implement), LLMs nowadays can quickly reformat it in a better form according to use case and extract whatever needed. It can help by virtually all of a module/application elements inside Service Studio, but among the most beneficial would be StaticEntities and Entities + attributes, Structures + attributes, Action in a flow (names + input/output parameters), etc.) in a text form. It is not the same as, but it would implicitly provide some solution for the problem from this idea: https://www.outsystems.com/ideas/11114/copy-multiple-property-names/