Often, one of primary reasons for using the Form action is to collect information about the person who is filling out the form. For instance, you might want their name, email address and phone number. This kind of information is requested so often that Rock has a feature to automate adding these kinds of questions to your form. As if that weren’t enough, this feature will also create a record in Rock if the person doesn’t already have one. If the person is in Rock, this will find their record and it can be used to update their information. Unlike other items on your form, you don’t need to create workflow attributes for these questions. As described below, all you need to do is Enable Person Entry and pick what you want to ask the person for. Let’s take a look. Enable Person Entry - The rest of the fields described here will only appear if Enable Person Entry has been selected. If your form doesn’t need to ask for a person’s information, then this should remain disabled.Person Form HTML - Just like the Form Header and Form Footer, you can add HTML to the top (Pre-HTML) and bottom (Post-HTML) of the Person Entry fields. This is a great way to visually separate these questions from other items on the form.Autofill Current Person - If Rock knows who the person is (e.g., because they’re logged in), selecting this option will automatically fill in the Person Entry fields for them. That means the person filling out the form doesn’t have to give you information you already have. This is also a great way to fill in gaps in your data. For instance, if Rock has an email address for the person but not a phone number, then the person’s email address will be filled in for them, but they’ll still need to enter a phone number manually.Hide if Current Person Known - Selecting this option can help simplify your form by hiding all the Person Entry fields if Rock already knows who the person is. However, it also means that the person loses the opportunity to update their information. Either way, keep in mind that selecting this option doesn’t always mean the Person Entry fields will be hidden. For instance, if you set the Address field to be Required, and if the person doesn’t have an address in Rock, then the Person Entry fields will still be shown. This ensures the Required information can be collected.Record Status - Like the Connection Status, you can choose what Record Status a new person should have. This only applies to new records that are created.Connection Status - The person filling out the form may be new to Rock. In that case, the Connection Status you select here will be applied to the person’s record when it’s createdShow Campus - If selected, a Campus field will be available on the form. The campus field will be required and can be changed by the person.Campus Type/Status - If you have Show Campus enabled, you can use these fields to restrict which campuses are available for selection by the person filling out the form. For instance, you might use these to limit the options to Physical campuses that are Open.Person Entry Fields - This is where you get to select which Person Entry fields you want on your form. For instance, if you don’t want the person’s Address, then you can Hide that field entirely. You can also choose to make each field either Required or Optional based on your needs.SMS Opt-In - Allows the Registrant to permit or deny permission to be contacted via text messages at their mobile number. The Options for this field are Hide, Optional or Required.Address Type - Only one Address Type will appear on the form, and this is where you’ll select which one it should be. If the Address field is set to “Hide” then this setting won’t be referenced.Spouse Entry - Enabling this option will provide a duplicate set of Person Entry fields on the form for the person’s spouse. If “Optional” is selected, then the person will be given a Show Spouse checkbox on the form that they can click to show these additional fields. If “Required” is selected, then the spouse fields will always be shown on the form. Except for the First Name and Last Name, which are always required, the Person Entry fields for Spouse respect the Hide, Optional or Required settings of each other field. In other words, you can set Spouse Entry to be “Required” but the other fields for things like Email or Birthdate will still be hidden, optional or required according to your setup.Spouse Label - Sometimes it will make more sense to say “husband” or “wife” instead of “spouse”. You can change what "Spouse" is called on the form by providing a different label here. Just keep in mind that the spouse fields are only intended for spouses, regardless of what you call them. Changing the Spouse Label to “Child” doesn’t mean the form is now collecting information on the person’s child. If you want the person to provide information for anyone other than their spouse, you’ll have to add those fields to your form outside of the Person Entry Configuration area by adding workflow attributes.Person, Spouse and Family Attributes - You can store the person, their spouse and/or their family in a workflow attribute using these fields. The Person and Spouse attributes should be of type “Person”, while the Family attribute would be of type “Group”. Storing this information in workflow attributes lets you easily reference the people or family later in the workflow. This works for both new records and for existing records that are matched according to the information provided in the form.Race - You can choose to collect a person's race, which describes their physical traits and characteristics.Ethnicity - You can also choose to collect a person's ethnicity, which is a cultural identifier. Person Entry Matching Logic Below are a few notes on how person matching will work in certain circumstances. For the most part things will work as you expect, but there are a couple of scenarios to be aware of. Spouse Matching When the person fills out the Person Entry fields for themselves and their spouse, Rock will attempt to match both people to existing records in the system. If it finds a match for both people, but if those two people aren't in the same Family, then a new record will be created for the Spouse. This new record will be added to the Family of the person filling out the form. Autofill Name Changes There is some special logic that occurs if AutoFill Current Person is enabled, but the Name fields are changed when the form is being filled out. If the person that was used to auto-fill the fields changes the First Name or Last Name, then Rock assumes they mean they mean to create or match a new person. If this happens, this matched or new person won't be added to the current person's family. For instance, let's say Ted Decker is logged in and filling out a form with AutoFill Current Person enabled. Ted's information, including first and last name, will automatically be populated. But what happens if Ted changes the name to fill out the form for someone else? There are different scenarios as described below. Scenario 1: If Ted changes the Name fields to his son's name, Noah Decker, then Rock will check to see if there's enough data to make a match to the existing Noah Decker. However, a match to the existing Noah Decker would need to match Noah's email and/or cell phone too, so a new Noah Decker record could easily be created.Scenario 2: If Ted changes the Name fields to NewBaby Decker, he might be thinking he is adding his new baby to the family. Instead, the same logic described above will be used, where Rock will try to match the person or create a new person. In this case, NewBaby Decker will probably be a new person in a new family.Scenario 3: If Ted changes the Name fields to Bob Smith (Ted's neighbor), Rock will do the same thing as described above. A new person in a new family will be created unless a matching person record is found. In this case, Rock is doing what Ted probably expects to happen. Security Exceptions Don't forget that person matching may be suspended due to Account Protection Profile considerations. It's possible a new record will be created for this reason, even if the person has an existing record. See the Admin Hero Guide for details.