Entity Attribute Locking for fieldtypes and specifications

How:

Add standard _IsLocked boolean control fields alongside main entity/specification attributes in Inriver. API integrations populate core data and set _IsLocked = True. AI enrichment scripts inspect these flags prior to writing, skipping any attribute where the lock is active.

Why:

Inriver’s native entity lock freezes the entire record. Attribute-level locking allows granular field governance—protecting authoritative system-of-record data while leaving empty or unstructured fields open for AI enhancement.

For Who:

PIM Administrators, Integration Developers, and Enterprise Data Governance teams managing hybrid workflows combining API master data with automated AI copy/spec generation.

Impact:

• Data Integrity: Guarantees core technical specs (ERP/PLM data) remain accurate and uncorrupted.

• Automation: Enables AI tools to populate missing content safely without manual validation.

• Control: Provides human teams full override capability by toggling locks off/on directly within Inriver Enrich.

Additional Context:

Unlocking a field in the UI lets AI enrich it on the next run. Conversely, configuring Inriver Server Logic to auto-set _IsLocked = True when human users edit fields prevents AI from overwriting manual entries.