Details
-
Bug
-
Resolution: Fixed
-
Blocker
-
COmanage Registry 4.1.1 (The Info MR1)
Description
"Nested Group memberships are not automatically resolved when a CO Petition is finalized and the CO Person record status is set to Active."
"I’m not sure what automatically resolved means here. Are you saying that a Petition adds a new Enrollee to Group A, and Group A is nested into Group B, but the Enrollee does not end up in Group B?"
"Yes"
"Without looking at the code I suspect that because the Enrollee is not active when added to Group A, the nesting calculation doesn’t put the Enrollee into Group B. However the subsequent conversion to Active status should cause the recalculation (and if it doesn’t that might be a bug).