Manage selected configuration items through recorded jobs

Purpose

Administrators maintain several catalogue items in one reviewed operation while retaining items that other records still need.

How It Works

An administrator selects catalogue items and chooses an available bulk action. Deletion preview distinguishes unused items from those still referenced by records. Usage counts help staff understand why a type remains. Approval uses the eligible count and the ordinary deletion safeguards. The list refreshes after processing. Status jobs are available only for catalogues that already have a status field. They use preview and application through the engine. Address and phone-number type lists currently offer deletion alone. Product has not yet resolved whether all status changes should use this path or whether those two catalogues should gain status. Configuration jobs cannot be restored through rollback.

Relationships

Counted bulk deletion provides the approval safeguards.
List dialogs provide the shared interaction.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Deletion explains which selected items are still referenced.Supported status changes have previews and job records.Catalogue bulk actions use a shared interaction.
Surfaces: consoleapi

Controls

24 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-CRY-001 TC-CRY-002 TC-CRY-003 TC-CRY-004 TC-DAT-001 TC-DAT-003 TC-DAT-004 TC-LOG-004 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

Key	Checked at	Scope
`crm.contact-types.bulk`	api	tenant
`crm.contact-types.delete`	api	tenant
`crm.contact-types.update`	api	tenant
`crm.contact-roles.bulk`	api	tenant
`crm.contact-roles.delete`	api	tenant
`crm.contact-roles.update`	api	tenant
`crm.organization-types.bulk`	api	tenant
`crm.organization-types.delete`	api	tenant
`crm.organization-types.update`	api	tenant
`crm.address-types.bulk`	api	tenant
`crm.address-types.delete`	api	tenant
`crm.address-types.update`	api	tenant
`crm.phone-number-types.bulk`	api	tenant
`crm.phone-number-types.delete`	api	tenant
`crm.phone-number-types.update`	api	tenant

Business Rules

8 rules, 6 to be proved before approval. A rule's product intent is derived from its origin: 0 confirmed by a product decision, the rest inheriting this capability's proposed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	A referenced configuration item is blocked from deletion with usage counts by record kind, while eligible selected items can be removed. proved by `ATS-PFM-DJE-007-12`, `ATS-PFM-DJE-009-14`, `ATS-PFM-DJE-010-01`, `ATS-PFM-DJE-010-07`, `ATS-PFM-DJE-010-08`, `TST-PFM-DJE-088`, `TST-PFM-DJE-116`	validation	service, database	test services-crm:modules/data-jobs/tests/integration/services/jobs/configuration-data-jobs.integration.spec.js#says both are blocked because they are in use
`02`must prove Proposed	Configuration deletion reports missing, system-protected and locked items with distinct refusal codes. proved by `ATS-PFM-DJE-010-02`	validation	service	documented services-crm:docs/data-jobs.md#Deleting records in bulk
`03`must prove Proposed	Typed deletion approval counts eligible items rather than the original selection, for example DELETE 10 contact types. proved by `ATS-PFM-DJE-007-12`, `ATS-PFM-DJE-009-14`, `ATS-PFM-DJE-010-03`, `ATS-PFM-DJE-010-07`, `ATS-PFM-DJE-010-08`, `TST-PFM-DJE-116`	calculation	service, console	test services-crm:modules/data-jobs/tests/integration/services/jobs/configuration-data-jobs.integration.spec.js#asks a person to type the number it would delete, not the number submitted
`04`must prove Proposed	Contact types, contact roles and organization types support previewed status jobs, treating satisfied changes as unchanged and intervening edits as conflicts. proved by `ATS-PFM-DJE-010-04`, `TST-PFM-DJE-089`	lifecycle	service, console	documented services-crm:docs/data-jobs.md#Deleting records in bulk
`05`must prove Proposed	Address and phone-number types have no status; status input is refused and their lists expose deletion only. proved by `ATS-PFM-DJE-010-05`	validation	api, console	documented services-platform:docs/milestones/PLAT-M20-small-bulk-operations.md#D3
`06`must prove Proposed	Deletion requires catalogue bulk and delete permissions, while status changes require bulk and update permissions; unavailable actions explain missing authority. proved by `ATS-PFM-DJE-010-06`, `TST-PFM-DJE-091`, `TST-PFM-DJE-108`	permission	api, console	test react-console:acceptance/data-jobs/playwright/journeys/dialogs/DJE-ACC-0109.spec.ts#DJE-ACC-0109
`07` Proposed	After deletion, the refreshed list retains the blocked selected items. proved by `ATS-PFM-DJE-009-14`, `ATS-PFM-DJE-010-08`	policy	console	test react-console:acceptance/data-jobs/playwright/journeys/dialogs/DJE-ACC-0106.spec.ts#DJE-ACC-0106
`08` Proposed	Configuration operations provide no rollback declaration.	policy	service	documented services-crm:docs/data-jobs.md#The routes

Scenarios

Id	Given	When	Then	Provenance
`01`	Two of twelve selected contact types are assigned to contacts.	The administrator reviews and applies deletion.	The dialog explains the two usage blocks, requests DELETE 10 contact types and leaves the blocked types in the refreshed list.	test react-console:acceptance/data-jobs/playwright/journeys/dialogs/DJE-ACC-0106.spec.ts#DJE-ACC-0106

Planning

Implementation

Manage selected configuration items through recorded jobs ​

Purpose ​

How It Works ​

Relationships ​