Back to the changelog

• Security

  Data Shield on nested fields

  **Data Shield** now also protects **nested fields**: marking a field inside an object (e.g. `cliente.codiceFiscale`) or the whole `cliente` object (covering all its sub-fields) is correctly pseudonymized before reaching the AI provider. Previously only top-level keys were handled — a **nested** sensitive value could slip through in clear. **Security bug fixed.** The sensitive-fields picker is now a **tree** (groups + indented sub-fields, each selectable). A declared-sensitive field that is simply **absent** from an item no longer blocks processing.

• Improvement

  Richer rule builder

  The **raw JSON** condition editor is now available as an advanced fallback **both** in transition rules **and** the data-gate rule (previously only in the data-gate). Item data with **nested** values (objects/arrays) now render full-width with indented JSON, no longer overlapping neighboring columns.