Differences

This shows you the differences between two versions of the page.

--- cobi.wms:print_settings [2022/09/01 10:08] – tkammer
+++ cobi.wms:print_settings [2026/01/06 14:10] (current) – [Authentication] thuth
@@ Line 11: / Line 11: @@
 This type of printing requires a network-capable printer, but no additional server-side software.  The Android device will contact the IP Address of the printer in the local network and send it the document to print.
+For label printing, the app uses templates in a custom HTML-based format which is described here: [[:COBI.wms:Label Templates]]
 ==== Method ====
@@ Line 34: / Line 36: @@
 This type of printing requires the COBI.wms Print Service to be installed on a Windows Server that can be reached from the Android mobile devices.
-Currently, the document printing feature works solely in combination with **coresuite designer** layouts.
+Currently, the document printing feature works solely in combination with coresuite designer and crystalreport layouts.
 ==== Print service address ====
@@ Line 46: / Line 48: @@
 ==== Authentication ====
-If you've configured the [[Print Service]] with multi-tenancy support, you must enter the correct ''AuthToken'' value into the ''Authentication'' text field.  Otherwise, you must leave the field empty.
+If you've configured the [[Print Service]] with multi-tenancy support, you must enter the correct ''AuthToken'' value into the ''Authentication'' text field.  Otherwise, you must leave the field empty. \\
+\\
+\\
-==== Print Mode, Layout ID, and Print Def settings ====
+===== Print Mode, Layout ID, and Print Def settings =====
 The rest of the print settings screen consists of **Print Mode**, **Layout ID**, and **Print Def** fields for each type of booking where the app supports printing.  These values must correspond to the the coresuite print modes, designer layout IDs, and print definitions.
+==== Where to find Layout ID and Print Def (coresuite designer) ====
+To print from COBI.wms via the COBI.wms Print Service to coresuite, the values entered in Layout ID and Print Def must match the identifiers configured in the coresuite designer.
+Important: Use the value from the field “Code” (not the “Name”) in:
+  * Layoutdefinition → Code = value for Layout ID
+  * Printdefinition → Code = value for Print Def
+Example (from coresuite designer):
+  * Layoutdefinition → Code: `T0000008`
+  * Printdefinition → Code: `T0000010`
+=== Steps (SAP Business One) ===
+  * Open SAP Business One (client where coresuite is installed).
+  * Go to Add-ons → coresuite designer.
+  * Open Layoutdefinition and select the relevant layout for your document type (e.g., Delivery, Sales Order, etc.).
+    * Copy the value from Code (e.g., `T0000008`).
+    * Enter this value in COBI.wms → Print Settings → Layout ID.
+  * Open Printdefinition and select the relevant print definition.
+    * Copy the value from Code (e.g., `T0000010`).
+    * Enter this value in COBI.wms → Print Settings → Print Def.
+=== How this maps to the Print Service XML ===
+If the fields are filled correctly, the Print Service will send the values as:
+  * Layout ID → `layoutid="..."`
+  * Print Def → `<param key="PrintDef" value="..."/>`
+Example:
+  <?xml version="1.0" encoding="utf-8"?>
+    <job>
+    <type mode="Print" formtype="140" layoutid="T0000008" />
+    <paramsets>
+      <paramset>
+        <params>
+          <param key="PrintDef" value="T0000010" />
+          <param key="DocEntry" value="575" />
+          <param key="FreeText" value="Test123" />
+        </params>
+      </paramset>
+    </paramsets>
+  </job>