View source | View content page | Page history | Printable version   

Projects:Modularity/Technical Documentation


Export process


Configuration script

Configuration script definition

Script elements

The elements that can be part of a configuration script are a limited set of database attributes. These elements are the only ones that can be within a clean configuration script. In order to allow more complex customizations the rest of elements can be exported as dirty configuration scripts.

In order to define which elements are script ones all the columns in the dictionary will have a check that will indicate whether the column can be part of a configuration script.

Backwards compatibility

When a script element becomes a non-script element the scripts containing this element will warning the user saying he is importing as clean something dirty but it will be imported anyway.

Script files

A script can be divided in two parts:

Exportation tool

The exportation tool allows to export as a set of modules and a configuration script any customization. When this tool is executed the result it gives is:


The way the exportation tool works is as follows:


While the exportation is achieved it can store a list of modules that the script is modifying, these modules will be necessary to apply the script so they should be saved as dependencies for the script. Note that though all they are dependencies there could be other modules that are also dependencies.

Exporting a customization

A common case of use is to export a customization as an industry template. In this case all the new elements that are part of modules should be in the “customization” module which should be checked as “in development”. The result of running the exportation tool would be:

Retrieved from ""

This page has been accessed 6,473 times. This page was last modified on 8 June 2012, at 05:28. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.