Configuration and change control
Your quality team reads the system, not a description of it.
How the system behaves is held as configuration rather than written into code. Studies, workflows, roles, storage, labels, retention and vocabularies are all settings, and the settings are readable as a single artifact.
How it works
- What your quality team approves and what is running are the same object
- A configuration change is a governed change: permissioned, audited, with its previous value kept
- Configuration is promoted between environments rather than rebuilt in each one
- A new study type, a new site or a new workflow is a setup rather than a development project
- Changes that affect a validated state arrive as a prepared package for your change control
You decide when a release is taken. Nothing is deployed into your environment without your approval.
See it in a working system.
We will walk a live workflow and show this capability behind the steps it governs.