Mapping an additional question to Status__c field will create a Registration flow issue.

[walt0019]

Describe the bug I was testing a solution to our alumni team wanting to know if registrants simply wanted to express regrets will registering. This use case is a typical for alumni and non-profit events. So I created a new question to populate Registration Status based on a question and after that additional question was completed, I was returned to the login page. The Registration record was created with the Status that I mapped, but it broke out of the registration pages, Confirmation, Submit, ect, because the Registration was not in a Started App.

To Reproduce Steps to reproduce the behavior:

1. Create a Summit Events Question that maps to Status__c
2. Make field Visible and Required.
3. Register for the event and when the Status field is mapped.
4. Registrant will return to login page.

Expected behavior I had high expectation that I would be able to continue with the registration as if nothing changed but the backend status. Please register for my event to see the behavior in action. #371

Screenshots If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context Will create a new enhancement issue for the ability to express regrets, while we may need to help text and a validation rule to prohibit users trying to create a similar process that I was attempting to do.

[walt0019]

This issue was already documented in https://github.com/SFDO-Community/Summit-Events-App/issues/371. I will say that St. Thomas Alumni are capturing the status within Qualtrics registration surveys and about 5 percent of the population expresses Regrets. Thad and I discussed additional workarounds for this use case and routing users to a Qualtrics survey if they'd like to express regrets and not necessarily break the Summit Events workflow.

[rdblake21]

@walt0019 Thanks for capturing this and documenting it. Sounds like you and @tcdahlberg have already had some discussions on this one specifically, which is great!

Let's keep this bug out here in addition to #371 so they are recognized as both a bug and enhancement based on expectations you had as well as it also being a relatively new feature.

We should talk more about if this needs to be resolved before we package again based on level of effort to solve for it.

[tcdahlberg]

@rdblake21 and @walt0019, It is important to note that code needs to know when a registration has ended. Currently, the registration has ended when it strays from the "Started" status. We could add more statuses to the list of statuses where the registrant can continuing to work on the registration (See line 209 of SummitEventsShared). However, this does not stop the issue of trying to map question objects to the status. We could have a secondary multi-pick list that shows what statuses are OK, for a registrant to continue in the registering in that state, but I fear you would be entering a documentation nightmare of explain what all that means.