Change Management in Decisions

I’m interested in understanding what’s the best way to track changes in Decisions. We do all our development in our test instance and then move things to the production system. Over time, changes, bug fixes, etc. may be implemented and moved to production replacing the initial versions. What is the best/easiest way to document these changes within Decisions? I know that auditing can be enabled, but that doesn’t seem to be giving me what I’m looking for. Is there a built in way to set version numbers or something similar for Flows/Forms, etc?
Comments
-
The easiest / most delivered way would be to set up a decisions repo server. Using this, you can not only get a trail (version / branch nunbers) of the changes but you can control what changes get pushed to Prod. I recommend checking out this doc on our repo.
https://documentation.decisions.com/docs/repository-overview
Howdy, Stranger!
Categories
- 4.3K All Categories
- 70 General
- 11 Training
- 206 Installation / Setup
- 1.1K Flows
- 109 Rules
- 268 Administration
- 212 Portal
- 496 General Q & A
- 707 Forms
- 338 Reports
- 3 Designer Extensions
- 48 Example Flows
- 56 CSS Examples
- 1 Diagram Tile
- 7 Javascript Controls
- 184 Pages
- 5 Process Mining
- New Features
- 182 Datastructures
- 69 Repository
- 228 Integrations
- 28 Multi-Tenant
- 27 SDK
- 81 Modules
- 57 Settings
- 25 Active Directory
- 12 Version 7
- 35 Version 8
- 130 Lunch And Learn Questions