Currrently, a group can be associated to an application. If done, all its ancestors and descendants must have the same application, and all data flows in all these groups must also be associated with the same application.
I find that too restrictive and plan to remove the relation between a group and an application, and all the related checks. This would allow to regroup all the data flows related to the devices/VMs of an application, including management flows that are "owned" by support application.
E.g.:
Group: App A
Sub-group: App A - Data flows > many flows associated with the business application A
Sub-group: App A - Management flows > AD, SSH, monitoring, etc. associated with the support applications "Active Directory", "Monitoring", etc.
Welcoming any feedback on that potential change, if some of you need a data flow groups' tree to be associated with a single application.
Currrently, a group can be associated to an application. If done, all its ancestors and descendants must have the same application, and all data flows in all these groups must also be associated with the same application.
I find that too restrictive and plan to remove the relation between a group and an application, and all the related checks. This would allow to regroup all the data flows related to the devices/VMs of an application, including management flows that are "owned" by support application.
E.g.:
Welcoming any feedback on that potential change, if some of you need a data flow groups' tree to be associated with a single application.