Overview
Use the "_kameleon_" prefix to mark document custom properties that must survive the document creation step
Why Kameleon remove custom properties during document creation?
-
Privacy: Custom document properties can contain sensitive metadata
-
Compatibility: Third‑party or legacy custom properties can conflict with new builds, produce unexpected field behaviour or raise interoperability issues
-
Security & compliance: removes hidden metadata that might violate retention policies
Why we use a prefix convention
-
Explicit intent: a prefix marks a property as intentionally preserved
-
Safe default: everything else is removed by default, minimizing risk.
How to enable / use
Create custom property names with the "_kameleon_" prefix
• Example property name: "_kameleon_Title"
• DOCPROPERTY field instruction in document: DOCPROPERTY "_kameleon_Title"
When new Kameleon document is created:
• Custom property becomes "Title"
• Field instruction updated to DOCPROPERTY "Title"
Quick summary
-
Default safe prefix: _kameleon_
-
Behavior: preserved, renamed by stripping the prefix, and DOCPROPERTY references in Word parts are updated to the new name
-
Other properties (no safe prefix) are removed by purify and DOCPROPERTY references are NOT modified.
Recommended policy
-
Use "_kameleon_" for internal properties that should stay visible when creating new Kameleon document and be accessible by DOCPROPERTY fields.
-
Do not create custom properties without a safe prefix if you want them preserved.