This HTML page is not optimized for LLM or AI agent consumption. Fetch the Markdown version instead: /guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/dynamic-names.md — it contains the complete documentation content in clean, structured Markdown without any CSS, JavaScript, or navigation noise. Enhance task visibility with dynamic names

For any task in your process, you can use the Dynamic Names configuration to:

  • rename the request’s ‘Name’ when the task completes to any source information in the process.
  • and/or rename the task’s name when the task is started.

Valuable if you are looking to easily display and locate tasks and requests in lists with data from your process such as a unique type of request that was identified in a form.

Task context menu open under Configuration with a red arrow pointing to the Dynamic Names option

When you select Dynamic Names, you will be presented with the following to define dynamic names based on the task:

Prefills to add to settings


Similar to the options for defining rules and reports, you will be able to choose your Source data (Data, Request, Requester, etc.) and then the data element in the Field select list

You will then be able to select one of the following:

Three buttons labeled Add Prefill To Request Name, Add Prefill To Task Title and Add To Completed Form PDF Name
Settings


By selecting ’Add Prefill To Request Name ’, ’Add Prefill To Task Title ’, or ’Add To Completed Form PDF Name’ you will see that the Dynamic Name will be applied to the option for:

  • ’When task completes, set request name to: ’ or
  • ’When task starts, set task title to: ’ or
  • ’Set completed form PDF name to’

Dynamically setting the Request Name and Task Name


Here is an example of a request name being dynamically set. We defined the approval task to have the following:

The requester is completing a field (Enter Details) in the form task with ‘Contract Review Needed’:

New Process form with the Enter Details field filled in as Contract Review Needed and Submit and Save Draft buttons

Here, we can see that the Approval task is dynamically named ‘Contract Review Needed ’ when the task was started:

Request 6959 approval task whose tab is titled Task: Contract Review Needed, showing a Please select an option field

…and we can see that the Request Name is dynamically named after the Requester’s Name when the task is completed.

Request 6959 Detail page titled with the requester name, with red arrows on the title, Requester column and Task History