Sist endret: 16. mai 2024

Translate-to-Norwegian

Data-elementer

Overview A data element consist of two parts: its metadata document and the actual data blob. This API work primarily with the blob while keeping the metadata document updated. basePath {org}/{appname}/instances/{instanceOwnerPartyId}/{instanceGuid}/data Get data Endpoint for downloading the data blob. GET basePath/{dataGuid} Accept: application/{xml/json} The response will depend on the type of blob. There are currently 2 primary types: form data based on a model and attachments. An Accept header in a request will be considered only when the requested data element is connected to a data model. »

Instanser

Overview An instance works as a form of envelope or folder where data can be collected and exchanged between the user and owner of the application. The instance document is a way for Altinn and external parties to track the state of one specific data exchange. How long an instance can live and how many interactions there can be between the application owner and user will vary from one app to another. »

Resource

Overview Your organization needs the scope altinn:resourceregistry/resource.write to be allowed to create and modify your organizations resources and policies. The resource describes the different metadata for a resource { "identifier":"brg_samordnet_registermelding", "description": [ { "language": "nb-NO", "description": "Elektronisk skjema for registrering av selskap" }, { "language": "EN", "description": "Registering a new entity or changing information regarding an existing entity" } ], "title": [{ "title":"Samordnet registermelding", "language":"nb-NO" }, { "title":"Coordinated register notification", "language":"en" }], "hasCompetentAuthority": { "organization": "974760673", "orgcode":"brg" }, "contactpoint": [{ "phone":"1231324", "email": "online@digdir. »

Tilstandsløse data

Overview A stateless data element is a data object based on a data model without relations to an instance, instance owner or a state. The data is never persisted anywhere, and the avilable endpoints simply creates, prefills and/or runs calculations on a data object before returning it to the caller. basePath {org}/{app}/v1/data Create new data Endpoint for creating a new stateless dataelement based on a data type. POST basePath?dataType=[dataTypeId] Accept: application/{xml/json} The dataType parameter is required and should reference one of the data types defined on the application that requires app logic. »

v2

2.5.10 Dependency on .NETStandard2.0 The package was changed to depend on .NetStandard2.0 in place of .NetStandard2.1. This should ensure that applications based on .NET Framework 4.7 can use the package. 2.5.9 Expanded the eFormidlingContract with SecurityLevel eFormidlingContract model was given a new property holding security level information. #5740 2.5.8 Extended eFormidlingContract with additional parameters eFormidlingContract model was given three new properties to support eFormidling in apps. #5740 2.5.7 Extended eFormidlingContract with a new property: sendAfterTaskId eFormidlingContract model was given a new property to identify which task should trigger an eFormidling shipment. »

Prosess

Overview All apps have a process definition that specifies start events, end events, tasks and the allowed flows (transitions) between these. A process is started by the application, which selects a start event to start and follows the sequence flow to the first task and creates a current task object to hold the process state. Process A process is represented by an process model in BPMN/XML notation. Each task has an unique id, which is used to refer to the task in the api. »

Instance events

Instance events All instance events, e.g. creation, read, save, change process state, … GET {storagePath}/instances/347829/762011d1-d341-4c0a-8641-d8a104e83d30/events Example of event data. { "id":"6dff32bc-0928-4ae8-937c-b362d6941c89", "instanceId": "60238/5c6b1a71-2e1f-447a-ae2f-d1807dcffbfb", "eventType": "deleted", "created": "2019-05-02T13:08:21.981476Z", "instanceOwnerPartyId": "60238", "user": { "userId": 338829, "authenticationLevel": 1, "enduserSystemId": 2 }, "process": { "started": "2019-05-01T12:45:01.3233Z", "startEvent": "Start_22", "currentTask": { "elementId": "Task_2" } } } Application events (for application owners) WARNING: This section will be redesigned Selected instance events. Created, first read, change process state. »

Validering

Overview There are multiple endpoints that can trigger validation and provide feedback regarding the state of an instance and its data. Some of them validates data already uploaded and stored in Altinn while others can validate input. Validate stored instance This action will validate an entire instance including the all data elements already uploaded and stored in Altinn. Validation will be performed based on current task in the process. Validation will ensure that all required data elements, as defined by the application metadata, have been uploaded and are valid. »

Breaking changes

As of v3.0.0 of app frontend, the font Altinn-DIN replaces the Roboto font that was used previously. Once an app is upgraded to use v3 of the app frontend, all CSS expects the Altinn-DIN font to be loaded. In order for the app to display fonts as expected, the font that is loaded with the app must be updated. In App/views/Home/Index.cshtml, replace the line <link href="https://altinncdn.no/fonts/roboto/latin/roboto.css" rel="stylesheet"> with <link href="https://altinncdn.no/fonts/altinn-din/altinn-din.css" rel="stylesheet"> The updated file, referring to v3 of app frontend, should reflect the changes of the file on the right: »

Breaking changes

We have added a new PDF handler to make it possible to hide pages and components in PDF. The new version of the Altinn.App.* packages have breaking changes: Updating to this version will require changes in multiple files. Updated package dependencies Navigate to you application repository and find App.csproj in the App folder. Update nuget dependencies in App.csproj to version 3.0.0. <PackageReference Include="Altinn.App.Api" Version="3.0.0" /> <PackageReference Include="Altinn.App.Common" Version="3.0.0" /> <PackageReference Include="Altinn. »