...
It may be desirable to support most or all of the current options going forward, however in general they should operate as External Matching currently does, requiring immediate resolution and appropriately linking (or not) the current Petition to an existing Person record (if found).
Invitation and Email Confirmation Validation
Background
Currently email address confirmation and invitation are conflated into the same step, and require clicking on a somewhat phishy looking link sent via email. These links are also susceptible to premature invalidation (eg: by email clients pre-fetching the URL) or confusion (an enrollee starts enrollment on their desktop, but then goes to their phone to check their email).
Approach
Going forward, Invitation may imply Email Confirmation as a side effect (since it is the same flow, basically) but the two concepts will not be as tightly linked. Instead of embedding nonces into URLs, validation will be via a code sent via email (or text message, etc). For self signup flows, the code will be prompted for inline without interrupting the current page. For invitation flows, a generic entry point will be established (eg: /registry/petitions/reply) that will prompt for the confirmation code and/or an Invitation ID, both of which can be copied from the email or text message. This page can also be independently linked from support pages, providing a verifiable path independent of the email URL.
Setup Assistants Replace Templates
Background
Enrollment Templates were originally created to provide easy-to-duplicate pre-configured Enrollment Flows to simplify setup of new Flows. They rely on Cake's ability to easily duplicate an object and its related models. As Enrollment Flow capabilities increased, not all configurations are easily Templatable. For example, EnvSource relies on an Org Identity Source plugin to be created, which might not exist in a given deployment, and so no Template can be shipped that includes a reference to an Enrollment Source.
Approach
Enrollment Templates will be replaced with a Setup Assistant, which provides common enrollment patterns and creates a default plugin configuration suitable for that pattern. Such patterns include:
...