Using Liquid Markup in Portals
  • 13 Mar 2024
  • 2 minute read
  • Dark
    Light
  • PDF

Using Liquid Markup in Portals

  • Dark
    Light
  • PDF

Article Summary

Liquid markup is used to conditionally display text within a static content block based on exports added to the "method query." Exports are used as merge fields to either display text conditionally or display the export value in the static content block.

Adding Exports to the Method Query

  1. Select Database on the top navigation bar and select Portals.

  2. Select the custom status portal to be edited.

  3. Select the method query.

  4. Select Edit Query.

  5. Add exports to the query that will be used to manage Liquid markup on the custom status portal. When adding exports to the method query, rename the exports to something computer friendly (for example, "program_study" rather than "Program of Study").

    If a prompt is configured with a short value, the default functionality of exports in Slate will return the short value in the method query, and this value will be displayed on the custom status portal via Liquid markup. If Liquid markup should display the "Extended Value," set this configuration when the export is added to the method query.

Using Liquid Markup in the View

Adding a Static Content Block

Once the desired exports are added to the method query, text can be displayed conditionally within a static content block in the view.

  1. Select Database on the top navigation bar and select Portals.

  2. Select the custom status portal to be edited.

  3. Select the portal view.

  4. Drag a Static Content block into the desired location in the view and enter the following configurations:

    • Name: Give the static content block a descriptive name (for example, "Static Content Widget - Liquid Markup for Admission to College & Major"). This name will not be seen by the public.

    • Status: Set to Active.

    • Filters: Add any filters needed to determine the records that will see the static content block. If the static content block is active, it will be viewed by any record that meets the filter criteria on the custom status portal. 

Customizing the Text with Liquid Markup

Deliver WYSIWYG

Static Content WYSIWYG

Liquid markup evaluations are initiated with the if tag and closed with the endif tag within the static content block. If the relevant exports are included within the method query, static text can be used to utilize Liquid markup and call merge fields.

For example, Liquid markup can be used to conditionally display text based on what school an applicant was admitted to and what major.

Note that as text is written out within the static content block, the Liquid markup and merge fields display without any highlighting or indication that they are active (blue highlighting is included for display only in the following image).

  Receive an error?

It is likely specific to the Liquid markup. Be sure to double check that tags, if statements, and merge fields are written correctly.

Testing the Liquid Markup

Always test Liquid markup! If Liquid markup is included within a custom status portal, ensure that each and every condition is behaving as intended.

  1. Select Lookup on the top navigation bar.

  2. Search for a test record that has an application in a period or round that is associated with the custom status portal.

  3. Select Impersonate > Status Page from the links on the right-side pane.

  Is the custom status portal not live?

Not a problem! When ready to test, refresh the test environment. Then, associate the custom status portal to a period or round and create a new test application record in the associated period/round. This will allow testing of custom Status Portal before showing it to the world!


Was this article helpful?