Skip to main content
Version: 2.2

Projects and Folders

There are two ways to organize your content in DRAW: Projects and Folders.

  • Projects are containers for all software pieces that share the same objective. They contain apps, user interfaces, data models, business logic, other folders, etc. Projects can also be used to create libraries of reusable bricks that can be imported into other projects.

  • Folders are containers to organize content inside a project. They contain apps, user interface components, data models, business logic, other folders.

Create a project, folder

Create one or the other by drag-and-dropping them from the marketplace on the right side of the screen into the main editor.

On the top-right corner of the project, click on the three dots. All elements can be manipulated using their contextual menu: folder



A Project* can not be moved inside another project. Only in Projects there is the possibility to import other projects.

Projects can only contain folders or bricks.

Moving Folders is possible only in the same Project.


Changing the name of a project or folder can be done using the Rename feature. This can be done either from the three dots (the contextual menu) or from the object’s path in the header.


Exporting a project produces and downloads an archive containing its content with <Project_name>.zip, (e.g. to create backups of older versions) and data is archived as .json files. Archives can be reimported later on a different environment. It can also be used as simple backup. In this case, the tags are not regenerated.


Duplicate feature allows the creation of a copy of a project a folder or of some of its content. Tags are regenerated.


Removing a project or a folder can be done via the Delete feature. A confirmation pop-up requires the user to validate the delete action. At the moment, there is no check for the dependencies with other components, therefore, the deletion is taking place even if dependencies are in place.

Show tag…

Displays the technical unique identifier of the tile in a pop-up window.

Project Editor

The Project Editor allows to create and edit projects and applications in DRAW.

The main interface is divided into four parts - Top menu, Sub-editor, Editor content, Right panel editor: interface

Projects have tabs on top: Folder, Spec & Doc, Dependencies and Runtime Data. project_structure


Home represents the root and lists all the root folders that exist.

Default represents the default root folder (e.g: name given by the customer to the project). It is created one time only at the beginning of the DRAW instance and it can not be deleted or moved.

A Folder contains organisational elements inside the project. It's pretty similar to a classic folder but can contains all the elements that a project can have. For the content, an icon (corresponding to the type of object), the name and the preview (if available) are displayed. Clicking on an object opens it in its appropriate sub-editor.

Content can be added and manipulated from the Marketplace items displayed on the right side of the screen:

  • Action

  • Data Model

  • Static Data Folder

  • Folder

  • Function

  • Media Library

  • ServiceApp

  • Screen

  • Theme

  • Visual App

  • UI Element

  • Visual Component

Spec & Doc

Contains a description of the Project. It can have a summary as a tooltip and/or a more elaborated description.


A project can import another project so as to reuse some components, data and logic, therefore, a project can include other projects as dependencies. This allows creating one project acting as a library of reusable bricks, which can then be reused across multiple other projects. Bricks of the imported project become then available in the Marketplace. Updates to the library project are immediately reflected in the importing projects as well. Only public bricks of the imported project are available in the Marketplace. dependencies

Runtime Data

Lists all runtime objects visible within the project. It contains the objects created within an app, containing models with their relations and properties.

The goal is to offer a view of the runtime instances that are in the database for the Project. Content is created via APIs at runtime or via the + button inside the editor itself. Dependency data on other projects are not listed and visible inside the Runtime Data editor.

global data set