Hello All,JavaScript has had ES6 and ES7 syntax since a couple of years. The new syntax provides some good features like lambda syntax, the 'let' keyword, the 'const' keyword, template literals etc.While some old browsers do not support all of the syntax, there are libraries like 'babel.js' ( https://babeljs.io/ ) which transform modern JS to ES5 (the usual JS syntax).It would be great if the OutSystems product allowed using modern JS directly in ServiceStudio.OutSystems can integrate the babel.js within the platform - so that it can convert any modern JS syntax to ES5 (older JS when required for old browsers, already most modern browsers do support ES6 , but not all..).Advantages:1. Developer productivity with modern JS will be very good. Many forge components rely on JS and JS libraries and having support for modern JS will be great.2. Modern JS is helpful for writing easier to read and maintainable JS code.3. On the mobile front in OutSystems - apache cordova for the mobile plugins is JS based - so supporting modern JS would be a win over there too.

Dear all,The AD has a chart with the overall technical debt trend for all applications within Outsystems factory, however should be very interesting to have something similar for each application.Something like:Best regards,João Paulo Pires

tl;dr : When refreshing a REST API definition, import only structures actually used by the imported methods, instead of *all* the structures exposed by the API. Details : When refreshing a consumed REST API definition, using the right-click "Refresh REST API..." context-menu item, you can select which methods will be imported. However, *ALL* the structures exposed by the API are imported, even if you import just a single method. This in turn triggers as many warnings as there are "Unused Structure", and we then have the tedious and error prone task of removing said unused structures. If only the actually used structures of the selected methods were imported, the task would be much easier and less error prone.

In Service Studio, static entities have a Description property (like all other things you can create like actions, structures, attributes and so on). However, given the nature of static entities, each record has a specific use, which currently can't be described. It would be nice if it were possible to add a description to each record, in addition to the static entity itself. This will help the developer assign the right value. This description could then also be shown when hovering over a record in the static entity selection pop-up.

Service Studio is supposed to be a WYSIWYG IDE. However, when working with things displayed in conditional situations, the layouts tend to shrink, resize, warp, or whatever else, breaking the preview. Example: This search with filters section is something very common to be found in many apps. This is a screenshot from the preview in Service Studio, and matches exactly what renders on the website after publishing. However a requirement came up to hide the bottom two under a role check, wrapping them in an If to only display them if they come up True: If published, rendered it looks fine, but the preview in Service Studio breaks There are some tricks; wrap the If in a container, put an empty container in the False branch... but those are just workarounds which shouldn't be necessary (and sometimes, as in the screenshots, they don't work) The idea, in short, is: make Service Studio render the contents as the CSS rules say it will render, If or no If

When I try to use the built-in action ListAny in a client action that needs to be a function, I currently get the error message sayingOnly actions that are functions can be used in other functions.From the documentation I get it that you don't want to perform asynch or server calls within a client function, but surely ListAny (or any other 'harmless' action) should be allowed?Or, at the very least, please make a function version of the built-ins ListAny, ListIndexOf and ListAny available.

Hello. I believe that we could have a new option to S ort by on OutSystems Forge: Component Creator and this option could be send to OutSystems Profile of the OutSystems Developer . Best Regards, Paulo Russo .

Hi everybody.I don't know wheter this is an idea or a question, or maybe we don't know a tool exist for this situation.We, at my company, are quite new working with Outsystems Platform. Some few days ago I did a minor upgrade from 9.0.0.2 to 9.0.0.19 version. Following the Upgrade Guide is a straightforward process but there is a point where things can become complicated: we have to republish every application and module manually, being specially carefull with dependencies.I think it would be really nice that this process could be automated as a taks performed inside the platform.What do you think?

In order to clean a project, sometimes we require to go to each eSpace, each action and check if there is any usage of, for instance, comment comment element.  It would save a lot of time if we could list all of the usages of Advanced Queries, Comments, Aggregates and so on.Cheers

The reactive web is taking its first steps, but right now it's not fully mature and doesn't have all the functionalities of the traditional web.It would be great to have a gap analysis document  which states what is now missing from Reactive compared with the Tradicional web. It would help to make the decision whenever a new application is going to be created. Should we go for Reactive or Tradicional?Example: Lifetime analytics not fully working in Reactive. Translations are not yet ready in Reactive. Etc.