> For the complete documentation index, see [llms.txt](https://dev.realpadsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.realpadsoftware.com/placeholders/document-templating/reclamation-documents.md).

# Reclamation documents

This document lists all available placeholders for Reclamation Documents:

* *Defect received from client confirmation*
* *Reclamation protocol*
* *Reclamation protocol general contractor*
* *Supplier reclamation protocol*

## Overview

This printer provides Reclamation-specific placeholders for defect management and reclamation protocols. Reclamation documents are generated for individual Reclamations or specific Defects and include Deal-level information, Customer details, Unit attributes, and a list of Defects with their properties.

***

## Simple Placeholders

### Date and Identification

#### `$today`

Current date when the document is generated.\
**Type**: DateWrapper

#### `$dealId`

Unique identifier of the Deal (numeric ID as string).\
**Type**: String

#### `$reclamationInternalId`

Internal ID of the Reclamation. Empty string if no reclamation.\
**Type**: String | **UI**: "Reclamation No." (`business_case_reclamation_internalid`)

#### `$reclamationReceivedOn`

Date when the Reclamation was received. Null if no reclamation.\
**Type**: DateWrapper | **UI**: "Received on" (`business_case_reclamation_reclamation_param_receivedon`)

### Customer Information

#### `$customerName`

Full name of the Customer (formatted according to person type).\
**Type**: String | **UI**: "Name" (`customer_param_full_name`)

#### `$customerMail`

Email address of the Customer.\
**Type**: String | **UI**: "E-mail" (`contact_param_email`)

#### `$customerPhone`

Phone number of the Customer.\
**Type**: String | **UI**: "Phone" (`contact_param_phone`)

***

## Unit Information

These placeholders provide information about the main Unit on the Deal.

#### `$flatId`

Internal ID of the main Flat/Unit on the Deal. Empty string if no flat.\
**Type**: String | **UI**: "Number in project" (`flat_param_internalid`)

#### `$floorNo`

Floor number of the Unit. Empty string if no flat.\
**Type**: String | **UI**: "Floor No." (`floor_param_floorno`)

#### `$buildingName`

Name of the Building containing the main Unit. Empty string if no flat.\
**Type**: String | **UI**: "Name" (`building_param_name`)

#### `$projectName`

Name of the Project containing the main Unit. Empty string if no flat.\
**Type**: String | **UI**: "Name" (`project_param_name`)

#### `$flat_property_list_number`

Property list number attribute of the Unit (known attribute). Empty string if not set or no flat.\
**Type**: String

### Dynamic Unit Attributes

Custom attributes defined for Units are available as placeholders at the document level (not inside a loop, since Reclamation documents work with a single Unit).

Note: Only Unit attributes (`AttributeArea.UNITS`) are supported. Deal, Project, and Customer attributes are not available in Reclamation documents.

Supported Attribute Types:

* String: The text value
* Integer/Numeric: The numeric value (also available as word variants: `$attribute_key_sk`, `$attribute_key_cz`)
* Boolean: `true` or `false`
* Date: Date value (DateWrapper, formatted according to user preferences)

Available Placeholders

For each attribute with key `attribute_key`:

* `$attribute_key` - The attribute value
* `$is_attribute_key` - Boolean indicating whether the attribute has a value

For NUMERIC and INTEGER attributes only:

* `$attribute_key_cz` - Value written in Czech words
* `$attribute_key_sk` - Value written in Slovak words

Example

If you have a custom attribute with key `flat_advert_description` defined for Units:

```velocity
#if($is_flat_advert_description)
  Advertisement Description: $flat_advert_description
#end
```

***

## Defects (Repeating List)

The `$defects` list contains all Defects associated with the Reclamation.

How to Use

```velocity
#foreach($defect in $defects)
  Defect: $defect.internalId
  Location: $defect.location
  Description: $defect.description
#end
```

### Available Properties

Each `$defect` item has the following properties:

Identification

#### `$defect.internalId`

Internal ID of the Defect.\
**Type**: String | **UI**: "Defect No." (`business_case_reclamation_defect_param_internalid`)

#### `$defect.externalId`

External ID of the Defect.\
**Type**: String | **UI**: "Defect No. according to the customer" (`business_case_reclamation_defect_param_externalid`)

#### `$defect.reclamationId`

Reclamation ID (Feature: NATLAND only).\
**Type**: String | **UI**: "Reclamation No." (`business_case_reclamation_internalid`)

Location

#### `$defect.location`

Location description.\
**Type**: String | **UI**: "Location (room etc.)" (`business_case_reclamation_defect_param_location`)

#### `$defect.room_location`

Formatted room name.\
**Type**: String | **UI**: "Location of the room to which the defect is related" (`business_case_reclamation_defect_param_room_location`)

#### `$defect.is_room_location`

Whether room location is set.\
**Type**: Boolean

#### `$defect.flatPart`

Flat part name or "other" value.\
**Type**: String | **UI**: "Part of the flat to which the defect is related" (`business_case_reclamation_defect_param_flat_part`)

Description and Notes

#### `$defect.description`

Defect description.\
**Type**: String | **UI**: "Reclamation description" (`business_case_reclamation_description`)

#### `$defect.note`

Additional notes.\
**Type**: String | **UI**: "Note" (`business_case_reclamation_defect_param_note`)

Developer Opinion

#### `$defect.opinion`

Latest developer opinion (localized).\
**Type**: String | **UI**: "Latest developer opinion" (`business_case_reclamation_opinion_latest_developer`)

#### `$defect.latestDeveloperOpinion`

Same as `opinion`.\
**Type**: String | **UI**: "Latest developer opinion" (`business_case_reclamation_opinion_latest_developer`)

#### `$defect.reason`

Latest developer reason.\
**Type**: String | **UI**: "Developer reason" (`business_case_reclamation_reason_latest_developer`)

#### `$defect.latestDeveloperReason`

Same as `reason`.\
**Type**: String | **UI**: "Developer reason" (`business_case_reclamation_reason_latest_developer`)

Supplier Opinion

#### `$defect.latestSupplierOpinion`

Latest supplier opinion (localized).\
**Type**: String | **UI**: "Latest supplier opinion" (`business_case_reclamation_opinion_latest_supplier`)

#### `$defect.latestSupplierReason`

Latest supplier reason.\
**Type**: String | **UI**: "Supplier reason" (`business_case_reclamation_reason_latest_supplier`)

#### `$defect.supplierName`

Formatted supplier names.\
**Type**: String | **UI**: "Suppliers" (`business_case_reclamation_supplier_plural`)

Dates

#### `$defect.receivedOn`

Date when defect was received.\
**Type**: DateWrapper | **UI**: "Detected on" (`business_case_reclamation_defect_param_detection_date`)

#### `$defect.fixedOn`

Date when defect was fixed.\
**Type**: DateWrapper | **UI**: "Fixed on" (`business_case_reclamation_defect_param_fixedon`)

#### `$defect.plannedDate`

Planned fix date.\
**Type**: DateWrapper | **UI**: "Fix planned on" (`business_case_reclamation_defect_param_planneddate`)

#### `$defect.localInspectionDate`

Date of latest local inspection.\
**Type**: DateWrapper | **UI**: "Local inspection" (`inspection_type_localinspection`)

#### `$defect.confirmedByCustomerOn`

Customer confirmation date (Feature: PENTA\_CZ/SK only).\
**Type**: DateWrapper | **UI**: "Confirmed by customer on" (`business_case_reclamation_defect_param_confirmed_by_customer_on`)

### Pictures (Nested List)

Each defect has a `pictures` list containing attachments of type `INCOMING_CUSTOMER_COMMUNICATION`.

```velocity
#foreach($picture in $defect.pictures)
  $picture.image
  Note: $picture.note
#end
```

#### `$picture.image`

Scaled image of the attachment.\
**Type**: Image

#### `$picture.note`

Note associated with the attachment.\
**Type**: String

***

## Reclamation Technician

#### `$reclamationTechnicianName`

Name of the Reclamation Technician assigned to the Project.\
**Type**: String | **UI**: "Reclamation technician name" (`business_case_reclamation_technician_name`)

#### `$technicianSignature`

Signature image of the Reclamation Technician.\
**Type**: Image | **UI**: "Reclamation technician signature" (`business_case_reclamation_technician_signature`)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dev.realpadsoftware.com/placeholders/document-templating/reclamation-documents.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.