We have traditional system built in Java/Strut with complex business logic along with state changes.
now we are migrating the system to camunda workflow with new greenfield technologies stacks.
so to migrate state change logic Do camunda provide some in built mechanism or at least
state field/ or column to maintain the state changes against process instance?
or We should reuse persistence logic and tables of states as it is and call persistent layer from camunda flow?
please suggest optimized/best practice approach