I have moved my update set to test and committed but i need to do few changes in dev instance
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 08:33 PM
Hi Community,
I have moved my update set to test and committed but unfortunately i need to do few changes in dev instance
Can i create new update set in dev again and move this new update set to test and commit this new update set in test instance
once committed both update sets, can we use batch update set concept
Old is a parent update set and add new one is a child or not?
Could you please confirm can i do like this?
Regards,
Srinivasu Sagiraju
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 09:10 PM
Hi @Srinivasu2
Not a best practice, but since it is in sib prod like test environment, I would suggest you to back out the update set in test environment, make the same update set in dev as In progress, complete your work and then move it to test.
Please mark it as helpful, if this response made a difference.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 09:31 PM
Hi @msd93,
Thank you for your suggestion, Instead of back out in test and make the same update set in dev as In progress.
Can i create new update set in dev again and move this new update set to test with few changes and commit this new update set in test instance
than Can i move these 2 update sets from Test to UAT.
Regards,
Srinivasu
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 11:28 PM
Hi @Srinivasu2
Yes, you may follow that approach as well. Once you move both the updates in test, confirm if your functionalities are working as expected and may be you could use the parent approach where in you could create a new update set as the parent and add the update sets as child (or) you could merge all the updates pertaining to one module/functionality as a single batch update set.
You could use any of these approaches to proceed further.
Ref for Batching Update sets: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/system-update-sets/hier-...
Ref for Merging Update Sets: https://docs.servicenow.com/bundle/tokyo-application-development/page/build/system-update-sets/task/...
I hope this helps you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-14-2023 09:48 PM
Hi Srinivasu,
You can create a new update set in DEV and move it to TST , from there you can tag both of these update set to one parent update set (You have to create one parent update set for batch) and move to PROD.