Hi,You all know probably the MS Excel macros, and how recording VBA macros fastened the development of macros and enhanced the user/dev experience.Why not implement similar feature in Outsystems, so that we can track the steps done to implement the different parts of the App, and could automate some of  them,for instance when I need 30 dropdown menus, I drop only one, I record the process, then I add a loop, to get it repeated 30 times.This makes things much faster, and make automation much easier.Besides, it could be used as second method of debugging.Kind regards,Sirajeddine

The current reactive version of the data grid is very useful for what it does.  However there are times when you want to extend the data grids capabilities from examples from on the Wijmo JavaScript DataGrid Demos page .  Unfortunately extending the current Reactive DataGrid component is due its internal GridAPI.  To extend the grid, a developer needs to understand both the Reactive DataGrids' GridAPI in addition to the to the wijmos API.It would be nice to have a OutSystem JavaScript DataGrid Component that justs loads the required wijmo libraries, registers the grid license, and binds to a DOM element id.

Hi,Currently it is possible to extract multiple actions into one single action but only a Client Action, it would be much useful if we could do the same but into Server Action, especially when we got this kind of warning:Performance WarningThe 'SendEmailOnClick' Client Action calls several Server Actions. To avoid performance issues, group them all in a single Server Action and call it instead.So I hope we can have both possibilities in the list whenever it is possible, ie extract to server action or to client action, or inside the extract to Action option, it should be a choice to select either client action or server action as extraction target.Kind regards,Sirajeddine

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.

The idea is to allow users to directly create a Light Process in Service Studio, without having to create a Process and then go to Service Center to enable Light Processes.This could be done by simply creating a separate folder from the Processes, named Light Processes, and we would then have validations in place just for Light Processes (e.g. no more than 1 activity).Additional to this idea, it would be nice to be able to launch Light Processes without having to link it to a database create event, and just launch it normally as we can do for BPT.

This is an idea for a forge component in order to convert the Outsystems App output (OML/OAP) exported file into a HTML, CSS, JS and .NET files .Next step would be upgrading this component by adding features to it or create separate converter (another forge component), that allow to convert OML/OAP into other Languages' format, this could be useful for small plugins that we want to use in other projects made with different programming language instead of writing the code once again in that other language.Regards,Sirajeddine

This idea is derived from my previous one, it raised when I was writing this: https://www.outsystems.com/ideas/12757/outsystems-code-portability/The new idea consists in allowing developer to add pieces of code in other programming languages such as Python, Java, Golang, C++, php or whatever (scripts, files, plugins, extensions, modules, ...)At the end of the day, all will be compiled/interpreted, and all will be converted into machine language (0's and 1's).This will be a huge enhancement for OutSystems ecosystemKind regardsSirajeddine

This idea can have relationship with Licensing, ServiceStudio, LifeTime, etc..Anyway, it is about allowing developer to get the code of his outsystems App, at least for 3 reasons:For maintaining/extension purposes, he might add whatever he want may in Languages not supported by Outsystems, adding plugins, scripts, or whateverAdding confidential parts that he doesn't want to share/publish on the Outsystems cloudSome customers ask imperatively for source code and put this as a key condition/requirements in the project's contract.Kind regards,Sirajeddine

Hi buddies,My idea is why not make it possible to make software and all kind of Apps via outsystems. As you know we can for now only develop either mobile App or traditional or progressive Web App.Why don't we take advantage of Outsystems platform and extend Service Studio's capabilities to the field of desktop Apps ?Kind regards, Sirajeddine

Hi,I'm not sure if this was suggested as I didnt' find anything recent about this, but please give us the option to order all local variables alphabetically. I'm sure it's a "simple" thing to implement given it already happens on client actions and sometimes we have lots of local variables and makes no sense to be looking for it, when it could be sorted.