English | English
German | Deutsch
Indonesian | Indonesia
Italian | Italiano
Spanish | Español
Turkish | Türkçe
36.4.14. Exchange plans
In an extension, you can to manage the controllability of the components of the exchange plan. To do this, set the value check flag when the extension is attached for the Components property of the exchange plan. You can also adopt a specific item of the components of the exchange plan in the extension. In this case, the following is transferred to the extension:
- Fag of participation of the configuration object in the exchange plan.
- State of auto-registration of changes.
For an adopted exchange plan, you can add attributes, tables, table attributes, forms, commands, and templates. An adopted exchange plan can include both native extension objects and objects from the extended configuration (which were not previously part of this exchange plan). You cannot exclude extended configuration objects from an exchange plan. In other words, an extension cannot reduce the amount of information passed by the exchange plan.
When attaching an extension, it checks:
- Match of the flag of participation of the configuration object in the exchange plan.
- Match of auto-registration of changes.
In an extension, you can create a native exchange plan. Such exchange plan will have the following features:
- A native extension exchange plan cannot participate in a distributed infobase.
- The system does not provide tools to automatically synchronize the components of extensions between data exchange nodes. This synchronization must be performed separately.