Where are messages saved?

This article is for BEE Plugin users (the embeddable version of BEE). If you are using BEE Free or BEE Pro, see Saving messages on beefree.io.


BEE Plugin does not store any messages.

When the user of the editor saves a message by clicking on a "Save" button (in the editor's default toolbar or in your application's user interface), the Plugin will call the function that you have specified in the configuration and return:

  • a JSON file
  • an HTML file

Saving a message

In your application, you will want to save:

  • the JSON file to allow the user to edit the message again later
  • the HTML file so that the message can be sent as an HTML email

Where is it saved?

It's entirely up to you how and where to save these files. You can save them as individual files in a file system, or save the code in a database field, for example.

Messages or templates?

There is no difference between a message and a template as far as the BEE editor is concerned: it's just a JSON file that you pass to the editor to allow your users to create a message (starting from a JSON document that you previously saved and present to them in a template catalog) or edit an existing message (starting from the JSON document that you saved when the user previously worked on it).

There three methods that save a document: Save, SaveAsTemplate, and AutoSave: see all the details in Configuring the editor.

Have more questions? Submit a request

Comments

  • Avatar
    Daniel

    Why not adding the Bee Pro feature, where you can save and lists templates/messages to Bee Plugin? It would be great.

  • Avatar
    Massimo Arrigoni

    Hi Daniel, thanks for your feedback.

    So far we have not gone in that direction because the many applications that have integrated the BEE editor via the Plugin - from what we've seen - each have their own way to store and display messages (and templates).

    This applies not just to the way messages and templates would be listed & searched for, but also to the functionality provided to users. For example, the "actions" associated with a message (apart from "Edit", which would open the editor for editing) change depending on the individual application.

    That said, if there is more interest in the BEE community for this type of feature in the future, we'll definitely look into it.

  • Avatar
    Nitish Singh

    Is there any option, to get the current JSON of email template.? We get the json and html on the events predefined in bee editor. but for some validations I need to get the Current JSON of email Template. Any workaround for that.?

  • Avatar
    Massimo Arrigoni

    Hi Nitish, you can invoke saveAsTemplate() to trigger the onSaveAsTemplate callback, which only returns the JSON of the message (see http://help.beefree.io/hc/en-us/articles/202991212-Configuring-the-editor). Because it only returns the JSON, it's much quicker than the Save() method, which returns both the JSON and the HTML of the message, and takes longer because parsing the JSON to generate the HTML takes a few moments. On this, please also see: http://help.beefree.io/hc/en-us/articles/207615549-Using-templates-and-messages-a-sample-workflow