Very basic and simple ideia, just what the title says: Reminders could have a different color than regular comments (orange?)Some complex logic often gets several comments on it and this would help to rapidly identify the reminders/todo/WIP from the "documentation"

Hi OutSystems Team, In the OutSystems Support channel , implement a time tracking rule based on SLAs , as some clients use this metric and end up counting elapsed time, which is incorrect. When the issue remains on the client's side, the SLA should not count, or if the client "disappears" and does not close the ticket, this time should also not be counted. This helps OutSystems protect itself from misunderstandings and potential penalties (fines) from the client, which could lead to misinterpretations. The current view considers tickets as either open or closed. Time tracking helps with OutSystems' resolution metrics and protects the company from other interpretations and metrics. It would be beneficial if this data were exported along with the ticket ( spreadsheet generation ).

It would be very helpful to have a consolidated view of all Consumed APIs and Site Properties within the Service Center, under the Factory tab. Currently, when moving from one environment to another, it's difficult to track where each API is being consumed. Even if we know the API is in use, we still have to manually navigate through each application, then into the module, and finally into the integration settings to make changes. The same challenge applies to Site Properties. Having everything in one centralized location would streamline the process significantly. Open to any suggestions! 🙂

It would be great to have a native Service Studio for Apple Silicon (M1/M2 Arm CPUs), instead of running them through the Rosetta translation layer. The performance and power consumption are not ideal at the current state.

Expose the data in your Outsystems application via an OData service (RESTful API). Just rightclick on the entity and the rest is done for you, including security, streaming and paging. The data is queryable from the outside. The data can be used in Excel, LinqPad, PowerBI, Tableau, and a number of other BI solutions.

Hi,It would be awesome to have options to ignore some differences when merging oml files.Some of the Ignore Options could be:Ignore Position ChangesIgnore Case and Spacing (Could be for Assign names of comments)Ignore White Spaces (for JS blocks or any text area like containers)Regards,Carlos Ardiles

During the Outsystems Usergroup at Nextstep 2019 in Amsterdam someone asked why the technical sessions weren't very technical or in depth. The reason for this is that there's a wide range of experience and expertise among the attendees of Outsystems and the technical sessions are open to all of them. This makes sense, but the short 20 minute sessions are hamstrung by having to go over basic stuff sometimes.Perhaps for the next NextStep you could implement some sort of complexity indicator for the technical sessions. For instance, associate and professional level technical sessions. This would allow the professional sessions to skip over the basics of development and get more technical or in depth on a specific subject.

In my opinion the combobox margins and padding's in the visual css should be bigger and should contain the OutsystemsUI variables as optionsAs you can see from above screenshot the combobox is really small when we are using variables and also I need to write the variables all the time or copy paste from somewhere else.

It happens frequently that you want to past code in a Forum post. This can be SQL, CSS, HTML, C# or something else. At the moment this code is pasted as normal text and is taking the styling of a normal text. For code this is not wanted. Please add a Code Block that uses a style that is normal for code. So it is using a monospaced font, have indentation support, colorization of the different elements in the code block of readability, allow to copy the code, etc etc. HighlightJS is one of the big frameworks that provide support for this. Perhaps it is possible to integrate with this? A few examples of working code blocks are;

Hi,My suggestion is that modules could reference a particular version of another module.This would allow teams to keep developing and evolving their modules and not being concerned about apps that are not currently being worked on becoming broken or needing someone to manually update them.This is a very common scenario in larger factories and even with proper architecture it will happen.The way I see this working in practice is tagging module versions as "stable" and any consumer could choose to reference "current version", which would be the same as it is now, or one of the "stable version".This extra concept of "stable version" might be needed otherwise we would always be selecting from a list of hundreds or thousands of versions.From a platform perspective I believe this is quite doable! We can already just clone any module and reference that one (thus creating a kind of stable version), the platform could do this behind the scenes and have that "hidden clone" as the Stable version.The biggest difference from what we can do now is that these clones MUST use the same physical tables of the main module! (as in: not creating new ones)It goes without saying that what I'm suggesting here is also the way most "traditional" languages work!Cheers,Hermínio