Config Mapping
Config mapping is when you point an integration config to a flow config to associate the two together.
Values you assign to the integration configs will be passed to their mapped flow config values. This makes it easier to set up config values once, then use them in other flows as needed.
An integration config can be mapped to multiple flow configs, but a flow config can only be mapped to one integration config.
The mapping process is different depending on if you add one flow or multiple flows at a time.
Add a single flow to your integration: Config mapping is a step in the process for adding the flow. You must map all configs in order to add the flow to the integration. Either map to an existing integration config, or create new integration configs as needed.
Add multiple flows at a time to your integration: You will need to map the configs after you add the flows to the integration. If you don’t map your configs (especially required configs), this may cause issues when syncing the integration.
Map flow configs when adding one flow to an integration
In Integration Builder, open the feature you want to add a flow to.
In the Flows section, select Add Flow.
Select Add Existing and choose a shared flow from the list.
Map each existing flow config to an integration configuration. Choose or enter a New Config Title from the dropdown list. Repeat for all configs.
If a flow config key matches an integration config key, App Xchange suggests a match. If you don’t want to use this match, you can choose a different config or enter a new one.
You must map all configs before you can add the flow to the integration.
Once you’ve completed mapping for all configs, select Next. The config mappings are listed, showing the flow config and their respective integration configs.
6. Review the details and select Save.
Map flow configs after adding multiple flows to the integration
In the integration builder, go to the Features page and open one of the added flows with unmapped configs.
Select Manage Configs and open the config details for the unmapped config. Example of an unmapped config:
3. At the bottom of the config details in the Integration Configuration Mapping section, select an integration config or enter a new one.
4. Select Save.
Unmap Flow Configs
Unmap flow configs from the integration builder
On the Configuration page, select the config you want to delete.
Select Mappings.
For each flow listed (if there is more than one), select the flow name. This opens the Manage Configurations window for the flow.
If the config is not being used by the published flow, select the config(s) you want to remove and select Delete.
If the config is used by the published flow, map it to a different integration config.Publish the flow in order to see these updates reflected on the integration configs.
Repeat these steps for each flow that the config is mapped to.
Unmap flow configs directly from the flow
Open the flow with config(s) you want to unmap.
Select Manage Configurations and open the details for the config.
If the config is not being used by the published flow, select Delete. The config will be removed from the flow.
If the config is being used by the published flow, map it to a different integration config.Publish the flow in order to see these updates reflected on the integration configs.
Repeat these steps for each flow that the config is mapped to.
You can verify that all configs are unmapped by checking the Configuration page in the integration builder. Select the config and verify that the Mappings tab is grayed out. This means the config is unmapped.
