48 lines
1.5 KiB
Markdown
48 lines
1.5 KiB
Markdown
# Requirements — Appraiser Review Letter Generator
|
|
|
|
## Purpose
|
|
Outline technical and functional requirements for Appraiser Review Letter templates in Salesforce CLM. Include assumed merge fields, integration points, edge cases, and design goals.
|
|
|
|
---
|
|
|
|
## Functional
|
|
- Reviewer completes form Q&A on Appraiser Review
|
|
- Each response drives tailored content in final letter (questions, comments, tables/blocks)
|
|
- Salesforce triggers CLM letter, merges data fields and Q&A collection
|
|
|
|
## Non-Functional
|
|
- Configurable (new Qs/fields easy to add)
|
|
- Audit and status tracking
|
|
- Support for complex/dynamic tables in output
|
|
|
|
## Key Requirements
|
|
- Support dynamic template merge fields (arrays/lists, booleans, enums)
|
|
- Render tables, paragraphs, and conditional sections
|
|
- Handle edge cases: nulls, empty lists, formatting gaps
|
|
- Provide fallback text for empty sections (e.g., 'No deficiencies found')
|
|
- Enable integration with Salesforce data model (objects: Appraisal, Deficiency, Reviewer)
|
|
|
|
## Example JSON
|
|
```json
|
|
{
|
|
"AppraisalId": "a1b2c3",
|
|
"DeficiencyList": [
|
|
{
|
|
"DeficiencyType": "Missing Docs",
|
|
"DeficiencyDescription": "Appraisal report lacking required documents."
|
|
}
|
|
],
|
|
"ReviewerComments": ["Well organized report."]
|
|
}
|
|
```
|
|
|
|
---
|
|
|
|
## Questions/Decisions
|
|
- What is the authoritative object and field schema for merge?
|
|
- Are custom field mappings needed for relationships (e.g. lookup fields)?
|
|
|
|
---
|
|
_Last updated: 2026-02-26 10:35 AM_
|
|
_Work in progress: Integration and schema expansion next._
|