COmanage Developers List

[Benn Oshrin <>]

On 11/30/12 3:33 PM, Heather Flanagan wrote:

> 1 - follow up on the potential need to have someone not in a CO be
> authorized to add people to the CO (and yet, not be CMP admin)

No ticket for this until we understand it better.

> 2 - concern about who can handle approvals and whether we have the right
> authorization group process associated with the enrollment flow (maybe
> create an authZ group per enrollment flow?)

CO-511

> 3 - Can you clone an enrollment flow? (do we have a ticket for this?)

We have CO-273 and CO-453, which are in the same ballpark. I've created 
CO-510.

> 4 - specify default value for historical records when new attribute defined

CO-508.

> 5 - An admin script to recursively populate id's?

CO-509. This would be a button, not a script.

> 6 - What if someone is an active member of two closely related CO?
> (similar to account linking problem)

Not sure if there is a specific follow up from this one.

Also:

CO-506: Better handling of identifier assignment especially if only one 
name.

CO-512: Reconcile against pending records.

-Benn-