Question: I have modified 1C:Drive with my own extension, where I have created new functional which I would not like to share with potential competitors. Is there any way to lock/password protect my work so it will not be accessible for study in the designer?
Answer: Although configurations which are developed by 1C company are open source, partners/developers can protect their work if they desire to do so. There are five different ways to achieve this:
-Keep your key functionality of the configuration in the common modules as much as possible and then password protect those common modules, where your functionality resides. This can be done in the designer, by opening the common module to be password protected and while it is the active window, selecting from the “Text” menu “Set password”. Please note that only the common modules which work exclusively at server can be password protected. It is not possible to password protect common modules which work at client or at client and server simultaneously.
-If you are releasing your configuration by making your own distribution, then while in the designer, before you begin creating the distribution, open Configuration menu -> Distribute configuration -> Distribution options window. There you can untick the “Include source texts of object modules to distribution” for each of the configuration objects. By doing so, only the compiled module data will be included in the distribution for a given object. Since the compiled data cannot be read and understood by a human being, nobody would be able to read your code then. In this method there are no restrictions on the kind (object, manager, form, common modules etc.) of module or where the module runs (client, server).
-You can sell the software as SaaS (software as a service). In this method your clients would use your configuration via web client and/or mobile client and in the enterprise regime only. Son they would simply not have access to the designer.
-Forbidding your client´s users the right to get connected to the info base from the designer, leaving the privilege of connecting the info base from the designer to yourself.
-Using third party DRM software.