Transforming Business with AI
Safe, traceable edits for Pimcore 11 and 12 when many people and automated jobs change the same data at once. Cooperative locks, version guards, field ownership, idempotency and a full audit trail for multi-writer installations.
In a large Pimcore catalog, many people and automated jobs save changes to the same products at the same time. Without protection, one silently overwrites another's work, a single save can trigger a chain reaction that floods the system with version history and stalls the queues, and nobody can tell who changed what. Every project ends up rebuilding the same fragile safeguards by hand.
PimTx becomes a mandatory chokepoint. You replace the standard save call with a governed transaction, and every write flows through one pipeline: preflight (policy, safety limits, idempotency), governance (field ownership, field firewall, approval gates), a cooperative lock (Redis primary, database fallback, token-guarded), mutation (no-op detection and an optimistic version check), persistence (scoped version and event guards), and audit (operation log, field diffs, outbox, metrics, lineage). Conflict resolution, diff detection, locking backends and notifiers are all pluggable.
System Architecture: Write call: governed transaction, Preflight: policy, safety, idempotency, Governance: ownership, field firewall, approval, Cooperative lock: Redis or DB, token-guarded, Mutation: no-op check, optimistic version check, Concurrent write, Conflict strategy: retry, skip, merge, Clean, Persist: scoped version and event guards, Audit: operation log, field diffs, outbox, lineage
Rather than override Pimcore internals, PimTx wraps the save call so every write, from the admin UI, workers, APIs and custom code, passes through one governed pipeline. The platform stays upgrade-safe and the governance lives in one place.
Reads are never blocked. Writes take a short cooperative lock and verify the element version before persisting, so concurrent writers compete fairly and a stale write is rejected instead of clobbering fresh data.
A save that changes nothing is skipped by field equality and a content hash. That single decision stops the listener cascades that otherwise fill the version table and crash queues.
Every phase of the pipeline emits a typed event, so teams can observe or veto a write without forking services or patching core.
Simultaneous edits are handled safely with no silent overwrites, the runaway version history is prevented, and every change is recorded with exactly what changed and who caused it. Shipped as version 1.0, a proprietary Oronts product, with a REST API, 35 command-line tools, a dual admin interface (React on Pimcore 12, ExtJS on Pimcore 11) and a live activity stream.
On a high-volume Pimcore platform, PimTx is the write layer, so imports and editors stop fighting each other.