When you configure Log Redaction to "Yes" it is only redacted if the header is sent on the exact same case as seen on Service Studio. It should have been case insensitive as RFC 7230 Section 3.2 states: Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace. This behavior happens with or without Name in Request set.

When using the SingleSignOnMobile plugin in my mobile app, I noticed it was taking some time to process my requests. On further inspection, I noticed that multiple server calls are made before redirecting to the SSO page. By looking at the code, I can easily tell that GetToken and GetRequestDomain are unnecessary server side calls. GetToken is used to do a string split. This can be done client side in javascript. ~400ms of processing would be saved. GetRequestDomain is used to get the current host. This is also achievable in javascript (look at window.location). Another ~200ms would be saved. In short, currently OutSystems apps that make use of this plugin take an extra half a second (or more) to process because the plugin code has some serious performance problems. This looks very easy to fix, just by replacing server calls with javascript. Can a new version of this plugin be released that tackles these issues?

 gRPC is a modern open source high performance RPC framework that can run in any environment. It can efficiently connect services in and across data centers with pluggable support for load balancing, tracing, health checking and authentication. It is also applicable in last mile of distributed computing to connect devices, mobile applications and browsers to backend services. https://grpc.io/

Hi,The use of domains is essential when doing factory governance, but this concept is stuck only in discovery. This concept is also essential in Architecture Dashboard, Service Center and Lifetime analytics.- ArchitectureThis is where it's more important because domains are the top of our architecture and we need to have this vision. It will facilitate domain technical debt control and facilitate reports.- LoggingIn service center and in Lifetime Analytics it would be great if we can filter all data by domain also, because this is our top level on our architecture and we need to have this top vision (errors, page accesses, general logs).In Lifetime analytics it will be great also if we can see the performance by domain an then we can start drill down, but this top level architecture vision is important.

Hi,It would be great if when create and index of a table we can chose the order of tenant_id column.Depends of the volumen of the data, the information (columns) and the filters you need, the order of the column inside the index it´ s high important. Sometimes, the better approach it´´  s put tenant_id in first place and we don´ t have this option (or we don´ t found).If we can select the order, performance is greatly improvedRegards.

Hi,If we are creating an index in a table with a lot of values (millons of records) and the table have a lot of usage (it´ s a core table and have a lot of actions reading and writting), the deployment fails creating a index with timeout error, and all the deployment it´ s aborted on stage 2.Also during the creation of the index the table have blocks and the users can´  t work.If the index include "online" attribute in the creation, all this problems desapear.Regards

 The Problem: The current badges page feels "heavy" because it treats every year, every event, and every status as a separate icon. This creates visual noise rather than meaningful recognition. Suggestions: First Milestones – Rename Getting Started section Member Onboarding – Merge Welcome and Autobiographer First Post First Idea First Asset Agentic AI Ready Online Community Answer Marked as Solution Idea Implemented Referral Program – Move to Community Growth Developer Survey OS Research Program Participant OS Research Program Pioneer OS Research Program Contributor OS Research Program Rock Star Knowledge Become an AI Developer OutSystems Developer School Publication – Move to Community Growth Top Technical Content Contributor Online Review – Move to Community Growth Certification Attained Project Finished Interoperability O11 and ODC Development First Asset – Move to First Milestones OS Component Contributor – Break them into multiple badges: Forge Contributor ODC Components Contributor AI Agents Contributor GitHub Pull Contributor 2021 Neo’s Odyssey – Move to Gamifications Interoperability O11 and ODC - Move to Knowldege Agentic AI ready – Move to First Milestones OutSystems Hackathon – Move to Gamifications OS Research Program Participant - Move to Online Community OS Research Program Pioneer - Move to Online Community OS Research Program Contributor - Move to Online Community OS Research Program Rock Star - Move to Online Community 2025 Agents vs Zombies contest – Move to Gamifications Events Speaker – Renamed to Global Speaker and introduce USG Speaker Webinar Led – Move to Community Growth User Group Organizer – Move to Community Growth Event Organizer – Move to Community Growth Award Attended ODC 2018 – Can be deprecated Spoke at ODC 2018 - Can be deprecated, Merged with Global Speaker Spoke at OSDC 2021 - Can be deprecated, Merged with Global Speaker Attended OSDC 2021 - Can be deprecated Challenges/ Gamifications 2021 Neo’s Odyssey OutSystems Hackathon 2025 Agents vs Zombies contest Groundhog Day Challenge Community Growth Referral Program Publication Online Review Webinar Led User Group Organizer Event Organizer Mentor – Introduce this Superusers MVP Champion MVP Alumni Champion Alumni Remove badges counts. Eg, in Superusers the member can have either of the badge - having 1/4 badges is irrelevant.

The server seems to be storing all date/time in UTC format. However while reading the errors/logs and other details in Service Center, the UTC format makes it difficult to comprehend (if the user is in different timezone than UTC). May be we can convert to user's local timezone and display the date (how it happens in react client side).

Currently "da - Danish" is missing from the OutSystems UI library. As mentioned in this thread https://www.outsystems.com/forums/discussion/57768/outsystems-ui-allows-for-translations-on-outsystems-ui-widgets/ we can not add this ourselves, so we hope this can be resolved by the OutSystems team.

Make it possible to consume Service actions from within a library. Within a library I can consume a REST API, but can not consume a service action. A REST API gives additional overhead in respect to a service action call, like additional authentication and autorisation. In a service action this is all safely handled by OutSystems.