For some background, I am using Flowable to replace an older workflow system. The old system used to track workflow directly in RDBMS using a series of step codes, and it kept track of what state the records were in by inserting new rows into a history table. I need to start planning out the potential approach for data migration (we are trying to avoid it, but must plan for it in the event it does happen).
Using the APIs, I can easily write some code that spins up a workflow and completes each task. So now what I have is a Flowable workflow that has the same tasks and the same users completing each task. The problem is that the dates are wildly off. Here’s a kind of simplistic example that hopefully illustrates the problem I’m trying to figure out:
I have a legacy workflow, let’s call it Workflow A, and it was started by susieq on 10/17/2021. It has one completed step, Step ABC, completed by jsmith on 10/25/2021.
I recreate this workflow in Flowable, still calling it Workflow A. When I migrate into Flowable, I can easily make susieq start Workflow A, and then have some more code that makes jsmith complete Step ABC. But Flowable will now say that Workflow A started on 11/16/2021 (the day I migrate), and Step ABC completed on 11/16/2021.
Is there an API that would let me tell Flowable to instead start Workflow A on 10/17/2021, and complete Step ABC on 10/25/2021? Or is the only solution to do the programmatic bits and then go into the history tables (ACTINST, PROCINST, and TAKSINST), start adjusting the dates by hand, and pray I don’t cause havoc?