Create PosSystem migration guide

poscreators/middleware-doc/general/communication/communication.md

@@ -5,6 +5,12 @@ title: Communication
 
 # Communication
 
+:::info PosSystem API (v2) Migration
+
+If you are an Austria (AT) or France (FR) customer currently using the v0 WCF or REST interface and planning to move to the new PosSystem API, see the Migrating from API v0 to PosSystem API (v2) guide.
+
+:::
+
 The fiskaltrust.Middleware supports different communication protocols, effectively giving our users the possibility to use it on all currently available platforms and implement the interface in all state-of-the-art programming languages. This enables our users to choose the communication type that suits their scenario best.
 
 The communication protocol is specified by setting the respective URL in the package configuration of the fiskaltrust.Portal. The buttons to the right of the URL field can be used to quickly insert the respective URL:

poscreators/middleware-doc/general/function-structures/function-structures.md

@@ -5,6 +5,12 @@ title: Function Structures
 
 # Function Structures
 
+:::info PosSystem API (v2) Migration
+
+If you are an Austria (AT) or France (FR) customer currently using the v0 synchronous `Sign`/`Echo`/`Journal` calls and planning to move to the new PosSystem API, see the Migrating from API v0 to PosSystem API (v2) guide.
+
+:::
+
 ## iPOS Interface
 
 This interface is a communication channel for interacting with the fiskaltrust.Middleware. It provides three basic functions: "echo", "sign", and "journal". The functions "echo" and "sign" return bare-objects, the function "journal" returns a wrapped-object.

poscreators/middleware-doc/middleware-at-rksv/appendix-at-rksv.md

@@ -17,4 +17,10 @@ https://www.lindeverlag.at/onlineprodukt/handbuch-registrierkassen-und-belegerte
 
 Ritz/Koran/Kutschera/Knasmüller, Handbuch Registrierkassen- und Belegerteilungspflicht, 2. Auflage 2019, Linde Verlag Wien. ISBN: 9783707335910
 
+:::info Upgrading to PosSystem API (v2)
+
+New features such as e-invoicing are available exclusively through the **PosSystem API (v2)**. If you are currently using the v0 interface (WCF/REST), see the Migrating from API v0 to PosSystem API (v2) guide for instructions.
+
+:::
+
 <div class="alert alert--warning" role="alert">Please note that this information is only complete when combined with the <b>General</b> part. To implement the Middleware, users should get themselves familiar with the general information first and then refer to the country-specific details listed here.</div>

poscreators/middleware-doc/middleware-de-kassensichv/appendix-de-kassensichv.md

@@ -7,4 +7,10 @@ title: Introduction
 
 This appendix expands on the General Part's information by adding details specific to the German market. This additional information is provided only where applicable. The remaining chapters, for which there is no further information required, were omitted.
 
+:::info Upgrading to PosSystem API (v2)
+
+New features such as e-invoicing are available exclusively through the **PosSystem API (v2)**. If you are currently using the v0 interface (WCF/REST), see the Migrating from API v0 to PosSystem API (v2) guide for instructions.
+
+:::
+
 <div class="alert alert--warning" role="alert">Please note that this information is only complete when combined with the <b>General</b> part. To implement the Middleware, users should get themselves familiar with the general information first and then refer to the country-specific details listed here.</div>

poscreators/middleware-doc/middleware-fr-boi-tva-decla-30-10-30/appendix-fr-boi-tva-decla-30-10-30.md

@@ -23,4 +23,10 @@ The technical specification of the data interface described in this document pro
 
 The interface specification is provided by fiskaltrust.Interface NuGet package, which can be found at https://www.nuget.org/packages/fiskaltrust.interface.
 
+:::info Upgrading to PosSystem API (v2)
+
+New features such as e-invoicing are available exclusively through the **PosSystem API (v2)**. If you are currently using the v0 interface (WCF/REST), see the Migrating from API v0 to PosSystem API (v2) guide for instructions.
+
+:::
+
 <div class="alert alert--warning" role="alert">Please note that this information is only complete when combined with the <a href="https://docs.fiskaltrust.eu/docs/poscreators/middleware-doc">General Part</a>.<br />To implement the Middleware, users should get themselves familiar with the general information first and then refer to the country-specific details listed here.</div>

poscreators/toc.js

@@ -370,7 +370,7 @@ module.exports = [
       },
     ],
   },
-    ],
+  ],
   },
   {
   type: "category",

posdealers/technical-operations/middleware/helper-possystemapi.md

@@ -16,6 +16,12 @@ After reading this, you can set up and configure the local PosSystem API Helper
 
 :::
 
+:::info Migrating from v0?
+
+If your POS system currently uses the v0 interface (WCF/REST) and you are migrating to the PosSystem API, see the [v0 → PosSystem API migration guide](../../../poscreators/middleware-doc/general/migration/v0-to-possystemapi.md) for a full overview of API and data model changes.
+
+:::
+
 ## Introduction
 
 The local PosSystem API Helper is a Middleware component that exposes a local endpoint through which the POS System communicates with the fiskaltrust Middleware. It acts as a bridge between the POS System and the underlying Queue, and is required for Launcher 2.0 deployments.