0 Replies Latest reply on Mar 4, 2019 9:18 PM by 3839496

    Preserving R12.1, R12.2 target responsibilities after cloning

    3839496

      Looking for a best practice means to preserve profile options and/or responsibilities in a clone target post clone.

       

      Basic process today:

       

      1. Clone Prod on top of target

      2. Manually change prod responsibilities and profile options not handled in adclone

       

      Desired process

       

      1. Preserve non-prod options (responsibilities - likely less controlled than prod, profile options - likely less controlled than prod, or perhaps email alerts going to a different location, templates showing "TEST ONLY - NOT PRODUCTION")

      2. Clone Prod on top of target

      3. Restore #1

       

      In the past I've done export/import (truncate option sometimes) of specific tables or done a script to create a restore script, then execute that script following clone.

       

      Curious as to thoughts of best practice to avoid all manual post clone steps regarding front-end changes that are unique to the Dev, UAT, etc. environments.

       

      Thanks for the help.