This workflow action will inactivate a given person's entire family, all of their families or only the individual.

The Multi-Family Logic setting controls exactly who is inactivated:

1. Inactivate individuals in the primary family
2. Inactivate individuals in all families
3. Inactivate just the individual

Additional action settings allow you to set the Inactive Reason and provide an Inactive Reason Note.

Allows you to update a person's address based on a provided location.

Here's an overview of the settings available for this action:

• Person: This is the workflow or activity attribute that contains the person whose family address should be updated.
• Location Type: If an attribute is entered for the Location Type (From Attribute) setting, this value will first be checked to see if there is a valid location type specified. If so, it will be used to determine the location type to update. If it is not specified, or is not valid, the Location Type setting will be used to determine the location type to update.
• Location: The address to set the person's family address to can either be entered explicitly or set from a workflow or activity attribute. If the address is not being read from an attribute, enter the address in this field.
Location (From Attribute): If you'd like the address to be set from one of the workflow or activity attributes, select the attribute here. This will only be used if the Location field is blank.
• Is Mailing Location: If you'd like to update the flag that determines if the address is a mailing location, you can enter a value here, or select an attribute. The value you enter or the value returned by the attribute should be either 'True', 'Yes', 'False', or 'No'. Any other value will be ignored.
Is Mapped Location: If you'd like to update the flag that determines if the address is a mapped location, you can enter a value here, or select an attribute. The value you enter or the value returned by the attribute should be either 'True', 'Yes', 'False', or 'No'. Any other value will be ignored.

This action will take a first name, last name, email, mobile number and birthday and search for a matching person in the database. The result will be placed into a selected attribute. If no person was found a new record will be created for you. If a match is found, it does not update the person record with any of the supplied values except the email address if enabled by the action setting.

The record with the highest score greater than 35 points is selected as the match (if no records score more than 35 points a new record will be created).

• First/Nick Name match = 15 points.
• Last Name match = 15 points.
• If Last Name doesn't match but previous name does = 12 points.
• Mobile Phone OR Email match (or both) = 15 points.
• Month/Day match with the birthdate = 10 points.
• Year match with the birthdate = 5 points.

Other similar routines (presumably registration, etc) in Rock also consider:

• Gender Match = 3 points
• Suffix Match = 10 points

Sets the selected person attribute of the person contained in a workflow attribute to either text you provide or the contents of another attribute.

This action uses two Person attributes to add a single person to a different family. The person will be added to the family of the person in the 'Add to Family With' attribute.

You can optionally assign a Role (Child or Adult) to the person being added using either a fixed value or a 'Group Role' attribute for the Family group type.

The person being added to the family can either remain in their old family or be removed from it, using the 'Remove Person From Current Family' setting.

This action allows you to set a person to follow a designated entity. The "Entity To Follow" field is where you enter an Entity Id or an attribute that contains the person or group to follow. This field supports Lava.

If you are trying to mimic what happens when a person follows another person (by clicking their photo), the Entity Type should be set to "Person Alias" and the Entity To Follow must be set to the followee's PersonAliasId.

In v13, we made this easier to do. When the Entity Type is "Person Alias", if your Entity To Follow attribute holds a Person (field type), Rock will automatically use the PersonAlias Id from the fieldtype instead of the usual PersonAlias Guid (which would not otherwise work). v13.0

Use this action to find Campus Team members and place them in a workflow attribute for use in later actions. You can provide a person attribute to find team members at that person’s campus.

If a campus attribute is provided, only team members from that campus will be returned. The campus in this attribute will be used regardless of the person’s campus, in cases where both attributes are provided.

Returns the person's spouse to a selected workflow attribute. When determining the spouse the action will look for an adult in the same family who is of the opposite gender and married. If more than one person is found then the first person will be returned.

Sets the configured Boolean workflow attribute to True or False depending on whether or not the configured Person is in the selected Data View.

This action adds a note to a person record. Optionally, you can set a caption, set the note author or mark the note as an alert.

Updates a person's phone number.

Here's an overview of the settings available for this action:

• Person: This is the workflow or activity attribute that contains the person whose phone number should be updated.
• Phone Type: If an attribute is entered for the Phone Type (From Attribute) setting, this value will first be checked to see if there is a valid phone type specified. If so, it will be used to determine the phone type to update. If it is not specified, or is not valid, the Phone Type setting will be used to determine the phone type to update.
• Phone Number: The phone number to use when update the person. The number can either be set explicitly or set from a workflow or activity attribute.
• Unlisted: If you'd like to update the flag that determines if the phone number is an unlisted number, you can enter a value here, or select and attribute. The value you enter or the value returned by the attribute should be either 'True', 'Yes', 'False', or 'No'. Any other value will be ignored.
• Messaging Enabled: If you'd like to update the flag that determines if the phone number has messaging (SMS) enabled, you can enter a value here, or select and attribute. The value you enter or the value returned by the attribute should be either 'True', 'Yes', 'False', or 'No'. Any other value will be ignored.
• Ignore Blank Values: If you do not specify a phone number, or you are setting the phone number from an attribute and that attribute is blank, this flag indicates if the phone number should be updated to a blank value or not.

Updates a property (name, email, connection status, etc.) of a person. This action will work with either a value you provide (Lava enabled) or an attribute value. When providing an attribute the value in the drop-down gives you a hint as to what type it should be. See the 'Additional Details' section below for more information.

Here's a couple of other tips to help you with this powerful action.

• When dealing with a property that is a defined value (like 'Title') you may either provide it with:
  1. An attribute of type Defined Value
  2. The Guid of the defined value
  3. The string representation of the defined value (e.g. 'Mr.')
• With properties that represent Enums (like gender). You can provide either the Enum as a string or an integer. The valid values are listed in the drop down.

Adds a person, stored as a person attribute, to the provided Organization Tag. If the supplied tag does not exist it will be created.

Like the Person Tag Add, this action removes a person from an Organization Tag.

This workflow action will add a Prayer Request for a person. The attribute values you provide related to the request, like the Category or Public options, will be included in the Prayer Request that's added.

It's important to note that you can provide the requestor in one of two ways:

1. As a person object through the entity passed to the workflow, or a standard workflow attribute that references a Person.
2. By providing a first name, last name and email address. If you choose this approach, you have additional options. If Person Matching is enabled then you can use the information to create a new person record, or match to an existing record. Or, you can disable Person Matching entirely to prevent the request from being linked to a person's record.

This action adds a reminder to the provided person's record. You can set the note text, the date for the reminder, how frequently the reminder is repeated, and how many times to repeat the reminder.