Scope: managed applications, mobile applications, and ordinary applications.
1.Do not forcefully select the Server call check box for all common modules with the Server flag. Such common modules must include only procedures and functions that are intended to be called from client code and guarantee that only actions (or data) allowed to a user will be executed (or transfered to the client). For example, a server function that implements a calculation algorithm must pass the client the final result of this calculation but not source (or intermediate) data for the calculation, which might not be available to the current user.
Pay special attention to procedures and functions that use the privileged mode or placed in common modules with the Privileged flag.
Place server procedures and functions that are not intended to be called from the client code in common modules without the Server call flag.
2.1. As a rule, when developing configuration objects (catalogs, documents, and other), it is assumed that instances of these objects (CatalogObject, DocumentObject, and other) are managed on the server in managed mode. Therefore, you might not be able to manage them on the client in managed mode.
In particular, in thick client in managed application mode, do not create or receive objects:
- In client common modules (using the ThickClientManagedApplication preprocessor commands).
- In ordinary forms upon startup in managed mode. We recommend that you use such forms in ordinary application mode only.
This will allow you to avoid executing object module code, event subscriptions on the client, and redundant server calls of common module procedures and functions from this code.
2.2. If a configuration is not designed to work in thick client, a managed application, clear the Thick client (managed application, client/server mode) check box to avoid false error messages upon configuration validation.