{"id":1579,"date":"2023-02-01T08:35:11","date_gmt":"2023-02-01T13:35:11","guid":{"rendered":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/writing-text\/using-dynamic-text\/"},"modified":"2026-10-22T11:04:58","modified_gmt":"2026-10-22T15:04:58","slug":"using-dynamic-text","status":"publish","type":"docs","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/writing-text\/using-dynamic-text\/","title":{"rendered":"Using dynamic text"},"content":{"rendered":"\n

Dynamic text lets you write a document or a message once and have AirSupervision fill in the personal details automatically for each person: name, licence number, address, the name of your organisation, today’s date, and so on.<\/p>\n\n\n\n

You place fields<\/strong> in your text. A field is a word between double braces, for example {{givenname}}. When the document is produced, sent or displayed, the field is replaced by the real information. “Dear {{givenname}} {{lastname}},” becomes “Dear Alex Martin,” for one member and “Dear Sam Taylor,” for another.<\/p>\n\n\n\n

\n
\"\"<\/a><\/figure>\n\n\n\n
\"\"<\/a><\/figure>\n<\/figure>\n\n\n\n

Where you can use dynamic text<\/h2>\n\n\n\n
Where<\/th>How to add a field<\/th>Which fields<\/th><\/tr><\/thead>
Dynamic documents and other texts written with VisualText<\/td>Portal Tags<\/strong> button > Contact, System or Sender. The field appears as a small framed label.<\/td>Member, sender and system fields (see the reference below).<\/td><\/tr>
Text boxes with the BBCode toolbar and printing buttons<\/td>Member’s fields<\/strong>, User’s fields<\/strong> or System fields<\/strong> menus. The field is written with its braces.<\/td>Member, user and system fields (see the reference below).<\/td><\/tr>
Automatic messages and emails set up by administrators (settings pages)<\/td>The default text already contains the fields that message can use. Keep them, move them, or delete the ones you do not need.<\/td>Fields specific to each message, for example the student’s name and the lesson title in a lesson notification.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
\"VisualText
In VisualText, fields appear as small framed labels, here “givenname”, “lastname” and “company_name”. They are replaced by the real information when the document is produced.<\/figcaption><\/figure>\n\n\n
\n\n\n

Tip:<\/strong> A field only works where it is offered. A field copied from one automatic message into another one, or from a dynamic document into a message, may stay empty or appear as typed.<\/p>\n\n\n<\/div>\n\n\n

Member, sender and system fields<\/h2>\n\n\n\n

These fields are used in dynamic documents and in texts with the printing buttons.<\/p>\n\n\n\n

    \n
  • Member fields<\/strong> (Contact in VisualText, Member’s fields in BBCode) give the details of the person the document is about, for example the member whose file you are printing.<\/li>\n\n\n\n
  • Sender fields<\/strong> (Sender in VisualText, User’s fields in BBCode) give your own details, as the person who produces the document. They are written with my_<\/strong> in front, for example {{my_lastname}}.<\/li>\n\n\n\n
  • System fields<\/strong> give the details of your organisation and the date.<\/li>\n<\/ul>\n\n\n\n

    Member fields<\/h3>\n\n\n\n
    Field<\/th>What it shows<\/th><\/tr><\/thead>
    {{lastname}}<\/td>Last name.<\/td><\/tr>
    {{givenname}}<\/td>Given name.<\/td><\/tr>
    {{givennameplus}}<\/td>Other given names.<\/td><\/tr>
    {{sup_inst_sexe}}<\/td>Gender: male, female, or N\/A when not set.<\/td><\/tr>
    {{licnumber}}<\/td>Licence number.<\/td><\/tr>
    {{dob}}<\/td>Date of birth (N\/A when not set).<\/td><\/tr>
    {{sup_inst_pob}}<\/td>Place of birth.<\/td><\/tr>
    {{citizenship}}<\/td>Citizenship (country name).<\/td><\/tr>
    {{visa}}<\/td>Immigration visa expiry date (N\/A when not set).<\/td><\/tr>
    {{address}}<\/td>Address.<\/td><\/tr>
    {{address_post}}<\/td>Postal address.<\/td><\/tr>
    {{phone1}}, {{phone2}}<\/td>Phone numbers. Empty when not set.<\/td><\/tr>
    {{cell1}}, {{cell2}}<\/td>Cell phone numbers. Empty when not set.<\/td><\/tr>
    {{fax}}<\/td>Fax number.<\/td><\/tr>
    {{skype}}<\/td>Skype ID.<\/td><\/tr>
    {{email}}<\/td>Email address.<\/td><\/tr>
    {{groupe}}<\/td>Group name (“no group” when the member has none).<\/td><\/tr>
    {{res_name}}<\/td>Emergency contact: name.<\/td><\/tr>
    {{res_parent}}<\/td>Emergency contact: relationship.<\/td><\/tr>
    {{res_address}}<\/td>Emergency contact: address.<\/td><\/tr>
    {{res_phone1}}, {{res_phone2}}<\/td>Emergency contact: phone numbers.<\/td><\/tr>
    {{res_email}}<\/td>Emergency contact: email.<\/td><\/tr>
    {{role}}<\/td>Roles.<\/td><\/tr>
    {{roleDetail}}<\/td>Roles with their description.<\/td><\/tr>
    {{sup_resp}}<\/td>Responsibilities.<\/td><\/tr>
    {{sup_tache}}<\/td>Tasks.<\/td><\/tr>
    {{courses}}<\/td>List of the courses the member is enrolled in.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

    Sender fields<\/h3>\n\n\n\n

    Add my_<\/strong> in front of any member field to show your own details instead, for example {{my_givenname}} {{my_lastname}}, {{my_licnumber}} or {{my_email}}.<\/p>\n\n\n\n

    System fields<\/h3>\n\n\n\n
    Field<\/th>What it shows<\/th><\/tr><\/thead>
    {{company_name}}<\/td>Name of your organisation.<\/td><\/tr>
    {{company_address}}<\/td>Address of your organisation.<\/td><\/tr>
    {{company_location}}<\/td>ICAO location code of your organisation.<\/td><\/tr>
    {{company_website}}<\/td>Website address of your organisation.<\/td><\/tr>
    {{admin_email}}<\/td>Email address of the administrator.<\/td><\/tr>
    {{sysdate_yyyymmdd}}<\/td>The date the document is produced, as 2026-10-22.<\/td><\/tr>
    {{sysdate_ddMMyyyy}}<\/td>The date the document is produced, as 22 Oct 2026.<\/td><\/tr>
    {{sysdate_DMddyyyy}}<\/td>The date the document is produced, as Thu 22 Oct 2026.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
    \"System
    The System fields menu of a BBCode text box. The dates shown in the menu are only examples: the field always shows the date of the day the document is produced.<\/figcaption><\/figure>\n\n\n\n
    \"Portal
    In VisualText, the Portal Tags button lists the same fields under Contact, Sender and System.<\/figcaption><\/figure>\n\n\n\n

    Text that changes with a value<\/h2>\n\n\n\n

    A field can also show a different text depending on its value. Write the field name, a vertical bar |, then pairs of value:text<\/strong> separated by semicolons:<\/p>\n\n\n\n

    {{field|value:text;value:text}}<\/p>\n\n\n\n

    The most useful example is the polite form depending on the gender (1 = male, 2 = female):<\/p>\n\n\n\n

    Dear {{sup_inst_sexe|1:Sir;2:Madam}},<\/p>\n\n\n\n

    A male member reads “Dear Sir,” and a female member “Dear Madam,”. If the value matches none of the pairs, nothing is shown.<\/p>\n\n\n\n

    Rules for the texts:<\/p>\n\n\n\n

      \n
    • Use only letters (accented letters are allowed), numbers, spaces and full stops.<\/li>\n\n\n\n
    • Do not use commas, apostrophes, hyphens or brackets inside the texts: the field would then be shown as typed.<\/li>\n\n\n\n
    • Write each value exactly as it is stored (for gender: 1 or 2).<\/li>\n<\/ul>\n\n\n\n

      Fields in automatic messages<\/h2>\n\n\n\n

      Administrators can change the wording of automatic messages and emails in the settings pages (for example notifications about lessons, credentials, audits, qualifications or registrations). The default text of each message already contains the fields it can use, such as {{_studentname}}, {{_lessontitle}} or {{_auditor_name}}.<\/p>\n\n\n\n

        \n
      • Keep the field exactly as written, including the braces and the underscore.<\/li>\n\n\n\n
      • You can move a field to another place in the text, or delete it.<\/li>\n\n\n\n
      • Do not invent new fields: only the fields of the default text are filled in for that message.<\/li>\n\n\n\n
      • Before changing a message, copy its text somewhere safe so you can put it back if needed.<\/li>\n<\/ul>\n\n\n\n

        These fields can also be used in most automatic messages:<\/p>\n\n\n\n

        Field<\/th>What it shows<\/th><\/tr><\/thead>
        {{_myusername}}<\/td>Your last name and given name.<\/td><\/tr>
        {{_myemail}}<\/td>Your email address.<\/td><\/tr>
        {{_myphone1}}, {{_myphone2}}<\/td>Your phone numbers.<\/td><\/tr>
        {{_mycell1}}, {{_mycell2}}<\/td>Your cell phone numbers.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        The signature added to text messages (SMS) uses its own fields, listed in the help window of that setting:<\/p>\n\n\n\n

        Field<\/th>What it shows<\/th><\/tr><\/thead>
        {{_act_name}}<\/td>Last name and first initial of the person sending the message.<\/td><\/tr>
        {{_act_licnumber}}<\/td>Licence number of the sender.<\/td><\/tr>
        {{_act_ph1}}, {{_act_ph2}}<\/td>Phone numbers of the sender.<\/td><\/tr>
        {{_act_c1}}, {{_act_c2}}<\/td>Cell phone numbers of the sender.<\/td><\/tr>
        {{_act_date}}<\/td>Date of sending.<\/td><\/tr>
        {{_act_time}}<\/td>Time of sending.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Common problems and solutions<\/h2>\n\n\n\n
        Problem<\/th>Why it happens<\/th>What to do<\/th><\/tr><\/thead>
        The reader sees {{givenname}} instead of the name.<\/td>A brace is missing, or the field name is misspelled.<\/td>Use the menu or the Portal Tags button to insert the field instead of typing it.<\/td><\/tr>
        The field is empty.<\/td>The information is not filled in in the member’s profile, or the field is not available on this page.<\/td>Complete the profile, or use a field offered on this page.<\/td><\/tr>
        The gender shows “N\/A”.<\/td>The gender is not set in the profile.<\/td>Complete the profile, or rephrase the text.<\/td><\/tr>
        A text with values ({{field|…}}) is shown as typed.<\/td>The texts contain a comma, an apostrophe or another forbidden character.<\/td>Use only letters, numbers, spaces and full stops in the texts.<\/td><\/tr>
        My details appear instead of the member’s.<\/td>A my_<\/strong> field was used.<\/td>Use the field without my_ for the member’s details.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

        Quick best practices<\/h2>\n\n\n\n
          \n
        1. Insert fields with the buttons and menus rather than typing them.<\/li>\n\n\n\n
        2. Check the result with the PDF preview before sending or printing for many people.<\/li>\n\n\n\n
        3. Make sure profiles are complete: a field can only show what is stored.<\/li>\n\n\n\n
        4. In automatic messages, keep the fields that are already there and do not add new ones.<\/li>\n<\/ol>\n\n","protected":false},"featured_media":0,"parent":1573,"menu_order":1,"template":"","doc_tag":[],"_links":{"self":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/1579"}],"collection":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/types\/docs"}],"version-history":[{"count":9,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/1579\/revisions"}],"predecessor-version":[{"id":5582,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/1579\/revisions\/5582"}],"up":[{"embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/1573"}],"next":[{"title":"Using VisualText module","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/writing-text\/using-visualtext-module\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/3598"}],"prev":[{"title":"Using BBCODE","link":"https:\/\/www.airsupervision.com\/wp-r\/docs\/general-knowledge\/writing-text\/using-bbcode\/","href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/docs\/1578"}],"wp:attachment":[{"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/media?parent=1579"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/www.airsupervision.com\/wp-r\/wp-json\/wp\/v2\/doc_tag?post=1579"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}