Results post cloning for application customizations

  • Release version: Zurich
  • Updated July 31, 2025
  • 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 information explains what ServiceNow customers can expect after cloning application customizations between instances, particularly focusing on the state of the base application and customizations before and after cloning. It also provides guidance on the necessary recovery actions to ensure customizations are properly applied and functional in the target (development) instance.

    Show full answer Show less

    Key Details

    • Base application not installed on target: If the base application is missing post-clone, customers must reinstall both the base application and the application customizations to restore functionality.
    • Base application in version 1.0 on source and target: Reinstalling the application customizations is required to recover the expected customizations on the target instance.
    • Application customizations managed in Source Control: When the base application exists but the application customization version is missing or shows as none, apply remote changes from the Git repository to recover the customizations.
    • Version mismatches between source and target: If the target instance has an older version of the base application or application customization compared to the source, reinstall the latest versions to align both instances.
    • Repository configuration (sysrepoconfig) considerations: If the sysrepoconfig record’s app field is empty after cloning, remove this record and re-import from Source Control to properly install the base application and customizations.

    Practical Application for ServiceNow Customers

    After cloning, verify the versions of both the base application and the application customizations in the target development instance. Depending on the state:

    • Reinstall missing base applications and customizations as needed.
    • When Source Control is in use, synchronize with the Git repository to apply remote changes and maintain version consistency.
    • Check repository configuration records and clean them up if inconsistencies are detected.

    Following these steps ensures that your development instance reflects the correct application state and customizations, enabling smooth development and testing workflows.

    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.