Evaluation of a generic approach for storing non SCL-Resources for multiple UI plugins

Evaluation of a generic approach for storing non SCL-Resources for multiple UI plugins

Description

The problem we are trying to solve is to store custom non SCL-Resources depending on the plugin which tries to store the data e.g. process for engineering-wizard, data-types & default data-types for templates-generator, …

 

Store custom data as SCL-Resource in the SCL file

Introduce a generic approach for storing content based on (type,tenant,name)

Store custom data as SCL-Resource in the SCL file

Introduce a generic approach for storing content based on (type,tenant,name)

:check_mark: endpoints already available

:check_mark: easy extendable for different plugins

:check_mark: no adaption on backend-side

:check_mark: easy to used for plugins

:check_mark: custom data can be assigned to plugin via type naming convention

:check_mark: if not used, does not affect the system

:check_mark: efficient queries when looking up specific custom data

:check_mark: generic approach for storing data for a plugin

:minus: mapping of different data to wrong SCL data-type

:minus: no way to efficiently filter for this custom types except loading everything from backend and parse the content

:minus: Loading from SCL-Resources will not work for this custom types

:minus: new endpoints must be created

:minus: generic approach, data is only interpretable by managing plugin

 

New data structure

Custom data DB table:

id

type

tenant

name

description

content-type

content

version

data-compatibility-version

id

type

tenant

name

description

content-type

content

version

data-compatibility-version

<generated>

engineering-wizard_process

transnetbw

Default Engineering Process

Standard Prozess für einen Netzbetreiber

json/xml/…

“{…}”

1.1.0

1.0.0

<generated>

<plugin-name>_<type>

customer name, default = “default“

 

 

 

 

 

 

We agreed to process with Option B and implement an additional endpoint to handle plugin specific data.

 

Related tickets: