Obsidian Registration Entry Prefills Wrong Registrar

[bezalelBU]

Description

The last page of the registration entry block prefills the first registered adult as the registrar regardless of who is logged in:
Adult1 is logged in but since Adult2 is the first registrant, the block defaults them as the registrar. Unless the fields are updated, Adult2 will be listed as the registrar.

Additionally, this results in signature documents being assigned to Adult2 (who was not logged in) even though they are signed by Adult1 (who was logged in). The registrar is also switched to the first registrant:

Actual Behavior

When going through the registration, Adult1 is prefilled, but I remove them and add Adult2 instead, and proceed to sign the signature form as Adult1 on behalf of Adult2:

I then complete the registration with myself (Adult1) as the second registrant and proceed to the final step, but instead of being prefilled with my profiles information, the block assumes Adult2 as the registrar. If I don't correct this, Adult1 is added as both the registrar and the assigned person for the signature forms. The 'Applies To' and 'Assigned To' persons remain the same:

Alternatively, if I register myself (Adult1) first, the last page defaults to that profile.

Expected Behavior

I would expect that the registrar is always the person who is logged in, especially when signing a legal document. I would not expect that the registrar field could be editable in that instance, and I would not expect it to switch the 'Assigned to' Person for the signature template over to a person who is not logged in and not signing the document.

To summarize:
1.) A logged in person has the ability to designate another person as the registrar even when completing a registration that requires a signature document.
2.) The block itself defaults the registrar to the first person that was registered, even when a different person is logged in.
3.) This assignment then changes the assignment of the signature templates, which are then logged as being signed by a person they were not assigned to.

Steps to Reproduce

Create a registration template with a signature document and two questions. Use the following 'details' settings, add a signature document, and leave everything else as is:

Create a new instance.

Ensure your profile has at least one other adult profile in your family.

Go to register with the new instance. Select two people to register and choose the other profile to register first. Go through the registration once for the other adult and once for your own profile, and then check the registrar first name on the last page of the form. Submit as is.

Check both the registration and the signature documents: both will show as being registered by and assigned to the first registrant instead of the person who was actually logged in. Since we elected to prefill the registrar in the template settings, we know the block originally had the correct registrar and that this was changed during the registration process.

Issue Confirmation

• Perform a search on the Github Issues to see if your bug is already reported.
• Reproduced the problem on a fresh install or on the demo site.

Rock Version

v18.1, v16.13

Client Culture Setting

en-US