Table of Contents

Description

“Scriptlets” is the name of our programming language used within Maileon newsletters to realize extensive requirements on data processing and output. Scriptlets allow for example generating random numbers or UUIDs for each contact within a sendout in order to attach it to some link. It allows generating an (MD5) hash of data like the email address or encrypt data with some given key and supports complex processing of data like parsing a string as a datetime object, adding 7 days and printing it in some other format. Also accessing external data sources for each individual contact is possible in order to e.g. display individual products for each contact.

Thus, Scriptlets support a huge number of language elements and even if it is not possible to create an infinite loop, you can use loops, e.g. when iterating over the items of some shopping cart in order to calculate the overall sum or to display the items in a newsletter.

The formal description is provided as BNF in the next section, however, most readers will benefit at the beginning more of some unformal description or the examples later on. Scriptlets are always wrapped in double square brackets [[ ]]. Inside the brackets, a Scriptlet is started with a “%” sign to avoid mixing up regular Maileon-Mergetags and Scriptlets. For Scriptlets a preorder syntax has been chosen, this means that the operator is in the beginning of an expression and the parameters follow behind, separated by a whitespace “ “. If an parameter is an expression with some operator itself, it has to be wrapped in single round brackets ().

Simple examples:

For date and time formats please refer to https://docs.oracle.com/en/java/javase/11/docs/api/java.base/java/text/SimpleDateFormat.html

Formal Description

 This section defines the BNF of the language elements.

Language Elements

The 'mine' Function

• mine

  • Description: Causes the message generation to fail. Can be used e.g. to not send an automated transaction mail under certain circumstances.

• mine <string>

  • Description: Same as “mine” without parameter but fires a “named” personalization error, if triggered.

String Functions

• to_string <none_void_expr>

• lower_case <string_expr>

• md5 <string_expr>

• capitalize <string_expr>

• normalize_space <string_expr>

• reverse <string_expr>

• trim <string_expr>

• uncapitalize <string_expr>

• upper_case <string_expr>

• default_if_blank <string_expr> <string_expr>

• default_if_empty <string_expr> <string_expr>

• remove <string_expr> <string_expr>

• remove_end <string_expr> <string_expr>

  • Description: Removes the second string from the end of the first string

• remove_end_ignore_case <string_expr> <string_expr>

• remove_start <string_expr> <string_expr>

• remove_start_ignore_case <string_expr> <string_expr>

• substring <string_expr> <numeric_expr> <numeric_expr>

  • substring 'abc' 0 2   = 'ab' substring 'abc' 2 0   = '' substring 'abc' 2 4   = 'c' substring 'abc' 4 6   = '' substring 'abc' 2 2   = '' substring 'abc' -2 -1 = 'b'

• substring_after <string_expr> <string_expr>

• substring_after_last <string_expr> <string_expr>

• substring_before <string_expr> <string_expr>

• substring_before_last <string_expr> <string_expr>

• substring_between <string_expr> <string_expr> <string_expr>

• random_alphabetic <numeric_expr>

• random_alphanumeric <numeric_expr>

• random_numeric <numeric_expr>

• to_string_on_off <logical_expr>

• to_string_true_false <logical_expr>

• to_string_yes_no <logical_expr>

• replace <string_expr> <string_expr> <string_expr>

  • [[ % replace '12.50' '.' ',' ]] à 12,50

• replace_once <string_expr> <string_expr> <string_expr>

• center <string_expr> <numeric_expr> <string_expr>

• abbreviate <string_expr> <numeric_expr>

  • Description: Cuts down the string to the given length INCLUDING the three abbreviation indicating dots. If nothing will be cut, the dots will not be added.
    [[ % abbreviate '123456' 6]] will be evaluated to '123… '
    Thus, the length MUST be greater or equal to 4.

• abbreviate_middle <string_expr> <string_expr> <numeric_expr>

• repeat <string_expr> <numeric_expr>

• random <numeric_expr> <string_expr>

• boolean_to_string <logical_expr> <string_expr> <string_expr>          

• join <sequence_expr> <string_expr>

• concat <sequence_expr>

• unescape_html <string_expr>

• date_to_string <date_expr> <string_expr> <string_expr>

• datetime_to_string <datetime_expr> <string_expr> <string_expr>

