An unlocked interaction has two prepared files and a current revision. As an updater, correct the subject and remove one file; read the revision and remaining attachments. Repeat a correction with a read-only caller.
The interaction scenario names the capabilities and rules it exercises. The coverage finding retains incomplete permission combinations and failure variants.
Coverage
Rulecovered
Transitioncovered
Validationcovered
Permissioncovered
Edgecovered
Failurecovered
Boundarygap: FND-CRM-ACT-070
Concurrencycovered
Invariantgap: FND-CRM-ACT-070
Interactioncovered
Test Scenarios
18 scenarios proving CAP-CRM-ACT-003; 8 bound to an existing test.
01Reject stale edits and missing versionsconcurrencyapinegativetest
Run-owned interaction has Scheduled standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses completed as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Completed standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in history and must satisfy any required completion duration and result.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Scheduled standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses cancelled as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Cancelled standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in history without completion-only requirements.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Completed standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses scheduled as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Scheduled standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in upcoming items; completion-only requirements no longer apply.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Completed standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses cancelled as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Cancelled standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in history without completion-only requirements.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Cancelled standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses scheduled as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Scheduled standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in upcoming items; completion-only requirements no longer apply.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Cancelled standing. The read version matches, updates are unlocked, and the proposed values satisfy the type’s field requirements.
Steps
An ordinary edit chooses completed as the interaction status. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Completed standing. The database refreshes status on the interaction’s links and captures the committed revision. The interaction appears in history and must satisfy any required completion duration and result.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Scheduled standing. Neither deletion nor update-and-deletion protection is set; deletion does not require a read version.
Steps
A caller requests removal. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Deleted standing. The interaction’s owned links and file entries are removed, and released files are submitted for cleanup. Import matching references are dropped and the committed deletion is captured in history.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Completed standing. Neither deletion nor update-and-deletion protection is set; deletion does not require a read version.
Steps
A caller requests removal. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Deleted standing. The interaction’s owned links and file entries are removed, and released files are submitted for cleanup. Import matching references are dropped and the committed deletion is captured in history.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.
Run-owned interaction has Cancelled standing. Neither deletion nor update-and-deletion protection is set; deletion does not require a read version.
Steps
A caller requests removal. Read the resulting record and affected projections after commit.
Expected
The resulting interaction has Deleted standing. The interaction’s owned links and file entries are removed, and released files are submitted for cleanup. Import matching references are dropped and the committed deletion is captured in history.
Data
Run-owned records in an isolated workspace; fixed clock for calendar checks.