The idea is to add the possibility to classify the type of advanced query we need. This is very important because when we are using a SELECT query, we need to insert the output correctly. But when we only want to create an UPDATE query or a DELETE query, e.g. bulk update or bulk delete, the output structure is not important and by classify, for example, we don't need to insert an output chosen by us.Another example of a rule applied using this type, there is no need to insert a TOP in the DELETE or UPDATE queries and of course no Max. Records.

Like existing built in functions(listfilter,listsort,etc) associated with list, we can have a list group by function to avoid adding custom logics. This will group by the list with respect to a column or filed.More advance function can be - supports multiple fields group by option.Thanks

Be able to create a unit test for a Server / Service / Client (?) / Screen (?) action that shall be executed without developer intervention, for regression purposes.

The idea here is to remove te Entity attributes that are not grouped as a possibility for the order by in an aggregate.

Hey guys,I think it would be really helpful to have a new tab besides the TrueChange tab that shows the Architecture Dashboard report for the specific module we're seeing.Apart from being more accessible, developers can easily look at the report in the module scope and more proactively reduce technical debt.

Sometimes, when creating a deployment plan, if the name of the Application is slightly bigger, a text-overflow: ellipsis; is applied. This is fine but the problem is that we don't have a tooltip that allows us to see the complete name of the Application and sometimes it becomes an issue.

It would be nice if on the Forge page of a Mobile Plugin there is information shared for which MABS  version this plugin is tested succesfully with or is compatible with.We currently can only see for which OutSystems version it is compatible with.

To keep the code cleaner and avoid circular dependencies, it would be interesting not to let a module publish when you had to create circular dependencies.

I don't know about you, but I always check if an Aggregate has actually Found something, instead of it being empty.So, in an If Condition after an Aggregate, I keep selecting the Aggregate.List.Empty suggestion, then editting it to "not Aggregate.List.Empty".Could ServiceStudio be updated so the not-variant is also present in the list of Suggestions?

Hello Team, If more study materials like e-books can be added in trainings, it will help to learn more with deep knowledge