• format_date <string_expr> <string_expr> <string_expr> <string_expr>

• format_datetime <string_expr> <string_expr> <string_expr> <string_expr>

• aes_encrypt_hex <string_expr> <string_expr>

• format_number <numeric_expr> <string_expr> <string_expr> <numeric_expr>

  • [[ format_number 1234.560' '.' ',' 2 ]] -> 1.234,56

  • Warning: if the number comes from a custom contact field (type float) and is not set, it returns the STRING value “NaN”, which will cause the formatting to fail. Use an “if” around the expression:

    [[ % if (negate(equals (contact 'float_number') 'NaN')) % format_number (contact 'float_number') '.' ',' 2 % endif ]]

• url_encode <string_expr>

  • Description: Encodes a string as a URL parameter that can be passed

• url_decode <string_expr>

  • Description: Decodes a string as URL parameters that will be interpreted

• assigned_voucher <string-literal>

  • Description: Print voucher code, parameter is pool name (not the ID)! Fails if voucher does not exist.

• assigned_voucher <string-literal> <string-literal>

  • Description: Print voucher code, parameter is pool name (not the ID) + fallback value! Fails if voucher does not exist.

• voucher <string-literal> <string-literal>

  • Description: Print voucher code, parameter is pool ID (as a string) + fallback value! Fails if voucher does not exist.

• conditional_content  <string-literal>

  • Description: Print COCO ruleset result, parameter is rulset name (not the ID)! Fails if the ruleset does not exist. Default COCO rulesets cannot be referred to as their representation is language dependent.

Logical functions

As Maileon uses a three state value for Booleans (not set, true or false), these methods define a fallback behavior, which is added in [brackets] behind the expression. They will return this result, if e.g. a custom field is not set. Methods without annotation will fail if the field is empty, so a check for existence is mandatory.

• to_boolean <none_void_expr>

• exists <none_void_expr>

• or <logical_expr>*
  This method checks every expression, even if earlier expressions evaluated to true

• logical_or <logical_expr>*
  or with early abort

• and <logical_expr>*
  This method checks every expression, even if earlier expression evaluated to false

• logical_and <logical_expr>*
  and with early abort

• negate <logical_expr>

• xor <logical_expr>*

• is_all_upper_case [false]

• is_boolean <none_void_expr> [false]

• is_number <none_void_expr> [false]

• is_date <none_void_expr> [false]

• is_datetime <none_void_expr> [false]

• is_string <none_void_expr> [false]

• is_time <none_void_expr>

• is_sequence <none_void_expr> [false]

• contains_whitespace <string_expr> [false]

• is_all_lower_case <string_expr> [false]

• is_alpha <string_expr> [false]

• is_alphanumeric <string_expr> [false]

• is_alphanumeric_space <string_expr> [false]

• is_alpha_space <string_expr> [false]

• is_blank <string_expr> [true]

• is_empty <string_expr> [true]

• is_not_blank <string_expr> [false]

• is_not_empty <string_expr> [false]

• is_numeric <string_expr> [false]

• is_numeric_space <string_expr> [false]

• is_whitespace <string_expr> [false]

• string_to_boolean <string_expr> [false]

• contains <string_expr> <string_expr> [false]

  • [[% if (contains (transaction 'someAttribute') 'X') % 'Contains X' % endif]]

• contains_ignore_case <string_expr> <string_expr> [false]

  • [[% if (contains_ignore_case (transaction 'someAttribute') 'X') % 'Contains X' % endif]]

• ends_with <string_expr> <string_expr> [false]

• ends_with_ignore_case <string_expr> <string_expr> [false]

• starts_with <string_expr> <string_expr> [false]

• starts_with_ignore_case <string_expr> <string_expr> [false]

• equals <string_expr> <string_expr> [false]

  • Description: Compares two STRINGS for equality. Not applicable, if variable content is numeric, in this case use “eq”

• equals_ignore_case <string_expr> <string_expr> [false]

• is_false <logical_expr>

• is_not_false <logical_expr>

• is_not_true <logical_expr>

• is_true <logical_expr>

• negate <logical_expr>

• seq_contains <sequence_expr> <none_void_expr> [false]

• seq_contains_any <sequence_expr> <sequence_expr> [false]

• seq_contains_none <sequence_expr> <sequence_expr> [true]

• seq_contains_all <sequence_expr> <sequence_expr> [false]

  • Description: Checks if sequence1 contains all elements of sequence2

• equals_any(_ignore_case) <string-expr> <sequence-expr>

• equals_none(_ignore_case) <string-expr> <sequence-expr>

• contains_any(_ignore_case) <string-expr> <sequence-expr>

• contains_none(_ignore_case) <string-expr> <sequence-expr>

• contains_all(_ignore_case) <string-expr> <sequence-expr>

• starts_with_any(_ignore_case) <string-expr> <sequence-expr>

• starts_with_none(_ignore_case) <string-expr> <sequence-expr>

• ends_with_any(_ignore_case) <string-expr> <sequence-expr>

• ends_with_none(_ignore_case) <string-expr> <sequence-expr>

• gt <numeric_expr> <numeric_expr>

• ge <numeric_expr> <numeric_expr>

• eq <numeric_expr> <numeric_expr>

  • Description: Compares numeric values, not strings

• ne <numeric_expr> <numeric_expr>

• lt <numeric_expr> <numeric_expr>

• le <numeric_expr> <numeric_expr>

• is_preference_true <string> <string>

  • Arguments: category name, preference name

• preference_has_value <string> <string>

  • Arguments: category name, preference name

• preference_has_no_value <string> <string>

  • Arguments: category name, preference name

• preference_has_no_value_or_false <string> <string>

  • Arguments: category name, preference name

• is_preference_false <string> <string>

  • Arguments: category name, preference name

• is_any_preference_true <string>

  • Arguments: category name

• is_matched_by_filter <string >

  • Arguments: Parameter is the name of the filter, not its ID! No failure if filter does not exist but returns false. Works reliably in regular mails only but might represent outdated results in transactional or DOI confirmation mails.

• is_not_matched_by_filter <string >

  • Arguments: Parameter is the name of the filter, not its ID! No failure if filter does not exist but returns false. Works reliably in regular mails only but might represent outdated results in transactional or DOI confirmation mails.

Numeric Functions

• to_number <none_void_expr>

• add <numeric_expr> <numeric_expr>

• length <string_expr>

• mul <numeric_expr> <numeric_expr>

• sub <numeric_expr> <numeric_expr>

• div <numeric_expr> <numeric_expr>

• pow <numeric_expr> <numeric_expr> 

• ceil <numeric_expr>

• floor <numeric_expr>

• round <numeric_expr>

• abs <numeric_expr>

• max <sequence_expr> 

• min <sequence_expr> 

• sum <sequence_expr>  

• seq_size <sequence_expr>

• mod <numeric_expr> <numeric_expr>

• datetime_to_time <datetime_expr>

  • Description: Translates a datetime into a timestamp

• date_to_time <date_expr>

  • Description: Translates a date into a timestamp

• parse_number <string_expr> <string_expr> <string_expr>

  • [[ parse_number '1.234,560' '.' ',' ]]

• increment <numeric_expr>

  • [[ % set $var 1 % increment $var % $var]] -> 2

• decrement <numeric_expr>

  • [[ % set $var 1 % decrement $var % $var]] -> 0

Sequence Functions

• split <string_expr> <string_expr>

• split (contact 'listField' ';')

• csv <string_expr>

• seq_add_all <sequence_expr> <sequence_expr>

• seq_add <sequence_expr> <none_void_expr>

  • Description: Add an element to a sequence. This method does not change the input sequence, make sure to save the result

• seq_replace <sequence_expr> <sequence_expr>

• partition <sequence_expr> <numeric_expr>

  • [[% partition <1, 2, 3, 4, 5, 6, 7, 8, 9, 10} 3]] -> [[1,2,3], [4,5,6], [7,8,9], [10]]

• reverse_seq <sequence_expr>

  • [[% reverse <1, 2, 3, 4}]] -> [4, 3, 2, 1]

