Description of the most common terms used in the documentation for Altinn Studio.
A actor is organisation or person that a user/system is acting on behalf of. As an example User A can fill out a form on behalf of Organisation B.
The Actor list is a list over person and organisation that a user can act on behalf of. This right is given through roles or rights delegations.
The type a Actor can be. Typical a person or organisation but also sub types of organisations.
Actor Type Requirement
The requirent a app has for the Actor. Typical checked when a app is instantiated
Reportee Type Requirement
Norways E-Governement plattform. Launched december 4. 2003. Read more on altinn.no
Altinn Apps is the infrastructures for running apps developed in Altinn Studio. Each organisation that is using Altinn Studio will have their own Altinn Apps Kubernetes cluster, isolated from other organisations.
The command-line interface for the new APIs in Altinn.
Is used by service owners for retrieving data submitted by users, for instantiating and for updating status.
Altinn Platform contains reusable microservices with functionality that can be used by apps. Platform can also be used directly by service owner systems using Altinn CLI and Maskinporten.
Currently these microservices are part of Platform: Authorization, Authentication, PDF, Profile, Register, and Storage.
Altinn Platform is running in its own Kubernetes cluster.
An Altinn environment is a isolated group of several Altinn solutions functioning together.
- AT - Acceptance testing of Altinn Studio, Altinn Apps, Altinn Platform and SBL.
- TT02 - App/service test environment used by the app and service owners.
- Production - The production environment.
Altinn Studio are our tools for app development.
Consists of Altinn Studio Designer, Altinn Studio Repos and a local code editor / development tool (e.g. Visual Studio Code).
Lets the developers create, edit, test and deploy applications. The apps are deployed as containers to a seperate infrastructure called Altinn Apps.
Altinn Studio Designer
Altinn Studio Designer is a web-based tool for creating, editing and deploying apps.
In Designer, it should be easy to create apps by re-using and configuring pre-made components.
Altinn Studio Repos
Altinn Studio Repos is the solution where each app is stored and versioned as a Git repository.
No matter which tool is used for development (Designer, Code, or something else), the app is stored in Repos.
Application Programmers Interface.
Short for Application. App is the name that is given for an app. It is used as repository name and as part of AppId and in different metadata. Inside an org the app needs to be a unique name. See also Application.
A AppId identifies a given application. It is has the following pattern [org]/[app-name]. The app-name is the same as the name of the name of the app repo.
An applications created in Altinn Studio is called an app, short for application. Apps are deployed to a Altinn Apps environment. The app provides two things:
- an interactive user interface for users wishing to submit data to an organisation, e.g. to fill out a form manually, to read information or to sign an agreement;
- an api that client applications can interact with.
The application also has a metadata representation in the application repository (platform storage), which defines the various element types that an instance of an application can have.
Short for Altinn Apps. See Altinn Apps
A user developing application in Altinn Studio.
Short for organisation. Organisation is the entity responsible for an app. Typically identified by an unique acronym, e.g. SKD, NAV, OSLK.
Application Owner Service Owner
A representation of a data element which is stored in the Altinn Platform.
A record of activites on a specific instance.
An instance of an application for a specific instance owner is represented as an object. Is created by organisation or instance owner. It contains information of the formdata and attachments stored associated with the instance.
The person or entity that is responsible for submitting an instance of an application to an organisation.
The user which is logged in in Altinn and performs actions for on behalf of an instance owner. A user and an instance owner can be the same entity.
A system for managing docker containers. See also: Relevant definitions within Kubernetes
Teh framework used for developing UI components.
Policy Administration Point.
Policy Administration Point.
Policy Administration Point.
Policy Information Point.
Policy Retrieval Point.
The Altinn 2 end user solution (SluttBrukerLøsning).
Applicaton that exposes SBL components as REST interface to Altinn Platform components. See all issues on GitHub related to SBL Bridge.
A statefull app uses Altinn Platform to store data
A stateless app is a application where no data is store in in the platform. This could be a app acting like a proxy to some external APIS. State could potensial be stored in the external API, so term statless is limited to how the App not use any state in Altinn Platform.
The set of tasks a certain app is made of, i.e. data, signing, payment etc. In Altinn Studio we use a *.bpmn file for the process.
XACML stands for “eXtensible Access Control Markup Language”. The standard defines a declarative fine-grained, attribute-based access control policy language, an architecture, and a processing model describing how to evaluate access requests according to the rules defined in policies.
Altinn Studio Apps uses the XACML standard for defining Policies for apps, the authorization architecture, and the request and response between PEP and PDP.