Results post cloning for application customizations

  • Release version: Australia
  • Updated March 12, 2026
  • 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 recovery actions for application customizations after cloning in ServiceNow. Understanding these results is crucial for managing application states between the source and target instances effectively.

    Show full answer Show less

    Key Features

    • State-Based Expectations: The document provides a detailed table that matches the state of application customizations pre- and post-clone, outlining the necessary actions based on the current condition of the application in both instances.
    • Recovery Actions: Specific steps for recovering application customizations are provided depending on the conditions encountered after cloning, ensuring that users can restore functionality as needed.

    Key Outcomes

    • Users can expect to manage their application customizations effectively, with clear instructions on recovery based on the state of the application in both source and target instances.
    • In scenarios where the base application is not installed, users are guided to reinstall both the base application and customizations to ensure operational integrity.
    • For instances where customizations are tracked in source control, users are instructed to apply remote changes to maintain the latest versions.

    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.