Import regions from a file
What It Does
Regional file imports populate or change the customer’s catalogue through the shared Data Job Engine. Regions hosts submission, review and control routes, while its adapter validates row values and calls the normal regional persistence functions. Assignment policy is configured separately.
The Flow
When Something Fails
Rejected rows and application failures remain inspectable through engine results. Already committed regional changes are not reversed, because these imports declare no compensating operation. Conflict handling depends on reject or overwrite policy and the supplied or resolved version; a changed record is not universally guaranteed to be skipped. Engine startup recovery, retry scheduling and source-key deduplication require the engine’s own proof.
Open Design Questions
Imports currently accept ordinary writable lock values, inheriting the unresolved audited-lock requirement. Delegated startup recovery and conflict behavior should be linked to the engine’s contract before implementation preparation relies on stronger guarantees. The scoped regional screens expose no file-import control.