Laserfiche has wide variety of ways it can integrate with other software, including the ability to run commands on SQL databases to allow integrations with 3rd party software. However, I agree that it might be problematic to have Laserfiche actively deleting data in databases used by other software (rather than just reading the data or inserting data). There's a couple reasons for that:

1. Laserfiche is unaware of how the other software uses this data, so any modifications would rely on a very thorough understanding by the person building the integration to avoid errors, poor behavior in the other application, or unintentional data loss
2. By trying to manage these database from within Laserfiche, you're rebuilding logic that should already be handled by the other applications
3. Laserfiche is likely not the most efficient way to handle the database modification. It is built around the idea of managing documents and metadata associated with those documents, not maintaining databases for 3rd party software.
4. Using Laserfiche for extensive monitoring and updating of 3rd part databases is going to put load on the Laserfiche system, particularly workflow, which could potentially slow down vital document management processes (or at least require a more heavy-duty machine)

It's difficult to say whether Laserfiche could or should do the things being asked without more specifics, but general, it is not designed to manage databases used by other software, and actually deleting rows from a database accessed by other software sounds risky.