Updating instances and prototypes

when an object is instantiated from a prototype, the object is weakly linked to the prototype, i e from the asset detail page there is a link to the prototype, and from the prototype detail page there is a list of all objects instantiated from it it is possible to link existing objects to a prototype, and to unlink objects from a prototype (see linking and unlinking ) updates to the prototype are not automatically applied to the instances, and updates to instances are not automatically applied to the prototype when any instantiation of a prototype has deviated from the prototype, either by updating the prototype, or by updating the instance, it is reflected in the detail page of the prototype, the detail page of the affected asset, and the detail page of the affected asset property updating an instance from the prototype by clicking the update from prototype button on the asset detail page, an overview is shown of the differences between the prototype and the instances created by it the overview shows the properties that have been updated in the prototype or the instances since the instance was created items with a green icon can be updated without user interaction, items with a red icon require manual intervention because both the prototype and the instance have been updated (see /#conflict resolution ) items are marked with ‘(no change)’, ‘(update)’, ‘(override)’, ‘(new)’, ‘(link and update)’ or ‘(link and keep)’ based on the differences between the prototype and the instance ‘(no change)’ means the property has not been updated in the prototype or the instance since the instance was created ‘(update)’ means the property has been updated in the prototype since the instance was created ‘(override)’ means the property has been updated in the instance since the instance was created ‘(new)’ means the property has been added to the prototype since the instance was created ‘(link and update)’ means the property has been added to the prototype since the instance was created and the existing property will be linked to the new prototype property and update according to the prototype ‘(link and keep)’ means the property has been added to the prototype since the instance was created and the existing property will be linked to the new prototype property and keep the existing value bulk updating instances from the prototype by clicking the bulk update instances on the prototype detail page, an overview is shown of the differences between the prototype and the instances created by it the overview can be shown prototype based or asset based prototype based ‘prototype based’ shows the asset prototype and its configured asset property prototypes and event configuration prototypes items with a red icon need manual intervention because both the prototype and the instance have been updated the number between parentheses signifies the amount of instances that have conflicts for every conflict, the user needs the select the appropriate /#conflict resolution strategy asset based ‘asset based’ shows the asset instances and their configured asset properties and event configurations by default only the assets with conflicts are shown, by clicking show full asset tree all asset instances are shown items with a red icon need manual intervention because both the prototype and the instance have been updated overview of changes in bulk update once all conflicts are resolved, an overview of changes that will be applied can be consulted by clicking the ‘bulk changes overview’ button the individual rows in the overview can be expanded to show the changes that will be applied to the instances when the changes have been reviewed, the changes are ready to be submitted by clicking the submit button conflict resolution when an instance of a prototype has been manually updated (overridden) and the prototype is updated too, there is a conflict that can not be resolved automatically in the update overview, these conflicts are marked with a red icon and require manual intervention in the conflict resolution view, the user can choose between ‘keep’ or ‘update’ keep will keep the manually updated value in the instance and ignore the update from the prototype update will update the instance with the new value from the prototype, the manual change will be lost