Released Properties disapear when "History of changes is active" in the Project

• Related Articles

• History of changes: Released symbol properties creating a lot of history of changes events

  Description In History of changes, released symbols generate a very high number of unneeded entries when Service Engine files are created. With many symbols and many screens, this can lead to impairments. This behavior has been modified. In the ...

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

• FAQ: Will the functionality of using Active Directory users in Service Engine be affected by the Windows Update in March 2020 for the Microsoft Advisory ADV190023?

  Tests have demonstrated that the functionality of using Active Directory users in Service Engine is not affected by the changes that are introduced with the update for the advisory. Service Engine uses Windows API functionality for the LDAP ...

• Checklist: Workspace/Project cannot be created, loaded or backed up

  Time estimate: 30 minutes Please go through all the points in the following checklist. If necessary, confirm with IT Department any information you cannot verify before contacting your local COPA-DATA Representative. Checklist usage: #. [Quick hints] ...

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