Common modules: Server call property

Scope: managed applications, mobile applications, and ordinary applications.

1. Do not forcefully select the Server call checkbox for all common modules with the Server flag. Such modules must contain only procedures and functions intended to be called by the client-side code, ensuring that only authorized actions or data are executed or transmitted to the client. For example, a server function performing a calculation must send the final result to the client, not the raw data used in the calculation, which might not be accessible to the user.

Pay special attention to server-side procedures and functions stored in common modules flagged as Privileged, and to those that use privileged mode.

Server-side procedures and functions that are not intended for client access must be stored in common modules with the Server call flag cleared.

2.1. Configuration object development typically assumes that object instances, such as CatalogObject and DocumentObject, are managed on the server side in managed mode. Thus, it may not be possible to manage them on the client side.

Specifically, in a thick client with a managed application mode, it is important not to create or receive objects in the following scenarios:

In client common modules using the ThickClientManagedApplication preprocessor command.
In ordinary forms when starting up in managed mode. It is best to use these forms only in ordinary application mode.

By following these guidelines, you can avoid running object module and event subscription code on the client and reduce the number of server calls.

2.2. If a configuration is not designed for a thick client in managed application mode, clear the Thick client (managed application, client/server) checkbox to avoid receiving false error messages during configuration validation.