Changes to automation object templates do not get inherited to all child instances (seems random) , way to debug analyse cause?

Hi  Jakob Agustsson and IDO BARZILAI 

I came across the same issue when I built a test galaxy with System Platform 2023R2. I made a small change in script in the template derived from $UserDefined one, in which Me.X = Me.Y * A; became Me.X = Me.Y * B; where Me.X was a calculated variable, Me.Y was from PLC and A or B was a coefficient. The instances that missed the update were in the deployed mode. A newly created instance appeared to have the change.

When I checked in the change, the check-in window showed a warning about propagating the changes, and no error was logged in OCL. There is no lock in my template.

The question is if the change made in the template can be propagated to its instances in the deployed mode. I am not aware if there is any method to allow users to synch up the instances with their template if some of them miss the changes.

Hi  Jakob Agustsson and IDO BARZILAI 

I came across the same issue when I built a test galaxy with System Platform 2023R2. I made a small change in script in the template derived from $UserDefined one, in which Me.X = Me.Y * A; became Me.X = Me.Y * B; where Me.X was a calculated variable, Me.Y was from PLC and A or B was a coefficient. The instances that missed the update were in the deployed mode. A newly created instance appeared to have the change.

When I checked in the change, the check-in window showed a warning about propagating the changes, and no error was logged in OCL. There is no lock in my template.

The question is if the change made in the template can be propagated to its instances in the deployed mode. I am not aware if there is any method to allow users to synch up the instances with their template if some of them miss the changes.

Hi Jakob,

In order to propagate the changes from a template to an existing instances (deployed or undeployed), you must use the template script locks before check-in the changes.

Thanks Ido. It worked. So, the general rule is to place a lock on a changed item in the template in order to propagate the changes well to existing instances.