Hello,A lot of OutSystems customers get confused regarding our Teams being Application Teams instead of User teams, and one scenario that they get confused with is that when they have multiple businesses/independent teams working inside the same infrastructure, they can't allow the users to create applications only inside their teams.The use case is that you have multiple independent teams working in your infrastructure, and you want them to be "somewhat" autonomous, but then in Lifetime you only really have 2 options:Give them permission to change and deploy as default so that they can create applications in your infrastructure, which means that they will have access to any application that they are not restricted to (Applications that are not on a team, which if you have many teams all creating applications, and they are all created without a team at first, will be a problem unless they have a very good internal process). And if you do this you still need to give someone access to assign the applications to your team, and you need to give them "Manage Teams and Application Roles" as default, and from the moment you do that, they can freely unassign/assign any user/application to any team, so in theory they have access to everything (since they can give themselves access to anything by unassigning an app from a team). So there's either no full autonomy or no full independence between the teams.Don't give them permissions to change and deploy as default and direct to some kind of infrastructure manager that responsibility, removing the autonomy from your developer teams since they always need to raise a ticket/ask the infra manager to create an app and assign it to one of the teams that they can actually change.So as you can see, as far as I know, there's no real workaround for this use case.In my opinion, one way of fixing this without creating a new permission layer would be a dropdown inside Service Studio when you are creating an application so that you could choose the "Application Teams" that you have Change & Deploy in and then allowing the users to create applications as long as they have Change & Deploy in at least one team and automatically assign the app to that team. The dropdown could include "No Team" if the user has Change & Deploy as default.The other option would be a new permission layer for user groups, which would mean being able to group your users (one user to only one team at any time), and then giving them permissions to applications assigned to that team (like the opposite of the Application Teams right now) would fix this issue, since then you could have List as default and change and deploy in your User Group, and all applications that you would create could be automatically assigned to your User Group.I hope the idea is clear enough, sorry for this wall of text!Thank you in advance!

Currently, OutSystems Service Studio organizes widgets, actions, screens, and entities in alphabetical order. However, users may prefer a more flexible arrangement based on their workflow. Introducing a drag-and-drop feature would allow users to customize the order of these elements, similar to how actions and widgets are placed within a screen. This enhancement would provide greater control, making navigation more intuitive and efficient. Users who prefer the existing alphabetical order can retain it, while others can rearrange items according to their preference, improving productivity and streamlining development workflows.

 The optional chaining (?.) operator accesses an object's property or calls a function. If the object accessed or function called using this operator is undefined or null, the expression short circuits and evaluates to undefined instead of throwing an error. Source: MDN This operator is widely used and supported but OutSystems still gives us a (wrong) warning when using it inside javascript nodes. I think this should be improved. Probably just an editor update is needed. Cheers, Tiago

Everywhere in the world, people with symptoms are being advised to call a specific line before going to the hospital. In Portugal this line is SOS 24. This happens because by going to a hospital, people with symptoms who are infected might contaminate others and, if they're not infected, they might become, just by interrupting the quarentine.Lines are clogged with calls from people who either have symptoms that do not match COVID-19 ones, or others who ask just plain stupid questions ( https://observador.pt/2020/03/14/a-que-horas-fecha-o-norteshopping-as-chamadas-que-entopem-a-linha-saude-24/ ). People with real symptoms might have to wait for hours on end for their calls to be picked up, which might accelerate their panic and lead them to visit the hospital.On twitter these last few days I've seen many portuguese doctors, nurses and pharmacists offering to answer questions posed to them there, to stop people from calling SOS24 unless their symptoms are 100% matching COVID-19 ones. Each person thinks their situation is very unique: "i don't have fever, but I have a cough, am I infected?", etc.My idea is: a platform where doctors, pharmacists and nurses would put their profiles - ideally with a link to somewhere online which proved they really are what they say they are (hospital webpages, or CVs, of linkedin - and allow people to reach out to them in order to ask questions that they would otherwise call health lines to do so. I think people will always try to call health lines, but if they're waiting in line ~4hours for their call to be picked up, they might as well post a question on this website and see what a certificate health professional has to say.I think this should be easy to build: first, a simple page with "I'm a doctor who wants to help" and a "post a question" for random users. Then, we would either round-robbin the questions that came via each professional in the platform or we would allow people to ask specific profiles of professionals available.

I have two suggestions to enhance the private messaging feature on the OutSystems platform ( https://www.outsystems.com/profile-messages ): 1. Add Edit Option for Sent Messages Currently, there is no option to edit a message after it's sent. It would be helpful to have an edit icon or option to quickly fix typos or update the message content without sending a follow-up message. 2. Allow .OAP/.OML File Uploads in Private Messages As of now, only image files can be attached in private messages. It would be very useful to support attaching .oap or .oml files as well, especially when discussing technical issues or sharing modules privately. Please consider allowing these file types or increasing the file size limit to support them. ⚠️ While the forum allows these files, private messaging is preferred when sharing sensitive or internal information.

Allow customize permissions to IT User using Lifetime. Today we have some permission pre-defined such as:Full ControlChange and Deploy ApplicationsOpen and Debug ApplicationsMonitor and Add DependenciesList ApplicationsAccessNo AccessCreate ApplicationsAdd System DependenciesManage Infrastructure and UsersManage Teams and Application RolesBut when we need people to be able, for example, to just change Site Properties and/or run Timer in a Production environment, we need to grant the "Change and Deploy Applications" permission which also allows you to change and publish an application directly in Production.

It would be nice if I can use the ListAppend/Insert, and just select the variables to create a record, so I don't need to define the record first, assign values and than use the listAppend/Insert.

Hello,The idea is to create a new role or option for the created users that have or do not have access to the "CSS inline" / theme and layout and other front end options to ensure that only authorized users can change the front end issues and guarantee the good experience and best practices.And create a "find all" css inline in the module so that it is possible to locate and change or not the code.Thanks

It would be useful for, for instance, schedule a solution to be published during the night.

Adding Windows Mobile 10 support for OutSystem Now(verison10) and Native App capability.OutSystems 9 has some support for windows mobile 8.1 (mentioned on OutSystems website) and windows mobile 10 (tested by me), but this has not been taken across to the latest Outsystems release, version 10.This has been confirmed by OutSystem Support team:"As for Windows Mobile 10 support, currently it is not supported as a native app, but you can propose that on our Ideas [2]page"