Reverting map or code list changes

If you check out a map or code list and upload changes to it, but then determine that you no longer want to update it, you can revert the changes. You can also revert changes if you deployed the resource (map or code list) to Customer Test Environment (CTE). These scenarios do not occur often.

About this task

The procedure to revert changes rolls back the map or code list to the previous production version and releases the check out of the resource. For this procedure, the user needs to reset the current CTE version of the resource to match the version that is live in production. Then, the user notifies IBM Support, and IBM Support finalizes the reversion.
Important: If the owner of the check-out did not upload a revised version, the resource owner, the company's admin, or IBM Support can use the Undo check out function to undo the check-out.

Procedure

  1. Download the current production version of the map or code list.
    1. Go to the Map details page for the map or Code list details for the code list.
    2. Click Production.
    3. For a map, click Source map, Compiled map, and then Input file to download these assets.
      Important: Note the location where you save the Source map, Compiled map, and Input file.
      Or, for a code list, download Production code list CSV file.
      Important: Note the location where you save the Production code list CSV file.
  2. For a map, upload the production map files.
    1. For a map, in the Upload modified map card, select the production Source map that you saved in step 1.
    2. Select the production Compiled map that you saved in step 1.
    3. Select the production Input file that you saved in step 1.
    4. In Change description, type the following comment. Replace the version number in the comment with the production version number of the map, and replace the Salesforce number with your ticket number.Abandoning this round of edits. Resetting the CTE version to production version X.X. Tracked in Salesforce case number XXXXXX.
    5. Click Upload to upload the production version of the source map, compiled map, and input file to Configuration Hub.
    Or, for a code list, upload the production code list CSV file.
    1. For a code list, in the Upload modified code list card, select the Production code list CSV file that you saved in step 1.
    2. In Change description, type the following comment. Abandoning this round of edits. Resetting the CTE version to production version X.X. Tracked in Salesforce case number XXXXXX.
      Important: Replace the version number in the comment with the production version number of the code list, and replace the Salesforce case number with your ticket number.
    3. Click Upload to upload the production version of the code list to Configuration Hub.
  3. If you did not deploy the map changes that you want to revert to CTE, skip to step 4. If you deployed the changes that you want to revert to CTE, in the Deploy to CTE card, click Deploy to CTE.
  4. Submit an update to your Salesforce case number to confirm that you reset the CTE version of the map or code list to the previous production version. Additionally, request that IBM Support mark the map or code list status as FINAL.
  5. IBM Support marks the map or code list status as FINAL.

    When the map or code list is marked FINAL, the check-out is released.

    When map or code list changes are reverted, no corresponding production version exists for that CTE resource version.

    For example, if you upload map assets (or deploy to CTE) for version 2.1 of map ABC and then revert the map changes, the reverted 2.1 map assets are available in CTE but not in production.

What to do next

If you want IBM Support to make map changes, open a Map Change Request according to your usual procedure. If you want to lock or check out a code list, refer to Locking and checking out a code list.