
Safety Catch Feature
In a MIM context we have been refining our Safety Catch to ensure that unwanted changes (not just deletes) are not replicated to target systems if the change count exceeds a threshold (% or raw number). The latest version is presently pending deployment for a long-term MIM site.
With the roll-out of more Broker+/UNIFYConnect implementations, an equivalent safeguard feature is now required - over and above the "connector delete threshold" native to UNIFYBroker itself. Until such a feature is available in a forthcoming release, a work-around should be considered for each implementation.
Answer

note that the outgoing safety catch feature will be dependent on the forthcoming pending export report capability - incoming feature should NOT be an extension of the existing capability but focused on the incoming adapter changes instead.

Customer support service by UserEcho
Tracking on new ticket: https://unifyvoice.userecho.com/communities/6/topics/5382-unifyconnect-update-thresholdsafety-catch