Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/pagerduty/servicenow-updatesets
This repo contains update sets to be used with creating Clone Data Preservers in ServiceNow. These are compatible with versions 5 and 6 of the PagerDuty app.
https://github.com/pagerduty/servicenow-updatesets
in-scope team-expert-services type-service
Last synced: about 1 month ago
JSON representation
This repo contains update sets to be used with creating Clone Data Preservers in ServiceNow. These are compatible with versions 5 and 6 of the PagerDuty app.
- Host: GitHub
- URL: https://github.com/pagerduty/servicenow-updatesets
- Owner: PagerDuty
- License: mit
- Created: 2018-10-18T16:23:54.000Z (about 6 years ago)
- Default Branch: master
- Last Pushed: 2020-03-20T22:41:36.000Z (almost 5 years ago)
- Last Synced: 2023-03-24T02:09:41.428Z (almost 2 years ago)
- Topics: in-scope, team-expert-services, type-service
- Homepage:
- Size: 14.6 KB
- Stars: 1
- Watchers: 6
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Update Sets for Clone Data Preservers in ServiceNow
## Getting Started
This repo currently contains one update set, which will work on both v5 and v6 of the Pagerduty app.
## Important to Note:
These update sets will not install the Pagerduty application, rather, they're used to preserve your PagerDuty data when cloning your Servicenow instance from one environment to another. For further context, hints, and instructions, please visit our Support article on the subject [here](https://support.pagerduty.com/v1/docs/servicenow-using-the-clone-data-preserver).
## Prerequisites
You will need to be an admin or clone_admin user in ServiceNow to utilize these.
## Uploading and Committing your Update Set
- Navigate to Update Sets to Commit
- Select import from XML
- Import your Update Set and Upload
- Click into the Update Set and Preview
- Once the Preview is finished, Commit the Update Set
## Questions? Comments?
Please reach out to [email protected]