Configuration

Configuration

Most people never need this page. It's for Studio Managers and administrators who want to adapt Studio to the way their organisation works. Everything lives under Configuration in the sidebar (/admin/divengine), which opens the Drupal admin area with the Gin theme.

Studio Managers see the configuration in the Studio theme; site administrators get Drupal's admin theme (Gin).

What you can tune

Area	Where	Examples
Artifact types	Divengine Studio → Artifact types	Add a type ("Interface specification"), add fields, change the key prefix, choose its lifecycle.
Lifecycles	Configuration → Workflow → Workflows	Rename states, add transitions, decide who may use each transition (via permissions).
Trace link types	Divengine Studio → Trace link types	Add a relation, set its inverse label and which kinds of records it may connect.
Diagram types	Divengine Studio → Diagram types	The notations available (BPMN, UML).
Unified Process	Divengine Studio → Unified Process	Development cases, lifecycle phase types, disciplines, process roles, activity and work product definitions.
Test management	Divengine Studio → Test management	Environments (with their default test URL), stages, priorities, tags.
Projects	Divengine Studio → Projects	Task stages (board columns and their category), task types (Epic, Feature, Story, Task, Bug) and their colours.
Code Source	Divengine Studio → Code Source	Allowed repository roots, largest file shown, git executable.
Text formats	Configuration → Content authoring	The Diagram button lives in Basic and Full HTML; QA issues use the QA Issue format with tables.

Unified Process configuration

flowchart LR
    PT[Phase types<br/>+ their milestones] --> DC
    D[Disciplines] --> DC
    R[Process roles] --> D
    AD[Activity definitions] --> DC
    WP[Work product definitions] --> DC
    DC[Development cases] --> DEV[Developments<br/>apply a case]

Loading

• Phase types: Inception, Elaboration, Construction, Transition, and the milestone closing each.
• Disciplines: Requirements, Analysis & Design, Test… and the roles that work in them.
• Process roles: what people can be responsible for.
• Activity definitions: what an activity means: its discipline, responsible role, inputs and outputs. Planning an activity from a definition fills those in.
• Work product definitions: the kinds of deliverables (Vision, Architecture Description…).
• Development cases: the tailoring. See Development cases & readiness.

✏️ Changing a Development case doesn't change running Developments. Each one keeps its snapshot until someone re-applies the case.

Test management configuration

Setting	Purpose
Environments	Development, Testing, Staging, UAT, Production… Each can have a default test URL: new runs copy it, and testers get an Open Test Environment button.
Stages	Unit, Integration, System, Regression, UAT.
Priorities	Critical, High, Normal, Low. QA issue priority is derived from these names.
Tags	Smoke, Regression, Functional, Negative, Boundary… for plans, suites and cases.

Re-applying the recipe

After updating Studio, you can re-apply the site recipe to pick up new default configuration without losing your changes:

vendor/bin/drush recipe $PWD/recipes/divengine_studio

It's non-strict: configuration you customised stays as it is.

Backups

Studio is a Drupal site: back up the database and the private files folder (evidence!) regularly. drush sql:dump and a copy of private/files are enough to restore everything.