Not Yet Implemented
This document describes the new Registry Enrollment mechanism being introduced as part of COmanage Registry v0.9.4. It is not yet available for use.
About Registry Enrollment
Default Enrollment
Enrollment Flows
An Enrollment Flow consists of a series of pre-defined steps, the execution of which is managed by Registry in accordance with the configuration of each specific Flow. Enrollment Flows support Plugins, see that page for some specifics.
Enrollment Flow Steps
A step may be considered Required, Optional, or Not Permitted, in accordance with the configuration. A Required step will execute both the core Registry functionality, as well as any Plugins. An Optional step will only execute Plugins, the core functionality will be skipped. Not Permitted means neither core nor Plugin functionality will be executed.
| Step | Description | Core Step Executes If | Plugins Run If Core Doesn't? (Optional) | Petition Status Following Step* |
|---|---|---|---|---|
| start | Initial step of an enrollment flow. The Petition artifact is created following successful completion (including any Plugins) of this step. | Introduction Text is defined | Yes | Created |
| selectEnrollee | Select an existing identity (CO Person or Org Identity) for this enrollment. | Identity Matching is set to Self | No | Created |
| petitionerAttributes | Collect attributes from the Petitioner. | Enrollment Attributes are defined | No | Pending Confirmation |
| sendConfirmation | Confirm deliverability of Enrollee email address. | Require Confirmation is set | No | Pending Approval |
| finalize |
*Status update may happen at beginning of following step.
Plugin Execution
Plugins are executed after the core step has completed, or if the step is considered Optional. When a Plugin is executed, handoff is via a URL. More details about this are in the Plugin Documentation. Because Plugins must be run one at a time, Plugins are executed alphabetically to ensure a predictable order. However, this order is subject to change in a future release. Once all Plugins have been run, the next step will be initiated.