Hi OS team, can we also have a IntelliSense looks alike whenever we use alias in advance SQL can be helpful when too many join/sub queries sample auto popuplate from the user table currenly this is the behaviour whenever i use alias on my tables -no suggestion

Currently, the OutSystems UI stylesheet applies a box-shadow effect through :focus when accessibility features are enabled. As a result, the focus indicator is shown both for keyboard navigation and mouse interaction. It would be preferable to use :focus-visible instead, so the focus indicator is only displayed when it is relevant, namely when users are navigating with the keyboard or using assistive technologies. This would provide a more appropriate default behaviour, improving the experience for mouse users while preserving a clear and accessible focus state for keyboard navigation.

Since "Wake Timer" can be called via code, it would be good to be able to pass paramters to it. J.Ja

In each training video on the OutSystems learning platform, include a “Schedule Call with Mentor” button (as shown in the attached image). When clicked, it can redirect learners to the ADP mentor list, allowing them to easily schedule a mentorship session. For freshers, this feature would be extremely helpful to learn faster, clarify doubts instantly, and gain confidence in their learning journey. Currently, many newcomers know about the forum, but not about the mentorship program. By placing this button directly within the training page, it encourages them to explore and connect with mentors proactively.

Quite often, I am repeating the same set of joins in queries (both normal and advanced), that I would ordinarily put in a view. Think e.g. of a CRM system that regularly needs "all active clients" or an ordering system that needs "all open orders". Of course if you need just that, it's easy to put it in an action, but I often find myself needing the result and join that with some other tables. Unfortunately, for some reason OS does not allow to define database views, which imho is a great gap. Therefore, I'd really like to see support for database views or something similar (e.g. queries you can define on eSpace level and join the result of with another query, but that amounts to the same).

OutSystems is actively supporting integration of ODC and O11. Currently, the only way to consume logic from each other is to use a REST API. This is cumbersome and portentially unsafe. It would be much easier if the Platform allowed consuming Service Actions instead (which in essence are also REST methods, but easier to use). So O11 logic could consume an ODC Service Action, and ODC logic could consume an O11 Service Action. This would greatly enhance easy operability, and be secure out of the box.

Most of the times I need to open Service Studio just to check code and I do not need to get the references. It would save a lot of time when we just want to check the code and not change anything

When building RAG pipelines in ODC against structured documents, the four native chunking methods treat all input as plain text. This works well for simple text stored in entity attributes but creates problems for documents that have structure: fenced code blocks, Markdown tables, and nested headings. A Markdown-aware chunking option would let developers preserve that structure during ingestion without needing a custom External Logic workaround. Three behaviours would cover most cases: heading path tracking so chunks carry their section context, code block atomicity so fenced blocks are never split across chunks, and table preservation so tables stay whole. The upstream Forge ecosystem already produces Markdown output via components like OmniDoc2MD . A native Markdown chunking method would complete that pipeline naturally. This is not a replacement for the existing methods. It is an additional option for teams whose documents have structure worth preserving.

A few months after go live, production users start complaining that they randomly lose their session in a mobile app.The conclusion from your testers is that users are logging out of a reactive web application in their desktop browsers, and 5 minutes later they lose the mobile session."IMPOSSIBLE!" - you say - "Logging out from the browser cannot possibly terminate the mobile session 5 minutes later, that's absurd and unheard of"So you try to investigate it yourself and, sure enough, the tester was right. Logging out from the desktop browser indeed terminates not only the mobile session, but every other session of the user. Oh, you also find out that this is documented and deliberate: "When the end user logs out of an application, all sessions are terminated".You investigate further, and begin to realize that it's impossible to preserve the mobile session after the user has logged out from a browser . It's also impossible for the user to use multiple browsers on different devices , or even multiple browsers on the same device, because any logout action would terminate all sessions in all browsers. This is unexpected behavior that contradicts how the web works.You reconvene with your testers to brainstorm workarounds, but you're not taken seriously: "Surely this very expensive platform and market leader can support an application running on two browsers simultaneously!" All you can do is wish it did...If this scenario has happened to you on any project, please like this idea and share with others. Together we can change how the Logout works, and enable this very basic feature which is having two independent sessions on distinct devices.

Hi,In Reactive Web Apps I've noticed that when navigating to public screens from other modules the transition is very slow - it shows a blank screen first, then it starts loading the screen and the CSS, causing a Flash of unstyled content.This takes about 2 to 4 seconds, making it a horrible experience.Upon further investigation, I've discovered that OutSystems is treating the navigation as a navigation to a totally different application, loading again all the necessary resources (JS, HTML, CSS). This is very atypical for a Single Page Application.This makes segregating front ends a major trade-off.Can this be improved?Thanks,Tiago