Can you spot the error in this placeholder text?

Hi @Vanderdecken 

As of now we don’t have a direct way to identify if the placeholder is inserted properly or has an issue with it. We’ll have this converted to an idea so our product team has visibility on the suggestion.

The issue is that the second right curly brace is not in bold, causing the value to be missed. This is due to the `<b>` tag cutting off the brace. Ensure HTML tags do not interfere with curly braces by properly closing them or removing bold formatting. This will allow the value to be correctly parsed.i have recently fixed the placeholder bug for inasaldiningprices, a famous fast food blog in philippines, covering mang inasal. everything went smooth and ok.

Without seeing the placeholder text, I can't directly identify the specific error. Placeholder text is typically used as temporary content to represent where actual content will appear later. Errors in placeholder text could include spelling mistakes, grammatical errors, or incorrect information  click here  that doesn't accurately reflect the intended content.

It looks like the issue was caused by the <\b> tag cutting off the second right brace in the expression, which prevented the value from being found. This insight into how Freshservice parses HTML in expressions might help avoid similar issues in the future. Thanks for pointing it out!

Certainly! If you’re referring to a common placeholder text, like "Lorem ipsum dolor sit amet, consectetur adipiscing elit," it might be helpful to check for a few common issues. Here are some examples of errors you might find:

1. Typographical Errors: Ensure all words are spelled correctly and appropriately.

2. Consistency: Verify that the text format and style are consistent throughout the placeholder.

3. Content Relevance: Check if the placeholder text suits the context where it is used. Placeholder text should not include unrelated or irrelevant content.

That’s an interesting catch! It definitely shows how sensitive Freshservice expressions can be with HTML formatting. The misplaced <\b> tag interfering with the second right curly brace makes sense — it’s a reminder to carefully check syntax when using dynamic fields. Also, don’t forget to explore Ambers Menu for some creative inspiration!

In Freshservice, when using placeholders within expressions, it's crucial to ensure that HTML tags, such as <b>, do not interfere with the placeholder syntax. An issue was identified where a closing bold tag (</b>) inadvertently cut off the second right brace (}}) of a placeholder, leading to errors in data retrieval.

To prevent such issues, avoid placing HTML tags within or immediately adjacent to placeholder braces. This practice ensures that the system correctly interprets and processes the placeholders without interruption

The error in the placeholder text is that the second right curly brace }} is not in bold format, while the rest of the placeholder is. Specifically:

{{ticket.requester.name}} has requested travel to {{ticket.ri_207_cf_where_are_you_going<b>}}</b>}, which is on the restricted list.

The <b> tag cuts off the second right brace, preventing the full placeholder from being parsed correctly. This causes the system to not find the value, resulting in a "Not given" error.

To fix this, the bold formatting should either be removed entirely from the placeholder, or applied consistently to both curly braces:

Correct (no formatting):
{{ticket.ri_207_cf_where_are_you_going}}

Or correct (consistent formatting):
<b>{{ticket.ri_207_cf_where_are_you_going}}</b>

This issue highlights how sensitive Freshservice's parsing of placeholders can be to HTML formatting, and the importance of carefully checking syntax when using dynamic fields in workflows or automations.