Behavior:
A DocuWare client can access several DocuWare systems at the same time. For example, a DocuWare user connected to the network via their Notebook can use both the central file cabinets and their own file cabinets on the Notebook at the same time. The DocuWare system to which a user logs on first (for example the company's central DocuWare installation), acts as the primary system. The user's local DocuWare installation (for example on their Notebook) must be set up as an additional connection within this primary system, so that the user can access the local file cabinets at the same time. Users can also configure the company's central DocuWare installation as an additional connection in their local installation (on their Notebook). If they then log on to the local DocuWare system first, the local system will act as the primary system. Users always have the functional rights which they have in the DocuWare system to which they log on first and which is therefore acting as the primary system. File cabinets in the system to which the user logged on additionally are indicated by a "(*)" after the file cabinet name.
Solution:
To ensure access to the additional connection, the necessary settings must be specified in DocuWare Administration under <Organization x>/Additional Connections.
A DocuWare client can access file cabinets in several DocuWare systems at the same time. The DocuWare system to which a user logged in first, acts as the primary system.
The user always has access to the stamps, RECOGNITION templates and OCR and barcode settings of the primary system.
You can use ACTIVE IMPORT and TIFFMAKER to store documents in the file cabinets of both the primary system and the additional system. However, if you have integrated RECOGNITION templates in ACTIVE IMPORT jobs or TIFFMAKER configurations, the extraction can only be run by RECOGNITION during an ACTIVE IMPORT or TIFFMAKER run if this RECOGNITION template exists in the primary system.
If you wish to use ACTIVE IMPORT jobs or TIFFMAKER configurations with integrated RECOGNITION templates in both systems, you must create the RECOGNITION templates and the ACTIVE IMPORT jobs or TIFFMAKER configurations in both systems.
Example:
A user has logged into system A and creates the "Invoices" RECOGNITION template there. He then integrates this template in the "Financial Accounting" ACTIVE IMPORT job, which stores documents in the "Financial Accounting" file cabinet in system A.
At another time, he first logs into system B, which then becomes the primary system. If he now starts the ACTIVE IMPORT job, this will run and store documents in the "Financial Accounting" file cabinet of the (now additional) system A, but it will be unable to carry out the embedded extraction by RECOGNITION.
To solve this problem, the user can log in first to system B and create a RECOGNITION template there that matches the "Invoices" template in system A. He then creates a new ACTIVE IMPORT job called "Financial Accounting B", integrates the new RECOGNITION template and specifies the "Financial Accounting" file cabinet in the now additional system A.
Now when the user works with system A as the primary system, he enables the "Financial Accounting" ACTIVE IMPORT job, but when he works with system B as the primary system he enables the "Financial Accounting B" ACTIVE IMPORT job. This allows him to store documents automatically in both systems, including the RECOGNITION extraction.