In Data migrator, Documentation exist

[yanavasileva]

Acceptance Criteria (Required on creation)

• The repository contains readme with following content
  • All limitations of the Migrator or unsupported BPMN notation elements are documented.
    • Runtime: With asyncAfter in C7, executions fire twice in C7 and C8. Options:
      • remove asyncAfter flags as a preparation step
      • TokenMove waiting process instances out of asyncAfter before migration
      • Ignoring the problem because of the idempotency of serviceTask
      • ...?
    • Runtime: C8 doesn’t support modifying multi-instance subprocesses (TODO: Is this applicable for Runtime only?)
    • Runtime: Each process requires a “migrator” task listener on their start events.
    • Runtime: For call activities, the legacyId needs to be passed to the sub-process instance.
      • By default, all parent process variables are propagated to a called process instance, but we should make this requirement explicit in the documentation.
    • History: The running process instances migrated by the Runtime Migration produce a new history but also have an old history from C7. I.e., we have two historic process instances per each running process instance in C8.
    • History: We only support process entities. Support for decisions and forms is out of scope.
    • History: The C7 history level is expected to be configured to FULL. Any other history level is unsupported.
      • With the skipping mechanism in place, the Migrator can keep track of entities that couldn’t be migrated due to missing related entities.
    • Both: Supports migration from/to the same database product. PG -> PG (V), PG -> Orcl (X)
  • Supported C7 and C8 versions (compatibility matrix).
    • We only support a migration from 7.24.0 to 8.8.0. We can increase the version compatibility in the future.
  • Write down tested scenarios (Postges and Oracle).
  • A basic user journey is documented. E.g., bringing processes in the correct state, stopping all C7 cluster nodes, migrating runtime first and history second, etc.
  • Alternative solutions are documented, like bringing your BPMN process to a different state (e.g., using modification) before migrating it to C8.
    • We need to align our docs and the following migration guide: https://docs.camunda.io/docs/guides/migrating-from-camunda-7/migration-journey/#prepare-your-camunda-7-solution-optional)
  • Bernd can give input and align the Readme documentation with the migration guide.

Hints

• Time estimate: 4 days

Links

Breakdown

Pull Requests

Preview Give feedback

No tasks being tracked yet.

Dev2QA handover

• Does this ticket need a QA test and the testing goals are not clear from the description? Add a Dev2QA handover comment