This topic came up with a client just last week. The client has PM's who use the copy feature often because it is the quickest way for them to recreate a similar project. But when they do this, it is causing issues with an integration and a custom field that PM's neglect to clear out during the copy process - namely the project number. Without this project number, they loose the ability to sync with the financial system and it destroys the integrity of the reporting.
Of course, turning off "copy" on a project would correct this problem but create another. So if, as an admin I was able to turn it off, I would want PMs to have the ability to create their own templates. Currently the client has not allowed users (e.g. trained them) to create their own templates for fear it will create clutter in the platform. However, its clear that the benefits of this, if having the ability to shut of "copy" are critical to efficiency.
Hi @Colleen Grenon‚ - this is great feedback. Thank you for providing it.
If we move forward with this enhancement, existing planner access levels will not have copy project enabled by default (unless these access levels have been updated in the last two months). This means that your client would need to go back and enable "copy" manually for those users who require it. Is that going to be a problem for your client or do you have any additional thoughts on this?
Hi Jeremy,
I like the concept of having an option to “enable”. This would allow the Admin to maintain some controls over Governance, e.g. “if you don’t remember to delete the content in the critical custom field, we will no longer allow you to have the privilege to copy a project”. This ability would also meet client needs, as it would not require added templates but still allow those few that have customized flows to still copy.
I like it!
Colleen Grenon | regoconsulting
Functional Consultant
(603) 235-5413
Connect with us on LinkedIn<>
Join our free training<> and webinars<>
[cid:image001.png@01D6B28D.25FE1630]
[A close up of a sign Description automatically generated]
we had the same problem and solved it by clearing those fields in Fusion if a new project has been created and has those fields filled. If you do not use Fusion, you could achieve the same by using the API.
