Is there a way to selectively promote changes made in the dev environment to prod?
If all or nothing is to restore a database dump from dev to prod then supported selective would be
- XOGing what can be xoged
- manually doing what cannot be xoged
Unsupported would be direct changes in db
Additionally there may be "configuration" of the Clarity files. They would have to be copied manually again vs backup and restore.
You may explore using Content Packages in Studio to collectively select and move the configurations as one file between the environments.
Refer to: https://docops.ca.com/ca-ppm/15-5/en/reference/ca-ppm-studio-development/ca-ppm-studio-content-packages
When you create a content package a .jar file is created and same file can be downloaded from that instance and used to upload to another instance as content add-in.
Hi shawn.tuttle ,
The best way to migrate is content package. Below is the screenshot of the content type which you can migrate.
You can create a new Content Package from Administration menu and choose the contents to migrate.
When I create content, I have two Jar files 1. Packages 2. Extracted Language File in Dev. I need to upload the Package JAR file and check "Install the Migration Mode" check box. Please correct if it is wrong.
Retrieving data ...