When creating a custom API log entity, it would be helpful to save a reference to the Service Center integration logs using the request key. We can use the Request_GetKey action to add the key to our custom entity. This key is visible on the Integration Details page or can be used to join the Log_Integration entity. Additionally, I propose the following improvements: 1. Add a “Request Key” column to the table on the Monitoring > Integrations screen in Service Center. 2. Include a filter field to search by “Request Key” directly in this screen. These changes would make it easier to find specific logs and enhance debugging and monitoring

 To optimize AO usage, multiple Static Entities can be merged into a single Static Entity with an additional "Type" attribute to differentiate records. For example, instead of creating separate Static Entities for Country, Currency, and Language, a single MasterData entity can be used with a Type column to categorize records. This approach significantly reduces AO consumption while maintaining flexibility. By filtering data based on the Type attribute, developers can retrieve only the required records, improving performance and maintainability. This method is particularly useful for applications with multiple Static Entities, ensuring better scalability while keeping AO usage low. Would love to hear feedback on this approach!

In advanced queries, It would be useful to see all the attributes of the output structure or entity.I should be able click my output structures and see all the attributes of that structure or entityFurthermore, if the query output is an entity, clicking on a specific attribute should select that attribute in the query.

There can be possibilities with showing data in a gallery widget and dynamically add columns and rows by adding lists and records in use, by putting a logic of dynamically adding buttons in Ui.

Make an upgrade path that can upgrade app from O11 to ODC. Make a clear checklist and check it against the application. The process must be secure and achieve with a minimum click.

Hi Team,Please gives us option to delete test data from entity directly from entity.Thanks1

 To use input mask in the platform it's necessary use third party components that are not supported by outsystems, and all forge's components that set input masks don't work in Android 4.0 or superior. Then, my idea is the platform natively offer support to input mask. Thanks

Due the desired movement of Outsystems into the Enterprise IT world, from my experience, sooner or later, it will be needed a way to easily connect to MQ based ESB's or EAI. It should be a native feature of the Agile platform to have a way to subscribe to a message queue (MSMQ or JMS) and fire an Action or a BPT process whenever a message with certain characteristics arrives to that queue. It should be analyzed the fact that an ESB or EAI processes thousands of messages per second, so I believe that a tie to the RDBMS might not be a good technical solution. It should also be possible to write to queues (the idiom should be the same as Webservices). At least the standard: Point-to-Point, Publish/Subscribe and Broadcast message transmission/reception models should be supported.

Hi,It is always a great idea to test API's in postman before implementing them. At the moment we cannot import a postman collection and need to define everything again. It would be nice if we could import  a Postman collection to get all the api's in the system without needing to define them again. It could work like uploading or referencing a swagger specification.

When we try to run an Advanced Query, in the test button, to see if the query is having the expected behavior, it happens that sometimes we have errors and the error message is never clear (eg: after ')').From what I suggest in continuation to my previous idea, of putting the numbering of the lines in the Adcanced Query, also indicate in this error message the line where we are failing. What do you think of this idea? It could help a lot.Nuno Miguel Verdasca