SOT replacing rule does not work after change on SOT if SOT is referenced in other SOT

• Related Articles

• Deleting of an Referenced Smart Object Template causes Zenon to Crash

  Summary Deleting a referenced Smart Object Template (SOT) causes zenon to exit unexpectedly. This error has been fixed. Description A SOT contains a zenon Logic project and a variable that is externally visible for zenon Logic. This SOT is referenced ...

• Checklist: Smart Client does not work

  Time estimate: 20 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

• SOT: The mapped variables are not shown in Extended Trend screen

  Summary Mapped SOT variables should be shown now correctly in the Extended Trend screen. Curves should work correctly and as well the cursor output list should display the correct mapped variable values Description Mapped SOT variables should be ...

• History of changes/Smart objects: A change in a property of the SOT (e.g. variable name) causes a change in all properties in the corresponding instances.

  Description Changing a property of a Smart Object Template (SOT) causes an entry to be made in the “History of Changes“ for all properties in the corresponding instances. This leads to a rapidly growing database with a lot of superfluous information. ...

• SO - Rule-based variable mapping

  Summary Smart Objects allow rule based variable mapping. Description Smart Object variables are now consumed in Engineering Studio and Service Engine for the licensing. The order of the rules for variable mapping can now be changed manually. The ...