Connect readable placeholders such as matter.caseNumber to XML XPath expressions.

Overview

Connect readable placeholders such as matter.caseNumber to XML XPath expressions. Dataset and mapping work defines the contract between application data and template content. Stable names and representative samples reduce downstream breakage.

Key points

• Each mapping stores a placeholder and an XPath.
• Mappings may be general or associated with a dataset.
• XPath normally starts at /data.
• Use explicit XPath when the friendly name does not mirror the XML hierarchy.
• Verify mappings before production use.

Example

{
  "datasetUuid": "<dataset-uuid>",
  "placeholder": "matter.caseNumber",
  "xpath": "/data/Matter/caseNumber",
  "valueType": "string",
  "verified": true
}

Replace bracketed values with values issued for the target environment. Never place production tokens, API keys, or client data in screenshots or public examples.

Recommended procedure

1. Start with representative source data.
2. Define or inspect the dataset tree.
3. Create explicit placeholder-to-XPath mappings.
4. Scan, validate, and test the affected template with missing and repeated values.

Troubleshooting

Validation reports MAPPING_REQUIRED

Create a mapping for every unresolved placeholder and run validation again.

A mapping resolves the wrong field

Look for normalized-name collisions and verify the XPath against sample XML.

An array field is missing from the inferred tree

Use representative sample data with at least one complete array item.

Related documentation

• Placeholder Normalization Rules
• Resolve Missing Field Mappings
• Validate and Browse a Dataset

Documentation source: feradelinc/feradel.render.api, reviewed against repository revision b2c3a710. Verify behavior against the deployed release before publishing exact routes, limits, or version requirements.