When recovering deleted code or working with another person in the same app, during merge and publish it would be very helpful to have an option to 'Select All' for the versions we want, instead of selecting them one by one.

We should be able to define the names of the fields we are exporting to excel.

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.

 O que é isso? Uma ferragem colaborativa integrada à plataforma sobre os desenvolvimentos podemos comparar, comparar e aprender com métricas de desempenho de aplicativos do mundo real desenvolvidos no OutSystems. Problema que resolve: Os envolvidos frequentemente enfrentam gargalos de desenvolvimento, mas não têm uma referência sobre o desenvolvimento de aplicativos semelhantes. Não há um local centralizado para compartilhar práticas recomendadas específicas de otimização. Cada desenvolvedor "reinventa a roda" testando soluções isoladas. Como funcionaria: 1. Contribuição de métricas anônimas Os desenvolvidores enviiam dados de desenvolvimento de seus aplicativos (tempo de resposta, consultas lentas, uso de memória) Informações confidenciais podem ser anonimizadas Sistema se compara à comunidade: "Seu aplicativo é 30% mais lento que aplicativos semelhantes" 2. "Receitas de Performance" Biblioteca de soluções testadas: "Reduzir consultas N+1 em ListRecords" com comparações antes/depois Votação comunitária: qual solução funcionou melhor? Integração com controle de versão: em qual versão do OutSystems cada solução foi eficaz? 3. Desafios mensais "Otimizar esta aplicação problemática" - colaboração comunitária Recompensas simbólicas: emblemas, reconhecimento, destaque de perfil 4. Integração do Service Studio Plugin que exporta automaticamente métricas de desenvolvimento Um clique para compartilhar com uma comunidade

Even though the ODC Portal is in its early stages, what do you think about adding some colours to the Stages dropdown? (Example: Dev=Green, QA=Yellow, Prod=Orange) We've been told that the ODC Portal is the "substitute" for the Service Center and Lifetime applications. In this ODC Portal, the Admin can basically configure and deploy applications for all the Stages . Although this is great because it has everything in one place, the absence of colour coding can lead to misconfiguration because the user might not notice he/she is in the wrong Stage doing the configurations. Attached are some prints to support the idea.

Sometimes we need to navigate through the module, when merging. I think that is a good idea to allow to navigate through the module while doing the merge, without the need to close the merge popup. This is usefull to check the code on other actions (not on the merge)

While using the Upload widget, it would be really helpful if there were built-in properties to set allowed file types (like .pdf, .jpg, .docx, etc.) and a maximum file size limit (in MB or KB). Right now, we have to write custom logic or JavaScript to validate these things, which takes extra time and can be tricky for less experienced developers. If these options were available directly in the widget, it would save time and make file uploads more secure and user-friendly out of the box.

Since we currently have a large influx of new users on the forum that love to ask for solution in OML format I think we need to have some form of notification about the risks doing so. Please add a notification before the actual download informing the user that an OML can contain malicious code and that you should not import the OML in your Enterprise Environment. Malicious code will almost always be run via a timer that is started On Deployment. Malicious actions can be; Uploading information about your environment (or data) to an external source. Creating user accounts to gain access now (or later). Providing access to your environment via an API or screen. Running a SQL query that can delete your data. and a whole lot more Perhaps it hasn't happened until now (perhaps it has) but it is better to be informed and warned before it is to late.

The new JavaScript editor for mobile apps, is great, but the autocomplete could use some work :)The feature catches comments and strings at the moment, see below.

The use of ReactJs in mobile applications not only allows a quick refresh of the screen but also makes the development process simpler, since it is not necessary to perform ajax refreshment explicitly. It would add value to Web applications