Clone Check List

In this articles we will guide you on all actions required prior and after the clone so we ensure all Quality Clouds features remains operational once all cloning process has completed.

Please ensure to follow these configurations both before and after the cloning process. Additionally, make sure to complete the necessary actions to confirm the successful completion of the cloning process.

Prior the Clone #

1. Install the Quality Clouds App in your Production Instance ( there is no need to configure the app at this point) 

2. Configure in the production instance the Table exclusion and Data preserver, according to this Link
   • All → System Clone – Clone definition → Preserve Data

• All→ System Clone → Clone definition → Exclude Tables

After Clone #

1. Please access the Guided Setup module and follow the configuration on the sections below.
   • All → Quality Clouds → Quality Clouds Guided Setup

2. Install Global Component section (if the global components were already installed in Production, this step can be skipped), otherwise please configure the sections below:
   • Please configure an Auth profile for the component Installer – Note: the user specified on the auth profile needs to have the admin role in order to be able to create and delete records in all the required tables.
   • Then configure the Apply Changes section
   • Deactivate deprecated content from old App versions.If you’re clonning the Quality Clouds App from the 9.6.x version or older, then you will need to copy the code contained in the following fix script and execute it on Scripts – background on the Global scope to deactivate the deprecated Global elements from older versions of the APP. Note: In case of a new installation, or If you’re upgrading the APP from version 10.x or higher, then you can skip this step.
     

3. Configure the API Key Verification section – Note: if the Table exclusion and Data preserver were already configured in Production, this step can be skipped)

4. Configure the Load app Configuration settings from the Backend – Note: if the Table exclusion and Data preserver were already configured in Production, this step can be skipped)

5. QC Roles, Group, and Users in ServiceNow – This configuration depends on customer’s policy regarding groups, and users)
   • Review of the Full scan users’ configuration
     • Test by launching the Full scan from the Portal
     • If not working – Review credentials and roles from the user added in the Full Scan

6. Validate System Properties section
   1. Reconfigure System properties with read/Write permissions of the user
      • X_qucl_qc_snow.write.access.username – Please add the read/write user (if it doesn’t exist it will need to be recreated)
      • X_qucl_qc_snow.write.access.password – Please add the read/write user (if it doesn’t exist it will need to be recreated)

Validations after the clone #

1. Launch a Livecheck configuration element

2. Launch Livecheck update set (it should be automatically completed without the need to click on “check status”)

3. Ask for a Writeoff (If the add-on is active)