Integrating Altinn Apps

How to override or enrich the automatic Dialogporten integration from your app

Introduction

Altinn Apps are automatically synchronized with Dialogporten. Every time a new instance is created, the dialog service will create or update a corresponding dialog that is visible to the end user in Altinn Inbox (“arbeidsflate”). This guide explains how the default behaviour can be adjusted and how you can take full control over the integration if needed.

Automatic dialog synchronization

By default, the synchronization is enabled for all applications. Updates to the instance, such as status changes, added activities or attachments, will be reflected in Dialogporten. The behaviour can be tuned in the app settings. See the reference information linked below for details.

Read more

• Reference information for Altinn Apps integration

Using the Dialogporten WebAPI SDK

Some scenarios require more control than the automatic synchronization offers. The Dialogporten WebAPI SDK gives your application programmatic access to Dialogporten so you can create and update dialogs yourself. This enables fine-grained handling of activities, transmissions and synchronization with Altinn Inbox.

Convention-based use of application texts

Altinn Apps can automatically resolve localized text content for dialogs by following a convention-based key lookup. It searches for specific keys in your application texts with a fallback mechanism.

Key Resolution Order

The system attempts to find the most specific key first, then falls back to more general keys in this order:

1. Active task for status - Most specific match
2. Active task - Task-specific match
3. Any task for status - Status-specific match
4. Any task and any status - Most general match

Key Format Structure

All keys follow this pattern (case-insensitive, converted to lowercase):

dp.{content_type}[.{task}[.{state}]]

Components:

• content_type (required): One of:

  • title - Dialog title
  • summary - Dialog summary/description
  • additionalinfo - Dialog additional Information
  • primaryactionlabel - Primary action button text
  • deleteactionlabel - Delete action button text
  • copyactionlabel - Copy action button text

• task (optional): Either:

  • A specific task name (alphanumeric with internal dashes or underscores)
  • _any_ for wildcard matching

• state (optional): The instance status, such as:

  • archivedunconfirmed, archivedconfirmed
  • rejected
  • awaitingserviceownerfeedback, awaitingconfirmation
  • awaitingsignature, awaitingadditionaluserinput
  • awaitinginitialuserinput, awaitinginitialuserinputfromprefill

Examples

Basic content:

• dp.title General dialog title
• dp.summary General dialog summary
• dp.primaryactionlabel General primary action text

Task-specific:

• dp.title.DataEntry Title for DataEntry task
• dp.summary.Review Summary for a Review task
• dp.primaryactionlabel.Sign Primary action for a Sign task
• dp.primaryactionlabel._any_ Primary action for any tasks

State-specific:

• dp.title.DataEntry.awaitinginitialuserinput Title for DataEntry task awaiting input
• dp.summary._any_.rejected Summary for any task when rejected
• dp.primaryactionlabel.Sign.awaitingsignature Action label A for a Sign task awaiting signature

Default Fallback Values

If no custom application text keys are found, the system provides built-in default values for summaries based on the instance status:

Title Text Defaults

Uses the Title of the app

Summary Text Defaults

Primary Action Label Defaults

Delete Action Label Defaults

Copy Action Label Defaults

Implementation Notes

• All keys are converted to lowercase during lookup
• Task names can contain letters, numbers, dashes (-), and underscores (_)
• Task names must start and end with alphanumeric characters
• Use _any_ as a wildcard to match any task name
• The system returns the first match found following the resolution order