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) |
|---|---|
|
|
|
|
New data structure
Custom data DB table:
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:
https://github.com/com-pas/compas-scl-data-service/issues/594
https://github.com/com-pas/compas-scl-data-service/issues/647