Website import

By default website import is available in builder by hovering New/Reset button and choosing Import option.
Import can also be implemented on your hosting website as a simple form. The form submits import request to your public demo URL in order to show your client how importer works. Here is an example:

Overriding existing help scenarios available since version 3.7.157 (enterprise only)

All enterprise builder scenarios are located in ./scenarios folder. Every scenario is its own folder,
where folder name is scenario ID. Scenario folder can contain subfolder gallery that should
contain all images and audio files used by that scenario. Scenario folder must contain .json
file with description of that scenario. JSON file name should be [scenario ID].json. See ""

If you want to override/change existing builder scenario, then instead of editing that scenario
create a copy with same name + -ext and edit that. For example if you want to override
scenario TextArea then create scenario with name TextArea-ext and it will
be used in stead of original.

JSON file structure

File structure is one JSON object with these properties:

Stringname
- Friendly name of the scenario;

Stringtemplate
- (optional) Builder site template identifier to load when this scenario starts;

Stringaudio
- (optional) Relative URL to background music file that will be looped while scenario is playing;

NumberrequireSpace
- (optional) Height of space in pixels to free up in websites body for this scenario;

Array of Objectsteps
- List of scenario steps that will be performed in order one after another;

Steps property value is JSON array of step definition objects with these properties:

Stringtitle
- Title of the step that will be shown in tooltip;

Stringtext
- (optional) Text/description of the step that will be shown in tooltip;

Adding custom builder plugins available since version 3.7.81 (enterprise only)

You can add your custom created plugins to your enterprise builder installation by placing them to folder
<builder_installation_root>/plugins.
You can enable your custom plugins by adding file <builder_installation_root>/plugins/plugins-ext.json.
File format is the same as <builder_installation_root>/plugins/plugins.json.
Those two files will be merged by adding custom plugins listed in plugins-ext.json file
to your builder toolbar after plugins listed in plugins.json file.

Since builder version "3.7.262" it is possible to place plugins to custom groups. When defining plugin group, set new
unique ID, name and icon.For icons you can
use bootstrap (ex. "glyphicon glyphicon-cloud")
or font awesome (ex. "fa fa-cloud") icons.
Ex.:

Scripts available since version 3.7.288 (enterprise only)

Scripts can be used in order to insert extra piece of code to clients' websites or into builder itself.
All scripts must be located in your builder installation folder /assets/scripts (create folder if it does not exist).Make sure that scripts folder is readable by Web server.