The app assumes that the binary content of attachments is kept in Cloud Client instead of the Odoo server. So, such attachments in Odoo become of the URL type, and you may any time access them either from the attachments box or from the Cloud Client.

After the setup, no manual actions are required, as the synchronization is fully automatic. Just decide which Odoo document types should be synced and set up a related model to sync for each of those (Customers, Sale or Purchase Orders, Tasks, Projects, etc.).

Yes, you can. To that goal, prepare a rule for each, and then those apply filters: for example by type of a project.

Try to make filters self-exclusive in order a document can be definitely assigned. For instance, 'customer but not supplier', 'supplier but not customer'. Otherwise, a specific document folder would jump from one model to another.

No. We have strong reasons to avoid real time sync:

• Performance issues. In case a sync is real time, each file upload will result in the loading screen.

• Conflict issues. If 2 users simultaneously change an item, it might lead to unresolved situations. In case of regular jobs we can fix it afterwards, while in case of real time we would need to save it as some queue, and it will be even more misleading for users.

• Functionality issues. In particular, renaming and restructuring of items. In the backward sync the tool strictly relies upon directories' logic, and during each sync 100% of items are checked. In case it is done after each update, it will be thousands of requests per second. If not: changes would be lost.

You may assign your name for models' directories (sale orders, opportunities, suppliers, etc.) for any document type.

For objects' folders (SO-001, John Smith, etc.), the tool relies upon the Odoo method to construct a display name for this document type. However, you can change that by defining the name expression. The exact syntax for Odoo email templates is used. 

No, starting from version 15, you should not change scheduled jobs. They are optimized to run every 15 minutes to guarantee the most stable and quick connection.

Ensure that your Odoo server timeouts are set for at least 15 minutes (900 seconds).

If you need to stop sync for a while, do that on a particular cloud client form.

Yes, starting from version 15, you can set up multiple connections. In this way, it is possible to sync some folders to one cloud client and others - to another.

Take into account that it is not any way possible to sync the same folder for a few cloud storages simultaneously.

Yes, depending on your cloud client configuration.

Starting from version 15, the app might be used stand-alone to structure attachments in folders and to provide a file manager interface.

However, if your goal is to establish a connection with one of its cloud clients, you would need at least one optional client-related app to be installed.

When a folder rule changes, the list of folders also changes. So, if a folder no longer matches the conditions of the folder rules - it is removed. If the files have been synced, the reversed sync returns them to Odoo and deletes them from the Cloud Client.

If a document's object doesn't match the conditions of a folder rule, then its folder will not be created. However, if it matches the conditions later, the related folder will be generated.

No, the tags are not synchronized. We considered this feature previously, but made a decision not to introduce such a feature due to a number of reasons:

• The connector library doesn't support getting or updating OwnCloud tags

• Odoo attachments do not have the attribute 'tags' and it is not fully clear when those tags would be assigned to users.

• Since the app provides bilateral sync, there might be critical conflicts during sync which would be difficult to resolve.

According to the current Odoo Apps Store policies:

• Every module bought for version 12.0 and prior gives you access to all versions up to 12.0.
• Starting from version 13.0, every module version should be purchased separately.
• Disregarding the version, purchasing a tool grants you a right to all updates and bug fixes within a major version.

Please note that the faOtools team does not control those policies. For all questions, please contact the Odoo Apps Store representatives directly.

The most straightforward approach is to use the Odoo store's built-in workflow:

1. Open the module's page and click the button Deploy on odoo.sh

2. After that, you will be redirected to the GitHub page. Log in to your account and click 'Create a new repo' or use the existing one. Please make sure that your repository is private. It is not permitted to publish the apps under the OPL-1 license. If necessary, create a new repo for your Odoo.sh project

3. Then, go to odoo.sh and click the Deploy button. In the pop-up window, submit the decision and click 'Continue.' This action will trigger the installation process.

These steps will install the app for your project's production branch. If you want to deploy the apps for other branches or update the module, you should undertake the following actions:

1. Upload the source code for the app from the Odoo store

2. Commit the module to a required GitHub repository. Ensure that none of the app folders/files are ignored (included in the .gitignore of your repo). Repositories are automatically created by odoo.sh, which might add some crucial items there (e.g. /lib) by default. You should upload all module directories, subdirectories, and files without exceptions

3. Deploy a target branch of the odoo.sh project or, if your settings assume that, wait until it is automatically built.

Yes, sure. Simultaneously, Odoo automatically adds all dependencies to a cart, so you should exclude previously purchased tools to avoid double payment.

A red/orange warning does not influence the app's features. Regretfully, sometimes our modules do not pass standard automatic tests since the latter assume behavior that conflicts with our app's goals. For example, we change the price calculation, while the standard Odoo module tests compare the final price to a standard algorithm.

So, first of all, please check the deployed database features. Does everything work correctly?

If you still assume that the warning influences real features, please contact us and forward full installation logs and the full list of deployed modules (including core and third-party ones).

No, we only distribute the tools through the official Odoo apps store.

Regretfully, we do not have the technical means to provide individual prices. 

No, third-party apps can not be used on Odoo Online. Unfortunately, Odoo SaaS blocks such a possibility.

Yes, our tool requires all modules marked in dependencies to work correctly. The price marked on the app page already includes all necessary dependencies.

The price for our modules is set in euros. The Odoo store converts prices to other currencies according to its internal exchange rate. Thus, the price in US Dollars may change when the exchange rate is updated.