Business rule not triggered on table duplicate_audit_result when insert/update is done by the duplicate processorIssue Business rule not triggered on table duplicate_audit_result when insert/update is done by duplicate processorReleaseParis and newer releases.CauseThere were changes in the Paris code on how updates are done to duplicate_audit_result table when duplicates are found. This was done as a performance improvement, some CIs end up have dozens of duplicates, in some cases hundreds, which would create many DUPLICATE_AUDIT_RESULT records.ResolutionPossible workarounds: A schedule job can be created to look for any newly created DUPLICATE_AUDIT_RESULT records and just update them, any update, just to trigger the business rule.Alternatively, a BR can be triggered from table RECONCILE_DUPLICATE_TASK. The business rule should not try to update the DUPLICATE_AUDIT_RESULT as at the time of creation for record on RECONCILE_DUPLICATE_TASK there is no DUPLICATE_AUDIT_RESULT. However, it could trigger an event. The event would be processed by a script action. The script action could then update the DUPLICATE_AUDIT_RESULT records.