Dova 24, 25 and 26: scope and changes

Current edition

This edition describes Dova 26.0.0. Check your installation’s active version before following a procedure. This reference keeps the route used by the Dova 24 manual; its historical sections remain below.

Changes in 26.0.0

1. DovaAI lets you select an element or area and review a screenshot and its safe context before sending them.
2. The launcher follows mouse or touch dragging, previews its docking space and animates docking and detaching from the bottom bar. The reduced-motion preference is respected.
3. Mappings Configuration organizes component fields, help and actions within the panel; Header mapping retains its own scrolling for columns.
4. The bottom bar prioritizes Tenant, Domain, Environment and connection state. Operational details groups Active, Workers, Queue, Plan, Autosave and Updated; space remains available for docked DovaAI.
5. Advanced, Validate, Save draft and Publish in the Mappings editor use icons with help and accessible names. Run is removed: the Session supplies execution and requires compatible capacity.
6. The Mappings header no longer repeats DEV; the environment stays visible in the bottom operational status bar.
7. The Mappings list removes Environment and Runtime filters and uses the active context.
8. The Mappings list aligns Search, the remaining filters and icon actions.
9. Sessions and Workflows lists adopt the same action toolbar. They remove only Environment and retain Runtime and the other filters.

Saving, publishing, promoting and running remain separate actions subject to permissions. This documentation describes controls and procedures; verify the active version and each operation’s outcome in your installation.

Functional baseline in 25.0.0

1. Tenant, Domain and Environment are selected from the user menu; a compact indicator keeps context and its colors visible.
2. Environment-specific permissions and Release Manager separate development from promotion to Production. ETL Developer has no Production access by default.
3. Administrator scopes workers, cloud connections, profiles, operations and pools to authorized environments; users and roles keep a shared identity.
4. The Administrator sidebar removes circular counters and follows Dova’s visual and navigation foundation.
5. Module loading and a bounded RAM read cache reduce repeated requests while respecting identity, role and context.
6. Configuration → Miscellaneous customizes the shared Tenant+Environment color, with preview and restore-default controls.
7. ES, EN and PT select interface language from the user menu.
8. VM controls use implemented provider capabilities and actual state and periodically reconcile cloud changes.
9. Remove VM and unlink retires owned capacity and, after cloud absence is confirmed, clears assignments and projects Unassigned without deleting versions or audit history.
10. The disk chart identifies free space, capacity, usage and sample time using Dova’s visual standard.
11. CPU, memory and disk show Not available without current telemetry; historical samples remain distinct.

These capabilities retain permissions, ownership, pending-operation checks and base-server protection. Each action depends on the implemented provider and effective authorization.

Changes in 25.0.1

1. Compact VM controls follow real provider state, with Start for Stopped and Resume for Paused according to permissions.
2. A DovaAI icon movable with mouse, touch and keyboard, with a local position per authenticated user.
3. Element or area selection shares context and a real screenshot prepared with redaction.
4. Compact chat supports pasted or dropped images, preview and removal before sending.
5. Dova and Administrator share left navigation and a user menu beside its button, fitted to the screen.
6. The menu’s Domain list follows create, update and delete operations while preserving the unsaved-change guard.

Fixes in 25.0.2

1. Administrator HTML navigation redirects an authenticated account without administrative permission to Dova; API authorization remains enforced.
2. Funding-period reconciliation avoids Subscription funding projection does not match through Billing’s canonical projection, without changing the period, cycle or granted credits.
3. Repository loads context with expired temporary drafts and offers recovery after read errors instead of remaining indefinitely in Loading.

The Tenant, Domain and Environment summary appears in the bottom operational status bar of Dova and Administrator. Click the summary to open the user menu with all three selectors. It retains the environment badge and color without a top strip or duplicate fields.

See this manual’s DovaAI, account-menu, Cloud workers and Repository procedures. VM operations, writes and publications require their own permissions and result verification.

Historical Dova 24.0.0 reference

Edition and active version

This manual describes Dova 24.0.0. Check your installation’s active version before following a procedure. Documentation describes capabilities; it does not establish that an installation’s promotion, execution or publication completed.

Main changes

1. Global Tenant, Domain and Environment context, initially Development.
2. Mappings, Sessions, Workflows, Connections and Monitor catalogs separated by context and authorized by the server.
3. Tabs, filters and local work retained per context; stale responses discarded and switching blocked during writes.
4. Save and publish controls identify their environment; Production requires explicit capabilities to modify definitions.
5. Fork to Development recovers definitions as separate drafts with compatible destination Connections and dependency review, without copying credentials.
6. Mapping, Session or Workflow promotions with exact published dependencies, preview, destination bindings, Production approval and manual restoration history.
7. Environment worker policies and distinct edit, publish, run, promote and Runtime administration capabilities.
8. DovaAI receives environment context and drops earlier conversations on a context switch. It remains a read-only diagnostic assistant.

Upgrade of earlier artifacts

Earlier artifacts without clear ownership are not automatically assigned to Development. Published and shared references are preserved through verified membership and an exact dependency chain. An ambiguous definition may need review and Fork to Development. Switching the selector never retags an artifact’s owner environment or updates published versions.

Earlier custom roles retain reading according to their permissions; new environment mutation capabilities require an explicit grant. Custom environments are never an implicit alias for Development or Production.

Limits and responsibility

Promotion and definition rollback neither execute pipelines nor reverse external data. Destination Connections keep their own credential custody. Worker availability, plan quotas and successful execution are checked separately.

DovaAI identifies causes and recommends options; users alone change configuration and confirm operations. Git provenance and manifest export support external review, without granting Git access or starting a DevOps pipeline by themselves.

See environments and promotion. The historical reference keeps its route and earlier-edition content.

GitOps kit per workspace

The GitOps kit 1.1.2 binds Tenant, Domain and Environment for queries, draft reservations, publications and leases. Use source.environment and source.domainId for exports; target.environment and bindings.domainId for imports. Defaults are Development and General; preserve state per target. See the Finance example and state recovery. Direct Production authoring requires governed promotion rather than the import command.