Note: Even when Role permission - "Copy / Paste of Processes" had been denied for a User (i.e. developer), the user must still be allowed- to copy/paste between different processes via clipboard
..... When the "Copy / Paste on Process" - Role permission has been set to Deny, for a developer., this forces the Developer to either use the current history option of "Check out" process / edit process
"Save as New Process" , to allow developer to effectively work with a copy of a process and this Option needs to ensure that this "copy" to a New process name, does not duplicate the production state of trigger.
.... Then, each company, if they wish, like mine, simply does *not* give copy/paste role permission to Developers, but only gives the Copy/ Paste - Permission to their Control Desk - Users.
.... This will easily give the best of all options, flexibility, and only minor changes needed to the overall existing process studio life cycle development design.