Similar to configuring a dynamic process context, which creates a unique name for each workflow execution, you can configure dynamic names for tasks and activities in a workflow. Just like configuring a dynamic process context, Dynamic Names are best used when you want task or activity names to hold unique values in the server and execution logs in order to ease finding them.
As shown in the image below, you can configure Dynamic Names for activities in the Property Panel after clicking on a Task Element. When you click on Use dynamic name and then on the small cube highlighted in red below, you will be prompted to choose the Workflow Variable or Business Entity field available from the task you've chosen. Double click on the field to move it to the dynamic name editor. In our example, we only have Workflow Variables configured for this task, but dynamic names can also be configured with Business Entities, or a combination.
Once you've chosen the Workflow Variable or Business Entity fields you need, you're already halfway to configuring the task's dynamic name. From the available workflow variable fields, we've chosen 'Water Plants' to be part of the title and have written 'Task:' before the workflow variable field in the dynamic name editor, as shown below. This will result in the name of the task changing from simply 'Task' to 'Task: Water Plants' if that is the assigned task in the previous workflow step.
Once you've started an execution of the workflow, the dynamic name is resolved at the beginning of its step in the workflow and is not updated afterwards. You can view the dynamic name change in the FireStart Client Workflow Execution Canvas (shown below) or in the Process Portal.
As you can see, the name has changed in the workflow execution view to correspond to the dynamic name configuration we set up in the workflow model itself and now reads 'Task: Water Plants'. The dynamic name also becomes the Name of the Step in the Server Logs and Execution Logs. The dynamic name as the Name of the Step is shown in the image below from the workflow execution logs in the Process Portal.
