Transferring changes between the working environments
Glossary Item Box
Overview
It often becomes necessary to transfer individual changes between the working environments (applications) in the development process, for example, when you install changes made in the development environment to a test environment.
There are several ways to transfer changes between configurations in the bpm'online:
-
To transfer custom packages between non-shared environments (e.g. development and test environments), you must first export these packages to the file system. How to do this, see the "Exporting packages from the application interface" article.
-
Since bpm’online version 7.11 marketplace application can be installed from .zip archive. The marketplace application is a set of bpm'online pacakges. Installation functions of the marketplace applications are available in the [Installed applications] section. More information about installation functions can be found in the "Installing marketplace applications from a zip archive" article.
- Schema import and export is used for transferring one or more schemas, for example, when exchanging incomplete features between developers. For more information about this method, see the "Transferring changes using schema export and import” article.
- Use version control system if you need to manage changes in different versions during development. This option is also recommended if several developers are working with the same schemas simultaneously. For more information about this feature, see the "Transferring changes using SVN” article.
- If you install service packs provided by third-party developers, use the WorkspaceConsole utility. A detailed procedure for uploading and downloading packages with the WorkspaceConsole utility is described in the “Transferring changes using WorkspaceConsole” article.
