C4C/CPI: Automatically adjust mapping for DEV namespace
As C4C development systems (that are in development) use a different namespace than non-dev systems, one challenge is to adjust the CPI mapping of extension fields when moving to test or production.
When you are finished with development and unit testing in your dev environment, naturally, all CPI iflow mappings that involve extension fields would be mapped to the DEV namespace. If you simply move this iflow/mapping to your test system, it won't work, as the DEV namespace is not known in the test/production environment.