Cigna has been testing Project Duplication and has some ideas about how we can enhance it in the future.
They are likely to need to start from different points in the process, when working with different projects - where all of the basic, generic work has been completed, and any work that is more customized to a particular client is not yet completed. That makes normal projects a largely ineligible place to start, when using Project Duplication.
They've been working on executing this by creating BASELINE projects – projects where all of the generic work has been completed, without doing any of the extra customized work. They've been doing this with test projects, but envision people doing it with a live project, and then using Clone Project to create a BASELINE project at the right point (if no BASELINE already exists for their type of RFP.)
Using BASELINE projects like this has the dual usefulness of making sure that the starting point is ideal, AND enabling users to easily identify the right project to use. Below is a video of Joshua walking through what he thinks is probably the approach they'll want to take in creating and then using BASELINE projects.
Project Duplication Baseline idea (https://urldefense.com/v3/https:/cigna.webex.com/cigna/ldr.php?RCID=2216aa40d5a6e748d4686aebd8d091a9;!!FEyU5bU!W9QQUEXv4owLn80jkP6tuHi3t0C33hiEepMLSdlAK_2418QmmNYKYjlTUqHsClqR8-o$)
There are two downsides to this approach, given the current functionality.
1) BASELINE projects will create clutter within the normal Project view
2) BASELINE projects will count against their license limit for active projects
As he's mentioned previously, adding the ability to have flags copy over would be very helpful.
Another thing that would be really helpful would be to have this idea of BASELINE templates formalized more in the feature-set, enabling them to:
1) Save a project as a "template" that can then be duplicated
2) Have a separate view for seeing Project "templates"
3) Not have these "templates" count against our active project count
Created date : 2022-04-29
Votes : 1
Comments for the idea :
Deepan Mathivanan May 2, 2022
Hi Kendall, I am reiterating the same which is mentioned by Sunder in an email. Originally we have planned it Q2 and now we are expecting earliest in Q3.