To help us understand this action better, let’s go back to the simple HR Position Request example from earlier, specifically the first entry form that Ted used to start the request. Below is a screenshot of the entry form action used in that workflow. Purpose - The Form Header is a great place to introduce the purpose of your form and any background knowledge that might be needed. As someone who uses Rock, we know you won’t make the mistake of writing a dry and impersonalized message. Instead, we're sure you'll remember to use Lava merge fields like {{ CurrentPerson.NickName }} to make your form feel personalized. That's just how you roll...Attributes - Next, you'll pick which Workflow / Activity attributes you want the person to complete. For each, you can select whether the fields are: Visible, Editable and/or Required.Logic - You can click the button next to any of the form fields to apply conditional logic. This allows you to configure this field to show or hide based on the value of other fields. For more details see the Conditional Logicsection below.Form Footer - The footer text is a great place to add information about what will happen next in the process.Commands - Finally, you can add differentCommandsto the form. These commands cause the entry form to be submitted and different parts of the workflow to be activated. We'll talk more about commands next. TipLearn MoreFor even more details about the Form action and the available options, be sure to check out the Workflow Actions Documentation.