update lock section

Author: oblomov-dev

docs/.vitepress/config.mjs

@@ -159,10 +159,6 @@ export default defineConfig({
                 text: "Geolocation, Maps",
                 link: "/development/specific/geolocation",
               },
-              {
-                text: "Stateful Sessions",
-                link: "/development/specific/stateful",
-              },
               { text: "URL", link: "/development/specific/url" },
               { text: "Formatter", link: "/development/specific/formatter" },
             ],
@@ -203,6 +199,10 @@ export default defineConfig({
           { text: "Downporting", link: "/advanced/downporting" },
           { text: "Renaming", link: "/advanced/renaming" },
           { text: "Builder", link: "/advanced/builds" },
+          {
+            text: "Stateful Sessions",
+            link: "/development/specific/stateful",
+          },
           { text: "Local", link: "/advanced/local" },
           { text: "RFC Connector", link: "/advanced/rfc" },
           { text: "FE Integration", link: "/advanced/fiori" },

docs/advanced/stateful.md

@@ -0,0 +1,15 @@
+# Statefulness, Locks
+
+By default, abap2UI5 runs stateless like any other UI5 freestyle app, meaning only REST calls are made to the ABAP backend.
+
+## Stateful Sessions
+
+In private and on-premise scenarios, abap2UI5 can also be used in stateful mode. Check out `Z2UI5_CL_DEMO_APP_135` and `Z2UI5_CL_DEMO_APP_137` for examples.
+
+## Locks
+
+In certain scenarios, locking of business objects may be needed. Stateful sessions (described above) are one way to achieve this.
+
+## Infinite Transactions
+
+Another option is to create an infinite session in the backend that holds locks while the UI5 app still communicates statelessly. Check out the documentation [here](https://help.sap.com/docs/ABAP_PLATFORM_NEW/6568469cf5a1460a8d85c58b83d21ec2/47db6c68e4282972e10000000a42189b.html?locale=en-US) and see the issues [here](https://github.com/abap2UI5/abap2UI5/issues/2003) and [here](https://github.com/abap2UI5/abap2UI5/issues/1971) for more information.