The Activate Actions activity is like a clear history button for the current activity. When this action is run, all actions for the current activity are set back to Uncomplete. So next time this activity is processed, all actions will be run again. The current processing will continue however, so further actions will execute and possibly be completed. Normal use of this action would be to place it at the end of your activity.

This action will launch (aka activate) a new activity of the type that you choose. This action is used heavily to control the branching logic of the workflow. The use of action filters is very powerful with this action.

Activities can be assigned to a person or group to help distinguish who is responsible for ensuring that the activity is completed if there are manual steps to complete. This action will set the assignee of the current activity to the value of a workflow attribute.

These three actions do very similar things, so we'll group them together. Like the previous action, they set the assignee of an activity based on a provided person, group or security role. It’s best to avoid assigning actions to a specific person because you'll need to maintain this assignment as individuals transition into new roles.

This action is pretty obvious. It marks the current activity as complete. The activity will not execute any more actions.

Temporarily pauses execution of the current activity until the set value is reached. The three value options are:

• Minutes To Delay: This delays for a set number of minutes.
• Date in Attribute: This delays until the Date in the selected Attribute is reached.
• Next Weekday: This delays until the next selected weekday (next Thursday, for example).

This action will present a person with a document that they need to sign electronically. The Signature Document Template must be configured in advance under Admin Tools > General Settings > Signature Documents. Person attributes can be used to define the person the document applies to, the person assigned to sign the document and the person who signed the document.

After the electronic signature is captured the person is asked to provide an email address so they can be sent a copy of the document for their records.

The Form action is one of the most powerful actions in Rock. It allows you to take input from a user and place it into the values of workflow attributes. Let's dive down into the details of this incredible action looking at each setting.

• Notification Email: This sends a selectable System Email Template out to the activity's assignee(s) when the action is reached during processing. This helps alert them that an entry step is waiting for them. This email can include links to the commands that are defined for the action. For instance, if one of the entry commands is Approve, you could include the approve link in your email so that the person could skip the step of visiting the form.
• Enable Note Entry: Enabling this will provide an area where the person can write notes in addition to the rest of the form. This is a great way for people to communicate with the next person in the process, or to track information that may not be stored as attributes.
• Enable Person Entry: Checking this box will cause the “Person Entry Configuration” section to appear within the Form configuration. Rather than manually creating individual workflow attributes for things like the person’s name, email, phone number or address, you can select what you want to ask and it will be added to the form for you automatically. You also have the option of asking for Spouse information. If the person or their spouse isn’t in Rock then this action will create a record for them. You can set the Person Attribute, Spouse Attribute and Family Attribute fields to store this information for either newly created or existing records, for use later in the workflow. On top of that, you can also enable Hide if Current Person Known to hide all the person entry fields if Rock already knows who the person is. Note, the fields will still show on the form if one of them is required and if that piece of information is not in Rock for the person.
• Form Header: This is a textbox that allows you to enter HTML combined with lava merge fields. This is a good place to add instructions for the user and help introduce them to the form they are about to complete.
• Form Fields: Next you'll see a list of all the workflow and activity attributes available. You can select which are visible, editable and required for the entry form. You can apply conditional logic to each field so that it only appears to the person if they give certain responses on other fields.
• Form Footer: Like the header, the footer allows you to enter HTML mixed with lava merge fields to help provide any closing content you would like.
• Commands: Finally, you have a list of commands to display at the end of your form. Each of the commands will be displayed as a button at the bottom of your form. The Command Label will be the label on the button. The Button Type describes what button style to use (these are defined under Admin Tools > General Settings > Defined Types > HTML Button Styles.) Next you can define an activity to run when the button is selected. This is very helpful for providing branching logic in your workflow. Finally, you can provide response text that the user will see when the action has been selected. Note that if a secondary form is available after the current form, this response text may not be shown. Instead the user will be taken directly to the second form.
• Command Selected Attribute: This optional setting allows you to insert the command label that was selected into the contents of an attribute. This is helpful when you're not activating activities from the actions.

This workflow action is the reverse of Set Attribute to Initiator. It allows you to change the Initiator to the value of an attribute.

Logs an error into the worflow's error log.

This action takes the user to a different screen after the workflow action is complete. You can set the action to redirect to either a URL or a URL Attribute.

The Processing Options field allows you to set how the workflow should continue:

• Always continue: Sets the workflow to continue processing regardless of the redirect status or if the action is running in the background.
• Only continue on redirect: Sets the workflow to only continue processing when the redirect is successful.
• Fail and Stop v16.7 (or Never continue): When this option is selected, the action will be marked as failed (error) and will not complete. The workflow will always fail/error at this point unless the "Run If" filter criteria cause this action to be skipped.

This action will add a new workflow note. The note property has the ability to customize the message using Lava. You can also customize the formatting of the note by selecting the Note Type. More on using workflow notes is discussed in the Workflow Notes article.

This is the Game Over action that marks the entire workflow as complete. No other activities or actions will be processed.

Simply put, deletes the current workflow instance.

This action allows you to display a large amount of information in the WorkflowEntry block, typically on the screen that appears after a person completes and submits a Form action. The HTML field takes either HTML or Lava, which means you have a lot of control over the formatting and display of the content.

See the article on persistent vs. non-persistent workflows to get a deeper understanding of this topic. This action marks the current workflow as persistent.

There is an optional parameter called Persist Immediately. Normally this action will cause the workflow to be persisted (saved) once all the current activities/actions have completed processing. Set this flag to true if the workflow should be persisted immediately. This is only required if a subsequent action needs a persisted workflow with a valid id.

This action will set the campus of the workflow using the given Campus attribute or the primary campus of the given Person attribute. If both are given, the Campus attribute will be used. If neither are given, the action will return an error.

This action will set the name of the workflow. This name will appear in the various workflow lists you use to manage and process your workflows. The text field of this action can use Lava merge fields to help you craft effective names. Many times these names will simply come from an attribute value that is entered through a user entry form.

This action sets the status of the workflow. The workflow status is simply a text field so you can set it to any value you choose. This field supports the use of Lava merge fields.

This action allows you to set the status of a different workflow. The workflow status is simply a text field so you can set it to any value you choose. This field supports the use of Lava merge fields. You can also query for the status using SQL commands. The "Process Target Workflow" option allows you to decide whether or not to run the targeted workflow after its status is set.

Every workflow has a log. Usually there's not much in them. But sometimes, it's useful for you to be able to write what's happening or what the value of an attribute is at a certain point in the workflow. Use this action to write an entry in the workflow's log. It supports Lava, of course!