--- title: "Task dialogs: fields of a task" slug: "task-dialogs-filling-in-the-fields-of-a-task" updated: 2026-11-10T15:33:48Z published: 2026-11-10T15:33:48Z canonical: "knowledgecenter.docuware.com/task-dialogs-filling-in-the-fields-of-a-task" --- > ## Documentation Index > Fetch the complete documentation index at: https://knowledgecenter.docuware.com/llms.txt > Use this file to discover all available pages before exploring further. # Task dialogs: fields of a task A workflow task asks you for a decision and, often, for information: an amount, a date, a cost center, or the name of the colleague who should check the next step. The person who sets up the workflow decides which fields the task displays and which it accepts. This article explains the kinds of fields users who complete a task meet in the **Process this task** section of a task and how to fill them in, whether you work in the side panel or on the details page. How to open and complete a task is described in [Tasks: completing workflow tasks](/help/docs/workflow-tasks-docuware-web-client). **Supported versions:** DocuWare Cloud + new DocuWare client only **On this page** - [How a task form is built](/help/docs/task-dialogs-filling-in-the-fields-of-a-task#how-a-task-form-is-built) - [What applies to every field](/help/docs/task-dialogs-filling-in-the-fields-of-a-task#what-applies-to-every-field) - [Field types](/help/docs/task-dialogs-filling-in-the-fields-of-a-task#field-types) - [When the task cannot be completed](/help/docs/task-dialogs-filling-in-the-fields-of-a-task#when-the-task-cannot-be-completed) #### Coming from the classic DocuWare client? In the classic client, open the new DocuWare client with the link **Open new DocuWare**. The fields of a task are the same in both clients, because the workflow defines them. These are the differences. - **Decisions** are now **process options**. - Missing or invalid entries are listed in a summary at the top of the form, with a link to each field. - User fields show people by their real name when the workflow is set up that way; in the classic client this works since DocuWare 7.15 as well. - The new DocuWare client is available in DocuWare Cloud only for now. On-premises systems continue to work with the classic client. - View [all current limitations of the new DocuWare client](/help/docs/docuware-web-client-key-features-and-limitations) ## How a task dialog is built Every task form has the following structure: - **Task overview**: The workflow name, the due date, the assignees, and the key data of the document. - **Process this task**: For example, **Approve** or **Reject**. The task fields, such as an amount, a date, a cost center, or the name of the colleague, are displayed based on the options defined in the workflow. - **Submit** completes the task. ![](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image-1791793852916.png) Fields marked with an asterisk are required. Fields that you cannot type into are read-only, the person who created the workflow uses them to show you information. For example. the invoice amount or the current status. ## What applies to every field - **Prefilled values**: Many fields already contain a value when the task opens, taken from the document, from an earlier step, or from a fixed default. You can change it unless the field is read-only. - **Select lists**: Some fields offer a list of values; in this case, you must select an option from the list. - **Field masks and limits**: A text field can require a certain pattern, for example, an order number with a fixed format, or limit the number of characters. The form tells you when an entry does not fit. - **Entries on the stamp**: When you complete a task with a stamp, the designer can show your entries on the stamp, so they stay visible on the document. More about [Completing a task with a stamp](/help/docs/workflow-tasks-docuware-web-client#completing-a-task-with-a-stamp). ## Field types The person who configures the workflow sets the type of each field. The type determines what the person completing the task can enter. When users complete a task, they will fill in each field of the task dialog according to its type. The following sections describe the types that can be met. ### Text and keyword fields A text field accepts free text. A keyword field accepts several values. Enter one value, confirm it, and add the next. Both field types can have a character limit, a field mask, and a select list. ### Integer and decimal fields An integer field accepts a whole number. A decimal field accepts a number with decimal places. The decimal and thousands separators follow the regional settings. ### Date and date-time fields Pick a date, or a date with a time, from a calendar. Alternatively, type it in the format of the regional settings. ### User, role, and substitution rule fields Choose a person, a role, or a substitution rule from a list, for example the colleague who should check the document next. The list shows people by their real name, as Meyer, Anna or Anna Meyer, or by their login name. The person who configures the workflow decides which one is shown. To find a person, type part of a name. The search matches any part of the displayed name. If two people share the same name, their login names are added in parentheses. ![User field in a task with people listed as last name, first name](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/base64-converted-image-1791793480640.png) *People in a user field, listed as last name, first name.* ### Link and description fields A link field holds a link, for example, to a ticket in another system; select it to open the target. ### Table fields A table field shows the rows of an index table of the document, for example, the line items of an invoice with cost center and amount per line. You edit the cells the person who created the workflow left editable; each column behaves like the field type it is based on, so a date column opens a calendar, and a select-list column offers values. Columns the person who created the workflow hid are not shown. A table can also be read-only. ## Notes for administrators - The fields of a task form are defined in the Workflow Designer under **Task > Decision > Dialog**; the available types and their options are described in [Creating tasks for decision makers](/help/docs/webbased-workflow-designer-tasks). Nothing has to be set up again for the new DocuWare client. - The **User display name format** option in the Workflow Designer now applies in the new DocuWare client as well. For a field of the type **User** in a task dialog, it decides whether the user picker shows the login name, first name and last name, or last name and first name. Select the **Task** activity, open its dialog configuration, select the User-type field, and set the format; then publish the workflow. The default display name is the login name. The field still stores the login name, so later workflow steps, reports, and integrations see the same value as before. - Users without a first and last name in user management are shown by their login name. With a real-name format, searching by login name finds nothing in the new client. If a user reports that a colleague "cannot be found anymore", check the format set on the field. ![User display name format setting of a User-type field in the Workflow Designer](https://cdn.document360.io/0108e24e-b3e8-446c-b670-66b1d2a9e861/Images/Documentation/image-GBP5B1YD.png) - Whether a changed prefilled value reaches the index entries of the document depends on the **Data assignment** of the decision. - Validation rules and their error messages are defined under **Decision > Validation**.