Can I use process variations to manage current (as-is) and future (to-be) processes?
I was in a Nintex webinar the other day and I saw the demonstrator using a process with variations for current (as-is) and future (to-be). This wasn't the focus of the webinar however it got me thinking about how to efficiently manage as-is/to-be processes going forward.
I'm thinking of setting up the following to manage this - I'd love to hear people's thoughts/experiences on this:
- Create process for the first time in Promapp (standard, current, and future variations)
- Publish current variation when process is finalised, leaving the future process as draft
- Everyone uses the published current variation
- The process owners/experts work on developing the future variation until they're ready to implement it
- This is where I still need to work out - Then either:
- Archive the current variation and then publish the future process (renamed current), or
- Update the current variation (copy text across from the future variation) and revert future variation to standard to start improvement piece again, or archive it and create new variation when improvement work is done again.
Is this feasible? One thing I'm unsure of is why the demonstrator had three process variations: standard, current, and future. Why not have just the standard as the current process, with one variation being the future (as-is) process? I can imagine this has something to do with reverting to the standard or tracking changes or publications/viewing permissions maybe...
I'd love to hear your thoughts - how have you managed current/future processes in Promapp?