Template Variables & Filters

Workflow Docs uses a combination of Built-in Variables (nouns that are ready to use) and Reserved Keywords (names that must be avoided).

1. Reserved Keywords (Do Not Use)

These names are reserved by Python or Docassemble. Using them as your own variable names will cause errors or unexpected behavior:

if	else	elif	for
while	in	is	not
and	or	def	class
import	from	as	return
try	except	finally	raise
None	True	False	self
dict	list	set	str
int	float	bool	type
metadata	modules	objects	buttons

For a full list of Docassemble-specific reserved names, see the AssemblyLine documentation.

2. Built-in Variables (Nouns)

Workflow Docs pre-defines many common legal nouns. These are not just names; they come with "smart" questions and logic.

• People Lists (ALPeopleList): clients, other_parties, children, witnesses, defendants, plaintiffs.
• Individuals (ALIndividual): advocate, spouse, notary_public, legalserver_primary_assignment, legalserver_current_user.

Jinja2 Syntax: Always wrap variables in double curly braces {{ }} to add them to your template. Access specific attributes using dot notation, and access items in a list using index notation:

{{ clients[0].name.first }}
{{ advocate.name.last }}

3. The ask and request Filters

These filters are the primary way to interact with users and external parties.

• ask Filter: Use this when the initiator (the person running the interview, like an advocate) needs to provide the answer right now.
• request Filter: Use this to route the variable to an external requestee (like a client or third party). They will receive an email or SMS asking them to complete that specific field (e.g., signing a document).

Jinja2 Syntax: Filters are applied by using the pipe character | after a variable name.

Filter Options

Both ask and request accept several options to customize the field:

Option	Description	Example
question	The main question text.	{{ var_name | ask(question="Name?") }}
subquestion	Extra help text or instructions.	{{ var_name | ask(subquestion="First and last") }}
label	A short label for the input field.	{{ var_name | ask(label="Middle Initial") }}
datatype	The Docassemble datatype.	{{ var_name | ask(datatype="date") }}
options	A list of choices (for radio/dropdown).	{{ var_name | ask(options=["Yes", "No"]) }}
default	The default value for the field.	{{ var_name | ask(default="English") }}
hint	Placeholder text inside the input.	{{ var_name | ask(hint="MM/DD/YYYY") }}

Complete Examples

Here are some complete examples showing how to use these filters:

Asking the initiator for a date:

{{ custom_date | ask(question="When did the incident occur?", datatype="date") }}

Requesting a signature from a client:

{{ clients[0].signature | request(question="Please sign the agreement", datatype="signature") }}

Allowed Datatypes

Workflow Docs supports all standard Docassemble datatypes, including:

• text (default), area (large text)
• date, datetime, time
• number, integer, currency
• email, url, file
• yesno, yesnomaybe
• radio, dropdown, checkboxes
• signature

---

4. LegalServer Data Integration

Variables starting with legalserver_ are automatically pulled from your case.

• legalserver_case: A helper object for accessing core case fields.
• legalserver_data: The raw JSON dictionary from the LegalServer API. See the LegalServer Data Reference for a detailed field map.
• legalserver_matter_uuid: The unique ID of the case.
• legalserver_site_abbreviation: Your site name (e.g., legalaid).

Jinja2 Syntax:

{{ legalserver_matter_uuid }}
{{ legalserver_data.county_of_residence }}

View the Full Variable List for a complete map of every LegalServer field and its alias.