Possible to make General Properties aspect open to changes, even if the library is in Released state?
I have created an extension library, which contains some General Properties aspects. These may be configured differently on different plants.
When the library is in Released state, the General Properties aspects are "locked" and can not be changed. One must then open the library, change the default values, and release the library again.
It would have been nice to be able to change the default values of these General Properties aspects in the object type structure for each plant, without the need to open the Released library.
I wonder if it is possible to configure the library so that only the General Properties aspects are open to changes in the object type structure, even if the library is in the Released state?
Voted best answer
Writing to a General Property require OPC write permission *and* object level Configure permission.
Inherited aspects cannot be modified with the exception of the poorly documented Auto Instantiate/Copy-To-Instance method that I IMHO call "1/2 inheritance". That method has several drawbacks.
Inherited aspects can be overridden.
Aspects belonging to Released / Closed libraries cannot be modified.
So, you must, without inheritance place the General Property outside of a Closed/Locked library on an object the user has Configure permission on object level and Write permission on OPC level.
I believe I've seen examples when General Properties have been put outside the protected object types of the library - maybe even on the library object itself.
There is a difference between "Configuration" and changing OPC Values.
If you allow to write the OPC Values in General Properties, you can change them (but probably not from Config View, via OPC e.g. from a Graphic Display), but not add/remove any Properties.
If this is not enough, then you already know the way to create Extension Libraries, so why not just create another one only containing the General Properties Aspects, that can then be left open?
As Stephan already answered, change the "Inherit" attribute of the General Properties Aspect to "Copy to Instance".
The General Properties aspect stays "inherited" until you make any modifications to it. At that time the inheritance breaks. However if you use graphic elements to write to / read from the general properties, then the inheritance will still be maintained.
Its not a "good" solution. But its the only one that works.