Templates parameter not properly displaying

It looks like you're facing an issue where some fields in the "Configure HTML Doc from Template" setup are not displaying correctly or not mapping as expected, even after re-uploading the document template with changes.

Here are some steps to troubleshoot this:

1. Verify Placeholder Syntax: Ensure the placeholders in your document template match exactly what you’ve entered in the "Find in template document" column. Appian is case-sensitive and expects exact matches.

2. Use Simple Placeholders: If the placeholders contain complex HTML or special characters, try simplifying them to plain text placeholders (e.g., ${fieldName}) to see if they map correctly. After confirming they work, you can revert to more complex placeholders if needed.

3. Re-Scan Template: After each update to the document template, click "Re-Scan Template" to allow Appian to detect new or updated placeholders.

4. Clear and Re-Map Fields: Delete the mappings for the problematic fields and re-enter them. Sometimes, Appian retains old references that can cause mapping issues.

5. Use New Template: As a last resort, try saving your document under a new name and uploading it as a fresh template in Appian. Sometimes, reusing the same file name can cause Appian to cache old template configurations.

It looks like you're facing an issue where some fields in the "Configure HTML Doc from Template" setup are not displaying correctly or not mapping as expected, even after re-uploading the document template with changes.

Here are some steps to troubleshoot this:

1. Verify Placeholder Syntax: Ensure the placeholders in your document template match exactly what you’ve entered in the "Find in template document" column. Appian is case-sensitive and expects exact matches.

2. Use Simple Placeholders: If the placeholders contain complex HTML or special characters, try simplifying them to plain text placeholders (e.g., ${fieldName}) to see if they map correctly. After confirming they work, you can revert to more complex placeholders if needed.

3. Re-Scan Template: After each update to the document template, click "Re-Scan Template" to allow Appian to detect new or updated placeholders.

4. Clear and Re-Map Fields: Delete the mappings for the problematic fields and re-enter them. Sometimes, Appian retains old references that can cause mapping issues.

5. Use New Template: As a last resort, try saving your document under a new name and uploading it as a fresh template in Appian. Sometimes, reusing the same file name can cause Appian to cache old template configurations.