Hi
Ler's say i want to create a common application where i would like to put all common parent groups for all the other appian applications and other common stuff.
When i create a group in an another application with parent group in the common application there is a cyclic precedents relationship between the two groups (the parent group relays on member group and the member group relays on parent group).
The only way i found to deploy common application first without receive the warning of "missing precedents" is to assing rule membership by rule.
I would like to know if there is a best practice in order to manage those kind of application design concerns.
I'm a java developer and for me it's really odd behaviour this cyclic relationship by desgin
Thanks a lot in advance
Discussion posts and replies are publicly visible
I would not make that global group the parent of the local group. Parentship in groups is about inheritance of permissions, not membership. A membership rule is the way I would go.