WarpCore

What you need to know

Fields lists the values each project of this template records. A holds a yes or no answer, text, a number, a date, or one option of a choice. People fill the values in on the project's page. A on a task or a transition tests them, so add the fields before the tasks that depend on them.

A field can also belong to each task instead of to the project: tick For each task, and each task fills it in for itself, such as the description of a ticket. Such a field is not in the project's Fields: the person who files a ticket fills it in, and the ticket shows it when it is opened. No condition tests it. A field marked Required must have a value before the ticket is filed. See File a ticket.

How to get here

In the template editor, select Fields in the left menu. It comes after Outcomes and before Tasks.

What is on this screen

Under Field list, one row per field, in the order they were added. Under Add a field, a Name, a Type, and Add field.

Part	What it does
The name	What the project page calls the value. Type a new name, then select somewhere else.
The type	Yes/no, Text, Number, Date or Choice. See Field types and comparisons.
Required	Marks the value as required on each project: “Shown as required on each project. Work is not stopped while it is empty.”
For each task	Ticked, each task holds its own value of the field: “Each task fills this in for itself, instead of one answer for the whole project. Conditions cannot test it.”
The trash icon	Deletes the field, after a question.
Options	On a choice only: the options a person picks from. Type one and press Enter. A comma does not split an option.
Shown answer	On a choice only, at the end of its options: where an answer shows on a task's card. When the field holds one answer, the card of one task shows one line, for every piece of work of the same engagement. Once set, it also reads the answer and the task, for example Edited at S73. Select it to see or change the Task, the Answer and the Line.

No records

What you can do here

Add a field: type its Name, choose its Type, and select Add field. Set the rest after.
Rename a field, change its type, or mark it Required or For each task.
Give a choice its options, or take one away with the × on it.
Show a choice's answer on a task's card: select Shown answer, pick the Task and the Answer, type the Line the card shows, and select Save. The task can belong to another template of the department, such as an engagement's task that shows an answer recorded on a property's work. To stop showing it, select Clear.
Then make a task depend on a value: Make a task depend on a value.

Who can do what here

A department manager or a company administrator changes the fields of a draft. Anyone with a role in the department can read them. On a published or retired version, the rows are grayed out and Add a field is not shown. A Shown answer that is set still opens, to show its setting, with nothing to change.

Things to know

A field that a condition tests cannot be deleted, its type cannot change, and it cannot become a field for each task. A message says which condition still tests it, on a task or on a transition. Remove that condition first.
Changing a choice to another type deletes its options, so it asks first: “Only a choice has options, so its options are deleted.” Its Shown answer is deleted too.
The option a Shown answer uses cannot be taken away. The option stays, and a message names the field and the answer and ends “stays an option. Change or clear its Shown answer first.” To rename that option, add the new name as an option, set the Shown answer to it, then take the old option away. See Removing an option was refused.
Deleting a field asks first: “Projects already running are unaffected — this edits the draft only.”
A choice can have up to 100 options.

Good to know

Required does not stop any work. A project starts with every value empty, so the mark only tells people which values to fill in.