In Service Center, it could be useful to have the Module Type in the module detail page.Also in the modules list screen, it could be useful to have a filter option on Module Type.

basically we would like to create an app to add to your ‘network’ the persons who crossed in the street. You would only see their nicknames and send messages if the persons allow you to.we would then have a network of persons whom have been near you. If you have covid you can mark your self as infected and all the persons near you in the last 10 days will be notified to be in quarantine, avoiding to contagious another persons.the set as infected person could be in a system as two factor authentication, sending the approval to a specified email or number.this is a first approach, we can discuss further details.this app will likely be much more of a use when we are at the stabilized phase of the corona virus spread.Using the location add on from forge.We have started by using the mobile development and I encountered some issues when setting up my developer account for Apple.kind regards,

Hi Team, OutSystems currently handles data types such as Identifier, Text, Date, Binary, and Lists effectively. However, I’d like to propose an enhancement to improve how we manage structures. Current Challenges: Checking Structure Emptiness: We currently need to verify each attribute of a structure individually to determine if it’s empty. Setting Fields to Null: Manually setting each attribute to null to represent an empty structure can be cumbersome, especially when dealing with complex structures. Proposed Enhancements: IsEmpty Property for Structures: Similar to the IsEmpty property for lists, structures could have an IsEmpty property to easily check if all attributes are uninitialized or contain null values. Set Structure to Empty/Null: Instead of manually assigning null to every attribute, there should be a built-in feature that allows the entire structure to be set to an empty state in one step—similar to how NullIdentifier works for identifiers. These enhancements would streamline structure handling and improve development efficiency, particularly when dealing with large or complex data structures. Looking forward to your thoughts!

Hi guys, I've got a small idea that I'm hoping would help both Companies looking for experienced certified Outsystems developers and unemployed Outsystems Developers looking for new challenges and opportunities. Case Study My name is Munyaradzi Kandoro and I am a certified Outsystems Developer and Architecture specialist with over 4 years of experience and currently open to work. At the moment, companies looking for experienced developers on the market would not be able to find people like me. If they are looking for people like me, they will have to rely on the services of LinkedIn where they will need to filter through unwanted information in order to find the right talent. I believe it would be a good idea to bridge the gap between these 2 parties by providing Companies/Partners with a Dashboard/list to view and be able to reach Outsystems to Certified Outsystems Developers. Please let me know what you think. Thanks

When consuming REST integrations, OutSystems generates the appropriate structures to match the json object, which is great. When a partialy compatible structure already exists, Service Studio will try adapt it to the new fields , and that often causes a problem. Imagine that I have an existing `Student` structure: { "name": "Alice Smith", "age": 20 } And the new integration I'm creating has a `Employee` structure: { "name": "John Smith", "age": 42, "salary": 9999 } By reusing the `Student` structure, Service Studio will create a `Salary` field on it, which makes no sense

 When I'm putting the output of an advanced query in a custom structure, I often find myself having to browse to the structure on the Data tab to see its fields. It would be nice to be able to do that in the AQ window directly, like this:

Hello,I think it would be nice if the "automagically" created index on primary keys shows up on the Entity indexes tab. As of now, it doesn't show up:The behavior could be the same as Foreign Key indexes.Cheers!

It would be helpful that their descriptions are in the list page of site properties like below.

 The ProblemI mostly create Structures for integration purposes, for both incoming and outgoing purposes. This structure is something that will be produces or consumed by an external party (mostly some other internal department). Before we start to actually develop the Integration logic we normally first want to agree about the data structure and our default documentation/negotiation format is JSON.Currently it's "hard" to get a JSON object from a structure defined in OutSystems. I either need to create a Server Action with a "JSON Serialize" action to convert the Structure to JSON and debug this action to grab the JSON or I need to add the structure as an input object to a REST action and open the Swagger documentation to copy the JSON from there. This main issue with this is, is that it's time consuming and initiate publishes which might not be needed/wanted at that time. The SolutionLet me export the structure to JSON via the context menu of the Structure. This is a similar action as "Add Structure from JSON" but the other way around. The result should be similar with the Swagger JSON.With this addition I could create a Structure, export it and share it without all the hassle of creating Server Actions or REST action.Check the screenshot below on the context menu in question. The "Export to JSON" should be somewhere in here.

For example when we open a aggregate get the executed sql. So we can speed up to investigate some queries.