History of changes: Interlocking - no entries logged if the changes are made via tree - instead of property window

• Related Articles

• History of changes: Menus- no entries logged if the changes are made via tree - instead of property window

  Summary The change entries will be created . Description The change entries will be created . Issue Number: 221300 Fixed on Date: 13.7.2020 Versions: 8.20 0 BUILD 67231

• By temporary login and value changes via keyboard screen the CEL stores entry with user SYSTEM instead the logged-in.

  Summary If you change the value via the keyboard screen (property: Write Set Value -> Use screen Keyboard and Choose a screen) and use the temporary login, then as user it is SYSTEM in the CEL displayed and not the logged-in user. CEL entries about ...

• History of changes: Recipe changes are only logged if you use the prop. window - It doesn't log if you rename via tree-view

  Summary The change entries will be created . Description The change entries will be created . Issue Number: 221298 Fixed on Date: 9.7.2020 Versions: 8.20 0 BUILD 67231

• History of Changes does not handle correctly the value changes with long texts.

  Summary In Editor - History of Changes of the project - the columns for old value and new value are allowing the maximum of 128 characters. While the History of Changes is active and properties are changed that have a much higher size, or no limit at ...

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

  Description Changing a property of a Smart Object Template (SOT) causes an entry to be made in the “History of Changes“ for all properties in the corresponding instances. This leads to a rapidly growing database with a lot of superfluous information. ...