Differences

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

--- cobi.wms:faq [2023/05/23 13:46] – tkammer
+++ cobi.wms:faq [2026/06/15 13:01] (current) – thuth
@@ Line 3: / Line 3: @@
 ===== General =====
+==== Does COBI.wms support SSL/TLS encrypted connections to MS SQL Server? ====
+Yes. COBI.wms supports SSL/TLS encrypted connections to Microsoft SQL Server (MSSQL), e.g. for accessing the Management Database.
+If SSL/TLS is configured on the SQL Server side, you can enforce encryption in COBI.wms by setting **Optional fields → Encryption** to **`require`**. This ensures COBI.wms will only connect if the connection is encrypted.
+**Note:** We recommend using a valid server certificate that matches the SQL Server hostname (DNS name) and is trusted by the client environment.
 ==== Which versions of SAP Business One are supported? ====
@@ Line 105: / Line 113: @@
+===== Picking & Packing =====
-===== Pick & pack =====
+==== How can you prevent two pickers from working on the same picking list? ====
-==== How to avoid two pickers accidentally working on the same pick list? ====
-You can fill in the "Picker" field of pick lists in SBO, and it will be displayed in the app, but that is all.  Any attempts at solving this issue via additional features poses significant challenges.
-Variant 1: Only let pickers open pick lists assigned to them.  This has the problem that the warehouse loses flexibility.  Often the employee who should take care of a pick list will change ad-hoc, and technical limitations on who can open a pick list only leads to confusion and frustration.
-Variant 2: Lock a pick list once it’s been opened by someone.  Let's see how this would need to be implemented, after which the problems with it will become apparent:
-  * There needs to be an additional UDF on the pick list that says “locked”
+COBI.wms provides a supporting feature for this scenario.
-  * Every time you open a pick list in the app, it needs to:
-    - Run a query to make sure the pick list is currently unlocked.
-    - Send an update to change the UDF value to locked.
-    - When you close the pick list, send an update to change the UDF value to unlocked.
-We would now be faced with the following issues:
+By enabling the option “Show if a picking list has been started”, the system can indicate whether a picking list is already being processed.
-  * Opening/closing is too slow:  Employees may want to quickly look into a few pick lists without really beginning to work on any of them, and if the app has to execute the query/lock/unlock steps every time, this will become too slow.
+Behavior when enabled:
-  * Unlocking is unreliable:  An employee may open a pick list, not really start working on it, but leave it open on the device.  (Either because the user was not instructed properly that this causes issues, or because they were distracted and forgot to close the list.)  This again leads to confusion and frustration.
+  * A user can actively “start” a picking list
+  * A corresponding flag (UDF) is set in SAP
+  * Other devices will see the list as already in progress (highlighted in green)
-For these reasons the app doesn't attempt to solve the problem where two pickers may accidentally start working on the same pick list.  The employees must communicate with each other to make sure this doesn't happen.
+Important:
+  * This is not a strict system lock
+  * The feature is intended to provide transparency and process guidance
+  * Technically, multiple users could still open and work on the same list
+===== Inventory =====
+==== Can multiple users work on the same inventory list at the same time? ====
-===== Inventory counting =====
+Yes, this is possible with the current COBI.wms version.
-==== Can two employees work on the same counting list at the same time? ====
+Starting from version 2.43, the inventory logic has been significantly improved by introducing an external inventory service.
-No, this is not supported. The employees would be overwriting each other’s inputs. Instead, two different counting lists should be created for the employees to be able to work in parallel.
+How it works:
+  * All counting data is initially collected from devices by the external service
+  * The service centrally gathers inputs from multiple users
+  * Values are consolidated (summed up)
+  * The final results are then transferred to SAP Business One
+Advantages:
+  * Multiple users can work on the same inventory list simultaneously
+  * Improved stability, especially for large inventory counts
+  * No blocking of the Service Layer during counting processes
+  * Reduced risk of data being overwritten
+Note:
+  * Final values are consolidated by the service before being posted to SAP
 ===== Label printing =====