---
title: "Person Attributes Form Advanced Block"
canonical: "https://docs.kingdomfirstsolutions.com/space/RPD/43810835/Person%20Attributes%20Form%20Advanced%20Block"
format: markdown
---
## Summary
---
This block is an advanced version of the core Rock Person Attributes Form block. It adds the following functions:
- Ability to use Person Fields in the forms.
- Ability to pass a Connection Request to the workflow upon form completion.
- Ability to add a Person to a Group upon form completion.
- Ability to create a Connection Request upon form completion.
- Ability to have the person sign a signature document as part of the form.
## What’s New
---
The following new goodness will be added to your Rock install with this plugin:
- **New Block:** Person Attribute Forms Advanced
## Using the Block
---
**This block requires a person to be logged in for them to complete a form.**
Each form you create in the block will appear to the user as another form page. If you have 2 forms, they will complete the first form, hit next, complete the second form, and hit finish.
Any Person Attributes you wish to access with this block must be set up under Admin Tools > General Settings > Person Attributes. This block will allow people to edit their attributes regardless of the attribute permissions.
#### Groups
Imagine you have a youth group that will be going to an event in your community. There is no cost, so Event Registration feels too complicated. You really just need some basic information and to add them to a group.
You can set up this block to require them to update their contact information and any person attributes, like emergency contact information or shirt size. With this block, you can use the group settings to allow you to pass a Group Guid or Group Id to the block in the URL. You can also specify a specific group in the block settings and not need to pass the information in the URL. After the user completes the form, their person fields and attributes will be updated and they will be added to the group. You can also launch a workflow using the new Group Member as the entity to send welcome emails, notify group leaders, etc.
#### Connections
Wanting to create a volunteer application? This block is your friend! There are 2 ways you can use this block with Connections.
The first way is to pass the Connection Opportunity Id in URL to this block. Your new volunteer then fills out your form with your choice of person fields and attributes. Once they submit their form, their person record is updated and a connection request is created for them within the connection opportunity. You can launch a workflow with the newly created connection request as the entity to send follow up emails, launch other workflows, etc.
The second way is to pass a Connection Request Id in the URL to this block. Doing this works with the Workflow setting on the block and sets the entity of the workflow to that connection request. When a new connection request is created, email the volunteer a link to this form with the connection request id passed in the URL. The volunteer completes their application, and the connection request is passed to the workflow selected in the block settings. This follow up workflow can be built to do whatever is needed for your process. You may want to notify the connector that their application is complete, launch another workflow to contact their references and send a thank you email to the volunteer.
The possibilities are endless. Want to automate your process for baptisms? Need a new process for managing applications for potential small group leaders? Gathering applications for a missions trip? Because this block ties in with groups, connections, and workflows, you are limited only by your creativity.
## Block Settings
---
| | |
| --- | --- |
| [1] | **Display Progress Bar:** Displays a progress bar to the user indicating how far along they are in filling out multiple forms. Not shown when there is only one form. |
| [2] | **Workflow:** An optional workflow to launch after the person has filled out all forms. |
| [3] | **Done Page:** An optional page to redirect users to after they have completed all the forms. |
| [4] | **Save Values:** Determines if values should be saved each time the user progresses to the next form or not saved until the end. An advantage of saving them on each form, saved values can then be used in the header and footer of following forms using Lava. |
| [5] | **Workflow Entity:** The entity that should be used to initiate the workflow. Options are “Person,” “Connection Request,” or “Group Member.” See further notes below for details on using Workflow Entities. |
| [6] | **Signature Document: **Select a signature document template to be attached to this form when it is filled out. |
| [7] | **Confirmation Text:** The message to display after all forms are completed if Done Page is not set. |
#### Workflow Entities
- If the block is passed a valid Connection Opportunity Id in the URL, a new Connection Request will be created in that opportunity when the form is completed. You can use that new Connection Request as the Workflow Entity.
- If the block is passed a valid Connection Request Id in the URL, that Connection Request can be used as the Workflow Entity.
- If the block is passed a valid Group Id or Guid in the URL, the person will be added to the group when the form is completed. That new Group Member can be used as the Workflow Entity.
- You can always use the Person as the Workflow Entity.
| | |
| --- | --- |
| [7] | **Form Title:** Each form can have a unique title. {{ Lava }} |
| [8] | **Form Header:** An optional HTML header that is unique to each form. {{ Lava }} |
| [9] | **Adding Fields:** Each form may have as many fields as you like. |
| [10] | **Form Footer:** An optional HTML footer that is unique to each form. {{ Lava }} |
| [11] | **Fields:** The label for each form field. If you would like to reorder field, use the 3 bar handle next to the field label. |
| [12] | **Source:** Displays whether this is a Person Field or a Person Attribute. |
| [13] | **Type:** Displays the field type for the Person Field or Attribute. This cannot be changed from within this block, but it will be helpful for knowing how the field will display on your form. |
| [14] | **Use Current Value:** Shows if the field is set to use the Person's current value for this field. |
| [15] | **Required:** Shows if the field is required for form submission. |
| [16] | **Add Form:** You may add as many forms as needed to this block. Forms will display in the order shown. |
## Block Properties
---
| | |
| --- | --- |
| [1] | **Name:** Name of the block. |
| [2] | **Display Family Member Picker:** Change to “yes” to display the Family Member Picker on the form. |
| [3] | **Display SMS Checkbox on Mobile Phone:** Select “yes” to show the SMS checkbox when a mobile phone is displayed on the form. |
| [4] | **Person Mode:** This is a person select mode. Select which type of person should be visible - family members, any person guid, or logged-in user only. |
| [5] | **Allow Connection Opportunity:** Determines if a URL parameter of OpportunityId should be evaluated when complete. |
| [6] | **Allow Group Membership:** Determines if a URL parameter of GroupGuid or GroupId should be evaluated when complete. |
| [7] | **Enable Passing Group Id:** If enabled, allows the passing of the GroupId instead of the GroupGuid. |
| [8] | **Allowed Group Types:** This setting restricts which types of groups a person can be added to, however, selecting a specific group via the Group setting will override this restriction. |
| [9] | **Group:** Optional group to add the person to. If omitted, the group's Guid should be passed via the query string. |
| [10] | **Group Member Status:** The group member status to use when adding person to group. |