"setCurrentLocal" is an action that allows us to choose the language of the application. For example, if I want the application's local language to be Portuguese, I would put "pt-PT" in the input of this action. Once we choose the language, it would be interesting if the built-in functions of OutSystems returned the output in the chosen local language, in this case, Portuguese. For example, using the formatDateTime(date, "ddMMMMyyyy") function would return "01Julho2023" instead of "01July2023" if the application's local language is set to Portuguese. This way, we wouldn't have to translate the function's output.

Currently all comments have the same color. In Dark Theme they appear black and in Light Theme they appear gray. This makes it difficult to distinguish important notes or identify who added them. The proposed idea is to allow users to define the color of their own comments so that in action flows it becomes easier to see who contributed. If full customization is not feasible an alternative would be to provide three predefined colors such as normal yellow and red to indicate severity or importance. This would help draw attention to critical comments and prevent them from being overlooked.

OutSystems already provides entity relationship diagrams after creating entities, but it would be even more useful to have a simple, editable flowchart feature to visually represent the data or process flow throughout the project. This feature would help developers and teams easily map out how data moves between screens, actions, and entities without needing to use external tools like Draw.io, Miro, or Lucidchart. It would be a quick way to narrate workflows or data movements directly within OutSystems during client discussions or internal planning. Example: For instance, consider a project with entities like Customer, Order, and Invoice. A built-in flowchart could show how data flows: Customer → Order → Invoice → Payment , and developers could edit or annotate the flow to demonstrate logic or upcoming changes. This visual approach would make it easier to explain ideas, document workflows, and align technical and non-technical stakeholders all within Service Studio.

The option to remove unused dependencies by eSpace is realy great! But I think it can be implemented to Applications at all. It wold be nice to have an option in ServiceCenter to remove all unused dependencies by an Application.

Setting the Oracle Parameters for case insensitive searchingWe need to set NLS_COMP=LINGUISTIC and NLS_SORT=BINARY_CI in order to use 10gR2 case insensitivity.  Since these are session modifiable, it is not as simple as setting them in the initialization parameters.We can set them in the initialization parameters but they then only affect the server and not the client side.  The following PL/SQL was used for a search screen:execute immediate 'alter session set NLS_COMP=LINGUISTIC';execute immediate  'alter session set NLS_SORT=BINARY_CI';

Sometimes you have two buttons that you want to have as the "Default" button based on different conditions. For example, if you have a screen with basic and advanced search, you want the "Search" button to be the default button, but you have a different "Seach" button in the If. J.Ja

90% of the times I use the 'ListIndexOf' function I follow it up with some variation of: MyVar = MyList[ListIndexOf.Position].val It would be helpful if there was a 'ListFind' function (client and server) that returns the element in that position, and not only the index.

Hi guys,A question that everyone has been asking after changing the certifications, and with this I think that was pleasing to many ... is why the specialization in Mobile does not appear in the Diploma that we download. I think it would be an asset to have this information also present in our certifications (and specializations) diploma from OutSystems.Cheers,Miguel

It would be nice if there is a comment widget I could place on Screens and Blocks of Reactive Web Apps and Mobile Apps, like it is possible for Traditional Web.

Please add a magical button to retry a failed deployment.It would be a time-saver to not have to create a new staging, validate the plan again and re-deploy.