I agree, a real concept of "domain" or "cluster" of applications is missing in the platform.

LifeTime has the concept of Team in which it is possible to group applications that are related to a development team but it is only possible to manage IT-users that are assigned to the Team and their permissions; the concept is really not useful in building a deployment plan as it is only possible to search applications by name.

As a workaround what we do to group applications by a "domain" is to include in the name of the applications a unique short letter code (for example 3 letters) so that we can easily filter them by "domain". Then it is possible to click "Select all" to select all the applications in the filtered list.

This will help you to build your deployment plan more easily.

--Tiago Bernardo

@Tiago Bernardo Thanks for the sugestion, it might well serve as a workaround for now.

I just found this idea to add "Search by Team" in the popup for adding applications to a deployment plan.

https://www.outsystems.com/ideas/6385/allow-to-search-for-team-in-add-application/

It is in status "On our Radar" so hopefully it will be implemented in the near future and it will allow you even to more easily add specific apps from a Team to your deployment plan.

--Tiago Bernardo

Just cam across this topic as I was looking for a Solution-based deployment approach. I fully agree that the App search based deployment is lacking efficiency.
At one end we have Solutions implement to group Modules/apps in a logical way to make versions and facilitate dependency refresh.
Why not allowing to search on Solutions in the deployment approach. This would enable much more flexibility than the Team-based deployment.
It would also tackle the domain driven architecture deployments as you could create your solutions based on your different domains.

I would rather have the concepts such as Solution used throughout the whole pipeline. Not only for quick ways to refresh your dependencies.

The workaround using a specific naming convention also has limitations. I don't see how you can manage this in the name of a user-facing app, let alone a Mobile App you need to distribute through public app stores.

Definitely a +1 for me on the Solution-based deployments.

Indeed for user-facing app or Mobile App, where the name of the application is very relevant, the workaround of including a short letter code in the name of the application is not applicable.
It was indicated as a workaround, not the perfect solution.
--Tiago Bernardo