DASTRA
English
English
  • What is Dastra
  • 🇪🇺USEFUL REMINDERS
    • What is GDPR ?
    • GDPR key concepts
      • Personal data
      • Record of processing activities (ROPA)
      • Privacy impact assessment
      • Data retention period
      • Data Subject Rights (DSR)
      • Privacy by design and by default
      • Security measures
      • Data breach notifications
    • Risk management
      • Definition of risks
      • Risk assessment
      • Vendor risk management
  • 🧑‍🎓GETTING STARTED
    • Setting up
      • Create and set up a workspace
      • Create and set up organizational units
      • Appointing a DPO
      • Add a lead authority
      • Invite users
      • Managing roles and permissions
      • Create and assign teams
      • Frequently asked questions
    • Tutorial
      • Step 1: Setting up
      • Step 2: Map your personal data processing and draw up a register
      • Step 3: Managing risks
      • Step 4: Prioritize actions
      • Step 5: Implement internal processes
      • Step 6: Document compliance
    • Support
      • The dastronaut's assistant
      • Online help
      • Request support
      • The customer support process
  • ⚙️Features
    • Dashboard
    • General
      • Advanced Filters
      • Import your data (Excel, Csv)
      • Tag management
      • Custom fields
      • AI Assistant
      • Email templates
    • Data Mapping
    • Record of processing activities
      • "Data controller" record
      • "Data processor" record
      • Establish your record
      • Export / import the record
      • Use a processing activity template
      • Declare a processing activity
      • Complete a data processing activity
        • General information
        • Stakeholders
        • Purposes
        • Dataset
        • Assets
        • Data subjects
        • Data subjects rights (DSR)
        • Recipients
          • Data transfers outside the EU
        • Security measures
        • Impact analysis
        • Documentation
      • Create relationships between processing activities
      • Processing freshness
      • Share the record of processing
      • Data visualization
        • View the treatment tree
        • View the record data map
        • View the transfers map
      • Frequently asked questions
    • Audits and DPIA
      • Create or modify an audit template or DPIA
      • Scheduling an audit or a PIA
      • Share an audit report or PIA
      • FAQ
    • Privacy hubs
      • Create a Privacy hub
      • Configure your Privacy hub
        • Homepage and general configuration
        • Questionnaires
        • Data subject requests
        • Record of processing activities
        • Attachments
        • Organizational chart
        • Contacts
        • Security
        • Appearance and design
      • Preview and share your privacy hub
      • Collecting data processing projects from a Privacy hub.
    • Contracts
      • Declare a Contract
      • Structure of a contract
      • Documents
      • Assets
      • Signers
      • Linked users
      • Sign the contract
      • Docusign integration
      • Contract versions
      • Contract templates
    • Risk management
      • Glossary of terms
      • Risk management process
        • 1. Identification
        • 2. Assess
        • 3. Monitor
        • 4. Control
        • Let's recap
      • Dastra / eBios RM comparison
      • Attach a risk to a processing activity
      • FAQ
    • Planning
      • Create your action plan
      • Create or modify a project or an iteration
      • Monitor, screen or export your tasks
      • Customise the task workflow
      • Share as calendar
      • Customise the task workflow
      • Go further with planning
      • FAQ
    • Data subject right request
      • Manage data subject right requests
      • Set up a data subject right request widget
      • Technical integration
      • API integration
    • Manage data breach notifications
      • Report a data breach
      • Export your data breach notifications
    • Manage cookies consent
      • Widget configuration
        • Preliminary study
        • Cookies scanning
        • Classify cookies by consent categories
        • The purposes of cookies
        • Implement a cookie consent widget
        • Collect proof of cookie consent
        • Go further on cookie consent
        • In case of unavailability
      • Technical integration
        • Functioning of the widget
        • Quick start
          • Wordpress
        • Language management
        • Test the integration of a widget
        • Blocking cookies
          • Blocking iframes (twitter/youtube...)
          • Google Tag Manager
        • Advanced Design
        • Manage consent programmatically
        • User identification
        • Mobile applications
          • Hybrid applications
          • Native applications
        • TCF 1.1/2.0
      • RGAA compliance
      • Breakdown service
    • Regular review (freshness)
    • Custom Reporting
      • Integration with data analysis tools (BI)
    • AI Systems
      • Establishing a record of AI systems
      • Risk analysis and business value
      • Transparency notice
      • AI Models repository
    • Advanced configuration
      • SCIM
      • Roles and permissions
      • Single Sign On (SSO)
        • SAML 2
        • OpenId
        • ADFS
        • Active Directory
        • Okta
        • Known problems
      • References
      • API key management
      • Notifications
      • Workflow steps / process flow
      • Incoming mail data collection
      • OneDrive/Google Drive integrations
      • Webhooks
      • SMTP configuration
      • Workflow rules
      • Message templates
      • Email domains
  • PARTNERS
    • Portal
  • 📄API documentation
    • Configuration
    • Authentication
    • API References
    • Integrations
      • Frequently asked questions
  • 🛡️Security
    • Security at Dastra
    • Security roadmap
    • Quality of Service
  • Certifications
  • 🤖Other
    • FAQ
    • Known problems
    • Changelog
  • Referentials
    • CNIL referentials
      • HR referential from CNIL
