1. Identification
| Parameter | Value |
|---|---|
| Object Type | Catalog |
| Name | RemoveExchangeExecutionSettings |
| Full Name | Catalog.RemoveExchangeExecutionSettings (Catalogs.RemoveExchangeExecutionSettings) |
| Alias | — (not specified) |
| Configuration | Accounting for Kazakhstan, edition 3.0 (version 3.0.74.2) |
| Status | Deprecated — determined by the prefix Remove in the name |
| Where to find | e1cib/list/Catalog.RemoveExchangeExecutionSettings |
Purpose. The catalog stores deprecated settings for data exchange with other information bases: parameters for scheduled (automatic) synchronization execution, transactionality of data export/import, conditions for starting the exchange, and error notification settings. The prefix Remove indicates that the object is preserved in the configuration solely for backward compatibility and data migration from older versions. In current releases, the exchange functionality is implemented through other mechanisms (the "Data Synchronization" subsystem / BSP). Direct user interaction with the catalog is not intended — it is only used during data migration and support for legacy integrations.
The object belongs to the technical part of the configuration and is not related to accounting, taxes, or calculations. It does not store monetary, tax, or accounting data, so Kazakh accounting parameters (VAT rate 16%, MRP 4,325 ₸, MZP 85,000 ₸, RK accounts, etc.) are not applicable and do not appear in examples.
2. Header Attributes and Table Parts
2.1 Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
ExecuteActionsWithFullRights |
Boolean (xs:boolean) |
Not checked | Flag for performing exchange operations with privileged access (SetPrivilegedMode), bypassing RLS restrictions and user rights |
UseScheduledTasks |
Boolean | Not checked | Enables/disables automatic execution of exchange on schedule through the platform's scheduled tasks mechanism |
ScheduledTask |
String (xs:string) |
Not checked | Identifier/name of the scheduled task associated with this exchange setting |
DynamicallyChangeIntervalBetweenExchanges |
Boolean | Not checked | Auto-adjustment of the interval between exchange sessions depending on the intensity of data changes |
Responsible |
CatalogRef.Users |
Not checked | User responsible for setting up and monitoring data exchange |
EveryProgramLaunch |
Boolean | Not checked | Automatically perform exchange at each launch of the client application |
EveryProgramTermination |
Boolean | Not checked | Automatically perform exchange at each termination of the application |
AvailabilityCheckDirectory |
String | Not checked | Path to the directory for checking the availability of the external system before starting the exchange |
PerformExchangeWhenFileAppears |
String | Not checked | Trigger file name: when the file appears in the specified directory, the exchange is initiated |
NumberOfItemsInTransactionForDataExport |
Number (xs:decimal) |
Not checked | Size of the data export package in one transaction; affects performance and stability of the exchange |
NumberOfItemsInTransactionForDataImport |
Number | Not checked | Size of the data import package in one transaction |
ErrorNotificationEmailAccount |
String | Not checked | Email account identifier for sending error notifications about the exchange |
ErrorNotificationEmailAddress |
String | Not checked | Email address (or list of addresses) for notifications about exchange errors |
Comment |
String | Not checked | Arbitrary explanatory text for the setting |
Standard fields of the catalog: Code, Name, DeletionMark, Predefined, Reference. Hierarchy/ownership indicators in the evidence are not identified — the catalog is generally linear (without hierarchy and subordination).
2.2 Table Parts
| Table Part | Purpose |
|---|---|
ExchangeSettings |
String set of specific settings detailing the execution of the exchange (the composition of columns in the evidence is truncated — …). Typical purpose: linking the setting to a specific node/scenario of exchange and its specific parameters. Requires verification for the specific release: full composition of columns of this table part. |
3. Forms
For catalogs of this purpose, the configuration includes standard forms (in the evidence, separate form modules are not attached):
| Form | Purpose |
|---|---|
Element Form (ElementForm) |
View and edit attributes of a specific exchange setting and rows of the table part |
List Form (ListForm) |
List of settings, opened via e1cib/list/Catalog.RemoveExchangeExecutionSettings |
Selection Form (SelectionForm) |
Select setting when substituting in other objects (if such links exist) |
Specialized forms for the deprecated service catalog are usually absent; in the absence of explicitly assigned forms, the platform uses auto-generated ones.
4. Key Module Procedures
Modules (object module, manager module, form modules) in the evidence are not attached, so below is a typical set of handlers for catalogs of this type. For deprecated objects, the application logic is generally absent or minimized.
Object Module:
BeforeWriting(Refusal)— standard control before writing (usually empty for service catalogs).OnWriting(Refusal)— if necessary, record related changes.FillingProcessing(FillingData, FillingText, StandardProcessing)— filling during input based on (not typical for this object).FillingCheckProcessing(Refusal, CheckedAttributes)— considering that the mandatory attributes are not checked, additional control is usually absent.
Manager Module: standard procedures for data selection/processing; for deprecated objects, specific business logic is not expected.
The actual composition of procedures for version 3.0.74.2 requires verification against the original modules — the attached evidence does not contain them.
5. Posting and Movements
The object is a catalog, not a document: it is not posted and does not generate movements in accumulation registers, information registers, and does not create accounting entries according to the chart of accounts. Accordingly, RK accounts (1210, 1030, 1330, 3310, 3130, 6010, 7010) and tax calculations (VAT, PIT, OPE, etc.) are not applicable — the catalog stores only parameters for data exchange settings.
The influence of the catalog is limited to the technical area:
- parameters of scheduled synchronization tasks (when
UseScheduledTasks = True); - size of export/import transactions;
- addressing of error notifications about the exchange.
Accounting consequences (movements in accounting) of the catalog record are absent.
6. Related Objects and Input Based On
- Catalog "Users" — through the attribute
Responsible. - Platform Scheduled Tasks — through
UseScheduledTasksandScheduledTask. - Exchange Plans / Synchronization Nodes — conceptual link: the setting describes how the exchange with the external information base is performed. In current versions, this role is performed by the data synchronization subsystem (BSP).
- Input Based On for the deprecated service catalog is not provided; it also does not serve as a basis for creating other objects.
7. Extension Points
- Configuration Extension: adding attributes/table parts and object module handlers or forms. Considering the deprecated status, extending the object is not recommended — new exchange logic should be built on current synchronization mechanisms.
- Migration: the main scenario for working with the object is transferring saved settings to the current exchange subsystem when updating from earlier releases.
- Event Subscriptions / Overridable Modules: for the service catalog, there are no typical override points; integration logic is implemented at the level of exchange plans and conversion rules.
General recommendation: do not manually create new elements of this catalog. Use it only for reading/migrating legacy settings. The full composition of columns in the table part
ExchangeSettingsand actual modules for version 3.0.74.2 require verification against the specific configuration delivery.