In integration project when opening an AML screen from a subproject the filter acts on wrong default project
Summary
In an integration project when opening an AML screen (or faceplate) from a subproject the filter behaves incorrectly: it can display alarms from another subprojects or not display alarms when it should.
Description
In an integration project when opening an AML screen (or faceplate) from a subproject the filter behaves incorrectly: it can display alarms from another subprojects or not display alarms when it should.
Solution
Issue was addressed in choice of default project. Now the default project is taken from function and not from screen.
Information
Issue Number: 33726
Fixed on Date: 20.2.2015
Versions: 7.11 0 BUILD 18023
Related Articles
[3D Integration] Default Camera positions doesn't work correctly
Description In 3D Integration, the default camera position is not used when opening in the Service Engine. However, the default camera position is used in the 3D configurator. This behavior has been modified. The default camera position is now also ...
Variable identification in the Variable Diagnosis screen cannot be translated in Subproject from Integration project
Summary In the Service Engine, not all variables are translated as configured in the Variable Diagnosis screen. This has been fixed. Description In the Service Engine, with Multi Project Administration, the identification for variables from the ...
wrong default filter setting for file format wne selecting a project.ini file
Summary The startup tool allowes to select a start project for the runtime. For this, you need to browse to the project.ini file of the desired project in the 'RT-path' property. Unfortunately, with default settings the ini file will not show up in ...
It takes long to display the AML and CEL filter if there are many Alarm Areas in the Global project.
Summary If Global project (in Editor) contains many alarm areas, then in the Runtime, to open the filter dialog in AML or CEL screen, in the integration project, takes significant time. The more sub-projects included - longer it takes. For example in ...
An integration project of version 7.10 does not show historical alarms of 6.51 subproject (subproject uses different server than integration project)
Summary An integration project with subprojects where subprojects have different project servers, running with older zenon version - due to a step-by-step update to 7.10, the integration project server is on zenon 7.10 and the other servers are on ...