Cloning From Sandbox To Dev, Dev To QA, QA To Production

[mrx]

We have four instances of ServiceNow.

I have went through and done some initial cleanup and made changes in the Sandbox environment.

I want to push those same changes in data and configuration up to Dev.

I tried Clone but got "Destination does not allow clone requests". Before I went any further, I want to make sure this is the correct process.

[Michael Kaufman]

Do you have data in your Production SN Instance? You don't want to clone over that if true. A clone copies the complete source instance database over the destination instance database. If you are not using ServiceNow in Production yet, you can ask SN Support to do that clone I believe.

Otherwise you should be using Update Sets to track your customization changes and move them to different environments. http://wiki.servicenow.com/index.php?title=System_Update_Sets

[mrx]

We are not in production yet, this was an initial cleanup and config.

[mrx]

We submitted a HI ticket, only to have them come back and say we could do it our selves in Berlin and then they closed the ticket.

But when we try to do it, we get:
Destination does not allow clone requests (Typically used by live production instances, a property was set that prevents the instance from being cloned over).

I get the error message, but they don't give any hint on how to enable clone requests.

[mrx]

I figured it out -- I think.

We needed to change the glide property glide.db.clone.allow_clone_target to True.

This can be done using some hints outlined here: http://wiki.servicenow.com/index.php?title=Adding_a_Property