• shuffle <sequence_expr>

  • [[% shuffle <1, 2, 3, 4}]] -> e.g. [2, 4, 3, 1]

• select_true_preferences <string>

  • Arguments: category name - return sequence of preference names that are true

• select_false_preferences <string>

  • Arguments: category name - return sequence of preference names that are false

Object Functions

• item <sequence_expr> <numeric_expr>

  • Description: Selects the n-th item from a sequence. The index starts with 0 for the first item.

  • [[ % item $someSequence 0 ]]

Date Functions

• now

• to_date <string_expr> <string_expr>

• cast_date <string_expr>

• time_to_date:<numeric_expr>

Datetime Functions

• date_sent

  • Description: The datetime of the sendout, also works for triggermails

• to_datetime <string_expr> <string_expr>

• cast_datetime <string_expr>

• time_to_datetime <numeric_expr>

• add_seconds <date_or_datetime_expr> <numeric_expr>

• add_minutes <date_or_datetime_expr> <numeric_expr>

• add_hours <date_or_datetime_expr> <numeric_expr>

• add_days <date_or_datetime_expr> <numeric_expr>

• add_weeks <date_or_datetime_expr> <numeric_expr>

• add_months <date_or_datetime_expr> <numeric_expr>

• add_years <date_or_datetime_expr> <numeric_expr>

