Working with the 1C:Enterprise edition
The Open Integration Package is originally developed as a configuration extension for the 1C:Enterprise 8 platform. Its methods are exposed as common modules and can be used in any configuration that meets the project requirements.
Development targets compatibility mode 8.3.10 with the check option set to Warn. The extension compatibility mode is set to 8.3.15.
Installation
To get started, add the Open Integration Package modules to your configuration. You can do this in several ways:
-
From an extension
CFEfile (recommended):Download
OpenIntegrations_x.x.x_lang.cfefrom the latest release or the Download section, then load it into your configuration's extension list in Configurator. -
From XML export files:
Download
XML.zip, extract it, and load the extension via the Extensions panel by specifying the folder that contains the XML files. -
From an EDT project:
Download
EDT.zipor connect the source project from the repository in 1C:EDT. For details see Build from source. -
Via compare and merge with a configuration CF file:
Besides distribution as an extension, the Open Integration Package is also shipped as a configuration
cffile. TheOpenIntegrations_x.x.x_lang.cffile can be used to compare and merge OPI objects with your main configuration if using an extension is undesirable or impossible.
Each delivery option is described in About release variants. Regardless of how you install, prefer files from a release, the downloads page, or the repository’s stable branch.
You may manually copy individual common modules from the sources into your project, but for regular updates it is easier to use the packaged distributions.
Client and server usage
Starting from version 2.1.0, all core Open Integration Package modules are available on both server and client. Unlike server-side calls, using OPI methods on the client comes with extra constraints:
- The
Web clientis not supported. - The platform setting for synchronous calls to extensions and external components of the main configuration must be
UseorUse with warnings. - Starting background jobs via the
dontwaitparameter in advanced call settings is not supported. - The first call to a library function that relies on external components will trigger installation of those components. See About external components for details.