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

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 intended.

This error has been fixed. Screens work correctly in Smart Objects of referenced Smart Object Templates.

 

To benefit from this fix:

  • Update your zenon Software Platform to the latest build of zenon 11 or higher.

 



Item ID: 262148
Version: 11.00 Build: 157700

    • Related Articles

    • zenon Changesets Excel

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in CSV format ...

    • zenon Changesets CSV

      Here, you can access a comprehensive list of changes across all maintained versions of the zenon Software Platform as Excel Worksheets. This includes both implemented bug-fixes and new features. Additionally, these lists are available in as Excel ...

    • 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 ...

    • Renamed references do not rename zenon logic programs when updating the SOT

      Description In a project references of a Smart Object Template (SOT) are renamed. When updating the SOT, zenon Logic programs are not renamed accordingly. The original names are still included. This behavior has been changed. When renaming ...

    • SOT : crash when creating a new SOT

      Description The creation of a new SOT via the Equipment Group led to an unexpected closure after a switch between projects. The issue has been addressed and the behavior is now as expected. To benefit from this fix: Update your zenon Software ...