Promote Changes to Production Environment

By - Updated June 25, 2015

New feature requests and bug fixes come up after a project goes live. These changes should be first implemented and tested in development environment before being promoted to the production. In this article, we will introduce the best practice to handle this process.

For all our implementations, we would suggest keeping track of every change that you make to the development environment and then propagating this to the production environment. There are a few tools you can leverage in Kepion when promoting changes to production, such as the export/import (forms, rules, dashboard) functionality. And most changes on the SQL Server Management Studio side can be done by creating or altering views and/or stored procedures.

For step-by-step details, please follow the flow chart below.