Commands allow people filling out the form to execute different logic based on their selections. For instance, on an approval entry you might add two commands of Approve or Deny. Depending on which command is selected, different activities and/or actions can be run. There are two different ways commands can trigger logic. Let’s consider both in detail. Commands That Launch Activities You can have your commands activate new activities when they are selected. You do this by selecting the activity using the Activate Activity property of the command. When selected, the command will activate the selected activity. Commands That Set Attributes Sometimes you may not want to launch a new activity based on a command. Instead, you can use actions within the same activity to process any next steps. In these cases, simply leave the Activate Activity field empty. When empty, the next action in the current activity will be executed when the entry form is completed. You can even have the command that was executed entered into a workflow attribute using the Command Selected Attribute. This is helpful when multiple commands are available, and you'd like to know which one was selected. When To Launch New Activities You might be wondering when you should launch new activities and when you should not. The choice is really up to you. But here are a couple of thoughts to help you drive your decision: In approval forms it's common for each option to launch a new activity. This allows the decision-making logic to be clearly separated into different activities.If you're using form chaining (more info below) based on a person's input, you may elect not to use new activities.