SCADA-LTS / Scada-LTS

Scada-LTS is an Open Source, web-based, multi-platform solution for building your own SCADA (Supervisory Control and Data Acquisition) system.
GNU General Public License v2.0
718 stars 287 forks source link

Extension of the Import/Export Project function #2731

Open Limraj opened 11 months ago

Limraj commented 11 months ago

Descrption The Import/Export functions of the project should be extended and the following defects should be corrected:

To Reproduce

  1. Login as admin;
  2. Created Virtual Data Source (update: 1s, enabled) as ds_1 nad Data Point dp_1 (binary, settable, enable, no change, start value 0 )
  3. Created two Schedule Event as se_1 and se_2: image image
  4. Created 'Compound event detectors' as ced_1: image
  5. Created 'Maintenance event as me_1': image
  6. Click on 'Data Sources' -> edit ds_1 -> on dp_1 click on 'Point properties': image and click on 'Point details': image and click on 'Add comment': image And set abc and click on 'Save': image
  7. Click on 'Import/Export', select 'Include Graphics folder', set 'Scada-LTS' in 'Project name' and click 'Export Project': image
  8. Next click on 'Choose file' (in english), select 'Scada-LTS.zip' and click 'Send': image
  9. Click on 'Import' and ok, and login as admin:
    • User Comment 'abc' for dp_1 is missing;
    • Maintenance Event me_1 is missing;
    • In ced_1 he did not modify the markings;

Spec:

fabiodurao commented 11 months ago

Yesterday I exported a project from one server and imported it to another and I had some problems, all with Scada-LTS 2.7.5.3 to 2.7.5.4:

1- The screen background images and components from the graphics folder were not loaded (I believe this has already been reported in other issues); 2- The special characters used in Portuguese such as "é" "ã" "ç" among others were not loaded correctly, I needed to edit the names of datapoints, datasources and graphic representations, HTML components among others; 3- The ids that are created in the auto-increment model are not maintained, for example, there were 4 screens, with ids 1,2,3 and 4 and links between them, when I imported they came with ids 2,3,4 and 5, I needed edit the navigation links for all screens. I've also had problems with other imports with the datapoint ids called dpids, they were changed and in this case, there was an integration with another software that collected data from the pointValues table using the dpids, it was necessary to map them again and redo the integration. The XIDs are kept intact, I don't know if there is any way to keep the ids too.

I hope I contributed to the topic.