Dear community, I am writing this post to inquire if anybody else experienced the serious issues we are having with using object wizards. Let me preface this by saying that we have a case opened with AVEVA tech support, but debugging this issue seems quite hard to do.
The problem is that at still unclear circumstances instances lose selected wizard options and start behaving unexpectedly. Let me give you a couple of examples.
Our area template has a wizard option that is off by default and visible only if a particualr wizard choice is selected. When the option is selected, a script is added to the instance that performs some SQL queries. Most of the areas do not have this choice selected, but for some reason they are trying to execute the script in runtime. Please observe the screenshots available here.
Screenshot1 depicts area template configuration. As you can see, wizard option "Statistika bušotine" is conditionally visible, off by default and has a script associated with it.
Screenshot2 depicts one of the instances and wizard choices applied to it. As you can see, there is no sign of "Statistika bušotine".
However, in Screenshot3 we can see that the Scripts tab of this instance shows the script, and the script is actually being executed in runtime and throwing warnings "Object reference not set to an instance of an object".
Upon validation of the instance, it displays that there are changes as shown in Screenshot4. Scripts that should not be there are gone however as expected (Screenshot5).
All of the object templates have several configuration attributes used for referencing IO attributes. Wizard gives you the option to choose how many of those you would like (from 1 to 5). Upon selection, you can configure the values of these attributes. At certain conditions, values entered in these attributes get lost and the instances stop working as expected. Similarly, event though the selected option is 3, only two items are visible in instance until that wizard option is toggled from 3 to 2 and then back to 3.
Other wizard options determine available attributes for an asset (valve for example). Valve can have only on signal (open/closed) or several (status, commands, percentage open etc.). The choices sometimes get lost resulting in object referencing attributes in OI server that are not defined as they do not exist...
The galaxy was started from scratch on version 2023. It has been since regularly patched and is now on 2023 R2 P01. The issue persists. We have tried numerous time to create a new galaxy from the backup or to start from a clean galaxy and import the objects, but it always circles back to these issues.
I am sorry if I have been confusing, however we are all rather frustrated. There are several thound instances in the galaxy and they are all prone to this failure resulting in huge burden in maintenance and in extremely unreliable experience for the operators.
Kindly share if anybody has experienced something similar.
