Details
-
Type:
Sub-task
-
Status: In Quality Assurance
-
Priority:
Important
-
Resolution: Unresolved
-
Affects Version/s: 4.7.23
-
Fix Version/s: None
-
Component/s: CiviCase
-
Labels:
-
Versioning Impact:Patch (backwards-compatible bug fixes)
-
Documentation Required?:None
-
Funding Source:Needs Funding
-
Verified?:No
Description
CiviCase has traditionally stored revision-history in the "civicrm_activity" table using multiple rows and the columns "original_id" / "is_current_revision". At the same time, CiviCRM also has a more general logging system based on shadow tables like "log_civicrm_activity". The duplicate approaches are harder to QA (leading to eg CRM-20151), and the "original_id" approach is harder to query/develop with.
CiviCase 5 will rely on the general logging. We need a setting to opt-out of the older logging system.