1. Identification
| Parameter | Value |
|---|---|
| Metadata Object Type | Document (Documents) |
| Name | DataExchangeScenarios |
| Full Name | Document.DataExchangeScenarios / Documents.DataExchangeScenarios |
| Synonym | — (not specified in the delivery) |
| Configuration | Accounting for Kazakhstan, edition 3.0, version 3.0.74.2 |
| Object Class | Service (technical) document of the data exchange subsystem |
Purpose. The object is intended for configuring and centrally managing automated data synchronization processes between 1C information bases. Each element describes one exchange scenario: a set of recipient/sender nodes, types of message transport, direction of actions (upload/download), and scheduling parameters through a scheduled task. It is used by administrators and integration specialists during the initial setup of distributed accounting systems and when changing the exchange topology. Work with the object is rare — episodic, during the deployment and support of integrations.
Important by type. In terms of accompanying materials, the object may be referred to as a "reference" — this is an inaccuracy in description. According to the metadata of the configuration, this is a Document (
Document.DataExchangeScenarios). Below, the structure is described as for a document.
Where to find in 1C:
- Navigation link:
e1cib/list/Document.DataExchangeScenarios - Through the interface: section “Administration” → “Data Synchronization” → “Data Synchronization Scenarios” (in some releases, the item is called “Schedule Configuration for Data Exchange”).
2. Header Attributes and Table Parts
2.1. Header Attributes
| Name | Type | Mandatory | Purpose |
|---|---|---|---|
| UseScheduledTask | Boolean | Not checked | Flag for activating automatic execution of the scenario according to schedule. When set, the system creates/enables the associated scheduled task. |
| Comment | String | Not checked | Arbitrary text description of the scenario for the convenience of the administrator. |
| ScheduledTaskGUID | String | Not checked | Unique identifier of the associated scheduled task in the system. Service field, filled and maintained automatically; not edited manually. |
| DisabledAutomatically | Boolean | Not checked | Indicator of automatic disabling of the scenario by the system in case of repeated synchronization errors (for example, when a node is unavailable or subscription limits are exceeded). |
Standard document attributes (Date, Number, Posted, DeletionMark, Reference) are used in a service role: date and number identify the scenario record, the posting indicator is not used in standard logic (see section 5).
Note. All application attributes are optional for user filling.
ScheduledTaskGUIDandDisabledAutomaticallyare managed by the system.
2.2. Table Part “ExchangeSettings”
Synonym: “Synchronization Settings”. Contains a list of synchronization operations performed within one scenario. Each row describes one action with one exchange plan node.
| Name | Type | Purpose |
|---|---|---|
| NodeOfInformationBase | ExchangePlanReference.* |
Node of the exchange plan (specific information base) with which the exchange is performed. |
| TypeOfExchangeTransport | EnumerationReference.MessageTransportTypes |
Method of data transmission: COM connection, web service, file directory, FTP, etc. |
| ActionPerformed | EnumerationReference.ExchangeActions |
Type of operation: unloading changes, loading changes, or both actions. |
Purpose of the Table Part. Allows describing a sequence of synchronization steps with different nodes and different exchange directions within one scenario, executed automatically according to a single schedule. The order of rows determines the sequence of operations.
3. Forms
| Form | Type | Purpose |
|---|---|---|
| ListForm / DataExchangeScheduleConfiguration | List | Main entry point: view all scenarios, create and edit, enable/disable automatic execution, manual start of exchange. |
| DocumentForm (element form) | Element | Edit a specific scenario: header attributes, fill the Table Part “ExchangeSettings”, configure and bind the schedule of the scheduled task. |
| Schedule Configuration Form (auxiliary / from BSP) | Service | Standard schedule dialog (ValueToStringInternal of the scheduled task) for launch parameters. |
If in a specific build 3.0.74.2 the set of forms differs, refer to the main list form (navigation link from section 1) — it is the working interface of the object.
4. Key Procedures of Modules
BSL sources for this object are not attached in evidence, so below is a typical set of handlers for documents of this purpose. Specific names/lines should be clarified in the object module and form modules of the corresponding build.
Object Module:
FillProcessing(FillingData, ...)— pre-filling a new scenario (default values for flags and Table Parts).BeforeWriting(Refusal, WriteMode, PostingMode)— control of the correctness of settings before saving.OnWriting(Refusal)— synchronization of the scheduled task state with the attributesUseScheduledTask/ScheduledTaskGUID: creation, update, or disabling of the task.ProcessingPosting(Refusal, PostingMode)— in standard logic does not generate accounting entries (see section 5); if implemented, usually empty or absent.
Application Logic of Exchange (object module / common module of the exchange subsystem):
- Scenario execution procedure (conditionally
ExecuteExchangeByScenario) — sequential iteration over the rows of the Table Part “ExchangeSettings” and calling the synchronization mechanism for each node consideringTypeOfExchangeTransportandActionPerformed. - Scheduled task management procedures — creating a task by GUID, setting the schedule, enabling/disabling, automatic disabling in case of repeated errors (setting
DisabledAutomatically).
Form Module (list/element):
OnCreationOnServer— initialization of visibility and availability of elements.- Form commands: “Execute Exchange” (manual start of the scenario), “Configure Schedule”, “Enable/Disable Automatic Execution”.
- Handlers for reacting to changes in the flag
UseScheduledTask(managing the availability of schedule settings).
5. Posting and Movements
The object is not an accounting document and does not generate accounting entries and movements in accounting registers. This is a service document of the data exchange subsystem. Accordingly:
- It does not make entries in the accounting register (standard chart of accounts of the RK: 1210, 1030, 1330, 3310, 3130, 6010, 7010, etc.) — these accounts are not related to exchange scenarios.
- It does not participate in tax and contribution calculations (VAT 16%, PIT, social contributions, OSMS/VOSMS, social tax) and in the formation of electronic documents (ESF/SNT). These mechanisms are implemented by specialized accounting documents, not by the exchange scenario.
- The “result of the object’s work” is synchronization operations: unloading/loading changes for the specified exchange plan nodes, recording service information about the progress and status of the exchange (registration log, service information registers of the exchange subsystem, updating the status of the scheduled task).
The posting indicator in the standard configuration for this document is functionally not used; the “launch” of the scenario is performed by a command (manual or scheduled), not by posting the document.
Requires verification (version-specific): in some releases, the posting mode for the document may be set to “Prohibit”. Clarify the value of the “Posting” property of the object in the specific build 3.0.74.2.
6. Related Objects and Input Based On
| Connection | Object | Nature of Connection |
|---|---|---|
| Exchange Nodes | ExchangePlan.* (any exchange plan of the configuration) |
Table Part “ExchangeSettings” refers to specific nodes of information bases. |
| Transport | Enumeration.MessageTransportTypes |
Defines the method of transmission for each row. |
| Action | Enumeration.ExchangeActions |
Defines the direction of exchange for each row. |
| Schedule | Scheduled Task (ScheduledTaskGUID) |
Automatic launch of the scenario; managed through the flag attribute and service GUID. |
| Transport Settings | Information registers of the exchange subsystem (connection parameters COM/WS/FTP/file) | Store connection attributes to nodes used during execution. |
Input Based On. For a service document of this purpose, input based on and use as a basis in the standard delivery are not provided.
7. Extension Points
- Configuration Extension: intercept
OnWriting/ scenario execution procedures to add custom logic (notifications to the administrator, additional validation of topology, custom error handling). - Additional processing before/after exchange: implementation of data preparation or post-processing steps in the iteration cycle of the Table Part “ExchangeSettings”.
- Event logic for nodes: reaction to changes in the composition of
ExchangeSettingsfor auto-configuration of transport. - Monitoring and notifications: processing the
DisabledAutomaticallyindicator for escalation in case of repeated failures (for example, integration with a notification system). - Form extension: adding commands for manual launch of individual scenario rows, diagnosing connection with the node, viewing the log of the last exchange.
When making modifications, maintain separation: accounting logic (entries, taxes, ESF/SNT) — in specialized accounting documents, while this object is solely responsible for orchestrating data synchronization.