Propulsé par GitBook
Sur cette page
  • General
  • How to use
  • Customise the model
  • Going further with custom fields
  • Create new custom fields from Input Data
  • Conditional blocks
  • The loops
  • Date format
  • A more complex example

Cet article vous a-t-il été utile ?

  1. Features
  2. General

Email templates

Learn how to use email templates and generate emails with dynamic content to communicate with your customers or colleagues.

Dernière mise à jour il y a 6 mois

Cet article vous a-t-il été utile ?

General

Email templates are a feature of data subject rights management, customised workflows and audits. Once saved, they are a quick way of communicating with stakeholders. The data set of an object can be incorporated into them, and it is even possible to set up conditions and loops to retrieve more information.

How to use

To select or create a template, click on "Select or create a template".

you can then search for an existing template in the list or the search function, or look at the templates available in the workspaces to which you have access or the templates created by Dastra). If you don't find a suitable template, click on "New template".

The model creation interface comprises 4 elements:

  • The name (so that the model can be found later)

  • The input field (body of the template, framed in green)

  • A Preview tab: displays the rendering of the email in real time

  • An Input Data tab: lets you view the data for the object concerned by the template

Customise the model

You can edit the template and apply styles, insert images or tables as required. You will see the result in the preview tab. If you click on "Custom fields" you will have access to a list of fields to insert. The value of the field will be inserted at the level of the mouse cursor. Of course, you can format the text as you wish.

Going further with custom fields

Create new custom fields from Input Data

By clicking on the "Input Data" tab, you can access the list of properties of the linked object. In the example below, I decide to display the message linked to the request:

  • I search for the field in "Input Data".

  • I enter the name of the field in the body of the message using the syntax {{message}}

  • I check the result using the "Preview" tab

That's it! Now you can create your own custom fields. But that's not all! You can also go even further by creating loops, conditions and applying formats to make the dates easier to read!

Conditional blocks

It is also possible to create conditional blocks that will only be displayed under certain conditions. To do this, you need to use the conditional tag system, which starts with

. In this way, I can write the following condition:

{% if attachments != blank %}

You have an attachment

{% endif %}

The block will only be displayed if there is an attachment in the request.

The loops

Loops work in the same way, except that this time we generate a variable internal to the loop. It works as follows:

{% for purpose in purposes %}
  {{ purpose }}
{% endfor %}

In the example above, I declare that I want to loop through the "purposes" list and assign the "purpose" variable to each item that I display directly.

Date format

You will quickly see that the dates you retrieve from Input Data are not presentable as they are. Don't worry, you can assign a format to the date.

{{dateCreation | date: "%d-%m-%Y à %H:%M"}}

Will be transformed into 15-03-2023 at 15:40

A more complex example

The body text below uses all the above elements

Hello, We have received your request to exercise your rights on {{dateCreation | date: "%d-%m-%Y à %H:%M"}} concerning Mr or Mrs {{givenName}} {{familyName}}. The request relates to the following purposes :

{% for purpose in purposes %}

  • {{ purpose }}

{% endfor %}

{% if attachments != blank %}

We have received the following attachments:

{% for attachment in attachments %}

  • {{ attachment.fileName }}

{% endfor %}

{% endif %}

Please accept my sincerest greetings and I will keep you informed of the progress of your request.

Yours faithfully {{operator.displayName}}

For the request currently being processed, it will be transformed as follows:

Hello, We have received your request to exercise your rights on 31-07-2023 à 11:55 concerning Mr or Mrs . The request relates to the following purposes :

  • Access

Please accept my sincerest greetings and I will keep you informed of the progress of your request.

Yours faithfully, Paul-Emmanuel Bidault

The fields surrounded by double braces are "variables". In other words, they will be replaced by the values of the corresponding object (in this case, a request to exercise a right).

For more information regarding the Liquid syntax, please go to .

⚙️
this page