Last modified: Jun 17, 2025

Post-Published Lifecycle

Altinn 3 Correspondence post-published lifecycle and recipient interactions.

Post-Published Lifecycle

After a correspondence is published, recipients can interact with it:

flowchart TD %% Post-published flow A[Start: Published] --> B{Recipient Actions} B -->|GetOverview or GetContent| C[Set Status: Fetched] B -->|Download Attachments from any state| G[Set Status: AttachmentsDownloaded] C -->|GetContent first time| E[Set Status: Read] C --> D{Recipient Actions} D -->|Mark as Read| E D -->|Continue to Confirm| H{Confirm?} E --> H{Confirm?} H -->|Yes| J[Set Status: Confirmed] H -->|No or Not Required| L{Purge?} J --> L{Purge?} G --> L L -->|By Recipient| N[Set Status: PurgedByRecipient] L -->|By Altinn| O[Set Status: PurgedByAltinn] L -->|No| P[End] N --> P O --> P style A fill:#f9f,stroke:#333,stroke-width:2px style P fill:#f9f,stroke:#333,stroke-width:2px style C fill:#99ff99,stroke:#333,stroke-width:2px style E fill:#99ff99,stroke:#333,stroke-width:2px style G fill:#99ff99,stroke:#333,stroke-width:2px style J fill:#99ff99,stroke:#333,stroke-width:2px style N fill:#87ceeb,stroke:#333,stroke-width:2px style O fill:#87ceeb,stroke:#333,stroke-width:2px

Post-Published Status States

  1. Fetched: Recipient has accessed the correspondence (via GetOverview or GetContent API)
  2. Read: Recipient has either accessed the correspondence content for the first time or explicitly marked it as read (requires prior Fetched status)
  3. AttachmentsDownloaded: Recipient has downloaded one or more attachments (can occur at any time)
  4. Confirmed: Recipient has confirmed the correspondence (requires prior Fetched status)
  5. PurgedByRecipient: Correspondence has been deleted by the recipient
  6. PurgedByAltinn: Correspondence has been deleted by the system

Status Rules

  • Fetched is automatically set when recipients call GetOverview or GetContent
  • Read is set either automatically when accessing content for the first time or explicitly via /markasread endpoint. This status is optional - recipients can confirm directly from Fetched without reading
  • Confirmed requires explicit action via /confirm endpoint and requires prior Fetched status
  • AttachmentsDownloaded can occur from any state after Published
  • Confirmation is only required if the correspondence has IsConfirmationNeeded = true

Recipient Interaction Process

Fetching Correspondence

  • Recipients access correspondence details (triggers Fetched status)
  • This is automatically triggered by GetOverview or GetContent API calls
  • Required before any other recipient actions

Reading and Confirmation

  • Accessing content automatically marks as read (first time only)
  • Can also explicitly mark as read via /markasread endpoint
  • Download attachments at any time (triggers AttachmentsDownloaded status)
  • Confirm if required (only if IsConfirmationNeeded = true)
  • Read status is not required for confirmation

Purging

  • Recipients can delete correspondence when no longer needed
  • System can also purge correspondence based on retention policies

Error Handling

During Recipient Actions

  • HTTP 400 Bad Request: Attempting to read/confirm without fetching first
  • HTTP 404 Not Found: Correspondence not available for recipient in current state

Notification Behavior

  • Reminder notifications can be sent for unread correspondences
  • Notification sending stops once correspondence is marked as read
  • Notifications are managed independently of the correspondence status

The system maintains a complete audit trail of all recipient interactions and status changes for compliance and debugging purposes.