Skip to content
Alle documentatie
Aan de slag

Veiligheid van bulkwijzigingen instellen

Configure Agent Bulk Update Safety

Configure the bulk-update safety policy shared by Richard and the application’s bulk workflows under Configuration → Agent Settings → Bulk Updates. Review the effective defaults, hard limits and protected fields before saving.

Voor wie

Beheerders, medewerkers en IT-teams die ITLedger gebruiken voor dienstverlening, assets, compliance en rapportages.

Taken

Kies je taak. De volledige werkwijze, voorwaarden en aandachtspunten staan hieronder in het Engels.

Configure Agent Bulk Update Safety

Configure the bulk-update safety policy shared by Richard and the application’s bulk workflows under Configuration → Agent Settings → Bulk Updates. Review the effective defaults, hard limits and protected fields before saving.

Who can do this: Tenant administrator

Before you start

  • Use an account with access to the stated page and permission for the chosen action.

Safeguards

  • Richard has an absolute backend ceiling of 25 records per conversational bulk update; tenant settings can lower that limit but cannot raise it.
  • Review the current hard limits shown by the interface. Tenant settings can only tighten the supported boundary.
  • Identifiers, tenant/user/permission tables, audit history, secrets, relationship IDs, and system-managed or structured fields are hard-blocked and cannot be made safe with a field override.
  • A field override can classify a permitted field as normal or risky, but cannot bypass a hard block.
  • The UI keeps rollback history required and partial execution blocked; these controls are displayed as locked safeguards.
  • Revert is available only for completed or partial update operations that retained before values, and a revert can itself report partial failure.
  • This capability configures safety policy; use the bulk_update operation or Excel bulk workflow to change records.
  1. Go to Configuration → Agent Settings and open the Bulk Updates tab.
  2. Review the effective policy, defaults, and backend hard limits before changing tenant values.
  3. Choose conservative record, field, risky-field, and preview limits for the tenant.
  4. Decide whether permitted risky fields are allowed and add only narrow field classifications when needed.
  5. Save the policy; Richard and Excel/frontend preflight checks use the new effective values.
  6. Use Recent Bulk Operations to inspect outcomes and revert an eligible update only after reviewing its retained before values.

Expected outcome: The user has reviewed the result of configure agent bulk update safety in the application.

Aanbevolen werkwijze

  • Begin bij de onderdelen die je team het meest gebruikt.
  • Houd de eerste inrichting overzichtelijk.

Gerelateerde handleidingen

Lees verder in Aan de slag

Basisbegrippen, navigatie, zoeken en eerste stappen in ITLedger.