Should be possible to change the attribute of the Group By attribute in aggregate

We have reasonably big (medium-big) sized OutSystems projects. We have number of objects (screens, blocks, server actions, entities, etc) in these projects. These projects go through multiple phases of constant development. There are multiple developers work on these projects, and many of the developers are hired when needed. These new developers start with very minimal knowledge about the application. These developers usually work on shared components. So, it would be easier, if there is an EXPORT option that helps us export the specific screen/server action/block that they work on. Before they start the development, they can export the component/object. This EXPORT-ed file/source can be used as a backup. So if we need to restore we can easily restore.

Hi Team , We found that some of Forge components are very old and has multiple versions so its very difficult to find particular version by clicking load more button at bottom. Also if someone searching forge component without login state of page not maintained after login we need to search it again. For example UltimatePDF if you click on Versions tab multiple versions are there its very tedious to look for old versions. Thanks & Regards Ashish Akolkar

When making an attribute in an entity that is a reference to a Static Entity, we need to be able to set the default value. Otherwise, when you deploy to an existing application, you need to find a way to set the value, such as manually editing the database or creating a one-time timer to set the values.

In our current project we need to use a Samsung Galaxy Tab Active 5. The resolution 960x600 (Downsized from the actual resolution 1920x1200) with an aspect ratio of 16:10. The responsive behaviour is different. I can't use the preview in Service Studio. Now I need to check it in Google Chrome using DevTools and Device Preview with the resolution. Would be nice if we can just configure the device resolution for mobile and tablet.

One of the main challenges parents are facing is how to keep a healthy routine for their kids, what activities to do, what assets can they use and share ideas with other parents... A lot of private WhatsApp groups sharing assets, examples of day planning and even notifications about remote events (live concerts for kids, etc...).The idea is to create an app where all can contribute, sharing and getting new assets to use to plan kids new home routines. The app will have the sections:- Contents: set of contents uploaded by the users with categorization by age and type of content (e.g. Math, Gramar, Music, , Games, Books, Gym...)- Day Planner: virtual schedule where the kids and parents can plan the day and track the achievements (share those plans with other users too)- Upcoming Event Information feed: information about upcoming events (like Live Concerts through YouTube or Facebook...)Besides the app there is a need to create a simple backoffice: in order to ensure that all the uploaded content is appropriate for kids a backoffice to approve the publication of the assets should be created. The community should name a group of persons that would be responsible to approve the contents (already have a lot of volunteers...)

When copying an action, web screen, web block, or structure from one eSpace to another, perhaps we can be given the option to paste without adding references to objects in the original eSpace.Yes, the new eSpace will then present errors but you should fix it accordingly then by either copying/moving the other objects or setting them as public and referencing them.The problem, my problem, with the way it is currently working is that junior/fresh developers are not aware of the automated referencing and many times they are creating circular dependencies that could have been prevented.Sometimes though, one would want to keep the reference to the original eSpace, i.e. when refactoring and separating web screen and server logic, thus I suggest having it as an option.

The notify  handling is very nice, but i think we miss some stuff to make it more powerful.1. ability to bubble the notify directly instead of going to an action "OnNotify" where the only thing is in the action:NotifyWidget( NotifyGetMessage())2. add a 2nd parameter which is called "MessageId", which is taken from the newly Introduced static-entity "Message".   so you can handle message in a consistent way without have to check the message with index/substr or whatever

Thanks for the new Service Center!Please just add a new Favicon, could be static like Lifetime, or even better, dynamic like when we finished publishing a solution, changing a site property, etc.Cheers,Luís

If would be nice to be able to set REST API "Send Default Options" per API Method request vs a fixed value for the entire REST API parent endpoint. Ideally each API Method should be able to set the REST API "Send Default Options" option on a per request basis based upon a referenced or calculated valued based from Site, Header, Input parameter, or Method Output parameter. Depending on the consumer of REST API, there tooling might not be able to handle complex JSON structures with missing parameters. This idea would allow optimization of JSON responses for clients that can handle sparse data while at the same allow non advanced clients to be to use the same REST API.