There are plenty of scenarios in which the base built-in actions are not enough. For example, if creation of a specific entity record demands that other entity records be also created, or if certain restrictions apply that cannot be modeled with static "default values". Or simply because you want to audit operations over sensitive entities. Currently the way to do this with the Agile Platform is clumsy: isolate entities in their own eSpace, make them available read-only, and create sets of actions to do the required tasks. This works, but: It is ugly - when actually using those actions, you will not see them associated with entities; you need to remember that they need to be imported, look for them under "referenced actions", remember from which eSpace they come from - or go look in the entity list; It can lead to errors - if a new developer in a project using the pattern, for some reason, is not properly informed, he might simply go into the eSpace and switch the read-only property off, anticipating that it being that way was an error.

It is great that the OutSystems demo Homebanking apps are multilingual and also available in German. Nevertheless it is obvious the translation was not done by a German native speaker. In this way it is - to be honest - a little bit funny, instead of being a serious business app. E. g. the credit card VISA was translated as Visum in German language, which only means a visa for a country, not the credit card. And a lot of other stuff. English name -> curent translation - suggested translation Visa -> Visum -> Visa (I think it the same for the Portuguese word here: Visto) Home -> Heim -> Startseite Balance -> Gleichgewicht -> Kontostand Amount -> Menge -> Betrag Continue -> Weitermachen -> Weiter Loans -> Loans -> Kredite View -> Sicht -> Überblick Share Receipt -> Aktienquittung -> Quittung It would be great if these Homebanking apps (maybe others also) could be checked by a native German speaking OutSystems employee of the DACH-region.

Add native Passkey authentication support to OutSystems, enabling secure, passwordless login using platform-level passkeys (FIDO2/WebAuthn). Passkeys are becoming an industry standard (and for good reason) as they have multiple advantages over traditional authentication methods. From Fido Alliance: This could technically be implemented via a Forge component, but given the complexity and security criticality it would be much better if the platform handled it.

In OutSystems, each Email Web Screen is counted as an Application Object (AO), and AOs directly impact licensing cost. In many enterprise applications, we create multiple Email-related Web Screens (for templates, preview, configuration, triggers, admin panels, etc.), which can significantly increase the AO count. My idea is to replace most Email Web Screens with an Extension-based approach. Instead of building multiple Web Screens for email management, we can: Handle email generation, templates, and logic inside an Extension Store email templates and configurations in the database Trigger emails via server actions or APIs without requiring dedicated UI screens How this helps customers: ✅ Reduces AO consumption by eliminating multiple Email Web Screens ✅ Lowers licensing cost for large-scale applications ✅ Centralized email logic in one reusable Extension ✅ Better performance and maintainability for complex email workflows ✅ Reusable across multiple modules and applications Example Use Cases: Transactional emails (OTP, notifications, approvals) Bulk marketing or system alerts Multi-tenant email templates per client Configurable email rules without UI-heavy admin screens This approach can help enterprises optimize licensing cost while still keeping email functionality flexible and scalable.

I would like to suggest that applications relying on deprecated elements (marked as DEPRECATED_) be considered as technical debt in the AI Mentor platform. By considering applications that depend on deprecated elements as technical debt, we can prioritize their resolution and allocate resources to address them accordingly. This approach will help us ensure that the AI Mentor platform remains up-to-date, efficient, and aligned with industry best practices. Thank you for considering this suggestion. I believe that by actively managing technical debt related to deprecated elements, we can enhance the overall quality and maintainability.

Currently, the Serialize node only provide an option to exclude attributes that have default values. However, there is no option to explicitly exclude custom-selected attributes. This capability is especially useful for logging scenarios . In many cases, creating an additional Structure just to map and exclude specific attributes is redundant and unnecessary. Most serialized outputs are eventually passed to a JavaScript node , written to logs, or stored in a database purely for logging purposes. Allowing developers to select which attributes should be excluded during serialization would significantly reduce development time, keep the code cleaner, and improve maintainability. It would also eliminate the need for extra mapping structures that add complexity without real value.

💡 A new input parameter, (defaulted to false obviously,) to REST calls called " ContinueOnError ", which causes the rest method to return successfully, but with 3 additional fields (or even a structure) returned with " Success ", " HTTPResponseCode " and " TextContent " fields. 📉 Some REST APIs return " failure " HTTP Response Codes for valid responses, such as " 404 Not Found " if the record doesn't exist. (Lets ignore the debate about using 404 for record not found *AND* page not found.) 🕞 In the context, this may not be an a error, but it's going to end up in the generic error handler where you are going to be parsing the text of the error message to try to see what actually went wrong, and possibly displaying a load of technical junk to the user. 📜 Even within a single error code, there could me a range of causes, with the details being in the response as JSON. 🔍 Now obviously , I know you can do all this with code in OnAfterResponse , but you can't set that on a API method level, only on the connection , so you're going to have some pretty ugly code in OnAfterRespose to work out which API of ten calls you made and whether it's really an error. 🎯 I suggest it would be far better to have an option to allow the API call to continue to the next step in the procedure, then check the response to see if it succeeded, and work out if we need to raise an error, retry, or just continue, based on the response. Edit to add: This doesn't seem like it should be particularly hard to implement. Edit to also add: Added icons because everyone else uses them

Currently when we are trying to create a new idea for ODC, we get this warning: While I understand why this exists, it removes a key value of the community: visibility, discussion, and voting. If the problem is to ensure that the suggestion goes directly to the ODC team, wouldn't it be better to just notify said team when a new idea is created with the ODC category?

When we create a new solution with some Modules use missing or inconsistence dependencies or some Modules have outdated dependencies or some Modules are Offline or Modules have outdated dependencies that may be incompatible" in... Service Center > Factory >Solutions > New Solution It would be good if we could filter by type of inconsistence. This is happening on version 11.22.0. Best Regards, Paulo Russo . www.paulorusso.pt

Our profile page has an Achievements section. While it is OK for regular users, some community members are too active in the forum for that to be searchable. That page becomes useless after a hundred entries. Can we have a filter like in Activity tab?