cobi.wms:faq
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cobi.wms:faq [2022/10/05 10:56] – tkammer | cobi.wms:faq [2023/05/23 13:46] (current) – tkammer | ||
---|---|---|---|
Line 110: | Line 110: | ||
==== How to avoid two pickers accidentally working on the same pick list? ==== | ==== How to avoid two pickers accidentally working on the same pick list? ==== | ||
- | You can fill in the " | + | You can fill in the " |
- | Any attempts at solving this issue via additional features poses significant challenges: | + | Variant 1: Only let pickers open pick lists assigned to them. |
- | + | ||
- | 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. | Variant 2: Lock a pick list once it’s been opened by someone. | ||
Line 120: | Line 118: | ||
* There needs to be an additional UDF on the pick list that says “locked” | * There needs to be an additional UDF on the pick list that says “locked” | ||
* Every time you open a pick list in the app, it needs to: | * Every time you open a pick list in the app, it needs to: | ||
- | - Run a query to make sure the pick list is still not locked (the user might not have refreshed the screen, so it could be that it was appearing as unlocked | + | - Run a query to make sure the pick list is currently |
- | - Send an update to change the UDF value to locked | + | - Send an update to change the UDF value to locked. |
- | - When you close the pick list, the UDF value must be updated again to unlock it. | + | - When you close the pick list, send an update to change |
We would now be faced with the following issues: | We would now be faced with the following issues: | ||
Line 164: | Line 162: | ||
===== Licensing ===== | ===== Licensing ===== | ||
- | ==== Is one license for device or for a person? How can we manage licenses? ==== | + | ==== What kind of SAP Business One Licenses are needed to use the app? ==== |
- | A COBI.wms | + | Apart from the COBI.wms |
- | If a device is licensed, any person | + | According to the latest licensing guidelines of SAP Business One (as of May 2023), **every individual employee (person)** who interacts with SAP Business One through any means (including third-party applications such as COBI.wms) must have some kind of SAP Business One License. |
- | If a user is licensed, they can log in to COBI.wms on any Android device. | + | If an employee who will use COBI.wms already has an SAP Business One License, such as Professional or Limited Logistics, then they don't need an additional SAP Business One License to be allowed to use COBI.wms. |
+ | |||
+ | However, if the employee doesn' | ||
+ | |||
+ | ==== Are COBI.wms Licenses for devices or for users? How can we manage licenses? ==== | ||
+ | |||
+ | A COBI.wms license can be assigned to an Android device **or** to a COBI.wms | ||
+ | |||
+ | If an Android device is licensed, any person can log in on that device and use it. Users don't require licenses in this case. | ||
+ | |||
+ | If a COBI.wms User is licensed, they can user their username and password | ||
Licenses can be freely swapped between devices and users. | Licenses can be freely swapped between devices and users. | ||
+ | |||
+ | Generally, licensing devices is the easier option, especially since you won't have to deal with COBI.wms User Management. | ||
+ | |||
+ | See [[COBI.wms: | ||
cobi.wms/faq.1664960185.txt.gz · Last modified: 2022/10/05 10:56 by tkammer