nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Migration

alcima

Is there any tooling or other methodology to assist with migrating from another workflow system to Activiti?

Find more posts tagged with

Comments

jbarrez

No. Only if the system uses bpmn 2.0 you can migrate the process definitions, but that's pretty much it I'm afraid.

alcima

I was asking more than about the actual processes - we manually converted the processes. Now we want to migrate the history and inflight cases from the old system. We have a mapping of the the old process to the new process and are writing tooling to create the new instance and then feed events to drive it to the corresponding state. Just wondered if there were other ways to do it, specifically where we can keep the historical date/time of the transitions.

martin_grofcik

Hi Alcima,

Now we want to migrate the history and inflight cases from the old system.
…
then feed events to drive it to the corresponding state

One possibility could be to use simulation (e.g. https://github.com/Activiti/Activiti/pull/267 or https://github.com/gro-mar/activiti-crystalball/wiki/Getting-started) to generate and run events on activiti with historical date/time of the transition.
(Do not forget job executions)

Regards
Martin