A release record covering version, project, runtime configuration, plugin data, and acceptance results.
Before you begin
- Acquisition, screens, alarms, and reports have passed the earlier checks.
- Test and runtime targets and plugin data locations are known.
01 · Capture a recoverable state
- Record host/plugin/project versions and back up projects, runtime configuration, view assets, and actual plugin data.
- ReportStudio and DynamicData use ReportStudio.db and PlgDynamicData.db respectively. Back up both using a supported consistent or stopped-service procedure.
- Verify restoration in an isolated directory rather than backing up assemblies alone.
A version-matched backup has been checked for recovery.
02 · Follow the correct release route
- For a delivered package, follow its version-specific deployment instructions without assuming customers have licensed source or SDKs.
- For source builds, compile the required solutions with .NET 8 SDK and build their frontends before copying artifacts with BuildScripts.
- Use ScadaV6WebPluginExtReact with ScadaWebExt for the React line; retain matching Legacy artifacts at existing sites.
The target contains plugins from the selected product line only.
03 · Apply configuration and inspect assets
- Confirm target directories and site URL, deploy built host/plugin artifacts, and preserve runtime configuration and plugin data.
- Upload the matching project and restart affected applications as required. Check /swe/app.js and enabled plugins’ app.js at the target site.
- Mimic uses official PlgMimicEditor, optionally embedded by the React host; do not install the removed React Mimic editor.
Host and enabled plugin resources load and menus open the intended pages.
04 · Retest with viewer and maintainer accounts
- As a viewer, check live values, trends, screens, events, and reports; as a maintainer, check save/configuration rights.
- Record one communication loss/recovery and one multi-page report export.
- Document backup location, restoration order, service operations, and support contact in the actual handover record.
Handover covers normal operation, recovery, and permission boundaries.
Troubleshooting
Menus exist but plugin pages return 404 after upgrading
Check that assemblies, language files, and app.js are from the same release in the actual runtime directory, then inspect Web logs/routes.
Configuration edits have no runtime effect
Verify the deployed instance and runtime target and required reload/restart. Preserve the site version rather than overwriting whole directories to experiment.