COmanage Developers List

[Benn Oshrin <>]

Currently, enrollment flows basically complete in one gigantic step, 
with subsequent confirmation and approval steps. The petition artifact 
(historical record of what attributes were created at petition creation 
time -- these go in cm_co_petition_* tables) and the operational records 
(cm_co_people and various other tables) are created at the same time. 
This means, for example, that if you view "My Population", you'll see 
both active records and records in various petition states.

As part of the big refactoring, the one gigantic step is being broken up 
into several smaller steps. This will allow, for example, attributes to 
be collected at multiple stages (eg: from the petitioner, from the 
enrollee, and from the approver), for petitions to be edited before they 
are finalized, etc. This creates two options for when attributes get 
populated into operational records:

(1) As soon as they are known. This is complicated because if (eg) the 
petition is edited before the it is finalized, we'll need to copy the 
updated attributes to the operational record. If the operational record 
is updated before the petition is finalized, the petition won't 
necessarily be updated. This could lead to various confusing situations 
where the petition attributes and the operational attributes are not in 
sync before the petition is finalized.

(2) Upon petition finalization. This is after any confirmation and 
approval steps are completed. The downside of this approach is that 
these records won't show up in "My Population", or maybe that's not a 
downside. However, it's possible that multiple petitions could create 
conflicting operational records if they're created in parallel, 
depending on how we implement matching.

Thoughts as to which option is better?

Thanks,

-Benn-