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.

• Related Articles

• FAQ: What are Installation and Security considerations of the zenon Smart Server and Smart Client?

  The attached document (English only) describes in some detail the specifics of the zenon Smart Server Application and the zenon Smart Client Application. Also a short explanation of security features and components is given. More information about ...

• Checklist: Smart Client cannot establish a reliable communication

  Time estimate: 60 minutes Please go through all the items in the following checklist. If necessary, confirm any information you cannot verify with the IT department before contacting your local COPA-DATA representative. Checklist usage: #. [Quick ...

• Smart Objects: Releasing a property of a symbol leads to renaming of zLo variables in SO-instances and therefore break of links

  Summary at update of a smart object template that has zenon logic variables the name of the variables at the instances are adapted correctly like at creation of an instance and not do not use the original name from the template. this is also true if ...

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

  Description A Smart Object Template (A) is referenced in another Smart Object Template (B). After changes in SOT A, the already existing Smart Objects of SOT B are unusable. Screens no longer work. However, newly created Smart Objects work as ...

• The history of changes may not log a screen element position change in the editor.

  Summary Despite the detailing level is set to "object", the history of changes may not log the change of a screen element position when using the "position" properties in the editor. DescriptionDespite the detailing level is set to "object", the ...