We have certification processes that will be half complete when we migrate. For example, a process with 10 letters, each with 10 recipients, for 100 total recipients. Half of those recipients have already completed their certification.
- When we migrate this process and have to push the 'Run' button, will all 100 recipients get new tasks, including those who have already completed their certification in classic OR will only the 50 who haven't completed their certification in classic get tasks?
- If all 100 recipients will get new tasks (which would be problematic and very confusing), do you recommend we separate processes so those we migrate are either all complete (every certification letter is signed) or all incomplete (no certification letter is signed)?
On a related note, we currently create a classic certification process for each of our plan cycles, which are quick long. Our certification processes often have 200+ people with 20+ letters that are due over a 3-5 month period. We send the letters out in waves as we move through the process (NOT all at once akin to hitting the 'RUN' button). Given these factors, how do you recommend we use the new certification process? Instead of one process for the entire cycle, do you recommend we split it into multiple processes? It will definitely be harder to track and manage than the currently functionality available in Classic but we can figure it out if that is what you recommend given the inflexibility to edit tasks in a process after the Run button has been pushed.
Appreciate any insight you can provide!