Separate Development and Operations environments

  1. Create and modify functionality in a separate Development environment.
  2. Create a version and deploy it to the Operations QA environment for testing and approval.
  3. When approved deploy the version to the Operations production environment.

How to configure and use DevOps Version Control

You create the DEVELOPMENT environment from a copy of the Operations production environment.

  • When using the default local-database repository it is a simple file copy, automatically managed from the Account window.
  • When using SQLServer repository you manually make a copy of the production environment database and then connect to that database and promote it to be the development environment. The promotion process is managed from the Account window.

Once the development environment is created you can make changes as needed and at an appropriate time decide to make a version from the “DevOps Version Control” window.

When creating a new version, what happens is that all changes made are “collected” and stored in a version-package that you can then export to a file that you in turn can apply to the operations QA or production environments.

Segments of functionality and data that are NOT under version control and hence excluded from version packages Not under version control
  • Variables
Data value Current value
  • Session log
Session log data
  • Job Server
Job scheduling
Last modified: 21 February 2023