We have released today on semarchy.com this patch for Semarchy xDM 5.3.6
You can read the release notes (5.3.6).

New Features

• MDM-12081: New Semarchy Text Tokens Plugin Enricher. This Enricher replaces tokens in a text using a dictionary of strings or patterns.
• MDM-12056: GCP Cloud SQL for PostgreSQL and SQL Server are now certified.

Bug Fixes

• MDM-11690: Performance improvement for the Delete/Publish Deletion/Cleanup Integration Tables task of the deletion process.
• MDM-12282: Graph view for Duplicates Managers flickers.
• MDM-12357: Updating a Data Notification with the REST API breaks its configuration and causes the Data Notification test feature to raise... (More)

Matching performance is a complex issue. There could be many causes that lead to unsatisfactory integration job processing times, including poorly optimized match rules that perform too many fuzzy-matching comparisons or logic bugs that ensure your integration jobs will simply never finish.

Assuming your data volumes are large and you've got adequate hardware allocated to xDM (memory, storage specs for the application server and database), if you've optimized and feel confident that there's no more to be gained by tweaking match rules, here are steps you can try to speed up your integration jobs.

These steps are very technical and... (More)

I have a question on Deletes. So it looks like these deletion methods documented here on the Community site and for Semarchy work on either Golden or Master records. What if I need to delete just one Source record?

Here is my use case: I have a Survivorship rule. This rule takes three columns and using a custom Source Loaded Date column, ranks by the load date ASC so that the FIRST Source record value for these columns will always be kept forever. It works well enough that no overrides on the Master or Golden record will correct a bad... (More)