Details
-
Type:
Sub-task
-
Status: Done/Fixed
-
Priority:
Trivial
-
Resolution: Fixed/Completed
-
Affects Version/s: 4.7.3
-
Fix Version/s: 4.7.7
-
Component/s: None
-
Labels:None
-
Documentation Required?:User and Admin Doc
-
Funding Source:Contributed Code
Description
Currently although some transactions can be reverted dedupes cannot. I propose that the requirement is
1) the insert 'Contact Merged' activity in the change log has a link to revert
2) the revert on that includes all changes for the 2 contacts involved for that connection (or other contact limits or lack thereof can apply)
I'm on the fence about fixing up the existing report to support this vs adding another - although I do feel making this stuff available to an api is part of the brief here, otherwise it will be hard to add testing.
Also, I am on the fence about reverting the Contact Merged activity itself - if we DON'T revert it then I think we need to update it to cancelled to reflect the revert
Note
all of these considerations are generic to a 'batch revert' except for the one about creating / updating the activity.