Description of the Class/CO Profile Itself

Description

Profile settings allow shaping the system’s behavior when interacting with it. These are settings related to both the server side and settings for client components.

Fields of the Class Profile Itself

1. name. Must match the key of the object describing this class.
2. name_ru. Not necessarily in Russian. This is the title that will be displayed in client tables, and also used in system messages during manipulations with this object (e.g., “User added”).
3. primary_key. System field, always id.
4. parent_table and parent_key. Used by client components (tables located inside a form or frame). They allow finding the parent form, obtaining the id of the parent record, and applying a filter to the table data.
   • parent_key is used either from this field or taken from the field profiles (the field that has the parent_key flag set).
5. server_parent_table and server_parent_key. Define the table’s dependency (direct hierarchy) on other tables. Multiple tables can be specified separated by commas. The number of keys must match the number of tables. Dependency on itself is allowed (e.g., d_location or d_storage).
   • Used to define dependencies during cascading deletion and cache clearing.
6. server_parent_key_for_dynamic_fields. Not used.
7. checkbox_where, checkbox_where_default_enabled, and checkbox_where_title. Allow displaying a checkbox in the table header, which when activated applies an additional condition to the data (as a JSON array of IOneWhere condition objects).
   • For the current date, NOW_DATE substitution is provided (format DD.MM.YYYY).
   • The initial state of the checkbox and its label can be specified.
8. param_checkbox (and additional fields). Not used.
9. ending. Used for inflecting system messages (e.g., for feminine gender “a” in the word “changed” in Russian).
10. default_order_by. Default sorting (e.g., id desc).
11. default_where. Default conditions (JSON string with an IOneWhere[] array). Applied to any request.
    • Can be canceled on the server by passing doNotUseDefaultWhere=true in rParams.
12. open_form_client_object. Name of the client object (form) that will open from the table’s context menu. Requires the new_by_modal_command flag.
13. child_client_object. Usage status not confirmed.
14. rows_max_num_list and rows_max_num. Configuration of the number of rows displayed in the table. Default: 10, 20, 50, 100.
15. new_command, modify_command, remove_command. Checkboxes that determine the possibility of creating, modifying, and deleting data. Checked on both the client and the server.
16. editable. If false, prohibits any actions with the data by the client (checked on the server).
17. additional_functionality. Allows connecting a client JS file of the same name to extend the table’s functionality.
18. distinct_columns. Names of fields separated by commas to add DISTINCT to the query.
19. use_cache. Possibility to disable caching for the class (used for system tables).
20. check_company_access. Obsolete/Not implemented (another mechanism is used).
21. count_large. Obsolete.
22. like_type. LIKE mode for search (%like, like, like%). Default is like.
23. hierarchical_table and do_not_set_deep. Determine the table’s hierarchy (self-reference). Fields node_deep, parents_count, children_count are automatically added.
    • Methods getTree, getParentIds, getChildIds are available.
24. do_not_use_cache_client. Obsolete.
25. child_class. Allows specifying a child class (and CO via a dot) to build a complex hierarchy of several entities in getTree.
26. command_get, command_add, command_modify, command_remove. Allow overriding standard commands. In the current version, implemented only for command_get in forms.