Retain supporting files with an activity

Purpose

Staff keep supporting documents attached to the interaction they explain.

How It Works

A client supplies files through Rhythm’s shared upload process. The activity save receives permanent references prepared for that record. Rhythm rejects a new file reference that bypasses preparation. The submitted attachment list controls which files remain and their order. A partial edit can leave the list untouched. Deleting the activity releases its references and requests shared cleanup. The console displays attached files and lets staff remove them. It currently has no control for adding uploads. The product should decide whether staff need that control before treating console attachment support as complete.

Relationships

Activity logging owns attachment saves.
Activity correction changes or removes the attachment list.
Platform file management owns storage and cleanup.

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: Managed attachment referencesFiles released with their owning activity
Surfaces: consoleapi
Preconditions: The workspace has configured managed file storage.

Controls

19 controls apply, from the corpus control catalogue.

TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-AZ-006 TC-DAT-001 TC-DAT-002 TC-DAT-003 TC-LOG-004 TC-LOG-005 TC-MON-001 TC-MON-002 TC-PI-001 TC-PI-004 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003

Permissions

Key	Checked at	Scope
`crm.activities.create`	api	tenant
`crm.activities.update`	api	tenant

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Proposed	An activity accepts no more than 20 attachments, with file names limited to 255 characters. no proof recorded yet	validation	service, database	test services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#refuses more than 20 attachments
`02`must prove Proposed	New attachment references must come from the shared file pipeline, which prepares a permanent copy for the activity and rejects unprepared references. no proof recorded yet	validation	service	test services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#refuses a file reference that did not come through the pipeline
`03`must prove Proposed	Submitting an attachment list retains unchanged files and removes entries absent from that list, while a partial edit that omits the list preserves it. no proof recorded yet	policy	service	test services-crm:modules/activities/tests/integration/services/persistence/activities.integration.spec.js#keeps an attachment sent back unchanged, and removes one left out
`04` Proposed	The attachment list determines the display order of its files.	policy	service	observed services-crm:modules/activities/db/activity-attachments.table.ts:ACTIVITY_ATTACHMENT_COLLECTION
`05`must prove Proposed	Activity deletion requests cleanup of released file references; the shared file service owns physical deletion. no proof recorded yet	lifecycle	service	observed services-crm:modules/activities/services/persistence/activities.ts:deleteActivity
`06`must prove Confirmed	An activity create replay does not copy its attachments again. origin: services-crm:docs/milestones/CRM-M8-activities-and-tasks.md#D-43 no proof recorded yet	invariant	service	test services-crm:modules/activities/tests/integration/services/persistence/activities.create-retries.integration.spec.js#copies nothing for the retry
`07`must prove Proposed	The activity editor displays existing attachments and permits removal, but provides no upload control. no proof recorded yet	policy	console	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0703.spec.ts#CRM-ACC-0703

Scenarios

Id	Given	When	Then	Provenance
`01`	An activity has an attachment prepared through the file pipeline.	Submit an unprepared file reference as a new attachment.	The activity save rejects the file reference.	test react-console:acceptance/crm/playwright/journeys/cross-application/CRM-ACC-0703.spec.ts#CRM-ACC-0703

Planning

Retain supporting files with an activity ​

Purpose ​

How It Works ​

Relationships ​