Prerequisites Your application uses version 7.1.0 or newer of the Altinn nugets. Application with a process containing a exclusive gateway Example process with exclusive gateways <?xml version="1.0" encoding="UTF-8"?> <bpmn:definitions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:altinn="http://altinn.no" id="Altinn_SingleDataTask_Process_Definition" targetNamespace="http://bpmn.io/schema/bpmn" exporter="bpmn-js (https://demo.bpmn.io)" exporterVersion="10.2.0"> <bpmn:process id="SingleDataTask" isExecutable="false"> <bpmn:startEvent id="StartEvent_1"> <bpmn:outgoing>Flow_s_t1</bpmn:outgoing> </bpmn:startEvent> <bpmn:sequenceFlow id="Flow_s_t1" sourceRef="StartEvent_1" targetRef="Task_1" /> <bpmn:task id="Task_1" name="Utfylling" altinn:tasktype="data"> <bpmn:incoming>Flow_s_t1</bpmn:incoming> <bpmn:outgoing>Flow_t1_g1</bpmn:outgoing> </bpmn:task> <bpmn:sequenceFlow id="Flow_t1_g1" sourceRef="Task_1" targetRef="Gateway_1" /> <bpmn:exclusiveGateway id="Gateway_1"> <bpmn:incoming>Flow_t1_g1</bpmn:incoming> <bpmn:outgoing>Flow_g1_g2</bpmn:outgoing> <bpmn:outgoing>Flow_g1_t2</bpmn:outgoing> </bpmn:exclusiveGateway> <bpmn:sequenceFlow id="Flow_g1_g2" sourceRef="Gateway_1" targetRef="Gateway_2" /> <bpmn:sequenceFlow id="Flow_g1_t2" sourceRef="Gateway_1" targetRef="Task_2" /> <bpmn:task id="Task_2" name="Bekreftelse" altinn:tasktype="confirmation"> <bpmn:incoming>Flow_g1_t2</bpmn:incoming> <bpmn:outgoing>Flow_t2_g2</bpmn:outgoing> </bpmn:task> <bpmn:sequenceFlow id="Flow_t2_g2" sourceRef="Task_2" targetRef="Gateway_2" /> <bpmn:exclusiveGateway id="Gateway_2"> <bpmn:incoming>Flow_g1_g2</bpmn:incoming> <bpmn:incoming>Flow_t2_g2</bpmn:incoming> <bpmn:outgoing>Flow_g2_end</bpmn:outgoing> </bpmn:exclusiveGateway> <bpmn:sequenceFlow id="Flow_g2_end" sourceRef="Gateway_2" targetRef="EndEvent_1" /> <bpmn:endEvent id="EndEvent_1"> <bpmn:incoming>Flow_g2_end</bpmn:incoming> </bpmn:endEvent> </bpmn:process> <! »
Prerequisites Your application uses version 7.1.0 or newer of the Altinn nugets. Application with a process containing a exclusive gateway Example process with exclusive gateways v8 <?xml version="1.0" encoding="UTF-8"?> <bpmn:definitions xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:bpmn="http://www.omg.org/spec/BPMN/20100524/MODEL" xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI" xmlns:dc="http://www.omg.org/spec/DD/20100524/DC" xmlns:di="http://www.omg.org/spec/DD/20100524/DI" xmlns:altinn="http://altinn.no" id="Altinn_SingleDataTask_Process_Definition" targetNamespace="http://bpmn.io/schema/bpmn" exporter="bpmn-js (https://demo.bpmn.io)" exporterVersion="10.2.0"> <bpmn:process id="SingleDataTask" isExecutable="false"> <bpmn:startEvent id="StartEvent_1"> <bpmn:outgoing>Flow_s_t1</bpmn:outgoing> </bpmn:startEvent> <bpmn:sequenceFlow id="Flow_s_t1" sourceRef="StartEvent_1" targetRef="Task_1" /> <bpmn:task id="Task_1" name="Utfylling"> <bpmn:incoming>Flow_s_t1</bpmn:incoming> <bpmn:outgoing>Flow_t1_g1</bpmn:outgoing> <bpmn2:extensionElements> <altinn:taskExtension> <altinn:taskType>data</altinn:taskType> </altinn:taskExtension> </bpmn2:extensionElements> </bpmn:task> <bpmn:sequenceFlow id="Flow_t1_g1" sourceRef="Task_1" targetRef="Gateway_1" /> <bpmn:exclusiveGateway id="Gateway_1"> <bpmn:incoming>Flow_t1_g1</bpmn:incoming> <bpmn:outgoing>Flow_g1_g2</bpmn:outgoing> <bpmn:outgoing>Flow_g1_t2</bpmn:outgoing> </bpmn:exclusiveGateway> <bpmn:sequenceFlow id="Flow_g1_g2" sourceRef="Gateway_1" targetRef="Gateway_2" /> <bpmn:sequenceFlow id="Flow_g1_t2" sourceRef="Gateway_1" targetRef="Task_2" /> <bpmn:task id="Task_2" name="Bekreftelse"> <bpmn:incoming>Flow_g1_t2</bpmn:incoming> <bpmn:outgoing>Flow_t2_g2</bpmn:outgoing> <bpmn2:extensionElements> <altinn:taskExtension> <altinn:actions> <altinn:action>confirm</altinn:action> </altinn:actions> <altinn:taskType>confirmation</altinn:taskType> </altinn:taskExtension> </bpmn2:extensionElements> </bpmn:task> <bpmn:sequenceFlow id="Flow_t2_g2" sourceRef="Task_2" targetRef="Gateway_2" /> <bpmn:exclusiveGateway id="Gateway_2"> <bpmn:incoming>Flow_g1_g2</bpmn:incoming> <bpmn:incoming>Flow_t2_g2</bpmn:incoming> <bpmn:outgoing>Flow_g2_end</bpmn:outgoing> </bpmn:exclusiveGateway> <bpmn:sequenceFlow id="Flow_g2_end" sourceRef="Gateway_2" targetRef="EndEvent_1" /> <bpmn:endEvent id="EndEvent_1"> <bpmn:incoming>Flow_g2_end</bpmn:incoming> </bpmn:endEvent> </bpmn:process> <! »
A application deployed to Altinn Apps will typical have a business process that users and systems need to follow.
Apps created in Altinn Studio uses BPMN 2.0 standard to describe the business process and the app will have functionality to support different types of tasks in the process.
The process is defined by the application developer in Altinn Studio. When a new app is created it a basic process is created. »
⚠️ Signing task require version 8.0.0 or newer of app-libs
Setting up a signing task in the process file requires a bit more work than a regular data, confirm or feedback task.
This page will walk you through what you need to configure and how that is connected to other parts of the configuration.
Defining and configuring a signing task A signing task in its simples format looks something like this: »
⚠️ Signing task require version 8.0.0 or newer of app-libs
Setting up a signing task in the process file requires a bit more work than a regular data, confirm or feedback task.
This page will walk you through what you need to configure and how that is connected to other parts of the configuration.
Defining and configuring a signing task A signing task in its simples format looks something like this: »
