I have a process which is working well in production. However, as user requirements change the process has grown to a point where it makes sense to split this into sub processes. While splitting the process diagram into three (or four) individual sub-processes is a relatively simple affair, I do have a few questions.
Firstly, is there an easy way to map the variables Out and In (these sub-processes will be Synchronous). There are quite a lot of variables that go to build up a cumulative record so there would be a large amount of effortinvolved to map these one at a time.
Secondly, I am wondering about the best strategy to put the new process(es) into production. My thinking is to leave the current process in place but remove the "Start" event so it doesn't appear in the New Case menu. Then add the new process(es) so that new cases are started with it. This will allow cases running in the old process to complete naturally. That way the users don't have to think about which version they are using and I don't have to worry about any cases being caught in limbo. When all the cases in the old process eventually complete I can then delete that process (assuming of course that all the data remains in the database).
This option does mean though that I will have to scrape the bottom of my barrel of SQL skills to sort out some KPI reports that get generated from Metabase every month.
So I'm wondering - is there an easy way to map the variables and, does my migration strategy make sense.