Updating CMC Preview maps based on the placeholder map

If you requested that IBM® Services create a new collaborative map creation (CMC) preview map based on the empty placeholder map, the map that is loaded into Configuration Hub establishes the name of your map in the system. The content of the map that is downloaded when you check out the map from Configuration Hub is not necessarily representative of the map structure that you create based on your own business requirements. Therefore, you replace the downloaded map with your own map. However, you must ensure that you maintain the same map name both within the map and as the map file name when you upload your new version.

Example

Consider an example where you request that MapXXX is created based on the empty placeholder:
  1. You check out MapXXX from Configuration Hub, which downloads MapXXX.mxl from the Configuration Hub repository to your local file system.
  2. You then create your own MapXXX.mxl by using the map editor and set the Description of the map to be MapXXX:
    1. Open your map in the map editor.
    2. Go to Edit > Details.
    3. In the Summary section, update the Description field to be MapXXX.mxl.
    4. Under EDI Associations, update the Transaction value on either the input or output side. Ensure that you follow the suggestions that were shared by IBM Services when the map was created.
    5. Click OK, then Save.
  3. Create your map logic to meet your business requirements.
  4. Save your map as MapXXX.mxl.
  5. From the Function menu, click Compile.
  6. Save the compiled version of the map (.txo) in the same directory as your mxl and txt files. Save the file as the same name as your mxl file. For example, MapXXX.txo.
  7. Run transformation tests from your local map editor to ensure your map functions as you expect.
  8. When satisfied, return to the Configuration Hub application and upload your new version of the map.
  9. Deploy the map to CTE.
  10. When IBM Services alerts you that a workflow that uses your map is ready, proceed with document flow testing.