External Data

Maileon can retrieve external data, either as JSON or plain HTML. The following facts and restrictions are valid for both features.

Maileon uses caching strategies to reduce the amount of request. Please make sure that the server always returns the same response for the same request within one sendout. As URLs can contain variables it might result in a lot of different URLs and thus, a lot of requests. Make sure your server can process the request fast enough as it will delay the sendout process. If a service times out, the mailing(s) the response was meant for are not processed any further and are reported as “failed sendouts”.

External JSON

Feed Structure

External JSON can be used to request data from external systems that is processed and rendered into the mailing. Please make sure that you do not return an array, directly, always return an object and there an attribute with an array content. I.e. do not return

But wrap it in an object with a named attribute, e.g.:

Syntax for retrieving data

{varName} is a free choosable name for the variable, the content is available in, later. It must start with a character. {url_with_personalization} is the url with protocol (https://) and personalizations e.g. from contactfields need to be in Mergetag-Syntax with only a single bracket, e.g. the E-Mail-Hash would be: [MD5|CONTACT|EMAIL]

Syntax Example

In this case the data of the “stream” will be available in variable “myData” and will submit some path parameter from a customfield called “jsonfile”. Variables can of course also used as query parameters (sometimes referred to as GET parameters).

Complex Parameters

Parameters may only be simple expressions, e.g. a variable, a path in a transaction, or a contact field. If more complex expressions are required, they need to be preprocessed and saved in a variable, e.g.:

Data Usage

From here, Scriptlets can be used to access the values using “ext_json” method, e.g.:

To save the array into variable myVar:

To save the first array element from myVar (example above) into variable myElement

Or simply use loops to display all elements

External HTML

The HTML provided by an external service provider will be included in Maileon as returned. Make sure to not return invalid HTML or HTML that causes display problems in Mail clients.

Please be aware that dynamic fields within returned HTML are not filled by Maileon. In other words: if a mergetag like [[CONTACT|FIRSTNAME]] is included in the returned HTML, it will not be processed by Maileon.

Syntax for retrieving data

Data Extensions

Expression

Data extensions are basically a small database system, similar to relational databases. It is possible to push in data and pull it, using queries. The basic retrieval inside a template is defined as follows:

• data_extension_name indicates the name of the data extension from which to retrieve the record.

• The match clause indicates the condition or conditions that a record must statisfy to be selected. Unlike where clauses in SQL select statements, the match clause only checks the equality of a field value in the data extension with a lookup value. The match clause must contain at least one condition. If multiple conditions are provided, the field names must be different, otherwise the expression causes a compilation error.

  • field_name indicates the name of a field in the data extension

    • number is a number literal

    • string is a string literal

    • boolean: true or false

    • contact_field_expr indicates the name of a contact field and optionally a fallback value if this field has no value for the contact

    • transaction_property_expr indicates the path of a string, number or boolean in the transaction object and optionally a fallback value if this path cannot be resolved

• The order_by clause is optional. If multiple sort statements are provided, the field names must be different, otherwise the expression causes a compilation error.

• The top clause is optional. If the top clause is not provided, then 20 will be used as default value.

  • records_count is a number literal that indicates the maximum number of records to be returned. The value must be between 1 and 50. Out of bounds values will be ignored and replaced with 50.

• The group_by_key clause is optional. Transforms a list of hashes (maps having strings as keys) into a hash where values of a specified field are mapped to lists of hashes.

  • $seq evaluates to [{"a": "x", "b": "i"}, {"a": "x", "b": "j"}, {"a": "y", "b": "k"}]

  • [[% group_by_key $seq 'a']] evaluates to {"x": [{"b": "i"}, {"b": "j"}], "y": [{"b": "k"}]}

• The group_by_unique_key clause is optional. Transforms a list of hashes (maps having strings as keys) into a hash where values of a specified field are mapped to lists of hashes.

  • $seq evaluates to [{"a": "x", "b": "i"}, {"a": "x", "b": "j"}, {"a": "y", "b": "k"}]

  • [[% group_by_unique_key $seq 'a']] evalutes to {"x": {"b": "i"}, "y": {"b": "k"}}

    • Since the value x appears twice, an arbitrary hash is selected!

  • [[% group_by_key $seq 'c']] evalutes to {}

• The returned record is a hash (a map) where all the field names of the data extension are mapped to string representations of their values in the record. Fields with null-values are not contained in the record. Lookup values of types contact_field_expr and transaction_property_expr that evaluate to NULL cause the expression return an empty object as a result. If the match clause matches more than one record, an arbitrary (matching) record will be returned. The expression will evaluate to an empty object if the data extension cannot be found or if the match clause does not match any record or if a field name in the match clause is unknown.

Please be aware: comparing is only possible against literals or contact/transaction fields. This means, only “final values”, no variables or expressions.

Wildcards

In the special case of a select_records expression, list wildcards can be used in transaction path expressions.

Example, using a transaction with following values:

Conditions in match clause:

• 'product_id' = (transaction 'cart[*].product_id')

  • will be interpreted as: product_id is p1 or product_id is p2

• 'category' = (transaction 'cart[*].tags[*]')

  • will be interpreted as: category is one of: games, toys or sport.

• 'category' = (transaction 'cart[1].tags[*]')

  • will be interpreted as: category is sport

Validation

• data_extension_name

  • Valid examples:

    • 'my_data_extension'

  • Invalid examples:

    • (lower_case 'My_Data_Extension'): This expression is not a string literal even if it evaluates to a string.

    • $extensionName: This expression is not a string literal even if it evaluates to a string.

• field_name

  • Valid examples:

    • 'my_field'

  • Invalid examples:

    • $fieldName: This expression is not a string literal even if it evaluates to a string.

• number

  • Valid examples:

    • 123

    • 12.3

    • 1.23

  • Invalid examples:

    • (pow 2 2): This expression is not a number literal even if it evaluates to a number

    • $number: This expression is not a number literal even if it evaluates to a number

• boolean

  • Valid examples:

    • true

    • false

  • Invalid examples:

    • (gt 2 3): this expression is not a boolean literal even if it evaluates to a boolean

    • (starts_with 'foo' 'f'): this expression is not a boolean literal even if it evaluates to a boolean

• string

  • Valid example:

    • 'example'

  • Invalid examples:

    • (lower_case 'eXaMple'): This expression is not a string literal even if it evaluates to a string.

    • $var: This expression is not a string literal even if it evaluates to a string.

• contact_field_expr

  • Valid examples:

    • (contact 'category'): The value of contact field category

    • (contact 'category' 'standard'): The value of contact field category. Use standard as fallback if no value is defined.

  • Invalid example

    • (contact $fieldname): The name of the contact field must be a string literal.

• transaction_property_expr

  • Valid examples:

    • (transaction 'cart.items[0].product_id')

    • (transaction 'delivery_type' 'standard' ): Transaction property reference with a fallback value.

  • Invalid examples:

    • (transaction $property): the property must be a string literal.

Data Extension Example

Examples

Multiple Statements

Comments

Hashes

Standard hashes

As SUBJECT or NAME are standard values for mailings, you can also access own custom values of mailings with just specifying the key name, e.g. [[ % mailing 'test' ]]

Maps

If the value of $var is a map (key-value pairs) then you can access some value by calling:

Example: Shoppingcart

Primitives

Output: truestring-12.34

Variables

Output: aA

Dates, Datetimes

 Current date and time

 Print date of yesterday

Sequences

Output: axbxcxaxbxcxd

Conditional Statements

Loops

Output: abcdef12

Usecase Examples

• Calculate MD5 hash over a concatenation of the email address, a transactional field “custom2” and “custom3”

  [[ % md5(concat{email, (transaction 'custom2'), (transaction 'custom3')}) ]]

• AES encryption of contact field “custom1” with key 0123456789abcdef.
  Please note: the key length has to be exactly 128 bit (16 byte, in this case 16 characters).

  [[ % aes_encrypt_hex '0123456789abcdef' (contact 'custom1') ]]

• Add 4 Weeks to the date when the mailing has been sent, this works for regular mailings only. For transaction mailings it will be the date of activation, see “date_send”

  [[ % datetime_to_string (add_weeks (mailing 'DATE') 4) 'dd.MM.yyyy' 'de']]

• Parse String from a transaction as number, take absolute value and print it with 2 digits precission

  [[ % format_number (abs (parse_number (transaction 'invoicePrepaidAmount') '' ',')) '' ',' 2 ]]

• Parse a date like "2019-11-06T02:00:00Z", and print it as "06.11.2019":

  [[ % date_to_string (to_date (transaction 'effectiveDate') 'yyyy-MM-dd\'T\'HH:mm:ssX') 'dd.MM.yyyy' 'de' ]]

• Parse a date like "2019-11-06T02:00:00.000+0200", and print it as "06.11.2019":

  [[ % date_to_string (to_date (transaction 'effectiveDate') 'yyyy-MM-dd\'T\'HH:mm:ss.SSSX') 'dd.MM.yyyy' 'de' ]]

• Check if transaction variable that is given as string is larger or smaller than 0 and print it

  [[ % if (gt (parse_number (transaction 'amount') '.' ',') 0) % 'It is larger' % else % 'It is smaller' % endif ]]

• Generate UUID v4

  [[ % upper_case (join {(random_alphanumeric 8), (random_alphanumeric 4), (random_alphanumeric 4), (random_alphanumeric 4), (random_alphanumeric 8) } '-')]

• Print Birthday

  [[ % date_to_string (cast_date (contact 'BIRTHDAY')) 'dd.MM.yyyy' 'en']]

• Add 3 months to birthday:

  [[ % datetime_to_string (add_months (cast_date (contact 'BIRTHDAY')) 3) 'dd-MM-yyyy' 'nl']]

• Add 3 months to sendout date:

  [[% datetime_to_string (add_months date_sent 3) 'dd.MM.yyyy HH:mm:ss' 'de']]

• Count up variable in a loop by 1:

  [[% set $counter (add $counter 1) ]]

• Unescaping HTML to display items

  [[ % unescape_html '•' ]] Ein Bullet [[ % unescape_html '•' ]] Ein Bullet

• Displaying Magento Price Reductions

  [[     % if ( is_not_empty '{{MAGENTO-PRODUCT|SPECIAL-PRICE}}' )         % '{{MAGENTO-PRODUCT|SPECIAL-PRICE|0.00de_DE}} CHF {{MAGENTO-PRODUCT|PRICE|0.00de_DE}} CHF'     % else         % '{{MAGENTO-PRODUCT|PRICE|0.00de_DE}} CHF'     % endif ]]

• Displaying Shopware Price Reductions

  [[    % if(or(is_empty '{{SHOPWARE-ITEM|PSEUDOPRICE|0.00de_DE}}') (equals '{{SHOPWARE-ITEM|PSEUDOPRICE|0.00de_DE}}' '0,00'))       % '{{SHOPWARE-ITEM|PRICE|0.00de_DE}} €'    % else      % '{{SHOPWARE-ITEM|PRICE|0.00de_DE}} € statt  {{SHOPWARE-ITEM|PSEUDOPRICE|0.00de_DE}} €'    % endif ]]

• Price Based on Language

  [[ % if (equals (contact 'LOCALE' 'de') 'de_CH') % format_number (mul (parse_number '{{magento-price}}' '.' ',') 1.15) '.' ',' 2 % ' CHF' % else % '{{magento-price}} €' % endif ]]

• Display 3 Elements out of a large Sequence

  [[EXTERNAL-JSON|nextMatches|"https://..."]] [[ % set $nextMatches (ext_json 'nextMatches' 'data') % set $part (partition $nextMatches 3) % set $next (item $part 0) % foreach $nextMatch in $next % set $homeTeam (property $nextMatch 'home_team') % set $awayTeam (property $nextMatch 'away_team') # Display here % endforeach ]]

   

• Calculate Age from Birthday

  [[ % floor (div (sub (date_to_time now) (date_to_time (cast_date(contact 'BIRTHDAY')))) 31536000000)]]

   

• Print number of days till a certain date

  [[ % round (div (sub (date_to_time (cast_date(contact 'Anreisedatum'))) (date_to_time now)) 86400000) ]]

FAQ

I am lost with the brackets. Where should I add brackets and where not?

As Scriptlets are a preorder syntax, operator comes first, then the parameters. Parameters of operations must be marked somehow and we use () for this.
Example:

• lower_case <string_expr>

lower_case expects exactly one parameter. If this value comes e.g. from a contact field and there are no brackets used, this writes as [[ % lower_case contact 'firstname']]. If the parser parses this, it sees “lower_case” and then “parameter 1 = contact” and “parameter 2 = ‘firstname’”. It will report an error, as “contact” is not a valid expression on its own, thus, not a valid parameter (and in general there is no second parameter expected, at all).
This, “contact 'firstname’ must be wrapped in brackets: [[ % lower_case (contact 'firstname')]]

Same scheme needs to be used in all other cases, e.g. for an if statement.
Example:

Here, we have NO bracket for the parameter behind the “if” because “if” expects exactly one parameter (a boolean expression) and the variable “result” is exactly this. If the evaluation should be added to the “if”, directly, brackets would be required, basically as seen in the assignment, as well (“set” expects 2 parameters, first is a variable, in this case “$result”, second is some value, in this case the boolean expression, thus wrapped in ()):

So in summary: always if a complex expression, which contains of more than one element, are used as parameter inside another expression, it must be wrapped in brackets to indicate, that this is a single entity that needs to be calculated before.

External-JSON: Scriptlets as parameters of links not working

While it is possible to add parameters to URLs, e.g. [[EXTERNAL-JSON|myData|"http://www.xqueue.com/[CONTACT|jsonfile]"]], it is not possible to add complex expressions, directly.

For example, the following approach will cause errors:

Instead, complex operations need to be done before, saved to a variable and can then be used inside the URL:

Changelog

Version 1.7

• Added example

Version 1.6 08.04.2022

• Added new string method: voucher

• Added description for external JSON and HTML

Version 1.5 26.10.2021

• Added examples

• Adde new datetime methods (sendout_date)

• Adde new string methods (url_encode, url_decode, assigned_voucher, conditional_content)

• Adde new sequence methods (partition, shuffle, reverse)

• Adde new numeric methods (increment, decrement)

• Adde new boolean methods (is_matched_by_filter, is_not_matched_by_filter, equals_any(_ignore_case), equals_none(_ignore_case), contains_any(_ignore_case), contains_none(_ignore_case), contains_all(_ignore_case), starts_with_any(_ignore_case), starts_with_none(_ignore_case), ends_with_any(_ignore_case), ends_with_none(_ignore_case))

• Added default behavior for boolean expressions when boolean value is not set (neither true nor false)

• Added preference methods (is_preference_true, preference_has_value, preference_has_no_value, preference_has_no_value_or_false, is_preference_false , select_true_preferences, select_false_preferences, is_any_preference_true)

• Added named mine statements

Version 1.4 (27.09.2019)

• New layout for documentation

Version 1.3 (07.02.2019)

• added parse_number: {string_expr> {string_expr> {string_expr>

• added format_number: {numeric_expr> {string_expr> {string_expr> {numeric_expr>

• added examples

Version 1.2 (28.03.2017)

• added substring <string_expr> <numeric_expr> <numeric_expr>

Version 1.1 (29.07.2016)

• added datetime_to_time <datetime_expr>

• added date_to_time <date_expr>

• added time_to_datetime <numeric_expr>

• added time_to_date <numeric_expr>

• added add_seconds <date_or_datetime_expr> <numeric_expr>

• added add_minutes <date_or_datetime_expr> <numeric_expr>

• added add_hours <date_or_datetime_expr> <numeric_expr>

• added add_days <date_or_datetime_expr> <numeric_expr>

• added add_weeks <date_or_datetime_expr> <numeric_expr>

• added add_months <date_or_datetime_expr> <numeric_expr>

• added add_years <date_or_datetime_expr> <numeric_expr>