Template Troubleshooting

This error occurs when the opening {{ and closing }} brackets of a bookmark are not properly matched, usually due to an issue with the closing brackets }}.

Solution

1. Navigate to the Edit page of the template where the error occurs.

2. Ensure that all bookmark fields have a matching closing tag.

3. After making the necessary corrections, save the template and run a test to ensure the error is resolv

This error occurs when the template engine detects invalid content inside a bookmark{{ ... }}, preventing it from being processed correctly. This usually happens due to:

• Unexpected content inside a bookmark field

• Another bookmark field nested within an existing one

These formatting issues can disrupt the template’s structure, leading to parsing errors during processing.

Solution

1. Navigate to the Edit page of the template where the error occurs.

2. In the HTML Editor, click on the Source Code button to view the template’s raw HTML.

3. Locate the elements containing the bookmark fields {{ ... }}.

4. Ensure that each bookmark field is a single word, including both {{ and }}, without spaces, additional HTML tags, or any other content.

5. After making the corrections, save the template and test it to confirm the issue is resolved.

This error occurs when a bookmark field or bookmark helpers that manage blocks in a template (such as Conditional Block helper and Grid Wrapper helper) is left unclosed, preventing the template from being processed correctly. It typically happens when:

• A bookmark field is inserted without }}

  • For example, {{offers-course_start.

• A closing helper tag(such as {{/each}} and {{/checkif}}) is missing.

Solution

1. Navigate to the Edit page of the template where the error occurs.

2. Ensure that all bookmark fields have a matching closing tag.

3. Ensure bookmark helpers that manage blocks in a template (such as Conditional Block helper and Grid Wrapper helper) have the closing helper tags.

   1. To check whether a bookmark helper requires a closing tag, insert the same helper through the Bookmark Panel and review its structure.

4. After making the corrections, save the template and test it to confirm the issue is resolved.

This can occur when bookmark fields are used to generate the Merge Document file name and the merged data contains special characters.

Some special characters may not be suitable for file names, depending on the operating system or environment where the file is saved. To help prevent file name issues, eBECAS/EDMISS Next Generation automatically converts certain special characters into safe text.

For example, if a bookmark value contains &, it may appear as amp in the generated file name.

Solution

If you prefer special characters to be handled in a simpler way, such as replacing them with an underscore instead of displaying the encoded text, use triple curly brackets for the bookmark field in the Merge Document file name.

For example:

Use {{{agents-agent_name}}} instead of {{agents-agent_name}}.

After updating the file name format, save the template and test the merge document to confirm the generated file name appears as expected.

This can occur when the generated Merge Document file name is too long.

Different operating systems and environments may have different file name length restrictions. To help prevent issues when saving or opening generated documents, eBECAS/EDMISS Next Generation automatically limits the length of the generated file name.

If the file name exceeds the maximum supported length, the system will shorten the file name by removing characters over the limit. The file extension is also included as part of the file name length.

Solution

Review the Merge Document file name format used in the template.

If the file name is generated using multiple bookmark fields, consider reducing the number of bookmarks or shortening the fixed text used in the file name.

After making the changes, save the template and test the merge document to confirm the generated file name is suitable.