Control flow tags

{% if Data.Callout.currency == "USD" and Data.Callout.amount > 10 %} True
{% elsif Data.Callout.currency == 'MXP' and Data.Callout.amount >100 %} True
{% else %} False
{% endif %}

• When used in Workflow, True and False must be spelled with the first letter capitalized.

• {{ }} is not required around each field since it is already in a logic {% %} .

{% if a.ProductCatalogGroup__c != blank %}
"ProductCatalogGroup__c": "{{ a.ProductCatalogGroup__c }}",
{% endif %}

{% if Data.Subscription.size > 0 %}
True
{% else %}
False
{% endif %}

{% if Data.ratePlans[index].lastChangeType %}

{% case Data.Subscription.Count_Name and Data.Account.Currency %}
{% when 1 and 'USD' %} One
{% when 2 and 'USD' %} Two
{% when 3 and 'USD' %} Three
{% endcase %}

Iteration tags

In Workflow Iterate task, you may enter a JSON payload that is not in the dropdown list. When doing so, you will need to format the payload by using the to_json filter so that the Workflow recognizes that what you entered is JSON.

{{Data.Callout[0].ResponseBody.order.subscriptions.orderActions | to_json }}

{% for RP in Data.RatePlan %}
{{ RP.Name }} - the piece that loops
{%- if forloop.last == false -%} , {% endif %} {%- endfor %}

{% for ii in Data.InvoiceItem %}
    {% assign index = forloop.index0 %}
    {% assign i = Data.Invoice[index] %}
    {% assign p = Data.Product[index] %}
    {% assign s = Data.Subscription[index] %}
    {% assign prp = Data.ProductRatePlan[index] %}
    {% assign prpc = Data.ProductRatePlanCharge[index] %}
{% endfor %}

{% for RPC in Data.RatePlanCharge %}
 {% if RPC.ChargeType != “Recurring” %}
   {% continue %} 
 {% else %}
   {{ RPC.Name }}
 {% endif %}
{% endfor %}

• {% continue %} causes the loop to skip the current iteration when it encounters the continue tag.

• {% break %} causes the loop to stop iterating when it encounters the break tag.

• You can use it as a way to do a form of the inner join between two arrays.

{% assign optics_total = 0 %}
{% for usage in Data.Usage %}
{% assign optics_total = optics_total | plus: usage.Quantity %}
{% endfor %}
{{ optics_total }}

Variable tags

{%- assign removeProducts = Data.Callout.ResponseBody.order.subscriptions[0].orderActions | where: "type", "RemoveProduct" -%}
{%- for rps in removeProducts -%}
{{rps.removeProduct.ratePlanId}}
{%- endfor -%}

{% assign AgentArray = "agent1, agent2, agent3, agent4" | split: ", " %}
{% assign AccountArray = "account1, account2, account3, account4, account5, account6" | split: ", " %}
{% assign AgentArraySize = AgentArray | size %}
{% for account in AccountArray %}
{% assign AgentIndex = forloop.index0  | modulo: AgentArraySize %}
{% assign Agent = AgentArray[AgentIndex] %}
     {{Agent}}
{% endfor %}

{% assign myItem =  Data.RatePlanCharge | sort:  ‘ChargedThroughDate’ | reverse  | first %}{{myItem.ChargedThroughDate}}

Use the Strict Variables option to verify Liquid expression

When setting up a Workflow task, you can choose to verify the Liquid expression specified in this task by using the Strict Variable mode.

By selecting Strict Variables in the task setting page, Liquid expression errors, such as "Liquid::UndefinedVariable", "Liquid::UndefinedFilter", will be raised during the task runs. However, if you leave Strict Variables unselected, the fields that contain undefined liquid variables will be left empty without raising any errors.

For example, if you use Data.abc to name a workflow task, but the variable abc doesn't exist, the task will be errored out with a "Liquid::UndefinedVariable" error in the Strict Variables mode. If Strict Variables is not selected in the task setting, the task will not be error out. Instead, the task will be named to "Add name to task", which is the default placeholder for the Task Name field.