*Note:* this path has to be absolute, a relative path won't work

h3. Add some sample projects \[optional\]

As actual version doesn't support projects persistence (don't worry its part of our road map ), you won't be able do save a project (although it can be exported and imported later on). If you want to test the "Open" functionality, you can add some sample data via the configuration file that will act as a database mock. To do so, a standard notation have been adopted. In you configuration file you can add the following line (after or before the PROJECTS_DIR property):

{code}
DB_MOCK = ProjectType:/Project/Absolute/Path:ProjectName
{code}
Where:


*ProjectType:* is the project type id (the editor actually support only two ids \['BPMNDesc' and 'BPMNExec'\])


*Project/Absolute/Path:* is the actual absolute path that point to a bpmn project file (for now it must be a zip file that contains both bpmn and bpmn-di files)


*ProjectName:* is the name that will be displayed on the user interface when selecting a project type

Here is an example :


{code}
DB_MOCK = BPMNDesc:/home/user/bpmn/pizzaiolo.zip:BPMN 2.0 Pizzailo example
{code}


In this example we add the project file (pizzaiolo.zip) in BPMNDesc project type and display the label "BPMN 2.0 Pizzaiolo example" when the project type is selected.

You can add as many as project by separating the standard notation with commas :

{code}
DB_MOCK = BPMNDesc:/home/user/bpmn/pizzaiolo1.zip:BPMN 2.0 Pizzailo 1 ,BPMNExec:/home/user/bpmn/pizzaiolo2.zip:BPMN 2.0 Pizzailo 2
{code}