How do I set Active=False for specific Scheduled Jobs when cloning down from Prod to non-prod instances?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2019 08:52 AM
When cloning down from Prod, we want to preserve the Active state of the Scheduled jobs in the non-prod instances and we want to preserve the REST Messages because they point to non-prod endpoints.
- Labels:
-
Best Practices
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2019 11:37 AM
ServiceNow has post clone cleanup scripts you can run after a clone is performed. https://docs.servicenow.com/bundle/newyork-platform-administration/page/administer/managing-data/con...
These scripts are configured on the source (prod) instance and apply to the target (sub-prod) instance after the clone. If you know what data needs to be modified, you can create a script to update the parameters of the REST Messages. If the scheduled jobs aren't already making themselves inactive, you can create another script for setting them to active=false.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2019 03:13 PM
Thanks Weston. This was helpful. I have a question - what did you mean by "If the scheduled jobs aren't already making themselves inactive"? Honestly, I have cloned down before and the scheduled jobs were not active. The thought the "Clear scheduled job node association" clean-up script took care of that, no?
