Which statement best describes a merge code in OmniScript?

Which statement best describes a merge code in OmniScript?

• A. A placeholder replaced at runtime with the value of a field using the %field% syntax.
• B. A HTML tag used for formatting.
• C. A reserved keyword for loops.
• D. A data type for numbers.

Answer: (A)

Merge codes are placeholders that get replaced with actual data when the OmniScript runs. They pull in dynamic values from the current data model using the %field% syntax, so the text can reflect user input or record values at runtime. For example, if a field named FirstName has the value Alex, writing %FirstName% in a text element will render as Alex when the script executes. This is exactly what the statement describes. HTML tags are for formatting, not dynamic data insertion; a reserved keyword for loops belongs to programming logic, not data binding in OmniScript; and a data type for numbers is just a type, not a mechanism to insert field values.

Merge codes are placeholders that get replaced with actual data when the OmniScript runs. They pull in dynamic values from the current data model using the %field% syntax, so the text can reflect user input or record values at runtime. For example, if a field named FirstName has the value Alex, writing %FirstName% in a text element will render as Alex when the script executes. This is exactly what the statement describes. HTML tags are for formatting, not dynamic data insertion; a reserved keyword for loops belongs to programming logic, not data binding in OmniScript; and a data type for numbers is just a type, not a mechanism to insert field values.