Finally, we'll define the activities and actions for our workflow. The activities for this workflow are shown below. Note how the Initial Entry activity is in green. This means that it's configured to activate when the workflow is initially activated. Let's walk through each activity now to look at its actions. We won't look at each setting of each action, but we'll give you an idea of the purpose of each. Initial Entry The purpose of this activity is to get the person's position request details. Some of these details will depend on whether they are asking for a full-time or part-time request. Entry Form - Initial entry form that asks for details about the position. One of these fields, Type, will allow the person to note if the position is full-time or part-time.Persist - Next, we persist the workflow, now that the person has entered information, so that we can maintain the values over time.Requester - We can now set the requester for the workflow with the current person who just entered the form.Name - Another setup step is to provide the workflow with a name. This name will be used on the various grid displays.More Information - Now we'll start asking for more information. This next action will get further details if the person requested a full-time position. Note that an action filter limits this entry form to only be displayed when the person selectedfull-timeas the position type.Full Time - The next step sets the position hours to 40 if the person selected full-time, using action filters.Part Time - This action collects information for part-time positions. It also uses filter actions to only display when appropriate.HR Entry - Our final action activates the HR Entry activity to handle the next step. This action is set to mark the current activity as complete when it runs. HR Entry This activity is responsible for getting additional details from the human resources department. It has the following actions. Assign - The first action assigns the activity to Alisha Marble, the human resources representative for the organization. This tells the workflow who is responsible for entering the human resources information.HR Entry - The next and final action is the human resources entry screen. This entry form is set to email the assigned person when the action is active. This saves us from having to add our own email action. The command on this entry form is set to activate the next step, which is the approval process. Approval Process This activity is responsible for getting the approval for the position. Achieving this might be easier than you thought. Consider these actions. Approver - Just like the HR Entry, we assign this activity to the approver who was entered by human resources.Approval Information - Then we add an entry form to get the approval information. This form has two commands: one for Approve and the other for Deny. Each of these commands launches an activity to process actions for each response. This entry form also has to be configured to send an email. This email has the Include Actions In Email enabled, which allows the individual to approve or deny the request right from the email. Approved / Denied Activities These activities are configured pretty much the same way, so we'll look at them together. Approve or Deny - The first action marks the request as either approved or denied.Response to Requester - Next, we email the requester with the approval response.Response to HR - Then, we send an email to the human resources representative so that they are aware of the approval state.Complete - Finally, we mark the workflow as complete.