System field

Navigation steps

Resulting path

Note: These examples are for a document template that is based on a custom object.

Project Name

1 name (ok)

.name

Project Number

1 numberString (ok)

.numberString

Project's Default Category

1 defaultCategory-> (traverse)

2 name (ok)

.defaultCategory.name

Contact-centric contact's last name

1 contact-> (traverse)

2 name (ok)

.contact.name

Contact-centric contact's first name

1 contact-> (traverse)

2 firstName (ok)

.contact.firstName

Contact-centric contact's default address

Must have a separate merge field for each field in the address. Example navigation:

1 contact-> (traverse)

2 defaultAddress-> (traverse)

3 street (ok)

Examples:

•contact.defaultAddress.street

•contact.defaultAddress.city

•contact.defaultAddress.state

•contact.defaultAddress.postalCode

Main assignee's last name

1 mainAssignee-> (traverse)

2 user-> (traverse)

3 contact-> (traverse)

4 name (ok)

.mainAssignee.user.contact.name

Main assignee's first name

1 mainAssignee-> (traverse)

2 user-> (traverse)

3 contact-> (traverse)

4 firstName (ok)

.mainAssignee.user.contact.firstName

Main assignee's role

1 mainAssignee-> (traverse)

2 type-> (traverse)

3 name (ok)

.mainAssignee.type.name

Current Phase

1 currentPhaseType- > (traverse)

2 name (ok)

.currentPhaseType.name

A system field from the parent record of the project

1 parent-> (traverse)

2 Then, navigate as described for the needed parent system field.

Examples:

•.parent.numberString

•.parent.mainAssignee.user.contact.name

Name of an assignee with a certain role

Map a loop@ merge field to assigneeList->, as described in loop@ Merge Field Mapping.

Or, map a filter@ merge field to assigneeList-> if you want the user to select the assignee. See filter@ Merge Field Mapping.

A system or custom field from a child record of the project (or from an embedded object record)

Map a filter@ merge field to childList->, as described in filter@ Merge Field Mapping.