DOORS History Tables Migration to DNG

Keep history tables together during migrationWorkflow at a glanceInputs and resultsTechnical fit and boundariesEvaluation questionsPlan your evaluation

Keep history tables together during migration

DOORS History Tables Migration addresses a specific DOORS Classic to DOORS Next problem: historical tables can become separate artifacts during migration. Its script sequence reconstructs the table as one artifact afterward. Migration leads can evaluate tables containing release history, status changes, authors, dates or comments. The objective is an intelligible target table rather than fragmented entries.

Workflow at a glance

Editorial overview based on vendor documentation.

1. Prepare the sourceUse the DXL script in DOORS Classic to convert the table into HTML.
2. Move the contentCarry prepared content through the agreed migration route.
3. Reconstruct and validateRun JavaScript reconstruction in DOORS Next and compare the resulting table with its source.

Inputs and results

Input is a Classic history table; HTML is the intermediate representation. Intended output is one DOORS Next artifact containing the table. This specialised conversion step does not constitute complete repository migration.

Technical fit and boundaries

The source does not specify supported releases, script deployment, accepted table structures, attachment handling or recovery. Define checks for rows, cells, dates, text and formatting before agreeing acceptance.

Evaluation questions

Are all links and history metadata migrated? That broader scope is not established. Can layout review be skipped? No; representative tables and unusual formatting require trial reconstruction and validation.

Plan your evaluation

Provide source/target versions, sample tables, migration route, expected structure and acceptance checks. Agree script availability, configuration, responsibilities and support; no lossless-migration or fixed-delivery guarantee is implied.

Related options to compare

• Softacus Migrator — Evaluate the broader migration route around this specialised table-preservation step; compatibility requires confirmation.
• Tables To Artifacts Converter — Consider a different workflow when rows should become artifacts instead of remaining one history-table artifact.

These are editorial suggestions for related scenarios; they do not imply a shared licence or a product integration.

Source: Official documentation.

Discuss your requirements