Results post cloning for application customizations

  • Release version: Washingtondc
  • Updated February 1, 2024
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Results post cloning for application customizations

    This document outlines the expected behaviors and necessary recovery actions for application customizations after cloning in ServiceNow, specifically for the Washingtondc release as of February 1, 2024. Understanding these expectations is crucial for maintaining application integrity post-cloning.

    Show full answer Show less

    Key Features

    The following table summarizes the states of application customizations before and after cloning, along with the corresponding recovery actions:

    • Base application not installed: Reinstall both the base application and app customization.
    • Base application version in Source Control: Remove the empty repository configuration record and reinstall from Source Control.
    • Base application version matches: Reinstall the app customization if the version in the target instance does not match.
    • Version upgrades: Reinstall both base and app customizations if versions differ post-cloning.
    • Retained repository configuration: Apply remote changes from the Git repository to synchronize the latest versions.

    Key Outcomes

    By following the outlined actions based on the state of your application customizations post-cloning, ServiceNow customers can ensure that their application environments are accurately restored and that customizations remain functional and up-to-date. This proactive approach minimizes downtime and maximizes application performance.

    The results to expect post cloning for application customization display the expected behaviors based on the state of the application, and the actions to recover your application customizations.

    The following are the expectations based on the state of the application customizations, and the actions to recover your customizations.

    Table 1. Application Customization expectations post cloning
    State of the App Customization on Source Instance State of the App Customization in the Target (Development) instance pre-clone State of the App Customization in Target (Development) instance post clone Action to take to recover App Customization in the Target (development) instance post clone
    Base application is not installed Base application version 1.0 and App Customization version 1.0 Base application is not installed Reinstall Base application and App Customization
    Base application not installed Base application version 1.0 and App Customization in Source Control Base application is not installed, and the sys_repo_config has an empty app field. Remove the repository configuration (sys_repo_config) record (the app field has been emptied) and import again from Source Control and install Base application.
    Base application version 1.0 Base application version 1.0 App Customization version 1.0 Base application version 1.0 Reinstall App Customization
    Base application version 1.0 Base application version 1.0 and App Customization in Source Control Base application version 1.0, repo_config is retained and the App Customization version displays as none in the all apps page. Apply the remote changes from the Git repository.
    Base application version 1.0 and App Customization version 1.0 Base application version 2.0 and App Customization version 2.0 Base application version 1.0 and App Customization version 1.0 Reinstall App Customization version 2.0 and Base application version 2.0
    Base application version 1.0 and App Customization version 1.0 Base application version 2.0 and App Customization version 2.0 in Source Control Base application version 1.0 and App Customization version 1.0, sys_reconfig is retained Apply the remote changes from the Git repository.
    Base application version 2.0 and App Customization version 2.0 Base application version 1.0 and App Customization version 1.0 Base application version 2.0 and App Customization version 2.0 is installed. Both Base and App Customization are at the latest versions.
    Base application version 2.0 and App Customization version 2.0 Base application version 1.0 and App Customization version 1.0 in Source Control Base application version 2.0 and App Customization version 2.0 is installed with repo_config retained, so the branch version is on 1.0 Both Base and App Customization are at the latest versions.