Template import/export

Developers often have the need to create Templates in bulk and to configure them. A tool is needed that abstracts the complexity of the GRAccess toolkit but is more [flexible] than Object CSV import/export functionality.

In addition to this there is also a need for a text-based configuration import and export functionality that can be utilised by Git repositories to facilitate version control.

The intent is for a user to be able to have 2 experiences:

1. A simple import export capability that allows a user to quickly create or modify a template with:

   1. Attribute names

   2. Attribute types

   3. Attribute values

   4. Attribute Description

   5. Attribute Engineering Unit

2. A full-blown Import/Export facility:

   1. The ability optionally configure features and their parameters e.g.,

      1. History

      2. IO

      3. Alarming

      4. Statistics

      5. etc.

   2. The ability to link content to the template:

      1. Graphics

      2. External Content

      3. Layouts

   3. The abilitiy to optionally create/modify Wizards - this could be done in a supplementary text file

The workflow should allow

1. Export existing Templates to a text based configuration file (e.g. CSV, XML, or JSON)

2. Create/Modify Templates in bulk by importing a text based configuration file (e.g. CSV, XML, or JSON)

3. The following Template features should be supported:

   1. Attributes

   2. Wizards

   3. Scripts

   4. Linking Content

      1. Graphics

      2. External Content

      3. Layouts

4. This method should either align easily with the existing CSV import/export to create instances or augment it

5. The Graphic Import/Export API can be utilised to allow creating graphics directly on templates

6. In an ideal world, the combined export will result in a file or set of files that could be stored in a git repository (on-premises or in a cloud repository such as GitHub) and that could be used to monitor and manage changes