Record deleted but no trigger created in remote library

• Article Type: General
• Product: Aleph
• Product Version: 20

Problem Symptoms:
When a record is deleted in the central database and the deletion is replicated to the local database, a trigger is NOT created, although one is set in check_doc_mandatory.

Cause:
Defect

Resolution:
This problem is solved with rep_change 2518 in Aleph 21.
Description: This fix is relevant only to customers who replicate data via ue_11 from a central database to a local database. When a record is deleted in the central database and the deletion is reproduced in the local database, no trigger is created according to the setting in check_doc_mandatory.
Solution: This has been corrected. The ue_11 daemon now supports the trigger mechanism via Z104 and the check_doc_mandatory table.