Revisions assume recording not only text changes, but also any updates in styles (technically, when you change HTML source code of an article). Some of those might be not clear from the first glance (e.g. a changed font size of a single word). Others might be drastic. However, any set of action Edit > Change anything in an article > Save would result in a new revision.

In KnowSystem, a section becomes visible on a website if it is published and contains at least one article. Even when it has subsections, it will not be visible, if there isn’t a single article in the section itself. This was made to avoid seeing empty sections, and make KnowSystem portal look appealing and easy to navigate through. If you want the section to be shown on the website, you can add one introductory or general article, which briefly describes or lists articles in subsections.

1. Right click on any tag on the left navigation panel - Create

2. Find the field 'Allowed partners'. For example 'clients - azure interior' to set up an access for the partner 'Azure Interior'. You can do the opposite: assign KnowSystem tags right on a partner form

3. Now go to a required article (or you can proceed the same using the action 'Mass update' for multiple records):

   1. If it is published: unpublish it if you don't want to make it available for all portal users and public visitors

   2. Assign a newly created tag (in the example it is 'clients - azure interior')

4. Now:

   1. All portal users related to the commercial partner 'Azure Interior' have an access to the articles with the tag 'Azure Interior'

   2. No other portal users (if different tag is not assigned) have an access to those articles

   3. Internal users are not influenced and can observe articles according the 'access to' logic of articles and sections.

The button 'translate' is not added to the article's body by the optional add-on 'KnowSystem: Multi Languages' on purpose. The reason is that HTML code is very difficult to translate in a simple popup body assumed by the button. There would very little text to translate and a lot of HTML parts (which also might be broken by the translator).

That's why it is assumed that to make an article on a certain language, you should log in under this language user. It might be a different user, or you can temporarily change your current user preferences. After that any updates made in article body would be done in that user language.

Also you can use the button 'Copy from another translation' under the article body, which allows at any moment get the article content from another language (useful in case article has been significantly updated in one of languages).

To that end you may use iframes. Switch an article to the raw HTML code editor and insert, for example, <iframe src="https://mycbms.com/" style="width:100%;min-height:600px;"> </iframe>.

Most probably you haven't granted KnowSystem rights for your user. Choose the right 'KnowSystem Editor' or 'KnowSystem Admin' refresh a page. The control buttons should be now shown.

Yes, by applying a user group (e.g. 'Sales Manager') which should pass this tour. If a user belongs to this group, he/she would see this tour. If not, the tour would not be shown. It works in the same way as security rights for KnowSystem articles and sections.

Take into account that if a tour doesn't have assigned groups, it is 'global' and it would be visible for everybody.

The header and the footer for articles PDFs is taken according to the company layouts. Please have a look at Settings > General Settings > the section Business Documents. Here you may define the company template which would be used for all document types, including invoices, sale orders, etc., and for articles as well. Such CBMS approach assumes that footer and header is a general company style, not an attribute of specific printings.

Each article has an internal (backend) and website URLs (in case the option 'KnowSystem: Website and Portal' is installed). Click on the 'Info' button on an article form to know website addresses of this record. You can insert any into your article body as a hyper link.  

Yes, to that end turn on the debug assets (on the settings overview screen) and get back to a current article. In the edit mode you will see the special icon '</>'. Click on this icon to observe and edit HTML and styles.

According to the current CBMS Apps Store policies:

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

Take into account that CBMS team does not control those policies. By all questions please contact the CBMS Apps Store representatives directly.

The easiest approach is to use the CBMS store built-in workflow:

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

2. After that, you will be redirected to the GitHub page. Login 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 CBMS.sh project

3. Then, go to CBMS ODOO.sh and click on the deploy button, submit the decision in the pop-up window and click ‘Continue’. The action will trigger the installation process.

These steps would install the app for your project production branch. If you wanted 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 CBMS store

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

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

1. Unzip source code of purchased tools in one of your CBMS add-ons directory

2. Re-start the CBMS server

3. Turn on the developer mode (technical settings)

4. Update the apps' list (the apps' menu)

5. Find the app and push the button 'Install'

6. Follow the guidelines on the app's page if those exist.

Yes, sure. Take into account that CBMS automatically adds all dependencies to a cart. You should exclude previously purchased tools.

No, we distribute the tools only through the official CBMS apps store

Regretfully, we do not have a technical possibility to provide individual prices.

No, third party apps can not be used on CBMS Online.

Yes, all modules marked in dependencies are absolutely required for a correct work of our tool. Take into account that price marked on the app page already includes all necessary dependencies.  

Red / orange warning itself does not influence features of the app. Regretfully, sometimes our modules do not pass standard automatic tests, since the latter assumes behavior which is in conflict with our apps goals. For example, we change price calculation, while standard CBMS module tests compare final price to standard algorithm.

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

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

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