↔️ Translation Codes and Content Blocks
Content blocks and translation codes allow transforming an input into an output. They are stored in the same table behind the scenes. Translations can allow a single input or a range of numerical inputs and return plain-text output. Content blocks allow a single input and return HTML output.
Slate mostly exposes Translations via queries. Content Blocks are mostly used via Liquid when rendering content for portals, emails, etc.
They have many uses:
- Mailings and portals can provide custom content based on either data Slate knows about the person accessing the email or portal or data about the record they are viewing. For example, an email might merge in the assigned counselor's HTML signature block.
- Translation codes can provide additional exports for prompts, which provide Exports 1-5 by default.
- Translations can transform test scores between different numeric scales or from numeric to alpha scales (i.e. 90% becomes A).
- Portals and forms can import scripts via Content Blocks (but check out Portal Components first).
Translation Codes and Content Blocks are stored in the same SQL table, [lookup.translation]. Entries from both appear in the "Current Translation Code List" standard query (Database > Standard Query Library).
It's possible to update (but not create) Content Blocks via the Translation Code Import source format.
Resources:
No Comments